World: r3wp

in photoshop, its like using the eraser to remove parts of a layer 
and reveal the bg. 


 what you say, looks more like adding a layer with a hole in it.  
 Do I understand your idea properly?

is that more obvious?

maxim thank you for the head hache :P

Pekr, from specs: "This might be a problem for VID, because we use 
only simple text for UI styles. Will we have to switch to rich-text 
instead, to fulfill the needs?" - it should not be a problem since 
all text in R3 GUI is rich text.

OK .... I put in some content toward accelerator keys into docs ...

What happened to the dedicated R3 gui team that was going to finish 
R3 GUI ?  Did they get side tracked or are they still working on 
it?

we are finishing a product for shipping.

the next project must use R3 and the GUI, so the work starts there 
again

this looks like an interesting GUI http://10gui.com/video/

yes, Amiga sliding screens from 1985, just horizontally, not vertically 
:-)

This is what I find pleasantly looking UI - http://www.vasanth.in/content/binary/FutureLotus Notes.jpg

Maybe Lotus notes is looking good now, Maybe.... 

But I had so many bad experiences with that crappy app, in the past.
No respect of the GUI santards. (F5 to quit).
No drag and drop.
Lof of useless confirmation boxes.
Useful actions hidden in deepest menus I ever seen.
etc...
It was a pain in the ass just to write a simple e-mail.

And slow, so slow

Steeve - yes, I agree :-) I was referring jut to look of the UI :-)

Heh ... lotusnotes looks like the way my application looks now ... 
three columns with a central tabbed view

One problem with tabbed views is that you can only see one tab at 
a time ... so if you have multiple screens, you can't use them.

E.g. browsers solve this by allowing to open tabs in their own windows 
and putting windows back into tabs.

hmm... the underline stroke in R3 rich text is not shadowed.

Christian .. good point ...

Offer users the choice

Hopefully the important work has started - http://www.rebol.com/r3/docs/view/graphics-ext.html

That part is pretty important, yes.

Well, it will allow Cyphre (or others) to work on View kernel. But 
as for VID, the work could continue in theory even without the above 
mentioned work?

As for VID, we probably need Carl's input too, to know what he has 
in mind for some concepts (layers for e.g.), but the hostkit is imo 
more important, so I think that we should not disturb him right now 
:-)

yes, I hope I can continue as soon as this other project is done.

No news is bad news?

it's moving. :-)

What's that mean?

... it means, that start of the implementation moved to 2011 :-)

Glaciers move too

implementation resumed a couple of days ago, although I'm out of 
the loop for a while.

http://www.imdb.com/title/tt1172060/

Oops, that was supposed to go in the glass channel :)

Henrik - will your site with screenshots become available again? 
.... and ... should we await some new creations in upcoming weeks?

yes, I'll try to post some shots when new styles come up.

hi, a little question on field widget

i would like to froce a field to be options[info] disabled

i try myfield/options: [info]

but it don't work !!!!

oups it was for regbui

rebgui ;-)

That explains it :)

GUI status discussion moving here.

Screenshots will be available when there is something to show. Worked 
out a few bugs regarding tab navigation yesterday and there is work 
being done on the basis for a grid system that will be used for tables, 
dropdowns, menus, etc. Someone has been added to the list of developers, 
as I don't have much time right now to do GUI work. He may speak 
up if he wants to. :-)

hehe, cool!

Any fixes for low level? I mean - draw, rich-text, etc.?

no, waiting for host kit for that.

I just wish one thing - things to not add layers of complexity. The 
initial VID work was imo really nice, and I hope it will not complicate 
much ...

Depending on what will be worked on next, we might delve into testing 
schemes. We want the R3 GUI to be easily testable: Fire random events 
at a GUI window and collect errors and crashes and also generally 
record and playback UI events to tell what a user did.

Maybe my fear is preliminary, but it is based upon the doc you created 
... looks like too many things to implement :-)

I volunteer to test, even preliminary versions. It helps me to understand 
gui, to study sources, etc.