Re: GUI in one package or several child packages?

[Preben Randhol <randhol+valid_for_reply_from_news@pvv.org>]

On 2005-02-10, Jacob Sparre Andersen <sparre@nbi.dk> wrote:
> I have made it a habit to use GLADE for prototyping.  Once I have a
> part of the GUI looking about right, I try to organise it in sensible
> packages.  Things which seem to be reusable are named as child
> packages of GtkAda, while more specific parts are kept in packages
> related to the project.

Yes I also have done it this way so far...

> I find it hard to see any arguments for keeping the whole GUI in one
> package.  As far as I can see, there is nothing that makes the GUI
> part of a program sufficiently different from other parts of a
> program, to make it sensible to ignore the general rule of separating
> code out in units with well-defined (and minimal) interactions with
> the remainder of the program.

One drawback is of course the increased dependencies. I mean if going to
a screen for editing you might want to change menus of the main window
while when you go back to another function you want to change them
back...

Another problem is that one end up with:

List.gui
List.gui.callbacks
Edit.gui
Edit.gui.callbacks

etc...

I still think the child package model is better eventhough it generates
more work, but I'm not 100% sure...

Pr:ben