RDFBase 
| resources: | Home Mailing List Installation Source Code Browse Source Bugs All Open Bugs Screenshots |
|---|
RDFBase Roadmap
This is a first draft roadmap or to-do-list.
The steps mentioned below is what I personally think will be the important first steps for us to do in this project.
I tried to keep those first step as simple as I could because I'm not quite sure how much help the project will get
nd I'm not sure how much time and resources I will be able to put in the project myself.
All roadmap issues have bug numbers assigned, so it's easy to track comments on them.
Feel free to comment on bugs and open new ones if needed!
Please send your wishes what the application should do and what to put into this list either to
me or our mailing list
What we have already done:
- [bug 253] Create a base XUL window (with a draft <tree> in it), with some (dummy?) menus, and hook the app into Mozilla's "Tasks" menu using an overlay. Create the needed (basic) skin and locale directories, hook up an (empty?) JS file to rdfbase.xul.
- [bug 3326] Convert from old tree widget to new "outliner" tree widget.
- [bug 254]
Implement and hook up JavaScript function for loading a simple RDF file (the default profile's panels.rdf
as a reference for starting) into our <tree>.
The RDF file should contain one <RDF:Seq> which lists our records (table rows) in its <RDF:li resource="urn:xxx"/> children. Some <RDF:Description about="urn:xxx"> tags beside the Seq element then contain other tags describing the fields (columns) of our "database" tables.
This format is what we should support in the first step to getbasic functions working. - [bug 255] Write JavaScript function for saving this simple database table again into a valid RDF file.
- [bug 256] Enable us to add/change/delete records of our table.
- [bug 257] Give us the ability to export/import from/to simple tab-separated text files.
- Let's get more complex!
[bug 258] Give us access to other elements than <RDF:Seq>, [bug 259] make a tree view of the datasource in the loaded file, icluding nested lists (<Seq>s etc.) - Include additional functionality (whatever that may be, please help us with your ideas!)
- Should we be able to access some information via a special protocol (using ProtoZilla)? What information should that be? How should it be accessible (URI syntax)? What should the protocol name be? Where would it be useful?
- Who can help to do all those steps?