World: r3wp

hum ?? ok so i can speak here if i do an opencl extension and its 
dialect and then do the port of cheyenne to it and a demo called 
that's my web server running on my ATI 5670 ?

We have the !REBOL3 GUI and !REBOL3 Extensions groups to handle that 
request. It's a work in process. What else?

i'm not the ordered kind of guy sorry i like chaos

I like your enthusiasm, but we're actively working on R3 right now. 
Except the OpenCL stuff, everything you are requesting is already 
being worked on.

shadwolf is gone owling to the moon in the deepe forest to ease his 
pain ....

I am personally not working on graphics, but others are. Right now 
I am working on optimizing the module system so the graphics work 
will be loaded better, faster, safer and more organized. Once that 
is done I can work on other projects, time and energy permitting. 
Your vote for OpenCL support has been added to the other requests 
for it that have already come in.

With limited man power it makes sense to work on the most blocking 
aspects of R3 development.  I don't know if anyone has created such 
a list ... and whether it would be adhered to anyway, as development 
is being driven by politics and money.

And that's not necessarily a bad thing because without money, we 
would be stuck with 0 progress.

driven by -> supported by

Not all of us can afford to donate their time/energy to this. Not 
even me as much anymore.

http://www.rebol.com/roadmap.htmlwas updated on Bastille day

This is a list of open projects .. but note that there is no prioritization 
visible

http://www.rebol.com/projects.html

The lack of coordination and exclusiveness of the current development 
methodology does not maximize the use of the community

Just because R3 isn't multi-threaded doesn't mean we can't be

Right now the main core of current development is coordinated. It 
would be nice to maximize the use of the community, but the interrelated 
projects are already being coordinated, and syncing up the projects 
that can be done independently would just add management overhead.

Anyone able to assess whether this is feasible http://www.libssh2.org/
as an extension or whatever ...

BSD license vs the LGPL license for libssh ( which also does server 
side ssh )

I have used it. Works very good. It's used in the communication layer 
I have done.

Are you releasing that or should we reimplement it?

It will be released. To really be convinient we need R3 callbacks. 
So, it's to much a prototype yet. My experience showed that things 
need to have a critical maturity level before others will pick it 
up and really use it.

So, did you do a R3 or R2 implementation?

ssh extension? this would be great!

It's not something I have any immediate need for, but it looks like 
an interesting project to try

Brian, you say "We have a task! type now, and have had it for a while. 
It doesn't work well but when last I checked it does work."


Could you elaborate on this? How does one actually use task!, with 
current R3?

In general, one doesn't. There is no infrastructure code around tasks, 
no way to stop or track them that I know of (they may stop on their 
own), and the only testing of them that I have done is to track down 
errors. But they seem to do something. The task-local user context 
is for the moment by definition rather than actual - it hasn't yet 
been implemented. But you can MAKE a task! and it will do something.

a: make task! [wait 5 print "Hello in a task"] do a print "Hello"

as you can see, it will print "Hello" first, and after 5 secs it 
will print "Hello in a task" .... the question is, if I got the usage 
right :-)

It's been like that for more than a year now. Oh, and if an error 
is triggered in a task and not handled, it will crash R3. I'm not 
sure it is stable to trigger an error and handle it either.

Yup, that works Pekr, and the task ends on its own.

>> a: make task! [wait 5 print "Hello in a task"] do a print "Hello"
Begin Task
Hello
>> Hello in a task
End Task

interesting. does nothing at all on linux, so i guess that's why 
i didn't ever notice that tasks actually do something.

but it indeed works fine on win32 R3. thanks for your help, guys!

There's a lot of R3 that only works on Windows for now, if there.

I wonder where the code is that prints "Begin Task" and "End Task"...

you've got me wondering how we could already setup some thread IPC 
and burst mode control with the current  !task.implementation.... 
hum... worth looking into.

the "begin/end task" printing happens somewhere in r3lib, and in 
native code, afaict

I hope it pays attention to the quiet setting.

timers cannot be started from another thread .. error

? Code?

Interesting .. so I can start my gui that way as a task

oh .. I think it's a Qt error message

Likely not, because task-local data isn't implemented yet. It's probably 
not safe.

I started up multiple Qt windows as tasks

Nope, it does not pay attention to the quiet setting.

Debug code then.

Surely, a bug nevertheless.

Well, nevermind. Considering that it's mostly unsupported functionality 
at this point, probably not worth a bug report :)

Yup, there is no point to reporting task! bugs yet, they all get 
deferred. But not deferred very long, if recent indications are true 
:)

When they are worth reporting, we'll let you know.

interesting .. this seems to be working well.

still a bug if you can't use it for cgi ...