From: Adrian B. <ad...@fa...> - 2007-12-03 19:42:42
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-1"><font face="Georgia">Actually on second thoughts this is a bit lazy, and results in a proliferation of plugins... I will see about getting the XSLT plugin to run on different XSLT engines. Dynamic dependencies on different library plugins (eg XalanPlugin+ SaxonPlugin) could be tricky though, it might be simplest to include both...</font></font><br> <br> Adrian Baker wrote: <blockquote cite="mid:475...@fa..." type="cite"> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <font size="-1"><font face="Georgia">The XSLT plugin provides a dockable UI where you can run an XSLT and inspect the output (I don't use it myself). It doesn't affect the edit pane itself AFAIK.</font></font><font size="-1"><font face="Georgia"><br> <br> One option is to add the sidekick mode as a separate feature of this plugin, however it should really be upgraded to use Saxon in this case, or allow the implementation to be configurable.<br> <br> At this point I will just publish the XsltSideKick parser + Saxon as separate plugins (Saxon as just a library). <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://plugins.jedit.org/releasing.php">http://plugins.jedit.org/releasing.php</a> suggests I need commit privileges for this?<br> <br> Also I notice that the XSLT plugin only exists in the cvs repository, not the newer subversion one: what's the process for getting these shifted across while preserving history?<br> <br> Adrian<br> </font></font><br> Alan Ezust wrote: <blockquote cite="mid:f37...@ma..." type="cite"> <pre wrap="">There is already an XSLT plugin, but it includes xalan not saxon. I haven't really used it so I don't know what it does. I originally thought you could add it to that one, but maybe not. What other jedit plugins out there use saxon? That's my main concern. We may need to break it out of whatever plugin includes it and turn saxon into its own plugin so that it can be used by the xsltsidekick as well as others. I don't want the XML plugin to depend on Saxon though, so it is probably a good idea to package it as a separate plugin. On Dec 2, 2007 10:51 PM, Adrian Baker <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:ad...@fa..."><ad...@fa...></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> Hi, I've written a simple Sidekick parser for XSLT: it extends the XML sidekick parser (xml.parser.SAXParserImpl) to compile the buffer using Saxon, in addition to the standard XML parse behavior. All other behaviour is identical to normal XML editing. Since the XML plugin already has sidekick parsers for HTML, XML, etc, is this best submitted as a patch to the XML plugin rather than as a standalone plugin? Adrian ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4">http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4</a> -- ----------------------------------------------- jEdit Developers' List <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jEd...@li...">jEd...@li...</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/jedit-devel">https://lists.sourceforge.net/lists/listinfo/jedit-devel</a> </pre> </blockquote> </blockquote> </blockquote> </body> </html> |