[Pythoncard-users] FW: are all your layouts fixed?

[Kevin A. <al...@se...>]

name and address withheld on this one...

ka
---
> I use the Microsoft standard widgets, which have some measure of
> flexibility, but not for re-sizing dialogs, fonts etc. A user can easily
> create super-ugly schemes. I do not provide for any re-sizing of any
> dialogs, alert boxes, property sheets, etc. And I assume "normal" type
> sizes. I have never ever had any complaint about the inflexibility of my
> UI designs, and I have a reputation for elegant and usable UIs.
>
> If stretch-O-matic displays are required for the current genre of
> xxnix/xxnux UI designs, you have my deepest sympathies. I just can't
> stand the thought of burning development cycles on stretch-O-matic UIs.
> Sorry if that seems harsh or heartless, but in the real world, with
> "ordinary people" as users, stretch-O-matic is superfluous. No one
> cares.

I want to support some form of sizers in PythonCard, I just don't know what
that will be yet, basically I'm relying on the GUI toolkit underneath
PythonCard to do the hard work, my issue is mostly in presenting a better
config to setting up the required calls and then let the user beware.

My backup plan since we're using resources is to just let people define one
or more layouts and then have the appropriate layout selected automatically
when the app starts up based on platform (win32, mac, linux, etc.). This can
also deal with language and we can even support the notion of a user
preferred layout style, so their preferred layout gets precedence. The
interesting part is that if the alternative resource say for Unix said use
sizers instead of fixed layout, then that would happen automatically as
well. This is pretty easy to do because we aren't sticking layout in the
source code. I'm so glad I learned my lesson from the Mac about separating
layout and code.

ka