The Hemi Framework project page was updated to include the Hemi_3.0.2.zip and Hemi_3.0.2_build.zip distributions, as well as a little more content.
The examples section still needs to be fleshed out. Rather than use static examples, I'm thinking of using the included unit-tests to drive the examples, and fixing up the Framework Designer for better anonymous use. The Framework Designer includes builders, with example implementations, for DWAC projects, tasks, components, fragments, templates, a runtime container, and pseudo-debug linkage to the Framework Profiler. I like the experience of opening one of the in-page editors and, for example, making a new task-list with selectable feature examples, and then being able to run it right there on the page, than making static examples of various combinations.
I also think the Framework Designer and Distributed Web Application Components (DWAC) features fit very well with Net Books and OS's like Chromium because authenticated and authorized users can create new Hemi facets (components, templates, fragments, tasks), projects, or deployments in the browser. These features would also work well in environments where Web pages with multiple client-side frameworks, and their corresponding widgets and tools, could be instrumented, updated, and deployed in-page and on-demand while being compliant to security policies and, if desired, released by a workflow.
[ Blog Content is Copyright by the indicated owner. ]