RE: [Pythoncard-users] moving menubar and getting rid of stack?

> From: Andy Todd
>
> I fully agree with moving the menu, but should it be associated with the
> background, or with the window?

Background in the framework is basically a Window; in wxPython terms it is a
wxFrame that contains a wxPanel. The list of 'components' could be a
separate entity such as a Panel or Layout or Group or Box or something else
that can't have a menubar, statusbar, scrollbars, etc. Even if we decide on
a different organization, we may have to wait a few releases before the
change can be implemented given the state of the framework.

> A window is the major component of an application (but it can have more
> than one), and an application must have at least one. All of the GUI
> toolkits that I have used have associated menus with the window rather
> than the background, but we don't have to stick with that metaphor if we
> don't want to.

As mentioned earlier, we have been doing Single Document Interface (SDI) so
each window can have a menu or not. worldclock doesn't have a menu. I don't
know how this will translate to the Mac. The Mac only has one menubar for an
application. I expect that once we have a wxPython Mac port we're going to
have to work through a variety of design and GUI issues.

> The separation of the window from the background is quite a powerful
> 'feature'. One of the neat things you can do in Oracle forms is
> dynamically/programatically swap the canvases (backgrounds in our
> terminology) within a window. This allows some pretty fancy layout - but
> then again may be too complicated for our kind of applications. Its a
> feature that I have used in the past, but I don't have a sample
> application in mind which would need it - yet.

Yes, this is a bit more like HyperCard. This still feels like an app that
should be built on top of the framework and not the framework itself. What
do other people think?

ka