french-paragon / aline Goto Github PK

At this point, we have this strange extension of Qt inheritance system, where subitems can be juste subitems of a main item, or managed in other meaningfull ways.

We need a proper function to deregister subitems, while also having classes which use subitems more tightly to be able to react appropriately when the user request to remove a subitem.

Options can be:

• to have a virtual method that subclasses of editable items can re-implement to properly manage special subitems.
• To have a notion of strong subitems, which are managed by the item in a special way and cannot be removed by a generic public method (deregistration function for any subitem can then be made private).
• other?

Instead of having to manually manage the links between items, someone could just use the reference and it would automatically take care of everything when a string is assigned to the reference.

Generating context actions like dynamic menus and toolbars for editable items is hard to do automatically.

We need to add, in Aline directly, some kind of manager class that can be queried and configured to do the job.

Ideally, this addition should leave the default behavior untouched.

At the moment, there is a function to edit an item, but no returned reference to the editor, which is problematic for actions who want more interactions with the editor for specific purposes.

There is a strange problem that cause a segfault when an app using Aline close -> this needs to be investigated and solved.

Doing everything automatically poses a lot of issues. While it is convenient, it also needs to be configurable.

Thus, a way to provided dedicated functions for conversions to and from Json is required.

In an ideal world the solution should:

• not require the developers of applications and modules to register their functions
• not require to implement anything in the editable item class itself (albeit it might be possible we have to implement something in the classes that needs a custom converter).
• not change the interface of the editable items (we do not want to give json or any other format a preferential treatment).

Currently, it looks like the child class functions have to ensure subitems have uniq refs!