TODOAlso see Helma roadmap. Helma 1.7.0
Gobi
|
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 2007/09/28 06:43Hannes, the browser extension for helma development sounds very interesting! Would you be able to give any more info about it? or is there code somewhere for others to look at / hack on? :-)
#2 by zumbrunn at 2007/09/28 12:47Hi mks, I was going to dive into that, either starting from scratch or as a plug-in to firebug. The first step would be to collect ideas for the features such an extension could have.
One thing I've thought about the last few days was to leverage the enhancements Hannes outlined here: http://dev.helma.org/wiki/Enhancements+for+response+buffer+handling/ in order to collect debug info in a client-side javascript objects data structure and use the browser extension to visualize that info.
Another possible feature (possibly related) would be to let the browser extension display which parts of the page/source were generated by which skins/macros etc. Kind of like a stack trace for page elements.