Helma Logo
main list history

Version 3 by hannes on 01. March 2006, 14:10

3# It's ok to do tricky things, but do them in the observable, in a an observable and traceable manner.

Version 2 by hannes on 01. March 2006, 14:09

1I thought it would be a good idea to start collecting thoughts and ideas that will be vital for Helma 2. I considered calling this page "Helma 2 Manifesto" but that sounded a bit too heavy# Extract the framework from an actual application, at least for its humble initial staterather than build a framework towards hypothesized applications.
2# As much as possible of what gives shape to the framework should be implemented in JS, not Java.
3* Extract from real application building experience. Helma 1 was in some respects conceived by myself sitting in my room without much experience developing real world web sites. Now I often sit and suffer when dealing with things I didn# It't know or consider at the time.s ok to do tricky things, Helma 2 should take into consideration every bit of web mechanics that can be expected but do them in a state of the art web site in 2006. The best way of achieving this is to start using Helma 2 for writing web apps from the start. Or put the other wayobservable, to write the cleanest possible web application and extract Helma 2 from itin a traceable manner.
4* Bridge the gap between client and server side scripting in a nice way. Helma 1 is pretty much client side scripting agnostic. With the resurrection and rising appreciacion of client side JS# Make assumptions for solving common tasks, this is a loosing proposition. Make the transition of code and data between server and client nice and seemlessbut provide ways to override these assumptions.
5# Make it easy to start a new application from scratch.
6# Know about other framework's strengths, but don't copy. Copying just isn't fun.

Version 1 by hannes on 14. December 2005, 17:37

1I thought it would be a good idea to start collecting thoughts and ideas that will be vital for Helma 2. I considered calling this page "Helma 2 Manifesto" but that sounded a bit too heavy, at least for its humble initial state.
3* Extract from real application building experience. Helma 1 was in some respects conceived by myself sitting in my room without much experience developing real world web sites. Now I often sit and suffer when dealing with things I didn't know or consider at the time. Helma 2 should take into consideration every bit of web mechanics that can be expected in a state of the art web site in 2006. The best way of achieving this is to start using Helma 2 for writing web apps from the start. Or put the other way, to write the cleanest possible web application and extract Helma 2 from it.
4* Bridge the gap between client and server side scripting in a nice way. Helma 1 is pretty much client side scripting agnostic. With the resurrection and rising appreciacion of client side JS, this is a loosing proposition. Make the transition of code and data between server and client nice and seemless.