forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin" <>
Subject ToDo List
Date Sat, 19 Jul 2008 12:39:15 GMT
Hi All,

Just reviewing the todo list page, it looks like most of that is done or

I'd like to trim the list down, so I'll put the list here for review and
hopefully I'll get some comments. Apologies there are quite a few.

1. - [code]  Please see our Jira issue tracker for tasks to be done. Note
that the Todo list below is old. We need someone to move those tasks over to
the issue tracker. → open

Ok, first todo item says a lot, so it seems we are to move any outstanding
todos to the Issue Tracker - perhaps because its more prominent to those
that can help fix them. If we end up with any left then I'll do that.

2. - [code] Rework the menu generation system to make it more flexible. See
thread Fixing menus → open

I checked back to the 2005 thread, I say this is done.

3. - [code] Define an 'object model' for Forrest sites, in the form of a
Cocoon pipeline, that defines - The directory structure of a site - Site
metadata (what currently lives in skinconf.xml + gump.xml stuff) - Perhaps
site.xml metadata for pages? This info can then be made public to the
sitemap (via XMLFileModule attributes) and the stylesheets (through
document(cocoon:/...) calls or inlined with source XML). → open

>From what I understand of what is written here, this is done too.

4. - [code] Finalise the project-definition DTDs, like status.xml and
module.xml; try to come up with a common format with others on → NKB

Done ?


5. - [code] Finish the RSS feed for status.xml. Aggregate status.xml and
project.xml to have all needed project data. → NKB


6. - [docs] Add stylesheets to render the enhanced status.xml file contents.
→ open

Done to a point, there exists an issue on Jira to improve this I think in
terms of the icons, so this can go too.

7. - [code] In skinconf.xml, change 'disable-search' to 'enable-search'. →

Not applicable any more. Either you have a search element or you don't.

8. - [code] Enhance the initial forrest toolbar for Mozilla. See email
discussion draft forrest toolbar for Mozilla. → NKB


9. - [code] Fix things so docs can be edited in src/*, and have the changes
appear immediately in the webapp. Involves creating/using an InputModule for
passing '' and other properties to the sitemap, so we can avoid
the @skin@ hack, and a bit of hacking. There are some
@tokens@ in a forrest-site CSS file that also need some sort of in-place
modification. Perhaps a @token@-to-value Transformer could be the same
${variable}-to-value Transformer mentioned in the RT [3]. → open


10 - [code] Act on 'Entities in XML docs' RT. I can implement Stefano's
suggested solution quite easily, but is such limited functionality worth the
cost of introducing a proprietary ${variable} syntax? Maybe.. Best
short-term alternative seems to be using the XNI XInclude processor for
pre-validation inclusion. → open

Done ?

11. - [docs] A lot of the info on the website is outdated. → open

Yes it is. No need to state it, it's an ongoing process, folks will update
stuff as and when.

12. - [docs] Using metadata from site.xml, it would at least be possible to
indicate how old the doc is, and perhaps indicate its relevance from a small
controlled vocabulary. → open

Needs more explanation, we have a last published date, good enough?

13. - [design] Develop a mechanism for supporting legacy URLs. See email
discussion - redirects with static sites → open


14. - [code] Fix up and integrate the Forrest Maven plugin. → open

Not applicable any more ?


15. - [code] Ensure that PHP-like stuff can be embedded easily in Forrest
files and document it. → open

I think there are issues for PHP incorporation, not sure how much PHP
integration has evolved lately.

16. - [code] Continue the development of the Libre facility - replacement
for */book.xml → open

Not applicable any more ?

17. - [docs] Start a community doc where we list tools such as "code". →


18. - [code] Migrate to a decent schema language, primarily so that we can
use namespaces in XML docs, allowing things like XInclude, in-line metadata,
in-line SVG, Jelly snippets, or anything else users can make a Transformer
for. → open

Some done, whats left to do, we can transfer anything left to a Jira.

19. - [code] Streamline the process of adding support for new schemas.
Ideally we'd have an auto-download system, e.g. 'forrest-update docbook'
would fetch and install the Docbook DTDs, create catalog entries, sitemap
mods etc. → open

Needs further explanation, so maybe move to a Jira.

20. - [code] Make a CSS Generator and a stylesheet to serialize it to text.

More info needed, move to Jira ?

21. - [docs] Add a document about authoring in XML for beginners.. → open

Hmm, I think we document quite well what we need to, anything else, go
to another site for learning it. Wont do.

That’s my thoughts, any more?



View raw message