World: r3wp

Graham - how can't you care? If it woudl be GPL, we could not use 
it at all ...

We
 as a RT may not ... but "we" as a user can ...

No, we can't. GPL is GPL. You either fit the license, or you break 
it, no?

If I don't distibute I can do what I like ...

Better break the license than some glass.

GPL only applies to software that you distribute

Pekr, "just wrapping" other code is not easy to do right, and takes 
time and effort. Less time and effort than rewiting it from scratch 
in some cases (likely including SSL and SSH), but still not a trivial 
effort.

Graham, a scheme that you can't distribute is of extremely limited 
use, too limited to justify the effort involved.

in your personal opinion of course

If google developed such a scheme, and kept it within their organization, 
that would be in keeping with GPL .. no need to release source

what I was envisaging was someone linking the host code to eg.  a 
gpl tls library and releasing instructions on how to build it yourself.

I don't see what is wrong with that.

All right, too limited to justify *my* effort. Or anyone who doesn't 
work for a large company.

I guess I just may have to get that book C for dummies from the library 
after all

hehe

Max, where's that progress report ...??

progress on OpenGL?

I don't see the point in this anyways, since there are decent SSL 
and SSH libraries with permissive licenses. We can ignore GPL code.

Still, I don't want to disuade you from brushing up on your C :)

starting .. not brushing up

yes, OpenGL

Have you created a GUI to replace VID using open GL yet ?

as I explained to sunanda, while doing the OpenGL port I decided 
to build my C code analyzer/compiler/converter to make the process 
as complete and painless as possible...


but I've hit a wall and need a better unit testing engine to complete 
that and the OpenGL convertion.

so you're stuck ...?

What about Qt ?  Is that feasible?

I've used that before but its more pain than gain.

I'm not really stuck, i'm just building a highway instead of a small 
road... so it takes a bit more ground work.

but the result will be 3 tools instead of one... and about the same 
time to accomplish the end goal.

and then the ability to create complete C extensions for just about 
any C useable tools in a few minutes.

sounds like grandiose ideation !  :)

no its how every other platform does it.

using tools like SWIG.

I want to do it using REBOL end-to-end.

and since the C analyser has a programable emitter, you will be able 
to customize what it does.

What's the ETA for this?  Knowing that you start university this 
week ...

honestly I don't know, but its a funded project overall, so it is 
my current job.  which means it will happen for sure.


I would love to have some usefull OpenGL stuff working in february.

one reason I'm doing Sea (the C converter) is that for each new improvement 
of extensions, we will be able to update our tools with a single 
rebuild of the extension. for large libs this is going to be a big 
deal.

is the funding contingent on delivery ? :)

well, usually, you get paid to get things done.  but this is an ongoing 
project.  It also has other libraries I must import which I can't 
talk about right now, but which might be very interesting for the 
community.

As I said above I don't use imap, and am not familiar with the protocol. 
 All this does is login using auth=login and grabs the first mail 
in the Inbox
http://rebol.wik.is/Rebol3/Schemes/Imap4

I don't parse any of the message flags etc.

Ok, what do we need for imap?  ( although I suspect doing all these 
email schemes is a waste of time without ssl ) ...

for developing, stunnel will help with immediate ssl issues

ssl AFAIK is under the protocol, so even with an SSL module, the 
schema should not really change.

stunnel adds transparency ... I guess

anyone got a how to on using stunnel ?

The r2 imap protocol is pretty basic ... so I don't see that we need 
do more than that ....except perhaps allow users to pass custom commands 
to the server.

stunnel -cf -P '' -d sourceport -r targethost:targetport

thanks

-c is for client mode, i.e. so that stunnel will connect to a server

-f is so that stunnel stays in the foreground (and you see debug 
output)

-P '' is to avoid creating a pid file (dunno if that is necessary 
on win32 stunnels)
-d sourceport tells stunnel to listen on sourceport
-r targethost:targetport to forward data to this target