GoNeeded.com

No Docbook Stylesheet Plugin.

To be more precise, the Docbook Stylesheets and their supporting Xalan java extensions didn't make it through Eclipse IP review. So unfortunately, this puts a partial damper on the requests we've had for some integrated support for Docbook in the XSL Tooling project.

However, I don't think all is lost, as with other projects, one can still download and use the stylesheets with the XSL support we provide. It just means you'll have to work a bit harder, and I'll have to become more creative on designing an example project.

I do plan on updating Chris's authoring article he wrote a while ago, so that it leverages the XSL Tooling project instead of old EclipseXSLT project. EclipseXSLT was one of the code bases that was used to start the XSL Tooling project, much of that code base has been rewritten since that initial contribution, but the same concepts still apply. So maybe I'll do that on my plane trip out to California next month.

My question for the Docbook users are, do you want the XML Schemas for Docbook to be included in the XML Catalog so that editing and content assistance support is available out of the box? If so, what versions do you want: 4.5 or 5.0?

For DITA, I think we can get the DITA open toolkit as an optional plugin configuration, but I'm not overly familiar with DITA or the open toolkit. So what would you need for us to support in the way of XSL support? Is there a standard set of DTDs or schemas for DITA? What do you want supported? Report your requirements here or in bugzilla.


XSL Validation Settings.

I've used many different XSL editing tools over the years. One of the items that has always puzzled me is that all of these tools lacked support for configurable Validation setting reporting. It's not uncommon to have XSL stylesheets that aren't completely runnable and pass validation by themselves. Many of these smaller stylesheets are included or imported into other styelsheets, and the whole is a valid stylesheet. With the latest release of XSL Tooling a user can now control the validation error reporting level for many pieces of the XSL validation.


This is great, for getting rid of extraneous Error messages, that other XSL editing tools don't allow you to control. You can thank my fellow committer, Doug Satchwell, for his tireless effort on working on this validation scenario and configuration. Currently the above is workspace wide, however, Jesper Moeller has volunteered to try and get the project specific settings implemented as well.

XPath Content Assistance.

I didn't make as much progress on this as I had hoped. Mainly because I got caught in the standard architects dreaded trap. That of trying to over architect the current problem, and looking to far ahead. Eventually, I'm going to need an XPath model, to offer some of the functionality I would like to offer, but for now, I don't think I need it. So, to fix some of the problems with content assistance for XPath, I'm going back to the basics and start over. Mainly to fix the issues and design choices that I had originally made when learning to implement it, but also to hopefully provide a better implementation for content assistance going forward. Hopefully, I can get that worked out for 0.5M8 next month.

XSL Tooling is moving right along, and the editor has advanced far enough along that for most my XSL editing needs, I have migrated to it. Where we are still lacking a bit is in the Debug support. Hopefully we can give that a bit more attention in the coming months.

As always, we are looking for community feedback, if there is something missing or not working please let us know.

Dave Carver: Authoring With Eclipse - Revisited
Dave Carver: Creating an XML IDE with eclipse
Dave Carver: XInclude Support in 0.5M6
Dave Carver: XSL Tooling Updates
Dave Carver: Generating Eclipse Help from Docbook
Dave Carver: XSL Tools 0.5M8 Milestone availabe
Dave Carver: XSL Content Assist - XPath update
Dave Carver: XSL Content Assist - Round Two

Apache Xindice is a database designed from the ground up to store XML data or what is more commonly referred to as a native XML database. The name is pronounced zeen-dee-chay in your best faux Italian accent. Don't worry if you get it wrong though, we won't mind. We just care that you spell it correctly. You might be wondering what a native XML database is good for? Well it pretty much has one purpose, storing XML data. If you don't have any XML data, don't want any XML data or think XML is the most over-hyped technology of the new millennium, then Xindice is not for you. We're not out to change the way data in general is stored, only to provide a good solution for storing XML data. If you survey your projects and see XML popping out of every corner, then Xindice might be a real help for storing that XML. The benefit of a native solution is that you don't have to worry about mapping your XML to some other data structure. You just insert the data as XML and retrieve it as XML. You also gain a lot of flexibility through the semi-structured nature of XML and the schema independent model used by Xindice. This is especially valuable when you have very complex XML structures that would be difficult or impossible to map to a more structured database.

Job Application Tracker within a Java Servlet JSP SQL Frame work. If you have to apply, possibly, for hundreds of jobs, here is a base frame to do so. Since I now have a job, i donate what I used to open source.

Sorry that I switched to eclipse for years and will no longer use JBuilder. I think I will not support jbCheckStyle any more :( Plase use Cheskstyle4JBuilder (http://www.pautinka.com/c4jb.html) if you want o use Checkstyle 3.X or above.

A personal webspyder. ¿Do you want to explore a website for things you're interested in but you don't have the time to do it? W3s does it for you and shows you the results in your Internet web browser.

With Log4J and the Java logging framework being floodgate-based, I personally still see the need for a bit-masked logging framework, where you not only have categories but actual event types instead of event levels. This will be that framework.

This project's goal is to provide an application for managing household issues. Currently, it is able to keep a list of food inlcuding their expiry dates so you always have an overview of what is going to seed soon.

My first Java program! This will be a simple dungeon game (like Zork). I don't think there will be a combat system, but if there is, it won't be implemented for a while. I will be working with a few friends, but help is welcome!

Put simply, Guice alleviates the need for factories and the use of new in your Java code. Think of Guice's @Inject as the new new. You will still need to write factories in some cases, but your code will not depend directly on them. Your code will be easier to change, unit test and reuse in other contexts. Guice embraces Java's type safe nature, especially when it comes to features introduced in Java 5 such as generics and annotations. You might think of Guice as filling in missing features for core Java. Ideally, the language itself would provide most of the same features, but until such a language comes along, we have Guice. Guice helps you design better APIs, and the Guice API itself sets a good example. Guice is not a kitchen sink. We justify each feature with at least three use cases. When in doubt, we leave it out. We build general functionality which enables you to extend Guice rather than adding every feature to the core framework. Guice aims to make development and debugging easier and faster, not harder and slower. In that vein, Guice steers clear of surprises and magic. You should be able to understand code with or without tools, though tools can make things even easier. When errors do occur, Guice goes the extra mile to generate helpful messages.

Do you have a Sudoku to solve? Or want to verify your solution? JSudokuSolver can do this for you! In contrast to other Sudoku solving tools, this program does so by using the same rules a human would. So you can improve your Sudoku solving skills.

JERC:Java Encrypted Relay Chat. Our goal is to construct a java program to allow our users to chat securely to each other. We want to make it so our users don't have to worry about they're chats being unintentionally intercepted by third parties.