Just wanted to give a quick update regarding my Mocha/Helma plans...
Since I've shared some thoughts about using Helma as the base for Mocha projects over a year ago, I've ported parts of my existing Mocha Engine to Helma and gained some real world experience with how the two concepts fit together. I learned a lot about "the Helma way" of doing things (I hope), which was an overwhelmingly positive experience.
While I at first implemented things the Mocha way, I often later realized that there already was an elegant Helma way of solving the same problem. For the most part I now appreciate even those aspects of Helma that I originally saw more critical.
As a result of that evolution, the ideas for a Helma based Mocha framework changed quite a lot. First the framework grew to resemble the old Mocha engine, then I experimented with "the Helma way" and trimmed it down until there was hardly any code left. I now started with a new approach ("OpenMocha") that I believe to be an interesting blend between "the Mocha way" and "the Helma way". I'll release a first build as soon as I have the core concept in a working state.
Due to the Ajax-hype and the resulting openness of web developers towards more complex javascript coding, there might be renewed interest in "our way" of building web apps. When I imagine a blend of
Helma
/
OpenMocha
/
Chopper
/
Prototype
, I see the line between server-side and client-side fading and I see "Javascript heaven".
I'm not sure how Gobi fits into this picture, since Gobi is less about putting a framework in Javascripters hands and more about putting the power of Helma in the hands of the Non-Javascripters. Does this interpretation of Gobi make sense?
Helma = the java based core framework --> for "scripting" applications using Javascript
Gobi = high level "web" framework --> for "configuring" solutions through the browser ?
OpenMocha = high level javascript based framework --> for "scripting" solutions using Javascript
13.06.2005, 16:39
