Jørn Wildt

How would you solve the problem that albums have different numbers of tracks? I'd like to add fields for Tracknr, Title, length, and a link for the lyrics.

That's not going to be possible anywhere in the near feature. But yes it would be really nice to be able to say:

I got one publication type with an associated list of other publication types - like a header and a table. When I create the header the table should be empty. When I delete the header I delete all items in the table. And I may insert elements in the table.

Hey - that's what my company does for a living (Maconomy - a Danish ERP system - www.maconomy.com). Maybe I can beat myself ... duh?

So in your case you have to use the html editor for the tracks - for instance with a list.

But isn't that exactly what the field-editor in the administration does?

Yes, but that is a hardcoded feature. The GUI framework can handle it, but the database model is definitely not able to do it in general for any pub. type.

This would be a great feature though I can understand that it will probably for a later release of the product. Once this is implemented though, we will have a Postnuke module for creating and maintaining the database structure as well as the user interface to interact with it. That is powerful stuff.

During the day, I am a programmer building applications on top of relational databases. So in my night life of building web sites, a tool like Pagesetter within the Postnuke structure is very appealing to me.

In the past, I have used a script called GenericDB (http://www.genericdb.com/) to handle the creation of a dynamic user interface over relational tables. It is not part of Postnuke though. What I like about Pagesetter is that, being a Postnuke module, it is administered through the web. This script uses config files.

Anyway, to echo other recent comments, Pagesetter is great and I will be building publication types and testing it. Thank you for a wonderful 1.0 version of an incredibly useful module with good documentation. I am excited to be part of the Pagesetter user base.

Same history here - got tired of writing modules from scratch for all the simple stuff.

Where I work we have a proprietary language for constructing relations+GUI in a way that lets you focus on the bussiness model instead of all the low level techie stuff. It is something like that which is needed for a CMS framework.