<<
"Make simple things simple, and complicated things possible"
>>
Good philosophy!
<<
If I can imagine changing View to follow that principle, I would favor
something like the following. If you write
view/options layout [... some widget specs...] [resize]
then ALL enclosed widgets would scale proportionally when the container
resizes. I'd add widget-by-widget attributes of
scalex
to mean fixed-height, scaling-width,
scaley
to mean fixed-width, scaling-height, and
noscale
>>
Excellent! I would vote for that functionality over any that I have heard so
far, unfortunately, that is not how it works. The resize flag simply allows
the window to resize, not any of the faces within the window. It does
however trigger the 'resize event which allows you to dynamically change the
size of the faces in the layout (or do anything else you may deem neccisarry
effectively enabling the resizeby example that you gave). Thanks to this
discussion, I am lit up with all kinds of wonderful ideas of how to create
dynamically resizing faces! Now as you can see, RT has fufilled half of your
philosophy, complex things are possible. Now just to get the the simple
things simple part...
Enjoy, my 0.8% of $2.50. ;-)
Ammon
> to mean just what it sounds like. Thus, for example, a vertical
> scrollbar
> would have SCALEY as an attribute to allow it to resize vertically but
> not
> change width, a horizontal scrollbar would have SCALEX, a thumbnail icon
> could have NOSCALE, etc...
>
> For any more complex scanarios, I'd put the monkey back on the
> programmer
> with something vaguely like
>
> view/options layout [... some widget specs ...] [resizeby function]
>
> where the offered function (by name or anonymous) would be invoked to
> handle the resizing, and would be able to use some simple interface to
> adjust the size of each component widget within the layout, so that a
> programmer wanting a more sophisticated layout-management strategy
> would have a way to implement it.
>
>
> Again, let me repeat that I'm not trying to play "duelling examples"
> here, but to ask the question "What could be done to make REBOL more
> attractive to users and developers who currently are not aware or
> interested?" I trust we all would like to see that result!
>
> -jn-
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
