World: r3wp

He said he was going to do so Monday, but had some things to tend 
to and so said Tuesday, but nothing was released Tuesday. Let's see 
what happens today. He usually starts talking in about 7-8 hours.

yes, evening here in EU is morning in the Ukiah :-)

For the record: I was opposed to the idea of Fireside from the beginning, 
because I thought he meant yet another forum/communications channel, 
since he talked a bit about allowing communication with "hundreds 
of users", not so impressive. We have enough of that with AltME.

When he talked about the existing framework, the working prototype, 
the source code altering and finally the code submission model, I 
changed my mind. I think this tool can be very powerful.

The first version will be done in R2, since VID3 is not yet up to 
the task (missing styles).

Small teaser - doing some basic tasking testing in console. I thought 
tasking does not work yet, but apart from missing IPC:// scheme it 
seems to work:


>> test: make task! [wait 10 print ["Does tasking work?" newline]]
== task!
>> do test
Begin Task
== task!
>> print "Doing something else in conDoes tasking work?

End Task
sole"
Doing something else in console

>> test: make task! [wait 10 print ["Does tasking work?" newline]]
== task!
>> do test
Begin Task
== task!
>> print "Doing something else in console..."
Doing something else in console...
>> Does tasking work?

End Task

>>

ah, put test in console twice, sorry for that. The first time 10 
sec was too short for me to type another print statement, so it is 
intermixed ....

but is it debugged?

Don't know if this is interesting to you, but:


http://www.hmkdesign.dk/rebol/files/082390c9260a1a8ce96cedddd8aad803-83.html#unique-entry-id-83

:-)

Thanks Henrik - it surely is VERY interesting and I suggest every 
one to read it, to get bigger picture of what VID3 is going to be 
about. It answers many worries in non-technical language, easy to 
understand main concepts ....

Great stuff

Henrik, thanks! Very interesting.

Very nice ! Thanks !

thank you for this interesting introduction of V3D ;-)  (means VID3)

Guess it needs to be tested in practise to see if this approach does 
indeed scale better.

ah, Graham, good blog topic there. :-) it scales pretty well.

Have any complex GUIs been written yet in V3 ?

a close button that close the window down .. but say I need to add 
additional functionality?

do I need to create a new type of close button?

there is an effects lab written in VID3 that would be impossible 
to make in VID or at least very difficult. would probably require 
2-3000 lines of VID code.

view layout [h1 "Goodbye, complex world!"]

Kaj, layout isn't necessary anymore :-)

'layout is redundant in V3 !

See, far too much to keep up with! :-)

it's still there, but built into View

how about alignments

grouping etc

And a good reason to educate people ;-)

Rebgui has done a lot of work here

with containers that allow you to create groups of widgets that move 
in concert

Graham, I will get to that. I may make another blog post on that. 
But VID3 behaves similarly to QT or GTK in this respect now.

don't know QT/GTK

some things are still not in place, but creating the layout in the 
screenshot is less than 1 kb of code.

what about background animations?

no timers, so not yet. they will come.

transparency

transparency is simple. it's everywhere.

previously R2 was limited to the common platform idea ..

so, if one platform lacked a feature .. it meant none of the others 
could have it

Hope that is being tossed into the bit bucket

yes, it's different now. however full hw-acceleration and those things 
will come later.

lots of stuff to finish first

great ... that was form of computer communism

Hope that postscript will be better supported as Carl said it would

we should in fact be able to scale down from full graphics to text 
console, if it's possible to make a usable interface in that.

Cyphre would know more about that. He's still adding features to 
DRAW.

like Amiga anywhere?

Taos or whatever it was called?

(although rather slowly these days :-))

is Cyphre still working on qtask?

I meant in terms of where a UI can be displayed. Not whether we can 
hard scale it to a PDA or an HDTV like they do. If you want to display 
big and pretty buttons on an HDTV, you'd use one set of styles. If 
you want to display on a text only console, you'd use a different 
set of styles, but the layout code would be the same. Some work needs 
to be done here before I can say anything more. We're only testing 
ordinary WindowsXP graphics for now.