World: r3wp

So, what I prefer for initial release is - introduce us to particular 
subystems, give us doc with description of how you aproach UI creation. 
Styles can be added later. But I want to have flexible base first, 
which will count on all things needed to support big GUIs.

pekr, about a gfx artist... maybe we already have one? :-)

Henrik - do you find gobs to be more difficult concept than faces? 
Or is it just that gobs are new, and you have to switch your thinking 
to the new concept?

Chris? :-)

perhaps :-)

or perhaps not... but the look might change a bit. perhaps the gradient 
color will change. :-)

insufficient! :-)

Pekr, sorry I'm teasing you about the GFX, but the final look will 
stay secret until it's done, as it's not open for commenting.

My guess is it will be a year before we can build large applications 
with it!

Graham - so far you can use RebGUI, no? If it needs year, then let 
it be one year. But I want to be able to comment on things like focusing 
etc. I don't want R3 VID being limited in any aspect ....

ie. I don't expect it to spring fully formed

keyboard support for games

Henrik - is there a concept of window in new VID? As I said - I would 
like to have one. We should decide upon what will view/new do. I 
am not sure I want it to open new OS level window. That will make 
plug-in apps suck big time. I would welcome the choice - for desktop 
apps let it be e.g. OS window, for plug-in, VID windowing ....

a way to render a browser window inside a vid window, or mpeg inside

keyboard handler? it needs to improve - there were no key-up events 
iirc, and also some very basic and needed key combinations to be 
supported - ctrl tab - this one is really needed to switch between 
tabs ...

Pekr, GOBs are more difficult, because they are more flexible and 
low level, so if you want to build just a three layer face of a color, 
a text and an effect, you need 3 GOBs. You need to define them and 
then put them together correctly. But there will likely be a simple 
way to build complex GOB setups skin makers, perhaps a dialect, so 
the outcome will be simpler than it was in R2.

I prefer non OS look, own style, which will identify rebol app. Definitely. 
All claims of otherwise I find false and unsupported by reality check. 
But I don't probably want my app to behave differently keyboard, 
focus wise, etc. Could be tough to achieve, as I remember OS-X has 
its own specifics :-(

re OS-X - I mean complete behavior of app in regards to system, docking 
etc.

pekr, "is there a concept of window in new VID? As I said - I would 
like to have one."


I don't really know, as I haven't looked at this part of VID3. Windows 
are different from GOBs. There are "Window GOBs", but I don't know 
exactly what that means.

oh, well, next time i'll forbid people from posting screenshots. 
:)

graham: the dialect is different, because it uses new dialecting 
methods from r3. also, the layout is intended to be abstract rather 
than concrete (ie you don't normally specify the size of things). 
the rendering is fully up to the "skin" and not to the layout dialect.

petr, you can't say what resizing is missing before knowing how it 
works. :)

petr, the plugin is a different host, in the normal host windowing 
MUST be left to the os.

Gabriele - re posting screenshots, I thought the same - if I would 
not see a screenshot, I would have nothing to complaing about :-)

Gabriele - why you think it must be left to the os?

so you want altme to open up some big window and have altme windows 
inside it?!?

Think of ViewTop for e.g. It is like desktop. Why not to have VID 
level windowing? Not as a default, but as an option?

give me one single reason to have vid level windowing (it's just 
a style away to be possible - the system does not care at all about 
how "windows" are implemented)

yes to Altme, why not? It is just layer, the only difference is, 
that dialog box does not appear on the OS taskbar ...

I am starting to think of R3 View as na OS desktop, so ... :-)

ie. i can make a "screen" panel style and a window style.

yes, that is what I meant .....

it would help plug-in at least ....

i think that in the case of plugin it's the host code that has to 
handle this. you should not have to change your app to work in the 
plugin.

Gabriele, do you (or other in the R3 dev team) know about GLUT? It 
may be a fast way for you to have e.g. key-up events on all platforms.

(although, of course, the environment is so different that the app 
may need to handle it as a special case.)

geomol, i'm sure cyphre knows about it, but i don't think we're going 
to explore that anytime soon. we have key-up for control, shift, 
and so on already.

ctrl tab  supported? :-)

ok, I was thinking, it might be a shortcut to many wanted features, 
until the final code is found for the different platforms.

i haven't tried ctrl tab

it was not trappable in R2 iirc ....

yes, i get event/key: #"^-" and event/flags: [control]

Gabriele - re plug-in - it is different kind of app. But I would 
hate any single window to pop-up, even for simple dialog. And I mean 
to that extent, that I would ban such app, or it would be blocked 
by some add-block kind of extension anyway.

(i'm on wine though.)

ok, that is good to hear, ctrl tab is used for switching between 
tab in tab style ...

petr, i think the plugin host should never open new windows, but 
that depends on the plugin developer.

ok, but if you think about your app, you need dialog box, right? 
And what did currently R2 plug-in did? It popped-up in front of your 
browser ... that is not good. So to avoid this, you need something 
like windowing styles directly in VID level ....

no, you need the plugin to open its windows inside the window it 
has available.

But you are right that it can be solved by creating such styles ...... 
have you seen portals? Big ones? E.g. websphere? User has one website, 
and it has kind of small windows (javascript probably), which can 
be moved, resized, maximised, minimised ....

VID does not even need to know about it.