- edited description
Reorganize packages
Issue #27
resolved
Currently the packages are a bit unorganized in two ways:
- Different base packages: Model has ca.mcgill.cs.sel.ram, other stuff has ca.mcgill.sel.ram and the GUI has also ca.mcgill.ram. ca.mcgill.sel.ram should be the general base.
- In the GUI the packages sometimes don't make sense (in regards to their contents) and some contain too much stuff and should be split, e.g., views.
I propose the following structure:
- Base package: ca.mcgill.sel.ram
- The base package of model, edit should conform to the base package
- GUI base package: ca.mcgill.sel.ram.ui
- Split specific view things and general views/components
- ca.mcgill.sel.ram.ui.views.(structure|message|state) for Structural/Message/State View things
- each of these has handler, handler.impl
- ca.mcgill.sel.ram.ui.scenes for scenes (and handler, handler.impl subpackages)
- Alternative: ca.mcgill.sel.ram.ui.handler with subpackages in there
Comments (4)
-
reporter -
reporter The new message view UI will use the following structure, which fits better with what we have so far:
- ca.mcgill.sel.ram.ui.views.message
- ca.mcgill.sel.ram.ui.handler.message(.impl)
Then, in the base package (views or handler) general classes can be located.
-
reporter -
assigned issue to
- marked as major
-
assigned issue to
-
reporter - changed status to resolved
- Log in to comment