History of ReleaseThree
Version 3
This is a work in progress and contains only proposals for new features
Add new features if you think they would benefit the bitweaver
Features proposed here are not guaranteed to make it to any release
Add new features if you think they would benefit the bitweaver
Features proposed here are not guaranteed to make it to any release
Proposed Features
Standardise User Interfaces
Give all content has standard views/actions, and allow other packages to extend these views/actionsExample views
- View
- Edit
- List
- View XML
- List XML
- Map Overview
Standardise Content Addressing
Biased on the standard and extended views/actions allow content to refer to content in another package in a standard manor that takes into account the base URLPortal Type Pages
Allow pages to be created either (nominally) as the start page or as the user page that:- Can contain blocks that can be easily arranged (and constrained)
- The blocks can be drawn from any package
Custom blocks can be created and passed though the smarty parser
Liberty Service Enhancements
Enhance Liberty Services so that:- Packages can call functions which return data
- Packages can define on a per-content bias what services are shown
- Services can offer hooks to other services
- Services of the same type can be used in a standard manner
In Place Edit
Allow any output generated by the Liberty parsers to be edited in place.Links
http://tool-man.org/examples/edit-in-place.htmlGreater JavaScript/XML/AJAX support
Put in the foundations to bitweaver for Javascript, AJAX, and JSON support at the content level.- Support for proper parsing of content, title, data, and other data to an XML or JavaScript compatable form.
HTTP Content Contract Complience
Make bitweaver behave like good web content- Set the HTTP Last-Modified header to the date the content was last changed
- For lists this could be the latest overall time