Things with Infonomix are chugging right along - I’ve been doing a bunch of code maintenance lately, a lot having to do with the code split, and some having to do with better management of node-sets in the XSL files.
So what else is new? Well I’m getting very excited about the possibility of running Infonomix and related applications on more than one application engine. It would be very cool to be able to run Infonomix on PHP, perl, Python, tcl, and even ruby.
Since Infonomix is mostly written in XSL, XML, and SQL, porting shouldn’t be too difficult!
One major factor behind this effort is that the subversion bindings for PHP aren’t available in the debian repositories. I have a feeling its due to a licensing conflict between PHP and subversion, like the issue with PHP and Readline.
Infonomix 0.05 is now ready for download. This release includes some major changes in the codebase, so there are likely to be some bugs. On the plus side, it represents some great work and improved focus on the purpose of the project.
I’m hoping that we’ll soon be able to use Infonomix to manage its own development!
Infonomix is going through some changes… they say change is good, right? Infonomix has start to become a Trac-like project management package, and so the time tracking / time clock system has been split off into its own project: Nextoclock.
This change will allow the two separate projects focus on specifics, rather than trying to balance out the functionality between the two.
Using the pecl svn PHP extension, Infonomix is now able to browse subversion repositories. 
Support is limited at the moment, but I’m hoping to switch from Trac over to Infonomix at some point in the future. When that happens, support will improve drastically!
Yay! Infonomix is now listed at HotScripts!
Infonomix @ HotScripts
This is good, hopefully Infonomix will get some more users and feedback from the community.
I’ve updated the demo to use the new dual-database connections, using the localhost as the read source. This will speed up performance as well as reduce server load.
Feedback is welcome as always…
I’ve just updated the demo to a more recent Subversion snapshot and it looks like its running OK. Lots of small bugs have been fixed lately and its shaping up for a new incremental release soon. Stay tuned!
One of the tickets (#20) asks the question of whether we want to add a wiki component to Infonomix. Its a great idea, but if we move forward with it, when should we start?
I’m leaning towards using either sycaless or private-wiki, probably private-wiki. I’ll need to decide how to implement including additional sitemaps, either the way I usually do with Nexista or an alternative method used with Cocoon.
As a follow-up to the recent incremental release, I’ve made a ton of cleanup commits to the Infonomix code base. The demo is working fine, and the interface is looking much better. There is still plenty to do but I feel that the setup is in a good place for now.
When using the demo, I think that visitors will get the idea of what’s going on pretty quickly - they can create new projects, tasks, and to-do’s, as well as start work on any of them. As I’ve been working on the interface, I’ve found a few miscellaneous bugs so testing is now a priority.
This is a minor release which matches the code we are now using to power the new Infonomix Project Management demo. Improvements include refinements to the data model, and removing code which referenced outdated resources, such as jpGraph.
