here's a list of (missing) features or things that should change in antville as a result of an evening in a "gastgarten" where hns and i talked about the rough "roadmap" towards antville 1.0. i hope i got everything right and didn't forget something, and sorry for not posting it sooner. the names in brackets indicate those responsible for implementing.

• Names of DB-Columns/Tables will be prefixed (or renamed to avoid usage of reserved names), plus adding SQL-scripts for other databases (at least oracle) [robert]
• the content of a story (which is now stored in separate columns, "TITLE" and "TEXT") will be stored as XML in just *one* column in the database. the reason is that stories can be "extended" with new parts (eg. lead-text, abstract, link ...) by simply modifying the form for creating a new story (input-tags could be named ie. "content:title"). eventually the story-table in database is extended with a single column containing the plain text of the whole story-content for keyword-search [hns]
• the language of system-messages changes according to system-language or weblog-language. all system-messages are basically skins that are defined in separate language-files (one for each) and can be reached at app.data[language-code]. this is already in CVS, for more see this posting.
• antclick will include McCoi as database instead of HSQLdb [hns]
• antville-setup: antville will provide a browser-based setup, meaning that parameters (like enabling/disabling auto-cleanup, language-settings, directories etc.) will be changeable without having to fiddle around in app.properties [robert, already in process].
• enable/disable posting of comments for each story
• two new macros: one for embedding the recent n stories located in a topic, and the other one for embedding a story/poll with a given id. with these macros users can customize the frontpage of their weblog.
• navigation issues: see hns's proposal for details

plus some ideas that could be part of version 1.0, but 'til now are not more than brief concepts:

• theme-support: every owner/admin of a weblog can export the design (meaning skins and those images referenced in skins) into a "theme", which then can be downloaded and imported by others. importing themes will support "theme-preview" (meaning that one can safely test a theme within the own weblog).
• integration of PARSS-functionality in antville: the idea behind is that users should be able to subscribe RSS-feeds which are displayed as "simple weblogs" in antville. from there one can easily use an RSS-item as basis for a new post in a weblog. this is still subject to discuss (tobi and hns can tell a lot more about that).

all of the above features are still open to discussion. and of course everybody is welcome to contribute (ideas/code).

just to know if it still makes sense to contribute: which of the features marked with a name in bracktes are in progress, already (except those where it's stated)?

how hard is it to allow blanks, underlines etc. in username?