as defined/proposed here? a short overview/approximate time plan would be nice.

that there are other views that Halvar should/will provide beyond the object tree. That's Views on prototypes, db mappings, code etc. Any thoughts about that?

At the last meeting we came up with a list of 3 different views I think, one of which was the object tree. Can't remember (exactly) what the other two were. (I'm searching for the pictures I took from the flipchart, will post them as soon as i find them.)

static view onto the object graph works.

what's next?

• xmlrpc-trans XML-RPC based object information transfer (status: hns will add functionality to helma core - when?).
• live-view Making the view live. How? Approach 1: poll & sync change history. Approach 2: poll & sync currently displayed objects (usually ~ n00?). Appproach 3: subscribe change listener (PubSub), get notified via XML-RPC - potential problem: firewalls. Experiments will have to be made.
• editable-views Making the views editable.
• prototype-tree Making prototype information (sources of actions, functions, skins available via introspection) available.
• hopshell-integration Integration of the HopShell (rewrite of the REBOL-based client component) and integration into halvar (scratchpad!).
• Long-term: plug-in integration into Java editor (jEdit?) or development environment (IBM Eclipse?).