should database (application) properties go in Designer??
We'll be adding some new ones, so we'll need more room to complicate the issue further.
Historically, they've been in the selection hierarchy of any infobox. Changes are immediate, and not batched in a transaction like form or view or any other design element editor.
With the first release of Designer in Eclipse, we'll have a mix of infoboxes and property panes (unless of course users decide they'd rather wait for us to rewrite all the infoboxes before releasing it...)
- is it ok to remove database properties from the infobox selection hierarchy in Designer (where infoboxes remain)?
- is it ok to have to click on the database header in the bookmarks or make another gesture to get to database properties?
thank you :-)