ANNOUNCE: Aejaks 1.1
I fixed a few bugs that were present in the 1.0 release. Most notably, a bug was fixed that prevented the MrPersister database package from running under Java 1.6.
I fixed a few bugs that were present in the 1.0 release. Most notably, a bug was fixed that prevented the MrPersister database package from running under Java 1.6.
It looks good, but I am not
It looks good, but I am not sure why I should use it? I have lots of custom components created with some variations to the main components. As I see this the configuration / UI is done using TCL, which is a new language to learn not only for me but for the whole team and new comers also. I have a framework which handles various things like validation, various mappings, EJB connections etc, Not sure how I am going to use all that with TCL.
It seems like a good project but somehow I am doubtful about its practical use. Is someone exploring this or using this?
May be Java development may have more lines of code but I still feel that its easier and quicker to understand, maintain and train people.
I am not really trying to discourage this, but I am just not sure how to start / use it effectively?
Regards,
Pawan
Certainly any unfamiliar
Certainly any unfamiliar language may seem hard to read, but with a little study, I think you'll find Tcl simple and concise. I would recommend http://en.wikibooks.org/wiki/Programming:Tcl as a nice introduction to Tcl. (The sections on Tk don't apply to Aejaks, but Aejaks does use that same programming model to display Echo2 widgets.) Tcl does have a few warts, but no more so than comparable languages.
As far as building applications in Aejaks, there are a few examples of what others are doing at http://aejaks.sourceforge.net/App_Gallery/index.html. It's still relatively new, so not a weatlth of public applications (yet.) Heck, it's hard to find many Echo2/Echo3 applications in the wild as well. I have been building several internal applications, but am unable to share those.
For me, writing less code is always better: less code to write, less code to test, fewer places for bugs to creep in, faster to get my app up and running. Interactive development is a big win also. Simply edit script code and reload my application URL. Server stays running, no compile and deploy steps. I use the 'Aejaks Console' sample application to test out new code, simply pasting into the console from my editor window.
Interfacing to your existing framework may or may not be must of a problem. The Jacl interpreter (Tcl implemented in Java) includes a 'java' package that allows any Java object to be instantiated, instance and static methods to be invoked, fields examined and set, etc. all done via the Java reflection package.