World: r3wp

BrianH - I noticed you several times mentioned changes to object 
semantics. Did I miss any discussions on that? I can't remember it. 
Or are you just expecting them to happen?

The discussions happened a year ago, mostly on Carl's blog and the 
R3 development world, but were put on hold until enough of the R3 
infrastructure was in place to do them properly (including binding 
changes and Unicode). The discussions will be resuming after Carl 
resurfaces.

Don't worry, it was just a year ago. I can still remember all of 
the major arguments on every side.

No classes though, so no worries there.

Much easier to fake class-based or other inheritance structures with 
the recend changes to BIND and IN that came out of Carl's VID work 
recently.

He's using those changes to do CSS-style inheritance for VID styles. 
Sometimes you have to do the high-level designs to get an idea about 
improvements to the low level that will have pervasive changes.

CSS style based that reminds me the desktop google and opera applets 
....

Not with actual CSS, mind you :)

The inheritance will work like CSS inheritance.

rebol wlll loos in originality .... and therefor ppl will say why 
to do GUI application in rebol since i can do them in desktop google 
or opera widgets with more functionalities

Um, no. VID is intended to beat HTML in functionality.

well I have to use it to see the benefit of it ...

I'm sure we can all agree to that.

but quite franckly i'm doing rebol to not have to spend weeks in 
GUI design ...

the oneliner VID  will not be possible anymore that's sad ...

I'm not sure about that. I expect that the one-liners will be more 
powerful.

Shadwolf - I suggest you to download R3 public alpha and study VID3 
from Gabriele. New VID3.4 from Carl will use different methods (frames, 
scenes), but flexibility of VID3 from Gabriele will be there ...

I have it

and i have heart beat and 1000 cows with 70 fps on my computer that's 
great would be even greater If gob could get a transparent background 
^^

but the way gob are writen I don't like it that's my taste ...

I saw vID 3 use filler to organize the widgets

so why do you think REBOL would loose in originality? What is original 
on VID2? Missing features? :-) VID3 is supposed to be next-gen VID. 
With all good, fixed bad, plus new stuff. If we lend some aspects 
from CSS (syntax will be block or dialect based, so still REBOL), 
I can see nothing wrong about it ...

Isn't there supposed to be transparency support in gobs? Just not 
in windows (yet).

well, Cyphre is trying to fix basic bugs for few months already, 
but it seems to me he is really busy, or RT is not willing to put 
him under contract, I don't know. The only thing I know is - we are 
very slow ....

Perk because organising a widget content in a CSS way is yes more 
readable but get more line of codes than VID2  way wich is not seen 
anywhere else

in opera widgets applet you have a CSS whay to setup the widget and 
in destop google applet you have a XML  way to setup the widget

I prefer "otherwise occupied" to "slow", but even that I am dealing 
with now (in my case at least).

that's lot of code for less efficiency but that's my point of view 
i prefere spend little time on the GUI and more time on what does 
the GUI ...

Shadwolf - then you might not understand VID3 layering as it was 
done. It was separated to three layers. CSS like one was kind of 
skin, allowing to set basic parameters. Who said it will be exactly 
like CSS?

less efficiency hum not sure you get the right though ....  hum efficiency 
here is related to coding scheme and not to performance wich are 
obviously stonich better with VID3

well that's my personal taste the only way to get me spend hours 
on a GUI  is when I write a brand new widget  ^^

other while I like the short GUI code provided in VID2

In general, how often do you write new widgets, and how often do 
you just use them?

hum depend with VID2 most of my work was doing widgets lol

With the exception of the resize code (my real biggest VID2 project), 
most of my VID work was just using them :)

but anyway that's another way to organise the code maybe the most 
of ppl will like it and I still can do a  bridge dialect VID2-> VID3 
 to keep my habits  in GUI  coding  hihihihi

I will label that bridge MakeVID2  lol

like a makedoc but for VID2 -> VID3

I did notice that you have to create new widgets in VID2 a lot more 
than seemed necessary to me. I hope that most people can get away 
with just using widgets in their code, and leave the widget creation 
to the GUI designers (which I am not).

yeah but hum with VID2 If you wanted something hum looking a little 
bit pro (before rebGUI) you was obligated to build your own widgets 
or customize the existing ones ...

Yup, that is definitely the case with VID2. With VID3, you are supposed 
to just be able to download a professional looking skin made by someone 
like Henrik and get back to the work of doing your aplication :)

but hum .... I like to play with widgets  ^^

Then you will be someone I will call upon when I need to do an application 
:)

lol

if i can use my makeVID2 we get a deal lol

(check private)

Oscar is in real world use even now, as part of Syllable.

No, it's ORCA

Sorry :)

I mistyped. How is ORCA doing?