Codename 'Nelso'. ;-) This is the first release supporting PostgreSQL for
storing forms data, effectively working equally well with all db backends,
that are currently supported by Trac itself.
Another big step towards a stable plugin. Thanks to all the kind people,
who helped with their contributions in many ways. It was another rewarding
experience to find the kinks and iron them out.
Now everybody enjoy the new Trac power under the hood.

This is just a small improvement to the interpreter. I feel that this could
be extended towards support for a full set of arithmetical operations, not
just sums. But it's already impressive to see current possibilities.

Yes, it is: Don't try to re-invent the Trac db cursor but just go and use the
native one, and i.e. MySQL/PostgreSQL compatibility comes for free by itself.

SQL rewrite details

introduce native Trac db type selector

drop DBCursor class with a lot of proprietary, unused special methods

remove 'DROP' SQL statements before dropping entire tables anyway

separate index creation SQL statements obsoleted and common suffix
for Trac db indexes to new TracForms indexes created automagicly
using db_connector.to_sql()

Thanks to osimons, who made this finally clear to me and again encoraged me
to do things in a cleaner fashion. Thanks to rblank for valuable hints on
proper use of Trac db cursors. And many thanks to Nelso G. Jost for
patiently testing published code as well as many more private iterations
of code changes in Trac environments using the PostgreSQL db connector.

This is by no means an atomic changeset but a huge, crazy code clash.
Both macros had rather different approaches regarding class definitions forCSS styles, so I had to partially change core logic to allow the creation of
some WikiCalendar specific HTML tags. While the CSS changes are not final,
the first goal of a regression-free product is reached, or at least close
enough for the visual presentation of both macros.

Short summary of changes:

include full embedded macro documentation for WikiCalendar

use 3-section-navigation from WikiTicketCalendar with both calendars now

combine CSS style definitions

remove dedicated subfolder 'css' from htdocs - too much for just on file