mbrenn / datenmeister Goto Github PK

In Demo extent, boolean properties are shown as 'false'. After opening and closing Detailform, the property is shown as 'False'. Find out reason.

DatenMeister needs to have a general icon

Currently, no useful information is given in the save and load dialogs.

It should be supported that one extent or one element of an extent is copied by keeping all type information to another existing extent.
This is also required to implement a good export function.

In table view, the object shall be shown correctly, if from type 'IObject'.

The Factory for each extent shall be made MOF-compliant.

At the moment, it does not reflect typical Windows Application behavior

At the moment, no scrolling is shown

When an item has been changed, the table list view shall not scroll up to the first position.

This might not be the case at the moment, but I expect so. The scrolling shall stay at the same position

A strategy, how to create a report shall be defined.

Lists and collection shall be supported by each extent in a MOF compliant way.
This means, that an access to a list shall return an object offering an IList interface, but also the MOF related interfaces.

This interface shall be returned by default.

Information: For later versions, the list shall only be returned, if the corresponding type has a property with multiplication > 1

Use of ActivationContainer is recommended

Depending on type (edit, new, etc)

From the detail view, the user shall be able to open the detail view of a referenced property.
If the referenced property gets changed, the other window shall also be changed.

After having changed the responsibility for window creation from application to library, loading and saving does not work any more

It shall be possible, that an object can be assigned to another IObject without using references.
The object shall be included as an object at the xml-node.

At least for xml, this should be supported.

When a certain property is selected in list view and user pressed F2 key, the detail window shall popup and the selected property shall be preselected in the detail view.

This allows a very fast change of properties.

And create a new extent view, showing elements of the type

No form is shown

A new library needs to get created, which contains the necessary files for weblayout
The core itself should have less dependencies.

It shall be possible to list all extents in the main window.
At the moment, it is not necessary to import/include new extents.

The pool provider shall be used via ObjectActivation instance.

Perhabs, other classes can also be put into the Object Activation instance concept.

At the moment: Ugly!

At the moment by library

The tabs in the mainwindow and their definition shall be stored as an extent, so user can create new tabs, if he likes to do so.

Top improve touch friendliness