Thomas Guettler wrote:

Thomas Guettler wrote:

...

I would like to add some things to the PropertyManager:

1. mulitple selections should be a list of check-boxes. I don't like the ctrl-click method in the select-box.

2. Would be nice if each property has a second name, which is used for displaying it to the user. This is neccesarry if you have properties with umlauts.

Would be nice to have a new data type, too: dates

thomas

If you want to propose new features to Zope, this is not a good place because your ideas will just get lost in the shuffle. Go to the fishbowl on dev.zope.org and write it up and tell ppl about it on the zope-dev mailing list. Proposals are also infinitely more credible if the author is willing to do the implementation. Wish lists, although interesting, usually don't get very far without a lot of lobbying. Specifically, these PropertyManager proposals, although useful, point at an overall lack of flexibility in the system. Rather than "I want property type X", I might suggest an approach like "I want property sheets to have extensible types" might get farther. Zope 3 will most certainly be an opportunity to look at this completely fresh. It doesn't take a long look at the current PropertyManager code, to see that it needs an overhaul 8^). -Casey

From: "Dieter Maurer" <dieter@handshake.de>

Thomas Guettler writes:

...

1. mulitple selections should be a list of check-boxes. I don't like the ctrl-click method in the select-box.

Please make this an option, not the default!

I don't think it should be done at all. The ctrl-click method is a standardized way of multiple selections in list-boxes together with shift-click multiple selection. There is no way you can get the shift-click selection with checkboxes. That means that selecting all will need you to check every single box. Having checkboxes for multiple selection can be useful sometimes, but as a general option for properties it's not a good idea.

...

2. Would be nice if each property has a second name, which is used for displaying it to the user. This is neccesarry if you have properties with umlauts. Agreed.

And optional description (the explain the use of the properties).

Yes, properties need properties too. And they need security. And they validation. And when you do need these things, you might consider moving the properties to a Formulator form. It has these things.