Wednesday, December 30, 2009

Random ideas for XINS and Logdoc

Here's a random list of possible enhancements to XINS.

First, a couple of changes that would make it much easier to configure an IDE (such as Eclipse or NetBeans) to work with XINS:

  • Move all Java source code to src/java/; currently it is spread out over src/java-common, src/java-client-framework and src/java-server-framework. Still, the JAR files can remain the same.
  • Put the generated Java source files also under src/java/, such as the Log and TranslationBundle classes.
  • Put all generated class files under build/classes/.
  • Make the Library classes detect the XINS version at runtime, instead of using a text replacement technique to modify the source code before compiling it.
Then some ideas on Logdoc:
  • Split out Logdoc from XINS. It's not needed inside XINS, all it needs is a JAR file and some Ant tasks for generating some stuff (like the Java source files and the documentation).
  • Make it easy to plug in a different logging library. Currently, Logdoc generates Log4J code, but it should be fairly simple to make it generate code for other logging libraries. It doesn't mean Logdoc should actually implement this, but it would at least facilitate it.
To be continued.

1 comment:

  1. I've just update the Netbeans project so that it detects Log better. Now all source files have the "green" status.

    As for logdoc, I did an investigation a few years ago and it is not as easy as it seems.

    Anthony

    ReplyDelete