Is anybody else thinking that it would be nice to have a simple search text box on every page instead of having to go to the search page in order to enter a search term? Well, as is so often the case, the only reason why this isn't so already is that I (having implemented the search feature) didn't know where and how to place it.

So if you suffer from the current click-to-search situation like I do, please step forward and let us know where you think this box should go and what it should look like!

this is a short note to the people who are flooding the image pool of this project weblog:

1. this project weblog is about discussing the antville weblog tool.
2. you can upload images to your own antville weblog, too (if you don't have one, simply create one).
3. i deleted your images here and won't hesitate to repeat this if the flooding should start again.

best regards, tobi

this is what i get. have i missed something? is there a new library i need?

java.lang.NoClassDefFoundError: javax/xml/parsers/ParserConfigurationException at helma.objectmodel.dom.IDGenParser.getIDGenerator(IDGenParser.java:16) at helma.objectmodel.db.XmlDatabase.getIDGenerator(XmlDatabase.java:47) at helma.objectmodel.db.NodeManager.initDb(NodeManager.java:86) at helma.objectmodel.db.NodeManager.(NodeManager.java:71) at helma.framework.core.Application.init(Application.java:269) at helma.main.ApplicationManager.start(ApplicationManager.java:79) at helma.main.ApplicationManager.startAll(ApplicationManager.java:129) at helma.main.Server.run(Server.java:252) at java.lang.Thread.run(Thread.java:496)

a part of my job includes the reworking of a big institutional website. the site is based on a way too complex and too expensive cough knowledge management system. i'm thinking of gradually replacing it by antville and helma. my basic idea is to build a website that works on two levels. one is the chronologically ordered frontpage (weblog) and the other is a well structured archive (the actual site).

here is a list of the features i would like to add:

1. the most important and most tricky one would be virtual directories, i.e. a way to assign arbitrary paths to every story. the main task is probably the development of a good gui and macros for breadcrumb navigation, the site outline etc.

2. i would like to define who is allowed to set stories online and assign paths to them. for example, contributors can submit stories and they remain offline till the content managers reviews them.

3. there was some talk here about a macro to include stories. this would be cool to add editable content to the templates.

4. multiple templates would be cool. i suppose one for the frontpage (with calendar and recent mods) and a simple one for the rest of the site should do.

i guess the last two points are also interesting for regular weblogs whereas the first two aspects clearly go further.

is the code for the structured content on helma.org available and can it be merged with antville? is anyone else interested in these features?

the main branch of the antville cvs repository now contains a merged version including the changes i developed so far in the "devjamtobi" branch.

i hope everything is still working... :)

what do you think about adding another optional attribute to the link macro to specify who is allowed to see the link? it would be cool to have links for contributors or admins only while regular users see the link text or nothing.

Two days ago, Matt Griffith has come up with the smart idea of using the HTML link element to point to a site's RSS feed from the site itself - thus allowing automatic discovery of RSS feeds.

By adding a line like this: <link rel="alternate" type="text/xml" title="XML" href="yoursite.antville.org" /> a site would be providing metadata as to the location of its feed - and this would allow newsreaders, browsers and search engines to automatically locate the feed. ...o'reilly network