currently all wxGUI modules are located within one package called
`gui_modules`. This was more or less sufficient in the early stage of
wxGUI development. As wxGUI code base was growing new modules has been
added. Some wxGUI components (eg. vdigit) are based on more modules
(vdigit.py, mapdip_vdigit.py, etc.).
As wxGUI code base is still growing and the new components are being
introduced (psmap, and now real i.class replacement) this structure is
becoming highly unsuitable and almost possible to manage.
At this stage I would like to propose more structured layout based on
several packages (core, gui_core, forms, lmgr or mapdisp) and non-core
sub-packages in `modules` package.
Please feel free to comment this proposal, better sooner than later. I
would like to start moving to the new package layout during next week
(in trunk). Later after some testing to introduce changes to `devbr6`
otherwise backporting bug-fixes will become almost impossible
(nightmare for wxGUI developers).
currently all wxGUI modules are located within one package called
`gui_modules`. This was more or less sufficient in the early stage of
wxGUI development. As wxGUI code base was growing new modules has been
added. Some wxGUI components (eg. vdigit) are based on more modules
(vdigit.py, mapdip_vdigit.py, etc.).
As wxGUI code base is still growing and the new components are being
introduced (psmap, and now real i.class replacement) this structure is
becoming highly unsuitable and almost possible to manage.
At this stage I would like to propose more structured layout based on
several packages (core, gui_core, forms, lmgr or mapdisp) and non-core
sub-packages in `modules` package.
Please feel free to comment this proposal, better sooner than later. I
would like to start moving to the new package layout during next week
(in trunk). Later after some testing to introduce changes to `devbr6`
otherwise backporting bug-fixes will become almost impossible
(nightmare for wxGUI developers).
At this stage I would like to propose more structured layout based on
several packages (core, gui_core, forms, lmgr or mapdisp) and non-core
sub-packages in `modules` package.
probably I would replace `modules` with something more appropriate.
`Modules` doesn't not mean python modules in this sense. What about
`components` or ...?
+1 from me too. `gui_modules` could really do with some restructuring.
Markus M
Best regards
Soeren
2011/11/9 Martin Landa <landa.martin@gmail.com>:
Hi all,
currently all wxGUI modules are located within one package called
`gui_modules`. This was more or less sufficient in the early stage of
wxGUI development. As wxGUI code base was growing new modules has been
added. Some wxGUI components (eg. vdigit) are based on more modules
(vdigit.py, mapdip_vdigit.py, etc.).
As wxGUI code base is still growing and the new components are being
introduced (psmap, and now real i.class replacement) this structure is
becoming highly unsuitable and almost possible to manage.
At this stage I would like to propose more structured layout based on
several packages (core, gui_core, forms, lmgr or mapdisp) and non-core
sub-packages in `modules` package.
Please feel free to comment this proposal, better sooner than later. I
would like to start moving to the new package layout during next week
(in trunk). Later after some testing to introduce changes to `devbr6`
otherwise backporting bug-fixes will become almost impossible
(nightmare for wxGUI developers).
At this stage I would like to propose more structured layout based on
several packages (core, gui_core, forms, lmgr or mapdisp) and non-core
sub-packages in `modules` package.
probably I would replace `modules` with something more appropriate.
`Modules` doesn't not mean python modules in this sense. What about
`components` or ...?
Why not keep the name `gui_modules`? There would not be regular python
modules, but gui-specific modules (ps.map interface, map calculator,
georectifier, v.clean interface, import guis etc).
2011/11/10 Markus Metz <markus.metz.giswork@googlemail.com>:
probably I would replace `modules` with something more appropriate.
`Modules` doesn't not mean python modules in this sense. What about
`components` or ...?
Why not keep the name `gui_modules`? There would not be regular python
modules, but gui-specific modules (ps.map interface, map calculator,
georectifier, v.clean interface, import guis etc).
I think it's not important to stress word `gui` in the `modules` name.
It's located in `*gui*/wxpython`, I think it's quite clear that they
are the gui modules. There are other packages with gui modules like
`lmgr` or `mapdisp` which are related to the core component of the
wxGUI. The `modules` should stress that there are non-core gui modules
formed as packages. These packages (eg. `vdigit`) implements given
wxGUI component like vector digitizer or georectifier. That was the
main reason why I suggested `components` or something similar as a
name for this directory (or package).