<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/xpe/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/xpe/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 26 May 2003 15:09:51 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/xpe/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Specify location for unknown DTDs</title><link>https://sourceforge.net/p/xpe/feature-requests/10/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, if a DTD referenced in a DOCTYPE is not in the same &lt;br /&gt;
directory as the XML file, it is not found, and the document fails &lt;br /&gt;
to load. This is a common problem with XML parsers. It would &lt;br /&gt;
be nice if, when a DTD is not found, that XPE prompts the user &lt;br /&gt;
for its location, then remembers where it is for future &lt;br /&gt;
documents with the same DTD.&lt;/p&gt;
&lt;p&gt;There is a workaround, but it is cumbersome. See the section &lt;br /&gt;
&amp;amp;quot;DocBook and Catalog Support&amp;amp;quot; on the Web site http://&lt;br /&gt;
xpathexplorer.com&lt;/p&gt;
&lt;p&gt;Note that in order to remember the settings, the app would need &lt;br /&gt;
to save data locally. Is this a job for the Preferences API?&lt;/p&gt;
&lt;p&gt;Related bugs:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://sourceforge.net/tracker/"&gt;http://sourceforge.net/tracker/&lt;/a&gt;&lt;br /&gt;
index.php?func=detail&amp;amp;amp;aid=638043&amp;amp;amp;group_id=54719&amp;amp;amp;atid=47&lt;br /&gt;
4579&lt;/p&gt;
&lt;p&gt;&lt;a href="http://sourceforge.net/tracker/"&gt;http://sourceforge.net/tracker/&lt;/a&gt;&lt;br /&gt;
index.php?func=detail&amp;amp;amp;aid=655886&amp;amp;amp;group_id=54719&amp;amp;amp;atid=47&lt;br /&gt;
4579&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Chaffee</dc:creator><pubDate>Mon, 26 May 2003 15:09:51 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netae5114e6e52225b0ebda8c765e6891f6038e81a8</guid></item><item><title>Highlight as you type</title><link>https://sourceforge.net/p/xpe/feature-requests/9/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Don't know if people would like this, but how about an&lt;br /&gt;
option to highlight matching nodes as you type your&lt;br /&gt;
xpath expression. (after each valid xpath expression.&lt;/p&gt;
&lt;p&gt;For example highlight matching nodes when the xpath is: &lt;/p&gt;
&lt;p&gt;/item&lt;br /&gt;
/item[@TypeId=3]&lt;br /&gt;
/item[@TypeId=3]/subitem&lt;/p&gt;
&lt;p&gt;but not when it is:&lt;/p&gt;
&lt;p&gt;/it&lt;br /&gt;
/item[@Typ&lt;br /&gt;
/item[@TypeId=3]/subit&lt;/p&gt;
&lt;p&gt;matias@mac.com&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 04 Apr 2003 14:50:55 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net10aec6a48c15d9813f78fd53b16ee3b70b24143b</guid></item><item><title>Set a default node from where to execute a xpath expression</title><link>https://sourceforge.net/p/xpe/feature-requests/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Maybe the user could click on a note and then click on&lt;br /&gt;
a button that says &amp;amp;quot;evalueate from here&amp;amp;quot; or &amp;amp;quot;set as&lt;br /&gt;
start node&amp;amp;quot; or something.&lt;/p&gt;
&lt;p&gt;This would be really cool!&lt;/p&gt;
&lt;p&gt;matias@mac.com&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 04 Apr 2003 12:19:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net3ec4dd610d0cadb9ad4e5891e2369872917e70be</guid></item><item><title>Switch Between Different HTML-Parsers At Runtime</title><link>https://sourceforge.net/p/xpe/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;1. JTidy can solve many HTML-junk. But there exists things&lt;br /&gt;
where JTidy do not solve but another HTML-Parser&lt;br /&gt;
can do:&lt;br /&gt;
&lt;a href="http://www.apache.org/~andyc/neko/doc/html/" rel="nofollow"&gt;http://www.apache.org/~andyc/neko/doc/html/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Example: I know a site with a lot of small nested&lt;br /&gt;
forms. Cause&lt;br /&gt;
of a incorrect HTML-Tag sequence JTidy will cut&lt;br /&gt;
several form&lt;br /&gt;
contents an make one 'mixed' garbage form. With&lt;br /&gt;
neko i  get&lt;br /&gt;
all small forms completly.&lt;/p&gt;
&lt;p&gt;2. Different Parsers will provide different DOM for the&lt;br /&gt;
same HTML&lt;/p&gt;
&lt;p&gt;A possibility to switch between different HTML-Parsers&lt;br /&gt;
will be nice. Perhaps a feature to plugin a parser&lt;br /&gt;
similar to httpunit could be suitable.&lt;/p&gt;
&lt;p&gt;I am not sure but HotSax could also be a candidate for&lt;br /&gt;
a plugin HTML-Parser.&lt;/p&gt;
&lt;p&gt;regards&lt;br /&gt;
Alexander&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexander Kunkel</dc:creator><pubDate>Tue, 01 Apr 2003 09:15:07 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net35a7b41e6a8a4ccbbce3cc4c38090fd471305f53</guid></item><item><title>Switch between Xalan and Jaxen at runtime</title><link>https://sourceforge.net/p/xpe/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;i found different results by evaluating xpath expressions&lt;br /&gt;
between jaxen and xalan. In my estimation xalan gave me&lt;br /&gt;
the right result.&lt;/p&gt;
&lt;p&gt;I suggest that i can switch while runtime between xalan&lt;br /&gt;
and jaxen.&lt;/p&gt;
&lt;p&gt;regards&lt;br /&gt;
Alexander &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alexander Kunkel</dc:creator><pubDate>Wed, 26 Mar 2003 10:25:32 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netedced98a110d14d4a4199ff5d15375bb51370034</guid></item><item><title>Stop Expanding Nodes button</title><link>https://sourceforge.net/p/xpe/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When you start expanding nodes, it might take a while. &lt;br /&gt;
There should be a way to stop expanding.  (Note that if &lt;br /&gt;
you select a new URL, it will stop already. Yay threads!)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Chaffee</dc:creator><pubDate>Mon, 16 Dec 2002 05:51:54 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net1ca62382f3d6a79f93539d9123c856f72109d3ea</guid></item><item><title>Expand single node</title><link>https://sourceforge.net/p/xpe/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There should be a way to expand all the children of the &lt;br /&gt;
selected node. This would be like clicking the handle (on &lt;br /&gt;
the left side) for this node and for all its children.&lt;/p&gt;
&lt;p&gt;This should be a menu item. For bonus points, it should &lt;br /&gt;
be a context menu (right click) as well.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Chaffee</dc:creator><pubDate>Mon, 16 Dec 2002 02:35:44 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net2703d194e44a1b6b4fd484070e6d48052eb28e4b</guid></item><item><title>Expand all nodes</title><link>https://sourceforge.net/p/xpe/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Now that big documents are left unexpanded by default, &lt;br /&gt;
there should be a way to expand all nodes in a &lt;br /&gt;
document. Probably a menu item.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Chaffee</dc:creator><pubDate>Mon, 16 Dec 2002 02:34:28 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net23792589a45c3dfd4cb3b6c7ba7a4eeade28fa2a</guid></item><item><title>WebStart/JNLP </title><link>https://sourceforge.net/p/xpe/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There should be a WebStart (JNLP) build option, and a&lt;br /&gt;
launcher on www.xpathexplorer.com (or&lt;br /&gt;
www.purpletech.com/xpe/launch)&lt;/p&gt;
&lt;p&gt;See &lt;br /&gt;
&lt;a href="http://www.vamphq.com/jwsfaq.html" rel="nofollow"&gt;http://www.vamphq.com/jwsfaq.html&lt;/a&gt; for help implementing&lt;br /&gt;
this&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Chaffee</dc:creator><pubDate>Thu, 12 Dec 2002 21:17:07 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net54c2b19e0900f4741221327df9b9eb28c210a471</guid></item><item><title>Select attributes</title><link>https://sourceforge.net/p/xpe/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, when you click on a line in the hierarchical &lt;br /&gt;
results list, it selects the element.  We should allow the &lt;br /&gt;
user to select an attribute.&lt;/p&gt;
&lt;p&gt;My current thinking is to add an &amp;amp;quot;expand attributes&amp;amp;quot; &lt;br /&gt;
checkbox, which would put each attribute on its own &lt;br /&gt;
line. The user can then select the line in the normal way.&lt;/p&gt;
&lt;p&gt;Alternately, we could try to trap the mouse click event &lt;br /&gt;
inside a line, and calculate which attribute was clicked &lt;br /&gt;
on.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Chaffee</dc:creator><pubDate>Sat, 16 Nov 2002 21:53:08 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta57e6323486d7a3ac112af9d1744853b38199173</guid></item></channel></rss>