parente
commented
14 years ago Initial version going. The major missing feature is a way to initially define a schema. The raw text editor box is pretty rough. I've been thinking about piggybacking on the collection editor to draft a schema by manipulating the columns of the grid. Adding a column, removing a column, and setting column properties can translate into basic properties for a schema.
Things like objects and arrays are not easy to define or edit in the collection editor. Right now, I'm not even sure what will happen. Maybe it appears as JSON? These need work.
We need to add a filter option to the collection editor to limit what's shown to items that match a query. Gary had this, but I haven't implemented it yet in the catalog widgets.
A delete option next to the name of a collection the db info tab would be a nice shortcut.
I'm working on this, but wanted to doc it. The uow.ui.DatabaseEditor will be a two-view widget with 1) database and 2) collection views. The database view will show all collections with controls to edit properties across them (e.g., Gary's access mode editor with the checkboxes). The collection view will show the properties of a single collection with editors for its specific properties: grid editor for data rows, access modes per role editor (same thing as the mode editor from Gary, but with a simpler UI for a single collection), and schema wizard.