World: r3wp

All that long message before the code is the notes of the comments 
sent by the creator when commiting the code. So that other developers 
understand his work.

All the code is available from thhis URL.

http://trac.geekisp.com/rebgui/browser

And there are some widgets wo/. comments like http://trac.geekisp.com/rebgui/browser/widgets/bar.r

So,  I will think that trac is not stupid is actually very easy an 
useful.

I suspect it is just intimidating when you use it without reading 
the docs

Got this error again !  third time now, and this was a screen with 
2 fields, and a couple of buttons

** Where: into-widget
** Near: unless find [object! block!] type?/word get
** Press enter to quit...

stack overflow ...

Referencing Henriks message in Ann-Reply "I need a way to show a 
sub-layout" and my own from 26-jun-2006


This is another point that the way 'display works is sub-optimal: 

When building a gui we need 3 actions: layout, display, event-handling.
Having these 3 as distinct actions works well.

Having 1 action for layout and 1 other for display and start of event-handling 
works.

BUT having 1 action for layout AND display doesn't make sense. Because 
you can't build sub-layouts, and you are stuck with a displayed but 
non-functional window after this step.

That said, Henrik, have you tried ctx-rebgui/layout ?

Ingo, no I haven't. I looked through the 'display source, but could 
not find the context of the layout function. If this is right, then 
thanks. :-)

Ashley, is there a way we can halt the recursion before it causes 
a stack overflow?

I thought there was supposed to be a switch in display to allow you 
to construct a layout without viewing it.

If not, it should be easy to add.

] [

Sorry, AltMe became the active window when I was typing code elsewhere. 
 Better to shut it down. Bye.

Anton - today I consulted with Cyphre, and it is really how I thought 
about it - drop-list, and its inside/outside argument really allows 
you to have the drop-list to go beyond the border of parent app. 
The case is, that there is simply a bug, which Cyphre nearly fixed 
(hilite stopped working)

Ah, sorry, I interpreted your initial comment poorly. My apologies.

Anton - that is absolutly ok :-)

guys, I would like to open some UI look chat .... not much, but a 
bit.... Cyphre will look for me to do some slight improvements, e.g. 
to allow gradients for tabs, etc.

Is there anyone else who thinks, that rounded tabs do not work? As 
well as rounded buttons? While we tried to stay WinXP look compatible 
as much as possible, in some situations, rounded buttons do not work 
- try to change tour.r background color to any of darker colors - 
those tabs look more like a leak, than real shape - simply disturbing 
a bit. I have such reaction independently confirmed by Bobik, and 
my brother objected too, without telling him what to judge ....

another example, although not so significant, is buttons near each 
other, e.g. in grid - there is small one pixel "hole" in each corner 
- http://www.xidys.com/rebgui-grid.jpg

Cyphre style pack's tabs look nicer with gradients - http://www.xidys.com/cyphre-styles.jpg

if there would be too much chat about that, I will ask Cyphre to 
do some changes just for my purposes, as everyone of us will have 
slightly different pov UI wise ...

I've often wondered if anyone would copy the original NeXTStep style. 
I think it's wonderfully sober and boring (meant positively) to look 
at

http://www.levenez.com/NeXTSTEP/EquationBuilder.gif

ah, rather old look, isn't it? What about Amiga? :-)

the funny part is that everyone else kind of emulated NeXTStep, including 
Amiga.

I like the old look, because I think patterns and gradients distract 
from text too much

http://www.ohlfs.com/keith/self/next/Workspace.gif<-- 1988...

Yes, somewhere along the line GUIs went out of control. It's nice 
to have all those fancy graphics, but does it make you more productive 
?

Man, you're making me nostalgic.

http://home.get2net.dk/yock/gallery/grabs/pedewb.jpg<--- this is 
of course personal preference, but texture overload :-)

I prefer rounded buttons and tabs for the most part.  And square 
for all the conditions you mentioned Pekr.

hmm, we would have to have two buttons ...

well, as for RebGUI, it is now nearly feature complete (in regards 
to R2 capabilities/limitations), so I don't want to open whole lot 
of possible new issues. As for R3, I propose graphicians contest 
to bring mockupus of possible R3 UI design. E.g. today I read that 
SkyOS got its design from one famous company ...

There is something that people that are making frameworks on the 
web are doing that I actually really like.


They hide all the UI until your mouse is over it.  What I like about 
this is that it reduces the noise of buttons you know are there, 
like [Close], [Minimize], [Resize].  If all windows conform, and 
you can truly trust them all to allow you to do everything, then 
I think this will become the preferred state.

But it only works if the UI is 100% consistent.

We are going to offer this as an option in Quilt.

http://www.hmkdesign.dk/rebol/tab-view/docs/example.png

Something I did a while ago

the button bitmaps are available in the parent directory: http://www.hmkdesign.dk/rebol/tab-view/tab-images.r

Feel free to grab them.

Cool.  Nicely done.

Perhaps buttons need a "touch" flag so that the side that touches 
another button takes of the rounded edges.

of = off.

yes, or simply ability to define what each edge to edge/corner to 
be round or not.  Automatic would be great though.

Yeah, automatic should prob be default.

I think we should nail the functionality down before worrying too 
much about the cosmetics.  Stack overflows and other issues are far 
more important to users.

For me, function is beauty

And I gather Windows Vista is going to bring a whole new heap of 
problems trying to match their new GUI