I am fixing few bugs before releasing the third release candidate. A recent files menu has been added and code indentation has been corrected. I am few days away from releasing it. After some more tests it will be ready.

I am also working hard on the new development branch of XPontus XML Editor which is plugin based. It will be available maybe this summer. Apache Maven is used to manage the project and its sub modules(plugins).

I will release the rc3 version of XPontus XML Editor next week. The application is pretty stable now but still misses some features.
I will only provide bug fixes to the stable version without new features added. It was a good experience and it showed the limitations and the issues with the way I coded the application.

I am working again on the development release which already have code completion and "of course" lots of bugs! :p . It shouldn't be long to get it done and release a pre1 version, maybe june?

Stay tuned!

I am taking some time off for now. I will try to get a bug fix release ready for next month which will be likely called rc3 .

I have been working on a new project called JHTMLCleaner . The software is almost ready. I am expecting to release it in few weeks.
I also received lots of comments about XPontus XML Editor current version. I am working on the next release too, but it will take time to get it done, the way I want it to be.

I am working on the user interface and code completion of XPontus XML Editor today.

I am thinking about the new API of XPontus. Most stuff depends on the main window which act sometimes as a wrapper for helper classes. I should get rid of the dependencies upon the main window. I will have to rewrite the API taking into account that the editor must provide extensions points where a plugin might "be plugged".

The 1.0.0rc2 version of XPontus XML Editor(http://xpontus.sf.net) was released today. I am about to get back working on the development version. Here is the list of features to add and test :

• xml code completion
• xpath
• xquery and stx support for transformations
• full caching of dtd and schemas
• better use of the docking framework
• virtual file system support
• tree view for xml editing
• xml code outline view
• xml signature support
• api to integrate xpontus into other applications

Here are the new user interface improvements before the 1.0.0rc2 releases. The tabbedpane now has close icons. On a double click, the document container is maximized.

The 1.0.0rc2 release of xpontus is ready. I will build the installers this week.
Here are the problems which have been corrected :
- Encoding detection
- Schema validation

Options has been added to customize the token colors.

Among the new features there are :
- auto close of xml tags
- package installers for solaris and freebsd
- dtd and schema caching when validating xml files

The code has been cleaned up and more comments have been added.

Code completion(based on dtd or schema introspection) is here but still very experimental.
Here are the remaining problems for the upcoming release :
When content assist is enabled, the typing is very slow.

• Code completion database doesn't process dtd subsets (the parser doesn't ready any sub-dtd)
• Plugin support is a must as lots of features will be added
• Some code must be rewritten to take advantage of the docking framework
• Virtual filesystem support is not complete
• XML Catalog is incomplete too
• XPath support doesn't support namespaces yet
• My other project jxsltdoc is in progress, it will be added as well as a schema documentation tool(xssdoc and dtddoc)
  

I finished the outline view to browse code structure and I re-coded lots of classes to make full use of the new docking framework.

The latest screenshot

I am a little bit late for the release, working on the user interface. I want to second release candidate to be great in terms of user experience, features and usability. It will be a great move towards a full featured XML editor.

Here is a screenshot of the new UI(I am making full use of the docking windows library)

I added syntax highlighting for XQUERY and DTD today. I will try to complete the code completion for XML the week end with some help from IRC.

I am now working on code completion. I hope to finish it and test the application before the end of the month. Inserting the end of a xml tag automatically is done, I am working on providing XML completion via schema introspection and it won't take that long.

The XML lexer is working! I also finished the sql, html, java, dtd and properties syntax coloring.
I am now focusing on the outline view to display the code structure and code completion.

Here is as usual the latest screenshot.

I Still have a nasty bug with syntax highlighting and multiline comments. This is preventing me from working on code completion.

See the latest screenshot

I still have few bugs with the xml syntax colorer. Javacc is tough but interesting!

The latest screenshot

I am almost done with the lexer stuff. Syntax highlighting almost behaves correctly. In few days, I will have a correct syntax colorer for common languages and add errors tooltips.

I have yet to start thinking about the best way to provide code completion. It shouldn't be that hard, but it must be fast!

Here is another screenshot of the syntax colorer

I am dealing with multiline tokens and I am making some progress. Still have to find a way to set the right amount of text to parse and color the tokens according to their type. The offset of the token is not computed correctly. Sometimes I have text already parsed appearing at strange locations.

I believe I will be able to solve it soon. The next step will be highlight errors and adding code completion.

I must release in the middle of december!

Here is a screenshot of multiline tokens handling

I've fixed few bugs today and improved the xpath support. I will remove all unready features and fix them until they are ready. My main problem is now multiline tokens for syntax coloring!
The auto-close tag mode is ready for XML. I have to find a way for auto-completion and put it as simple as possible.