Features going to be implemented and progress.
- Nodes Manager
- Tabbed interface
- Basic facilities
- Advanced functions (context menus, close buttons, icons …)
- Node viewer
- Comments viewer
- Attachments viewer
- Node editor
- Nodes search & filtering
- Taxonomies tree
- Taxonomies editing
- Nodes listing
- Comments listing
- Archive based listing
- Tabbed interface
- Users and access control
- Modules management
- Block management
- Menu management
- Aggregator
- Remote preferences editor (using remote configuration API)
- Local preferences (Drupman's preferences)
- Log viewer
- Client side logs
- Server side logs
Road Map
Implement Drupal remote Form Renderer
One of the core components of Drupal Manager is the Form Renderer. This component can render a form by request form data (compatible with Drupal Forms API data) from the server and combine it with a XBL template (the template will have a simple format with XUL notation and attach points). All the processes are performed using JavaScript and DOM. There’s (maybe) another approach of using Mozilla templates and RDF data sources, but I found this approach is too complicated and thus not feasible. The Form Renderer also take care of how to send collected data (in Forms API compatible format) to the server and parse the response (validation errors, failure notices, etc ..). This component in general will “ajaxify” Drupal forms and provide a method for remote rendering those forms.
The corressponding part of the FormRenderer on the server is an API that allows developers to combine Drupal forms into a single root tree.
Remote preferences editor
Refine nodes manager
Tabbed interface facilities