World: r3wp

Carl should imo write down notes about how he envisioned GUI 3.4 
to work, especially non finished things like events (still from Gab's 
VID), layers, guides, resizing, etc.

Carl, you posted a specs document to me some time ago regarding guides, 
layers and better layout capabilities. I lost it. :-) Can you post 
it again?

G: Before I can do anything, I need to be sure that we've got the 
basic design well stated in a document.  We can always add from there.

I'd like to integrate those specs with the wiki specs document.

H: I'll take a look around. Probably in R3-GUI world, no?

I posted Carl a list of main topics. IMO the goal is to sort our 
what Carl really can do only by himself. All the rest can be done 
by a group of people. The main effort will be to get the design right. 
If this is done, the rest is "only"  implementation

Carl, I can take a look again.

Yes, I think we have a good critical mass of skillful developers.

We need a good enough solution, that is open enough that we can drive 
it forward. At the end of the day, the GUI must fit the developer 
needs. I'm not seeking for perfection (Ok, I do) but for time-to-market 
(because I learned/know that it's more critical these days).

Real artists ship
 :-)

Well, Robert, I'm glad that you are pushing it !

Q: why does Control-C in an area halt R3 ?

Is that a GUI or a core issue?

A: Bug.

Event issue, so core.

Carl, looked twice now and only found a small document regarding 
tags (which are implemented now).

Ok, 1 min... searching....

seems you can't use reflection functions on events either.

but I found the window in focus to be inside event/window

so no issue now on dealing with untrapped keys?

well, the issue is whether the method is correct. now, when no focal 
face is there, the window on-key actor is used.

but, there is no limitation in the event system. the problem is just 
to shape the mezzanines correctly.

I don't recall this being a limitation in R2/vid ... when using keys 
to activate faces

I believe there was some kind of sensor face.

Probably the best way for us GUI noobs to be able to help is for 
Carl to provide coherent docs for us to read and to start writing 
scripts ....

now tab navigating... only you can't see it yet and there are some 
screwups with the built in "tab navigation" in fields.

navigating using the tab key, or navigating a tab panel?

except we don't have tab panels yet :(

should be simple to do. we worked out how yesterday.

how's resizing now that you have tags?

something we'll look at later. there's a logical sequence of things 
that we need to get working before we get to resizing.

Carl, good to see you back in the GUI fray :)

Nice to see the events evolving...
The community needs a GUI system and creates a team

Reichart wars Carl that something is moving on on this front and 
needs his attention

Carl pop up in the group and catches the wave hoping the GUI sysytem 
does not take the wrong direction (I suppose).
Everyone is happy about this ! :-)

(wars=warns)

Big note now that says docs are inaccurate http://www.rebol.net/wiki/The_Graphical_User_Interface

Good. Kr Bacon really messed things up, and this is a source of much 
of the confusion about R3's GUI.

probably very preliminary, but could this be kind of the design we 
are heading for? Looks clean, simple, yet nice enough. IIRC Cyphre 
used similar theming (blueish) for his styles-pack:


http://www.zive.cz/ShowArticleImages.aspx?id_file=423472159&article=141664

Presumably there are some fundamentals that have to be solved before 
the esthetics can be dealt with

Graham, correct.

Any progress?

I'm busy with something else right now. Hope to continue tomorrow. 
Carl is working on docs.

good to hear Carl is documenting his ideas for the GUI. Is Cyphre 
already doing some low-level work? :-) Is there actually any priority 
for low level work? E.g. unicode display, better cross-platform font 
handling, draw improvements, transparent top windows, etc.?

Cyphre is down with the flu right now and a sporadic internet connection 
due to snow, so I have no immediate status of what he's doing, other 
than waiting for the host kit, but what he's shown me, based on a 
separate AGG build, shows that there are a lot of ideas for what 
to do.

some two or more weeks ago he told me he is working on some demo, 
showing some AGG capabilities. That is probably stuff you saw? Will 
it be demoed? :-) Or is it just internal build to have some ground 
for further architecture improvement talks?

He was testing the bottleneck for parsing and drawing DRAW blocks 
as quickly as possible, and he calculated that the bottleneck for 
PARSE was much lower than that for AGG's draw routines, so it didn't 
make much sense to have to avoid PARSE according to his measurements. 
It might still become possible anyway to bypass PARSE, but I'm not 
sure.

The separate AGG build is just there until he can get a hold of the 
host kit and to test ideas.

So getting View under the wraps of the command! Extension interface 
is absolutly essential in order to proceed ....

on a low level yes. on VID level, there's more than enough to do.

Henrik - will you restart your "teaser" screenshot web, as you proceed? 
:-)

yes, I can put one up now