Helma

Helma 1.7 introduces a much requested feature to create HopObject collections programmatically and on the fly, without having to define them in the prototype's type.properties file. HopObject constructors now have a new static getCollection() method ... [More] that takes a single JS object argument. The argument contains the collection properties as you would normally define them in the _children section of the type.properties file, e.g.: var c = Page.getCollection({ order: "name", filter: "id > 10", }; You can also specify the type of contained objects using the "collection" property, so the following collection is equivalent to the one defined above: var c = HopObject.getCollection({ collection: "Page", order: "name", filter: "id > 10", }; Note that for "nested" properties such as group.order or local.1 you have to use quoted "flat" properties, not nested objects: var c = Page.getCollection({ group: "author", "group.order": "author", "group.prototype": "AuthorGroup" }); Since I thought it would be handy, I also implemented "limit" and "offset" collection properties to implement easy pagination: So to fetch pages 11-20, you would do something like this: var q = Page.getCollection({ limit: 10, offset: 10 }); Note that "limit" is just an alias for "maxSize" introduced to be more consistent with the underlying SQL syntax. This feature is currently implemented and known to work on MySQL, Postgresql, and Oracle. [Less]

Update: the functionality described in this proposal has been implemented by HopObject.getCollection() - see Creating Collections programmatically. I've been thinking about a query feature that allows to build HopObject collection on the fly. Under ... [More] the hood, the query object would be a HopObject with a custom DbMapping. The SQL query would probably be built using a subnodeRelation built from properties of the query object's filter property. These filter conditions could cover a number of common comparison operators: columnname - add equal to clause for the columncolumnname_not_equal - add not equal to clause for the columncolumnname_less_than - add less than clause for the columncolumnname_greater_than - add greater than clause for the columncolumnname_less_or_equal - add a less than or equal to clause for the columncolumnname_greater_or_equal - add a greater than or equal for the columncolumnname_like - add like clause for the columncolumnname_not_like - add not like clause for the columncolumnname_is_null - add is null clause for the columncolumnname_not_null - add is not null clause for the column Query objects could be created by a constructor or factory function passing the arguments as object literals. var q = new HopQuery({ type: Page, filter: { createtime_greater_than: t1, createtime_less_or_equal: t2, type_like: "update:%" }, order: "createtime desc" }); [Less]

This page docuents new features in Helma 1.7. As Helma 1.7 hasn't been released yet, this page is incomplete and work-in-progress. Contents [hide]Case sensitive HopObject property namesProgrammatically generated collectionsProgrammatically defined ... [More] HopObject mappings Case sensitive HopObject property names Property names in HopObjects are now case sensitive. This means that obj.foo, obj.Foo and obj.FOO no longer point to the same property. This feature should help to enforce good programming habits and speed up property access. Programmatically generated collections Helma 1.7 defines a new static method on HopObject constructors that allows to generate HopObject collections via JavaScript. The method is called HopObject.getCollection() and takes a single JavaScript object as argument. It returns a HopObject that is equivalent to the one you would get by defining it as a collection in a type.properties file. Programmatically defined HopObject mappings There is a new and experimental definePrototype function that allows to define prototype mappings via JavaScript. In its current implementation, there is a global function called definePrototype() that takes two arguments: The prototype name, and a JavaScript object describing the type mapping. [Less]

Some vague feature ideas for Helma 1.7 Contents [hide]Decouple Objectmodel APIAlternative Session ImplementationsAllow skins to extend/inherit from each otherLibrary and ModulesVarargs Support for res.write() and consortsMore Ideas Decouple ... [More] Objectmodel API Try 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. Status: HopObject-less Helma applicationsProgrammatically defined HopObject mappings Alternative Session Implementations Start using SessionManager to actually implement different session management schemes. db persistenceclient based persistencereplication/load balancing Status: nothing so far Allow skins to extend/inherit from each other This 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. Status: Still trying to come up with a syntax for this that is neither ugly nor breaks existing code. Library and Modules Extend and enhance helma.File.js and other modulesUrl.js that parses all fields (rfc3986) and allows to set them. examples: python like urlparser or minimalistic parseUri Start removing core extensions in favor of modules? Status: Some work done on helma.File and helma.Mail.No decision yet on removal of core extensions. Varargs Support for res.write() and consorts Allow 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. Status: pending due to performance considerations regarding java varchar. More Ideas Provide full configurability when running Helma in embedded (tomcat) mode.Support Jürg Lehni's rhino extensionsSupport JSAdapter already in helma 1.6.2allow apps.properties extensions to be defined in app.properties (without the "appname." prefix)Rewrite helmadoc to rewrite with standard rhino (no more token patch)Drop helma.doc package, maybe in favour of jsdoc-toolkit, or get token parsing funcitonality accepted into rhino cvs.Debian/Ubuntu package for Helma [Less]

Helma 1.7 introduces a much requested feature to create HopObject collections programmatically and on the fly, without having to define them in the prototype's type.properties file. HopObject constructors now have a new static getCollection() method ... [More] that takes a single JS object argument. The argument contains the collection properties as you would normally define them in the _children section of the type.properties file, e.g.: var c = Page.getCollection({ order: "name", filter: "id > 10", }; You can also specify the type of contained objects using the "collection" property, so the following collection is equivalent to the one defined above: var c = HopObject.getCollection({ collection: "Page", order: "name", filter: "id > 10", }; Note that for "nested" properties such as group.order or local.1 you have to use quoted "flat" properties, not nested objects: var c = Page.getCollection({ group: "author", "group.order": "author", "group.prototype": "AuthorGroup" }); Since I thought it would be handy, I also implemented "limit" and "offset" collection properties to implement easy pagination on dbs that support it (Postgresql and Mysql AFAIK): http://www.sql.org/sql-database/postgresql/manual/queries-limit.html So to fetch pages 11-20, you would do something like this: var q = Page.getCollection({ limit: 10, offset: 10 }); Note that "limit" is just an alias for "maxSize" introduced to be more consistent with the underlying SQL syntax. This feature is currently not supported on Oracle. If somebody can provide the SQL syntax needed to make this work on Oracle plus some testing support, I'll happily add this. [Less]

To store your HopObjects into a relational database system you need to define a database mapping. This is done in the type.properties files located in the persistent HopObject's prototype directory (e.g. apps/myApp/MyPrototype). The type.properties ... [More] files contain no JDBC connection information, which is located in the db.properties file in the Helma installation directory. Contents [hide]Configuration SettingsDatabase relatedInheritanceObject ManagementSimple PropertiesReferenced ObjectsCollectionsMountpoints Configuration Settings Database related _db = datasourceName The _db entry describes the database source to use for managing objects of this type. datasourcename is the connection's name defined in the db.properties, which is located in Helma’s installation directory or the application directory. The db.properties file contains information about the JDBC connections, like the JDBC driver, the connection URL and the database username and password. _table = tableName The _table entry tells Helma which table to use for objects of this type within the database. To avoid problems with reserved words of SQL or your database system you should prefix your table names. (e.g. T_Story for the Story prototype’s table) _prototype = prototypeColumnName Helma can store multiple prototypes into one single database table. This feature could be useful if you extend prototypes for inheritance and if you want to store all sub-prototypes into the same table. To enable this feature just add a column to the table where Helma can store the prototype’s name. This column is referenced in the type.properties of the affected prototype. This picture shows a database table where Animals and Dogs could be stored. A Dog is a sub-prototype of the Animal prototype. It inherits every property from the Animal and defines two new properties called "Breed" and "Color". Note: The Dog’s type.properties just defines the two new properties. All other stuff will be inherited from the Animal. _extensionId = String or Integer If you extend a prototype, Helma will use the name of the sub-prototype as value for the _prototype database column. This could slow down the performance. Better would be to choose a numeric value, which result faster index retrievals and queries. You can define this numeric value in the _extensionId property of the sub-prototype. Example: If Helma needs all cats, the db-layer can filter all animals with the value '260486'. The value '260486' is defined in the cat’s type.properties as _extensionId! For dogs the _extensionId is set to a 'dogu dugu' string. Animals’ type.properties defines no _extensionId, so Helma uses the prototype’s name, which is 'Animal'! Download the animal demo application: nametypesizetypeproperties_prototype.pngimage/png12229 bytestypeproperties_prototype_helma.pngimage/png7529 bytestypeproperties_prototype_extensionid.pngimage/png10996 bytesdemo_animalfarm.zipapplication/zip3156 bytes Inheritance _extends = Prototype The _extends entry engages Helma to inherit properties, functions and skins from another prototype. This can be compared to Java’s subclassing mechanism. For example could be a Dog's _extends value the Animal, which inherits to the Dog prototype basic properties like father or mother, some skins and standard functions like getBiologicalClassification() Object Management _id = primaryKeyColumnName The _id entry defines the column to use as primary key. Helma requires a single primary key with no other functionality. You can read this unique ID from the _id-property of the HopObject. _parent = localPropertyName, localProperty.parentsCollectionName, root.collectionName The _parent entry contains a comma-separated list of properties of objects of this type to be used as parent. Objects must know their parent in order to generate correct URLs in their href() function. If a property in the list is null, Helma will look on the following one to fetch a parent object. If an entry in the _parent item does not contain a dot, it is interpreted as an object property of the current object that acts as the object's parent. If an entry contains a dot character, the part after the dot is interpreted as a collection in the parent object in which the current object is contained. Alternatively or additionally, a second or third dot separated part may indicate an object reference instead or in addition to a collection or mountpoint. If the _parent is specified as "root", it is not interpreted as a property of the current object. Instead, the application's root object is used as parent object. The _parent entry solves a very specific problem: HopObjects do not know their canonical URLs if you call the href() function, since they can be members of more than one collection. Example: James Nachtwey, Steve McCurry and Annie Leibovitz are well known photographers. A photographer might work for an agency, so the photographer’s prototype contains a property acency, but if they don’t, it’s null. Nachtwey and McCurry are war photographers, so a root.warphotographers collection cointains both. Leibovitz is neither taking pictures in war zones, nore working for an agency. All photographers are stored in the root’s photographers collection. The Photographer's types.properties looks like that: _parent = root.warphotographers, agency, root.photographers agency = object(Agency) Helma’s href() will look first in the war photographers collection and return an URL like /warphotographers/nachtwey, if the person is member of this. Now you call href() on the object Annie Leibovitz. She isn’t member of warphotographers, her agency property is null, but she is member of root.photographers, so href() will return /photographers/leibovitz. _children Simple Properties simplePropertyName = DB_COLUMN_NAME A simple property maps a property name of the object to a column of the database table. The type of the table's column need not be specified. Helma does all necessary conversion when reading or writing a property value. simplePropertyName.readonly = true Makes the property read only and initializes it with the value from the database. simplePropertyName.private = true The private flag forces Helma to update this column only in the database, but prevents any updates on collections and references containing the modified object. Referenced Objects obj = object(SomeHopObject) obj.local obj.foreign obj.local.X obj.foreign.X obj.logicalOperator Collections coll = collection(SomeHopObject) coll.local coll.foreign coll.loadmode coll.cachemode coll.order coll.filter coll.filter.additionalTables coll.hints coll.maxSize coll.accessname coll.group coll.group.order coll.group.prototype Mountpoints moutpointName = mountpoint(SomeTransientHopObject) [Less]

Most activity in the wiki currently revolves around working drafts for additional documentation and around Helma NG with a newly added dedicated Helma NG Wiki space. Other important wiki pages are the lists of Related Projects and Sites using ... [More] Helma, to both of which you are welcome to add your own or other missing entries. Also helpful to find what you are looking for, may be the search page, the updates page, the tags cloud and the list of pages in the general wiki, which contains ideas, drafts and other miscellaneous bits and serves as an incubation space for new projects and documentation pages that may later be moved to their dedicated spaces. Don't hesitate to just add a new page if you have something to contribute and are not sure where otherwise to put it. List of the recent changes: namemodified bylast modifiedHOWTO improve Helma 1.xdaniel2009/03/06 10:15Helma Reference ErrataPhilipp2009/03/01 03:57Helma 1.7 wishlisthannes2009/02/19 12:21Cronjobshannes2009/02/19 12:14Configuring Jetty in Helma 1.xhannes2009/02/19 11:54Pure JavaScript applicationshannes2009/02/19 10:40Many-to-many Relationshipsmaks2009/02/18 23:31helma.org redesignhannes2009/02/18 00:29Helma Roadmaphannes2009/02/17 23:20Helma and MySQLhannes2009/02/17 22:57Helma and log4jhannes2009/02/17 22:48Helma Logginghannes2009/02/17 22:43Cachinghannes2009/02/17 22:39Helma NG Wishlisthannes2009/02/17 20:16XML-RPC Samplehannes2009/02/17 20:14Minutes from the Helma Spring 2008 Meetinghannes2009/02/17 13:48Handler for rendered skinshannes2009/02/17 13:16Sites using Helmaanton2009/01/26 11:35Modules and Scopes in Helma NGhannes2009/01/25 19:48Rabbittobi2008/12/20 13:13Setting Up A Web Application With Jetty And Helma 1.xtobi2008/12/11 15:14Helma 1.6.3 Changelogzumbrunn2008/11/25 17:39Related Projectszumbrunn2008/10/31 22:22URL Rewriting With Jetty And Helma 1.xtobi2008/10/20 16:06HopRepltobi2008/10/15 15:31ModuleSystemKris Kowal2008/09/06 22:57Helma NGhannes2008/08/20 12:53on Helma 1.6.x and the scope of source code in "prototype" folders.breton2008/08/06 07:16Test PagePhilipp2008/08/01 16:09philippPhilipp2008/06/06 15:35Helma NG 0.2hannes2008/05/21 20:46Documentation Draftszumbrunn2008/05/15 16:53Object Reference Mapping (1:1 relation)zumbrunn2008/05/12 15:38Wiki Overview Text Draftzumbrunn2008/05/09 14:24Collection Mappinganton2008/05/08 19:59mariusmarius2008/05/07 20:14Helma Meeting Spring 2008marius2008/05/07 20:10matthiasmatthias2008/05/02 12:10Helma NG 0.1hannes2008/04/23 15:29antonanton2008/04/22 13:12Helma 2 import featureshannes2008/04/19 01:15Nice things in Djangohannes2008/04/16 15:59Helma 1.6.2 Changelogzumbrunn2008/04/14 12:50Axiom Stackhannes2008/04/04 11:25Continuationshannes2008/04/03 23:32RFC: Optional property type declarations for embedded dbmaks2008/04/03 05:29Server Migrationhannes2008/04/02 14:31Basic Scaffoldingmaks2008/01/25 05:49Additional Filename Conventionszumbrunn2008/01/22 17:51e4xd and jhino - experimental soft-coding scaffold using JOMPzumbrunn2008/01/22 17:16RFC: New JSON based DB for Helmamaks2008/01/21 23:59Comparison of JSAdapter and JOMPhannes2008/01/15 12:27TODOhannes2008/01/14 10:45Helma 1.6.1 Changeloghannes2008/01/11 09:40Testing Helma with jala.Testhannes2007/12/12 15:56Pluggable Rhino Debuggershannes2007/12/11 17:22Workspacephilmaker2007/11/19 08:11Helma AJAX Requestsphilmaker2007/11/19 06:02Helma in a Nutshellphilmaker2007/11/19 06:01HelmaSwarmhannes2007/11/16 19:35Update build script to Subversionhannes2007/10/11 15:50Parent related problems in Helma 1.6.0hannes2007/10/08 14:16Enhancements for response buffer handlinghannes2007/09/24 12:56HopObject Query Objecthannes2007/09/21 10:39Builder Applicationmaks2007/09/04 03:34HelmaLibzumbrunn2007/07/09 14:21Mocha Inheritancezumbrunn2007/07/08 18:50Helma 1.6.0 Changelogzumbrunn2007/06/30 18:53Rhino Bugs & Patcheshannes2007/06/28 15:03New HTTP-related Features in Helma 1.6hannes2007/06/15 20:46Upload Demohannes2007/06/05 21:46New Skin Features in Helma 1.6hannes2007/05/02 15:35JavaScript Template EngineLehni2007/04/22 07:23Alternative Lazy JavaScript Inheritanceluchkovsky2007/04/21 12:24Helma 1.5 skin rendering is brokenhannes2007/03/31 09:04Helma 2 Templates - hanneshannes2007/03/17 16:17Helma 1.5.0 Changeloghannes2007/02/23 14:47Helma 2 Templates - ORF.attobi2007/01/12 14:10Helma Logohannes2006/12/19 16:06E4Xhannes2006/11/29 10:37RhinoLoaderhannes2006/11/29 10:17Using Helma 2 as Libraryhannes2006/11/29 01:32Java 5 Concurrency Utilitieshannes2006/11/29 00:59aemkeiaemkei2006/11/27 12:18Helma Moduleshannes2006/11/24 14:55tobitobi2006/11/03 19:27JS-based implementation of snippets (aka subskins)tobi2006/11/03 19:22dev-nulltobi2006/11/03 19:21suggestion for helma user documentationtobi2006/11/03 19:21Helma 2 alpha 1hannes2006/10/24 15:14JavaScript Inheritance Sugar - LehniLehni2006/10/20 12:08Helma Project Bylawschl2006/10/11 01:59Helma 1 Compatibility Layerhannes2006/08/12 01:55JavaScript Inheritance Sugarhannes2006/07/28 11:33Html Processinghannes2006/07/25 11:29Helma 2 Templatestobi2006/06/26 15:08Request Path Mappinghannes2006/06/18 01:51Helma 1.5 Javascript Librarieszumbrunn2006/04/18 17:26Helma 2 Templates - juergLehni2006/03/19 04:54 [Less]

I am currently working on improving and extending Helma 1.x. This page serves as a public todo list summing up tasks that should be or could be done (but are no bugs) to improve Helma 1.x. HopObjectdeprecate either count() or size(), I'd prefer to ... [More] deprecate count()deprecate invalidate(id), as it can be done as get(id).invalidate()rename the magic properties (__id__, __parent__, ...). Some properties currently exist with one underscore in front (_property) as well as with two in front and two at the end (__property__). Some only use one syntax, some are case-sensitive, some others are not.move getById(id, proto) to app.getById(proto, id) or remove it as it is unrelated to the HopObject called on, leave Constructor.getById(id) as it is.rename getChildElement to onGetChildElement to reflect that it is an event handlermake getOrderedView() return something else. Currently it returns some object that is similar to a HopObject, but is not a HopObject. Some functions are missing, some throw an "unsupported exception". There should be something like a HopCollection, being extended by HopObject.some functions like getOrderedView() throw RuntimeExceptions when called on an incompatible (transient) HopObject, some others just return null. I propose to change all functions to throw exceptions, as one can check with isPersistent() before doing a call that might not be supported.Properties filesAs every other directory or file is configurable, the location of the db.properties file should be too. I'd suggest to add dpPropsFile.Scripting enginesImplement a configurable class shutter implementation for RhinoMove configuration properties only influencing a specific scripting engine to it's own properties file (i.e. have separated configurations). [Less]

Most activity in the wiki currently revolves around working drafts for additional documentation and around Helma NG with a newly added dedicated Helma NG Wiki space. Other important wiki pages are the lists of Related Projects and Sites using ... [More] Helma, to both of which you are welcome to add your own or other missing entries. Also helpful to find what you are looking for, may be the search page, the updates page, the tags cloud and the list of pages in the general wiki, which contains ideas, drafts and other miscellaneous bits and serves as an incubation space for new projects and documentation pages that may later be moved to their dedicated spaces. Don't hesitate to just add a new page if you have something to contribute and are not sure where otherwise to put it. List of the recent changes: namemodified bylast modifiedHelma Reference ErrataPhilipp2009/03/01 03:57Helma 1.7 wishlisthannes2009/02/19 12:21HOWTO improve Helma 1.xhannes2009/02/19 12:16Cronjobshannes2009/02/19 12:14Configuring Jetty in Helma 1.xhannes2009/02/19 11:54Pure JavaScript applicationshannes2009/02/19 10:40Many-to-many Relationshipsmaks2009/02/18 23:31helma.org redesignhannes2009/02/18 00:29Helma Roadmaphannes2009/02/17 23:20Helma and MySQLhannes2009/02/17 22:57Helma and log4jhannes2009/02/17 22:48Helma Logginghannes2009/02/17 22:43Cachinghannes2009/02/17 22:39Helma NG Wishlisthannes2009/02/17 20:16XML-RPC Samplehannes2009/02/17 20:14Minutes from the Helma Spring 2008 Meetinghannes2009/02/17 13:48Handler for rendered skinshannes2009/02/17 13:16Sites using Helmaanton2009/01/26 11:35Modules and Scopes in Helma NGhannes2009/01/25 19:48Rabbittobi2008/12/20 13:13Setting Up A Web Application With Jetty And Helma 1.xtobi2008/12/11 15:14Helma 1.6.3 Changelogzumbrunn2008/11/25 17:39Related Projectszumbrunn2008/10/31 22:22URL Rewriting With Jetty And Helma 1.xtobi2008/10/20 16:06HopRepltobi2008/10/15 15:31ModuleSystemKris Kowal2008/09/06 22:57Helma NGhannes2008/08/20 12:53on Helma 1.6.x and the scope of source code in "prototype" folders.breton2008/08/06 07:16Test PagePhilipp2008/08/01 16:09philippPhilipp2008/06/06 15:35Helma NG 0.2hannes2008/05/21 20:46Documentation Draftszumbrunn2008/05/15 16:53Object Reference Mapping (1:1 relation)zumbrunn2008/05/12 15:38Wiki Overview Text Draftzumbrunn2008/05/09 14:24Collection Mappinganton2008/05/08 19:59mariusmarius2008/05/07 20:14Helma Meeting Spring 2008marius2008/05/07 20:10matthiasmatthias2008/05/02 12:10Helma NG 0.1hannes2008/04/23 15:29antonanton2008/04/22 13:12Helma 2 import featureshannes2008/04/19 01:15Nice things in Djangohannes2008/04/16 15:59Helma 1.6.2 Changelogzumbrunn2008/04/14 12:50Axiom Stackhannes2008/04/04 11:25Continuationshannes2008/04/03 23:32RFC: Optional property type declarations for embedded dbmaks2008/04/03 05:29Server Migrationhannes2008/04/02 14:31Basic Scaffoldingmaks2008/01/25 05:49Additional Filename Conventionszumbrunn2008/01/22 17:51e4xd and jhino - experimental soft-coding scaffold using JOMPzumbrunn2008/01/22 17:16RFC: New JSON based DB for Helmamaks2008/01/21 23:59Comparison of JSAdapter and JOMPhannes2008/01/15 12:27TODOhannes2008/01/14 10:45Helma 1.6.1 Changeloghannes2008/01/11 09:40Testing Helma with jala.Testhannes2007/12/12 15:56Pluggable Rhino Debuggershannes2007/12/11 17:22Workspacephilmaker2007/11/19 08:11Helma AJAX Requestsphilmaker2007/11/19 06:02Helma in a Nutshellphilmaker2007/11/19 06:01HelmaSwarmhannes2007/11/16 19:35Update build script to Subversionhannes2007/10/11 15:50Parent related problems in Helma 1.6.0hannes2007/10/08 14:16Enhancements for response buffer handlinghannes2007/09/24 12:56HopObject Query Objecthannes2007/09/21 10:39Builder Applicationmaks2007/09/04 03:34HelmaLibzumbrunn2007/07/09 14:21Mocha Inheritancezumbrunn2007/07/08 18:50Helma 1.6.0 Changelogzumbrunn2007/06/30 18:53Rhino Bugs & Patcheshannes2007/06/28 15:03New HTTP-related Features in Helma 1.6hannes2007/06/15 20:46Upload Demohannes2007/06/05 21:46New Skin Features in Helma 1.6hannes2007/05/02 15:35JavaScript Template EngineLehni2007/04/22 07:23Alternative Lazy JavaScript Inheritanceluchkovsky2007/04/21 12:24Helma 1.5 skin rendering is brokenhannes2007/03/31 09:04Helma 2 Templates - hanneshannes2007/03/17 16:17Helma 1.5.0 Changeloghannes2007/02/23 14:47Helma 2 Templates - ORF.attobi2007/01/12 14:10Helma Logohannes2006/12/19 16:06E4Xhannes2006/11/29 10:37RhinoLoaderhannes2006/11/29 10:17Using Helma 2 as Libraryhannes2006/11/29 01:32Java 5 Concurrency Utilitieshannes2006/11/29 00:59aemkeiaemkei2006/11/27 12:18Helma Moduleshannes2006/11/24 14:55tobitobi2006/11/03 19:27JS-based implementation of snippets (aka subskins)tobi2006/11/03 19:22dev-nulltobi2006/11/03 19:21suggestion for helma user documentationtobi2006/11/03 19:21Helma 2 alpha 1hannes2006/10/24 15:14JavaScript Inheritance Sugar - LehniLehni2006/10/20 12:08Helma Project Bylawschl2006/10/11 01:59Helma 1 Compatibility Layerhannes2006/08/12 01:55JavaScript Inheritance Sugarhannes2006/07/28 11:33Html Processinghannes2006/07/25 11:29Helma 2 Templatestobi2006/06/26 15:08Request Path Mappinghannes2006/06/18 01:51Helma 1.5 Javascript Librarieszumbrunn2006/04/18 17:26Helma 2 Templates - juergLehni2006/03/19 04:54 [Less]

This is a wiki page intended for the collection of pending changes/additions to the reference guide. The reference guide for Helma 1.x is maintained using subversion and is automatically generated using the jsdoc toolkit. If you notice any errors ... [More] or omissions and do not have commit access to directly make the fix in subversion, please add a notice or a text recommendation here. Contents [hide]Missing:Pending Changes:in general Missing: I just looked after helma.Http.evalUrl and it isn't in the reference. multumesc, philipp. Pending Changes: _prototype, _name, __created__, __lastModified__, __fullname__, __hash__, __node__ HopObject properties are not documented: http://helma.zumbrunn.com/hopbot/2007-08-08 http://helma.zumbrunn.com/hopbot/2008-08-05HopObject.subnodeRelation is missing in the docs. It allows to dynamically adjust the .filter usually set in type.propertiesGlobal.path documentation code example is broken. Because path is not a real array, in that it is keyed on prototype names, Not integer indexes, therefore the code should be: for (var i in path) { res.writeln(path[i]); } in general All reference pages should include an index with links to all contained methods and properties, the way the HopObject page already does. [Less]