| 29 | | * File related things need to be extracted in a separate module. They are dependent on Views. Views are the most dependent part of the application. So |
| 30 | | * view (app, book etc...) , layout, halos, hud, logics, boundcontrols, dialogs, menus utils and other things in messy should be separated in a module. |
| 31 | | * !FileMenu and !MenuItems in it should be extracted in a module, dependent on former. |
| 32 | | * The module should provide extensions for the !AppView. |
| 33 | | * .... (NOT FINISHED!!!) |
| | 29 | * File related things need to be extracted in a separate module. They are dependent on Views. Views are the most dependent part of the application. So view (app, book etc...) , layout, halos, hud, logics, boundcontrols, dialogs, menus utils and other things in messy should be separated in a module. |
| | 30 | * !FileMenu and !MenuItems in it should be extracted in a module, dependent on latter. |
| | 31 | * It should provide extensions for the View, in order to be loaded as a plugin. |
| | 32 | * The module => org.sophie2.main.view.file should contain: |
| | 33 | * !FileMenu, !MenuItems in the !FileMenu. |
| | 34 | * Dialogs are impossible to be separated from the view module and put in the File module since: |
| | 35 | * Logics invoke Dialgos |
| | 36 | * Logics and View are tightly connected - the correlation between Logics and View is two-directional. |
| | 37 | * File things should be dependent on View and NOT vice versa. |
| | 38 | * So if Dialogs are in the File module but the Logics are in the View module, invoking Dialogs from the Logics will need a dependency which is NOT appropriate. |
| | 39 | * Extension point for the !FileMenu in the !AppView will be added. |
| | 40 | * !FileMenu will be an extension created by a !FileMenuProvider. |
| | 41 | * !FileMenu will have an extension point for the !MenuItems |
| | 42 | * !MenuItems will be extension of the !FileMenu. |
| | 43 | * !MenuItemProviders should be implemented. |
