Helma 1.7 feature scratchpad
hide
ContentsSome vague feature ideas for Helma 1.7 New Persistence API implemented in JavaScriptTry to decouple helma.objectmodel from the rest of the framework, and start layering a javascript interface on top of it so it can be used in stand-alone/explicit fashion. Alternative Session ImplementationsStart using SessionManager to actually implement different session management schemes.
Allow skins to extend/inherit from each otherThis is a very useful idea to take from Django. This allows developers to create a base.html template with the shared XHtml boilerplate code, and let sub-templates fill in the actual content. The subskins feature introduced in Helma 1.6 are a perfect fit for this. Extending a skin would have the same effect as partially overriding a skin from another repository: Some subkins may be overridden, the others (and usually the main skin) are inherited from the base skin. What about syntax? Currently I sympathise with the idea to change subskin syntax from The old Library and Modules
Varargs Support for res.write() and consortsAllow to pass 0..n arguments to res.write(), res.writeln(), res.debug() and similar methods. My proposal is to write out arguments separated by a single whitespace like print does in python. More Ideas
|
navigation
Download
Community
Weblog
Mailing Lists
IRC Channel
Documentation
Introductions
Tools
Reference
Project
Roadmap
Bug Reporting
Source
Wiki
Tags
Updates
Related Projects
Sites using Helma
Shop
search
tags for this page
all tags
Tagsapps (1) bugs (2) class (1) community (2) compatibility (1) concurrency (1) continuations (2) Documentation (4) Documentation ORM (1) dogfood (1) formatting (1) gobi (1) helma (6) helma 1.6 (13) helma 1.7 (8) helma 2 (13) helma ng (7) hopobject (1) html (1) inheritance (5) introspection (1) java (2) javascript (5) jetty (1) JSDoc (1) lazy (1) marius person (1) metaprogramming (2) modules (3) oop (1) organization (2) ORM (1) parsing (1) project (2) projects (1) prototype (1) Rabbit (2) REPL (1) rhino (4) roadmap (3) shell (1) shop (0) Skin Rendering (5) Snippets (1) source svn (1) sugar (3) templates (13) testing (4) Tobi (7) tobi repl shell introspection (0) xml (1) Pages linking to this page: Wiki Overview Text Draft |
Comments
#1 by maks at 2008/01/10 01:51Hannes,
BUT will this mean having to switch over to using the rhino bundled in java6 ???JSAdapter turns out to be just a Java class and its now added in helma 1.6.2 in package helma.scripting.rhino- Also is proposing using JSON as an alternative format for config file to radical for 1.7 ? If so I would propose it for 2.0 instead
#2 by Philipp at 2008/04/08 16:17A huge improvement would be a better documentation. It's impossible to get a "quick" overview over Helma and it's features. If you see some advanced source at work it's really hard to understand what's going on.
Maybe this point is a nice job for a "HTL-Diplomarbeit" or bachelor thesis. I know some really good HTL examples from the past, but I've no idea how it's today.
#3 by maks at 2008/04/09 03:07As a first step to decoupling the Persistence API (which I do think is a fantastic idea) could be to implement http://helma.org/bugs/show_bug.cgi?id=612
which should then allow new persistence schemes to be "tried out" in pure js.