I do very little work with XML, but just got involved in a recent project to convert XML documents to the health industry standard format, HL7. The documents we are getting have no CR or LF in them which for me made it hard to work with them. I picked your editor out from a quick web search. I copied and pasted the data into the app and with two quick commands had excellent access to the data elements I needed in two nice, clean, simple interfaces, one the parsed data and the other the nicely aligned XML document. I am sure it can do much more than I will ever use it for, but it is absolutely great for what I needed.

...a small but irritating bug. Often when you drag to select some text, the cursor jumps to the first character in the whole file instead of the location where you did the mouse-down, so you end up with a huge selection. Similarly, often when you click somewhere and press ctrl-V to paste some text, it puts it at the beginning of the file. When you repeat the action, the problem usually does not happen. It seems to happen mainly when working at the beginning of lines, so maybe it has to do with the program not recognizing that the cursor is at the left margin, and thinks you want to be at the beginning of the file... If you carefully click on the very left edge of the right pane, but maybe one pixel to the right of where the pointer turns to a double headed arrow, the cursor will often go to the top of the file. Seems like it is not getting or computing the character position correctly if the mouse click is in that very narrow zone.

In preferences, the indentation type defaults to 0 spaces. If I change it (to any number) it reverts to zero. HOWEVER, if I set indentation type to tabs, then choose OK to exit the dialog, then when I open preferences again, the number in the spaces field is set to 1. If I select spaces and change the number, the setting presists.

Download the latest firstobject XML editor here.

Summary of foxe 2.4.2:

filename first in foxe title bar

-run on command line arguments

period for data value in tree customization

foal: increased the size limit on num

foal: CMarkup updates

foal: fix for file read mode *Thank you Aditya Raut!

foal: StrTrim with optional flag 1=left, 2=right

Watch mode in the View menu

Watch file extensions in Preferences

Details below.

Is there a size limit on the 'num' datatype? I appear to be getting a numeric overflow when trying to sum financial information in an XML document. I used the 'Generate Program'->'Sum' function to sum the value of an element in the file, the actual sum of the value is [over 27000000.00], yet the generated program returns the sum as [a large negative number]. If there is a limit, is there any other data type that I can use to avoid the overflow?

I mistakenly released build number 404 instead of 416 on June 12, so I've put the correct one up. Minor differences included right-click bug in tree editbox.

Release 2.4.1 lets you edit XML in the tree view and see the changes in the text view as you go. This is a safer way to edit XML because it will do the escaping of special characters for you.

The most noticeable change in this release of the editor is that the tree background is grayed out whenever you edit the text view. This is a visual cue to signify that the tree is out of sync with the text document to make it more self-explanatory why the behavior can be unexpected such as when you click into an element in the tree that no longer exists in the actual XML document text. But there are lots of actions that cause it to be parsed and synchronized again such as F5 Refresh and F7 Parse, or even F8 Format, File Save etc. However, when you are editing in the tree then both views remain in sync.

tree view background is grayed when you edit the text view until re-parsed

edit XML element and attribute values right in the tree view

tree customization values are green to differentiate from data values that can be edited

command line pre-select text e.g. foxe -offset 10 -fromoffset 5 file.xml

command line execute FOAL script e.g. foxe -run program.foal

command line -watch argument for auto-reloading and read-only viewing the tail of log files

improvement in the way expanding a node in the tree view makes the child nodes visible

documents that do not begin with < are assumed not to be markup and the tree stays blank

fix: foal filenames were broken for non-ASCII, now support your Windows locale characters (still not ideal, I know)

fix: foal StrUpper StrLower memory leak

Download the latest firstobject XML editor here. Release 2.3.5 introduces help search and CMarkup release 11.1 file mode subdocuments (see file mode sections of GetSubDoc and AddSubDoc) for handling pieces of XML files in memory and splitting large xml files.

Help search. Pressing F1 on a term in a Program will search on that term if it is not a function or method. Type search terms into the editbox above the help

CMarkup release 11.1 methods, features and fixes

mouse wheel code corrected for the editor and added to the tree

foal: improvements in the debugging display for CMarkup objects in file mode; the read and write file offset and the current position

output box right-click function to "Open in document window"

Redo Ctrl+Y now puts the cursor in the correct location

Undo Ctrl+Z combines consecutive typed characters on a line and will also combine consecutive backspaces on a line, and consecutive deletes on a line

Release 2.3.4 has better text drawing performance which is especially noticeable when a lot of far eastern text (such as Chinese or Japanese) is in view and Windows GDI++ is on. This is a big step up from the solution started in 2.2.5. This release also completes tree customization lower level child element, minor resource string improvements, and does not display a parse error when loading non-markup text documents.

This update of the firstobject XML editor integrates CMarkup 11.0 changes, more complete encodings including GB18030, and fuller tree view manipulation. With CMarkup 11's file read mode in FOAL scripts, you can now parse huge XML files with negligible memory usage. To try it out, go to File -> New Program, paste in the following script, modify the XML file pathname to a file you have on your machine, and hit F10 to watch as you step through the elements of the file (click on the xml variable in the watch list to see the window into the document text as you step).

test()
{
  CMarkup xml;
  str sTag;
  xml.Open( "C:\\test.xml", MDF_READFILE );
  while ( xml.FindElem( "//*" )
  {
    sTag = xml.GetTagName();
  }
}

The new tree functions and hot keys are expand all, collapse all, expand descendants, collapse descendants, home, end, page up and page down. Here is the complete list of tree functions and keyboard shortcuts:

*	expand all
/	collapse all
+	expand children or expand all descendants if children already expanded
-	collapse children or collapse all descendants if children already collapsed
right arrow	expand or go to first child if already expanded
left arrow	collapse children or go to parent if no children or children already collapsed
enter	display and select corresponding location in text editor view
Ctrl+C or Ctrl+Insert	copy portion of document to the clipboard
Ctrl+X or Shift+Delete	cut node from tree and portion of document from text editor view to the clipboard
Ctrl+V or Shift+Insert	paste clipboard text into document before the selected node
Context Menu: Paste After	paste after the selected node in the tree
Delete	delete node from tree and portion of document from text editor view
Home	go to the first element
End	go to the last element or attribute visible (uncollapsed) in the tree
Page Up	go up one page
Page Down	go down one page
up arrow	go up one line
down arrow	go down one line
F4	toggle focus between tree and text editor view

UTF-16BE (big-endian) support and a new optional encoding argument in ReadTextFile and WriteTextFile came with the integration of CMarkup 10.1. Alt+F7 validation with MSXML now loads MSXML 6.0 if it is available on the machine (otherwise it looks for 3.0, 4.0 or 5.0), which also came with CMarkupMSXML in the CMarkup release 10.1. Two tweaks in tree customization allow you to specify what to display for an element instead of its data, and to specify a wildcard item especially useful for attributes like id that can occur for any element. For example, the following line in your Tools -> Preferences Tree Customizations will cause an id and/or name attribute value to be displayed for any element in the tree that has either of them.

* @id @name

See Tree customization in the firstobject XML editor.

I am using your firstobject XML editor to read in an xml file and parse through the data and then save the data to a file. Can you tell me how I can get the name of the file that I am parsing so I can create an output file with the same name?

As part of foxe 2.3 being portable software, I posted at portablefreeware.com and they let me know it was still leaving behind a couple of unnecessary registry settings (for MDI document type). So this was just a quick release to remove those, so foxe shouldn't be touching the registry at all now.

I've implemented a very simple installer. This has benefits:

• prompts you to close the editor if you are running a previous version
• copies the editor to the Program Files firstobject folder for you
• creates a start menu entry
• provides a convenient link to uninstall

To keep things simple, the latest editor will be at the download link on the firstobject XML Editor page.

Release 2.2.6 has just a couple of small fixes for annoying problems where the line up gets stuck when the line above contains tab and then word-wrap, and where the small tree view won't go away and the divider is in the wrong position.

Great tool. I just found it and I love it. It would be great if you could edit data in the tree view, though. Also, an auto-refresh would be nice so that the tree data stays up to date as you edit things in the file view.

foxe225Beta.zip 374k.

This release greatly improves performance of displaying non-ASCII characters on Windows machines with full Far East fonts installed. Technical details: under certain Windows configurations the Win32 API for determining text draw dimensions slows down dramatically; I'm guessing it is due to very large Unicode font sets (this build uses caching to minimize calls to GetTextExtentPoint32W, but a much better solution was implemented later in 2.3.4). There is also a small fix for screen position on down arrow.

I tested FOXE on a brand new installed Windows 2003 SP2 system. I found that the Validate with MSXML function did not work. MSXML4 is not installed on the Windows 2003 and XP system by default. Is it possible to fallback to MSXML3, or try MSXML6, if MSXML4 is not on the computer? Using MSXML3 can also validate the document with a schema.

foxe224Beta.zip 372k.

This release fixes quite a number of small but significant issues related to expected functionality. Until now, if you tried to perform an Undo while in the tree view you couldn't; you had to click into or switch (F4) to the document view, even if it was to undo a Cut or Delete done from the tree view. Now Undo will work from the tree view, plus Redo and Paste too. With Paste and Paste After you can now Cut/Copy and Paste to move elements around in the document or between documents conveniently using the tree view. A New Program action was added to the File menu. Two problems were fixed when reloading a document changed outside the editor: syntax coloring and the work-wrap setting. Even more minor fixes included 1) the first find on selected text going forward whether or not the cursor was at the beginning of the selection, 2) Find dialog remembering ignore case setting, 3) double-clicking in FOAL select document dialog, and 4) hiding tree view when document not markup.

I've just been put on to FOXE [the firstobject XML Editor] by a German user in a text editor forum where we've been asking for years to incorporate some unicode/UTF-x support, and the response has always been "too hard". Bzzzzt. They were just resoundingly proved wrong. I've been using and developing (self-relating) software since CP/M days, always learning stuff as I go. When I got to XML, I thought (like the text editor developers I mentioned) whoa, way too hard. But you've not only done it, you've done it better than any of the "major" players.

The first thing I did with FOXE on my system (Win XP x64, lots of RAM, multiterabyte disks) was open a simple MySQL XML dump (72Mb and growing) that's given complete hernias to XML Notepad 2007, IE (32 & 64) Firefox (32 & 64), Textpad, etc, etc etc. They either take more than 20 minutes to open (displaying the simplest formatting), or crash (XML Notepad especially). FOXE opened and displayed the entire db structure in less than 2 seconds, and figured out where the formatting bug was, and displayed mixed charsets (cyrillic, hebrew, greek, korean, simplified chinese, and japanese) without error or pause.

I'll look forward to see what you can fix or implement in upcoming versions. I stopped learning XML when I couldn't find an editor that worked in 2003. That's going to change. Thanks for your efforts, you have no idea how much your program is going to be thrased in the next few months here. :) Kind regards, PC Pete Audiography

Thanks for making such a simple, lightweight but very powerful xml editor, and it's free! I love how focused it is on doing a specific job and doing it well, unlike certain other expensive XML tools. A couple of really useful additions would be:

• The ability to enter an XPath string and have the matching node or nodes highlighted in the tree and text editor.
• Ability to highlight an element/attribute in either the tree or text editor, and generate an XPath string that will return that element/attribute (similar to "Path" but returns XPath).
• Expand/Collapse all elements in the tree view.
• Expand Collapse all elements below a selected element in the tree view.
• Validate XML against an XML Schema

I know it's a free application so some of these may be a bit too much. However the XPath query capability by itself would make it the best editor by far, in my view.

I wonder about the support for XML entities (e.g. < for >) in XML editor. Currently, they are displayed as literal strings, which makes them editable, but on the other hand it makes the text look messy if it contains lot of them. Would there be an option to view them as the characters they stand for (they would have different color than the actual tags)?

The Cancel button is not responsive during a Find operation; either route window messages during the find or use separate threads for the UI and operations.

foxe223Beta.zip 372k.

• Undo and Redo ensure cursor is visible
• File open files added to Windows shell Recent Documents
• simple indent aid when writing FOAL program code (same indent as previous line)
• context function reference help from FOAL program (press F1 with cursor at function name)
• FOAL: WriteTextFile changed to not expect a str reference, EnvRandInt renamed to IntRand, and bit-wise not ~ implemented
• Recent file list and find dialog configuration settings committed immediately
• CDataEdit::ReplaceSel leaves selection cursor after inserted text
• Streamlined replace all in find dialog

foxe222Beta.zip 371k.

• Now you can set a Tools Preferences option to run only one instance of the editor at a time. This means that when you click on an associated file it will open into another window within the application rather than starting a new editor. You can also use command line switches -new and -same to control how the editor opens.
• Command line arguments to specify the line and offset (column) or just the offset from the beginning of the document. i.e. foxe.exe file.xml -line 6 -offset 5
• Configuration (GetProfileInt etc) system overhauled in order to save settings immediately. Settings are still in Application Data\firstobject\XML Editor\settings.xml
• FOAL: UnicodeToStr function name changed to StrFromCodePoint and added StrToCodePoint. Plus StrInsertGrowBy StrAppendGrowBy function names changed to StrInsert and StrAppend.

foxe221Beta.zip 362k.

• Scrolling the tree upwards is now efficient with any number of sibling elements.
• MSXML Validate now gracefully handles MSXML 4.0 unregistered, though I am not yet sure why some recent Windows machines don't have MSXML 4.0.
• fix: remembers maximize setting on startup.
• EnvRandInt function fixed for values between 32767 and a gig (2^30).
• Added ReadTextFile and WriteTextFile functions
• Added StrInsertGrowBy and StrAppendGrowBy functions

This is freakin' great for large XML files. it absolutely buzzed through my many MB file that eviscerated Eclipsed, annihilated notepad, waylayed Word, & exterminated XMLSpy. i could not believe how fast it was...i would have been happy if it just worked, let alone worked so responsively.

foxe215Beta.zip 332k. Another incremental release just to make these fixes available. The tree view vertical scrollbar should be solid now (thanks again W. Jordan). Also, here are fixes for the num type rounding functions and additional num locale conversion functions.

foxe214Beta.zip 330k. The num type was implemented in FOAL to support numbers with decimal places. This is not a C-style floating point number as it is implemented with integer arithmetic and it recalls the number of decimal places. So if you set a num variable to 3.0 it will retain one decimal place. Also several aspects of the Find and Find/Replace dialogs were fixed/improved: bug in Find from end of document, replace to move past replaced text, edit boxes select all when they gain focus, and focus set to Close after Replace All.

Thank you for a very needed software. I was able to write in Arabic. I used UTF-16 because when I used windows-1256 I had all square shapes. I have a question: I want to use a specific Arabic font, since now I only was able to use the default Window Arabic Font (Arial). Can I use your software to choose specifically an Arabic font? Thank you.

foxe213Beta.zip 345k.

• sense which files have changed and offer to reload them when you switch to the editor
• fixed: missing vertical scrollbar *Thanks W. Jordan for exact steps to reproduce
• sense read-only files and prompt on Save *Thanks Joachim for specific feedback
• more efficient memory usage for format align and indent
• syntax coloring in help
• FOAL real reference type and reference argument defaults

Great tool. The only thing I'm missing is the use of regular expressions for find and replace.

foxe212Beta.zip 337k. This fixes the scrollbar flashing annoyance which occured with certain line length combinations in the editor when word-wrap was off and in the tree view. Also it uses CMarkup 9.0 and has these other fixes: standard attribute path elem/@attrib instead of elem@attrib, Cancel/Close button in Replace dialog, F1lp in menubar, splitter bar memory on toggle view text, and right-click Path in document. The zip file also includes the runtest.foal program which you can open and step through (F10) with the firstobject XML Editor to see FOAL programming.

Ben, I don't know whether my last post went through before my PC spontaneously rebooted itself; I hope it did - it was witty and urbane, whereas this one will be utilitarian by necessity whilst I scan my PC.
1) Please use FindFirstChangeNotification or at least add a "reload file" hotkey and menu item; closing the file and then reopening it takes too much time
2) You can't close the help without undocking it
3) If you close the last window, the menu looks like "File View Tools F1lp"; still works, but it looks like the F1 shortcut text is getting laid on top of the Help menu
4) Once you toggle the text view off, foxe forgets the previous location of the splitter bar - thus, it won't toggle it back, and the tree view and text view toggles act as if the are mutually exclusive (until you manually reposition the splitter)
5) The beta did not carry across the number of spaces in my indent preferences to the new settings file
Sorry this is so terse. Keep up the good work.

Excellent and lightweight! I just needed a tool to look at a HTML file in a tree view to learn how to modify it with Perl's HTML::TreeBuilder. Before finding your tool I installed two bigger packages that did not serve the purpose. Thanks a lot! Toni

foxe211Beta.zip 335k. Introducing FOAL! Generate, run, develop and debug programs (with C++ syntax) right in the editor. Also, configuration has been moved out of the registry into a settings.xml file in your user Application Data folder; help (F1) is now a docking window with hyperlinks instead of an XML document; the MSXML Validate hotkey has been changed to Alt+F7; and there are fixes for IME and Chinese locale tree customizations.

foxe205Beta.zip 245k. Tree customization for non-ASCII tag names was causing a crash (see 8.2 Bug: SavePos/RestorePos with non-ASCII names). MSXML validation was only working for inline DTDs, but now your DOCTYPE can reference a DTD file.

foxe204Beta.zip 244k. MSXML Validate is in the Tools menu or F9. You will need msxml4.dll on your machine for it to work. The editor positions the cursor at the error position indicated by MSXML. This beta release also includes a fix for character encodings in the Preferences Tree Customization and displaying path in the status bar mentioned by w. jordan. It is not Unicode but it properly handles your Chinese or Japanese locale encoding so that it is not displayed or used improperly. Also, most message strings have been moved to resource strings to aid in localization.

I noted that in the Status bar, the character position is displayed. Would it be possible to display the Row/Column data?

Hello, the 2.01 enhancement's really a cool feature [see below]. However, the preferences window does not support entering Unicode characters, such as Chinese or Japanese. I hope that Unicode support can be added to this feature. And how about providing an optional Schema validation feature with MSXML? If the user installed MSXML, it will validate the document. If not, it prompts the user to install one.

I notice you have Developer licenses, but the purpose of those seems to be to grant extra functionality. I am wondering - what sort of license does one require to use this product in a business setting, and how much does it cost? I am not interested in the extra functionality - I like this program because it is small and fast and allows me to edit files with little fuss.

Ben, Could you also please make File->Open dialog open the directory of the file opened in the current window.

foxe203Beta.zip 243k. "Go to line" in the Edit menu or Ctrl+G. (Make sure you get build 2.0.3.123 in the Help About dialog; 122 was posted for a couple of minutes with a small bug).

Oh, I forgot, one more request: an easy way to reload a file. Ideally, also monitoring for changes by another process, with a prompt for reloading if it's been changed.

I want to thank you for making available the firstobject XML Editor. It's a great tool with some great features that set it apart from the rest. And the price can't be beaten! I have a couple of little requests/suggestions that I believe would greately enhance the usability of this tool:

1. Go To Line. This is very important for debugging XML code like ant files.
2. replace-all functionality should be modified (or have an option) to replace only within a selected region if there is a selection.
3. I would suggest having a toolbar in addition to the menubar with for commonly used operations, but that's just cosmetic.
4. "Expand children" (by one level), and "expand descendents" (recursively) options on the navigation tree.
5. in the navigation tree, you may want to consider displaying some of the attributes (which ones should be configurable by the user) inline with the element name. When working with Ant files, target (name=compile) is much more usable for quick navigation than having to expand "target". Although "Expand children" per (4) would help somewhat.

Hi, the editor is failing to parse the following html code...

<html>
<body>
<script type="text/vbscript">

set xmlDoc=CreateObject("Microsoft.XMLDOM")
xmlDoc.async="false"
xmlDoc.load("books.xml")

set nodes=xmlDoc.selectNodes("/bookstore/book")

for each x in nodes
  document.write("<xmp>")
  document.write(x.xml)
  document.write("</xmp>")
next

</script>
</body>
</html>

It is considering the xml tag within quotes as a potential xml tag

There used to be a drop-down list in version 1.7 for the Find and Find and Replace dialogs with the most recent searches used. What happened to them?

foxe202Beta.zip 242k. Expand item no longer clears that item's tree customization. Fixed tree behavior of left and right arrows and + and - keys.

Some common tree navigation keys don't work with XML tree:

1. Gray "+" and "-" to expand/collapse the node.
2. Gray "*" to expand all nodes.
3. Left arrow doesn't move left (uplevel), but only collapses the node.
4. Home, End, PageUp, PageDown don't work at all.

I prefer to use the keyboard and mostly ignore the mouse. Arrow keys are MUCH quicker than clumsy mouse hunting.

It also will be very convenient to show the tree as a GRID with expandable/collapsible nodes, like that:

+<li>  | title="DOM Developer's Guide" href="htm/dom_devguide_overview_2g1j.htm"
  +<li>| title="Starter Kit" href="htm/dom_starter_0110.htm"

or maybe:

+<li>  | title="DOM Developer's Guide" | href="htm/dom_devguide_overview_2g1j.htm"
  +<li>| title="Starter Kit"           | href="htm/dom_starter_0110.htm"

Example: Peter's XML editor.

Your XML editor is very nice and very powerful! Tree customization is really great! I used it to edit tree-structured files like sitemap or table of contents. A possible TOC format looks like that (modified from xmlsdk40.chm):

<li title="DOM Developer's Guide" href="htm/dom_devguide_overview_2g1j.htm">
  <li title="Starter Kit" href="htm/dom_starter_0110.htm">
    <li title="What is the DOM?" href="htm/dom_starter_0h7x.htm"/>
  </li>
  <li title="Concepts" href="htm/dom_concepts_2yur.htm">
    <li title="Introduction to the DOM" href="htm/dom_concepts_2lkd.htm"/>
    <li title="How the DOM Works" href="htm/dom_concepts_0myb.htm"/>
    <li title="Working with XML Document Parts" href="htm/dom_concepts_1u9f.htm"/>
  </li>
</li>

I added this line to tree customization to instantly see the titles:

li @title

However, when I expand the <li> node, the title drops down to next line. It's very inconvenient to the eyes (try it yourself with this XML snippet). You don't always need to see ALL the attributes, just SOME of them. Could you please add an option to HIDE attributes in the tree, or setup a filter of what attributes to show? Or maybe show all attributes on a single line after the node: title="DOM Developer's Guide" href="..."

foxe201Beta.zip 242k -- this REALLY makes the tree view handy!

The full release process is too time consuming to allow rapid releases so a "Beta" version and notes are available here. The Beta is simply a newer version without some of the testing and source code preparation involved in the latest official product release on the firstobject XML Editor page.

When I try to input polish letters I get (eg \aogon using Latex notation): UTF-8 is C2 B9 Unicode hex B9 (195) Latin-1 Supplement 0080 - 00FF (31 in windows 1250). And polish characters display as black square or Latin 1 characters with the same ASCII codes as Polish ones. I use Windows XP, selected font has Central European Script. For \zacute and \oacute input works fine.
Could you put row and column number somewhere in visible place? Offset from the beginning is rather not useful.

Great product for the price! However if I enable arabic or hebrew IMEs although I can type into notepad and paste the resulting (relevant language) text into firstobject file correctly, actually typing using the IME puts in 8859-1 characters incorrectly. It says it works with chinese... I have tried both in unicode and in arabic windows with arial and lucida unicode fonts....

XML Editor is great. For perfection can you add line numbering and the diplay of comments in tree view.

I pasted the xml of the Code Project Lounge into the editor. When I search for the string "xsd" it crashes. If I paste instead a little garbage text from the home line on the keyboard, it hangs.

It would be convenient to have Cut/Copy/Paste functions on the right-click context menu.

It would be nice if when the focus is in the tree view, an element is selected and refresh is selected (F5) that the text view would highlight the corresponding text. It works well in reverse (highlight the test and it takes you right to the location in the tree).

I know this is non-trivial, but I would like a regular expression search and replace. With this and the ability to go to a line, I can stop using the Visual Studio editor entirely for XML.

How about an option to print in black and white (maybe use italics and / or bold instead of color)?

It would be nice if you could apply the align or indent just to the current selection (if applicable). I work around this now by pasting into a new document, performing the operation, and pasting back. I do this frequently for XSL files, where I am indenting the XSL tags at one level and the output at another.

I would definitely use the Go To Line feature, especially when I encounter a parse / indent error. It would also be nice if the indent would indent as much as it can up to the error; after all, you can always undo.

It would be nice if pressing tab / shift-tab would indent / outdent a multi-line selection, instead of replacing the whole selection with a tab.

I would like to integrate firstobject into my multi-language editor in Windows dot net application. Is firstobject an open source project? Where can I download the source code for it?

Often I have to read XML files of others instead of writing my own. If I navigate in the left panel, switch to another application, then come back, the focus always goes to the right panel. It would be nice that
- the focus remains where it was
- there is a keyboard accelerator so that I can switch between the panels quickly.

I have enjoyed using this XML editor, however, it would be even more useful if you included a feature to display line numbers and provided a way to jump to a specific line (similar to the Edit > Go To... feature in Notepad). Just a suggestion!

Hi, been enjoying the use of your XML editor. Found a couple things in it that could be improved. 1) Word Wrap option is not persisted across program re-start. 2) If Word Wrap is turned off and a line extends past the edge of the screen, then 'End' key does not move the cursor to the end of the line. It just move the cursor to the last character at the edge of the screen. 3) It would be nice if Attribute names and values had their own colors so they would be more visibly different from Element names and Text. 4) I use the 'Indent' feature a lot ? its very useful. Would be great if it had its own Function key for quick usage.

The XML Editor is great, and especially great is the fact that it is free :-) It would be great if the window title would show the full path of the XML file, not only the file name. When one uses the editor, say, to edit Ant build files, you often end up having several files of the same name, build.xml, in different directories, and if you have two of them open in different windows, and the window title says only "build.xml", it is easy to mix them up.