Helma Logo
main list history

Version 18 by hannes on 21. May 2008, 20:46

1Helma NG 0.2 is the next version of *Helma NG* and scheduled for release in was released on May 21 2008.
3===This page serves a historic purpose only as it was used as idea scratchpad during development. Features already implementedFor up-to-date release info about the release, head over to the *Helma NG 0.2 page|/ng/Release 0.2* in the NG space.
5=== Some of the implemented features
6
13=== Planned features (work in progress)that weren't implemented
23=== IdeasOther ideas, Dreams, Feature requests (feel free to add your own)mostly not implemented

Version 17 by hannes on 16. May 2008, 11:54

10* A logging module based on Apache log4j.
19* A logging module. should we keep helma logging?

Version 16 by hannes on 05. May 2008, 18:03

8* Support for continuations. Needs to be started with with -Drhino.optlevel=-1 though.
9* Static file serving with the development server.
18* Static file serving with the development server.

Version 15 by hannes on 24. April 2008, 00:46

18* Static file serving with the development server.

Version 14 by hannes on 23. April 2008, 19:27

5* Low level skin support, and support for skin parsing and rendering. Low level skin parsing will use a callback based approach. The parseSkin() function will take two arguments: the name of the skin resource and a javascript function that will be called with the skin parts as arguments as they are parsed. It is expected that modules that implement skin rendering functionality build on top of this low level API to provide more abstraction. For example, the *simpleweb module* will provide skin functionity similar to that in helma 1.

Version 13 by hannes on 23. April 2008, 19:26

6* helma.simpleweb skin support, supporting module implementing basic helma 1 skin functionality, subskins and *skin inheritance|http://dev.helma.org/wiki/Helma+1.7+feature+scratchpad/#Allowskinstoextendinheritfromeachother*.

Version 12 by hannes on 23. April 2008, 19:26

3=== Planned features (work in progress)Features already implemented
5* <strike>Low Low level skin support, and support for skin parsing and rendering. Low level skin parsing will use a callback based approach. The parseSkin() function will take two arguments: the name of the skin resource and a javascript function that will be called with the skin parts as arguments as they are parsed. It is expected that modules that implement skin rendering functionality build on top of this low level API to provide more abstraction. For example, the *simpleweb module* will provide skin functionity similar to that in helma 1.</strike>
7* *JSAdapter* support for modules. Just define any of the following functions, and the module will behave accordingly.
8* Support for continuations. Needs to be started with with -Drhino.optlevel=-1 though.
9
10=== Planned features (work in progress)
11
20* <strike>JSAdapter support for modules? Would be terrific. How can it be done?</strike>
25* <strike>Support for continuations.</strike>

Version 11 by hannes on 22. April 2008, 12:14

5* Low <strike>Low level skin support, and support for skin parsing and rendering. Low level skin parsing will use a callback based approach. The parseSkin() function will take two arguments: the name of the skin resource and a javascript function that will be called with the skin parts as arguments as they are parsed. It is expected that modules that implement skin rendering functionality build on top of this low level API to provide more abstraction. For example, the *simpleweb module* will provide skin functionity similar to that in helma 1.</strike>
19* JSAdapter <strike>JSAdapter support for modules? Would be terrific. How can it be done?done?</strike>
24* Support <strike>Support for continuations.</strike>

Version 10 by hannes on 20. April 2008, 10:04

14* Move over rhino serialization code from helma 1.
22* Include gobi markuplib as module?
23* Make module for functional programming utils contiaing partial() from gobi markuplib. Check with functional programming pundits for what else to include.
24* Support for continuations.

Version 9 by hannes on 20. April 2008, 00:40

13* Support for running web server and shell simultaneously, running compiled and interpreted code in the same app, and launching the debugger in running apps.
21* Support for running web server and shell simultaneously, running compiled and interpreted code in the same app, and launching the debugger in running apps.
22

Version 8 by hannes on 20. April 2008, 00:38

6* A logging modulehelma.simpleweb skin support, supporting basic helma 1 skin functionality, subskins and *skin inheritance|http://dev.helma.org/wiki/Helma+1.7+feature+scratchpad/#Allowskinstoextendinheritfromeachother*.
7* A modules module that provides meta information about loaded modules. In addition to an overview of loaded modules, currently I think we'll need the following:
8** modules.name - the name of the current module
9** modules.path - the path of the current module relative to the 'root' module (for href generation in simpleweb)
10** modules.parent - a reference to the module that loaded the current module (for relative resource paths in skin loading)
11** maybe a way to retrieve the file system path of the module, but I think getResource() covers this already.
12* A logging module. should we keep helma logging?
12* Maybe rethink Rethink the module namespace. Does very generic stuff such as File IO need the 'helma' prefix? (hns)
13* JSAdapter support for modules? Would be terrific. How can it be done?
14* Allow modules to define which properties to export, and keep the others private? This would again require some sort of wrapping.

Version 7 by hannes on 19. April 2008, 12:35

12* Maybe rethink the module namespace. Does very generic stuff such as File IO need the 'helma' prefix? (hns)

Version 6 by hannes on 19. April 2008, 12:34

12* Maybe rethink the module namespace. Does very generic stuff such as File IO need the ..'helma' prefix?

Version 5 by hannes on 19. April 2008, 12:32

3=== Planned features (work in progress):progress)
8* Port over more modules from Helma 1.
9
10=== Ideas, Dreams, Feature requests (feel free to add your own)
11
12* ...

Version 4 by hannes on 19. April 2008, 12:30

6* A logging module.
7* Support for running web server and shell simultaneously, running compiled and interpreted code in the same app, and launching the debugger in running apps.

Version 3 by hannes on 19. April 2008, 12:30

7* Support for running web server and shell simultaneously, running compiled and interpreted code in the same app, and launching the debugger in running apps
8* Support for running compiled and interpreted code simultaneously
9* Support for launching debuggers in running app

Version 2 by hannes on 19. April 2008, 12:28

1Helma NG 0.2 is the next version of *Helma NG* and scheduled for release in May 2008.

Version 1 by hannes on 19. April 2008, 12:27

1Helma NG 0.2 is scheduled for release in May 2008.
3Planned features (work in progress):
4
5* Low level skin support, and support for skin parsing and rendering. Low level skin parsing will use a callback based approach. The parseSkin() function will take two arguments: the name of the skin resource and a javascript function that will be called with the skin parts as arguments as they are parsed. It is expected that modules that implement skin rendering functionality build on top of this low level API to provide more abstraction. For example, the *simpleweb module* will provide skin functionity similar to that in helma 1.
6* A logging module
7* Support for running web server and shell simultaneously
8* Support for running compiled and interpreted code simultaneously
9* Support for launching debuggers in running app