Every repository with this icon (
) is private.
Every repository with this icon (
) is public.
| Description: | Helma NG is a JavaScript runtime and shell based on Rhino providing a CommonJS conformant module library and web application framework. edit |
-
So we're going to start using github's issue tracking system. This means we need to bring over open issues from trac. We might want to do a shakeout and reexamine or reformulate existing issues along the way.
Here's a full list of issues on the Helma trac:
https://dev.helma.org/trac/helma/report/6And of course, keep those new issues coming.
Comments
-
0 votes
0 comments Created 3 months ago by hnsImplement test suite for helma.webapp moduletestingxWe really need a test suite for the helma webapp module and related submodules. Two possible approaches that come to mind: Either implement mock objects, or launch a httpserver on localhost.
Comments
-
Add tests for storage modules. Ideally, the same tests should work with any store implementation by simply plugging in the matching setup code.
Comments
-
0 votes
3 comments Created 3 months ago by hnsSupport for Jetty continuations (long polling) in helma.webapp0.5xAdd support for long polling requests in helma.webapp using Jetty 6 continuations.
Comments
Working implementation of long polling using Jetty's ContinuationSupport:
exports.poll = function(req) { var session = req.session.data; if (session.message == null) { session.c = ContinuationSupport.getContinuation(req.servletRequest, lock); session.c.suspend(30000); } var message = session.message || ""; session.message = null; return new /*JSON*/Response(message); } exports.ping = function(req) { var session = req.session.data; session.message = req.params.message; if (session.c) { session.c.resume(); session.c = null; } return new Response(); }Simon Oberhammer wrote a full helma-ng chat application using long-polling XHR requests:
-
The Helma NG README file should be rewritten to be more concise. Currently, it's a whole getting started/documentation kind of README. Instead, it should provide an overview and links to the relevant places and wiki pages.
Also, writing the file in Markdown might be useful. (I already did that for the current version on the NG wiki.)
Comments
-
Implement a package manager compatible wiht narwhal/tusk packages and repositories.
Comments
-
After the good experience with HTTP parameter and file upload parsing, I'm planning to rewrite the skin/template parser in JS as well.
Comments
-
0 votes
0 comments Created about 1 month ago by hnsAdd stream-factory parameter to file upload0.5xWe now have file uploads working, but uploads are always stored in memory. For best flexibility, the parseFileUpload() function should take an optional stream-factory function that can be invoked to get a stream to write the upload to. Actually, the function should return a custom stream-like object that also supports a close() method that returns the value to store in the parameter map.
As example, some useful patterns could be:
- an object whose write method writes to a /tmp file and whose close method returns the path of that file
- an object whose write method writes to an app specific file and whose close method return the path of that file
- an object whose write method writes to a memory buffer and whose close method returns that memory buffer as ByteArray or ByteString
Comments
-
0 votes
1 comment Created about 1 month ago by hns0.5xUpdate support for module meta objectcommonjsxhttp://wiki.commonjs.org/wiki/Modules/Meta
New features not supported so far:
- module.uri
- require.main as the main module object
- require.paths
We also may want to implement the module.resource() feature suggested on the mailing list
Comments
-
Helma NG makes some use of symbolic links which makes the demo app break on windows:
- storage and jsdoc apps are linked into the main demo app
- test suite is linked into modules
Comments
-
- -c, --charset or -E, --encoding
Comments
