World: r3wp

there are still a few bugs (the partially blanked button in 226

 - yes, that is a Draw bug as it looks. BTW, it has nothing in common 
 with the new resizing scheme, the above new resizing scheme test 
 just exposed the bug

twitter: Successful branch: Cyphre can do R3 builds now, including 
native graphics extension module.

Is this the hostkit ??

yes, there are a few internal releases of the host kit.

Some resulting exes:

07/10/2010  12:45 PM           267,776 r3.exe
07/10/2010  12:46 PM            28,672 r3core.exe
07/10/2010  12:34 PM           393,216 r3lib.dll

You can build an R3/Core without AGG.

The current hostkit zip file size is 773 kb.

The structure is squeaky clean. Even I can figure it out.

internal releases meaning a restricted release

the POSIX part is not complete and Robert has some compile problems.

what is the r3lib.dll used by?

it's used by the executable.

(I'd like to see a 28 kb R3 too, but alas...)

So, how can we load this dll into R2?

I'm not sure how one would do that...

But wouldn't it be good if we could??

I suppose someone else can answer that.

Graham, from what I remember from the old "host kit" (2007), i don't 
think you can do that, as you had to pass a function table to the 
dll.

ie. the dll needs to be able to call into the host kit code, and 
you can't solve that with callback!

you might be able to create your own dll though. not sure about that.

So, you need the hostkit running as well... so it might still be 
possible

i suspect it would be far easier to just communicate through tcp 
:-)

So, what exactly does the dll hold?

Most of rebol I guess

the actual "REBOL" :)

(again, i can only speak for how things were in 2007 or so)

the DLL is the closed part, I suppose. The executable contains the 
open parts.

Ideally one should be able to load the dll into another language 
to use it

I think that's one of the intentions of the DLL.

and one of those languages should be r2

except it sound like R2 is not up for the job.

the single DLL can't imo work. It just contains language interpreter 
plus api structures on the surface imo. It means e.g. all networking 
code (simply code that does something), or OS dependant functions, 
will be in the host kit, hence I am not sure the DLL itself is much 
usefull separately ...

the gui and parser ....

The DLL is the plain Rebol interpreter. All the sourrindings, named 
host-kit, that you need to make use of Rebol on a particular platform 
is in the EXE. The EXE loads the DLL at init time.

As the interpreter is plain C is should be portable to different 
platforms very fast. That's something that Carl always needs to do. 
Than all the host-kit stuff (meaning the interfaces to the Rebol 
interpreter) need to be ported to the target platform.

For example: If you can't get AGG to work, you need to do a replacement 
with an equal API layer.

Graham, I don't see a real good case to use the R3 DLL within R2. 
Why to do this? And the interpreter in the DLL is nothing "useful" 
on it's own. It requires at least a simple host environment to do 
something useful.

In situations where the app can not be ported to R3 yet

Than stay with R2. The effort it takes to mix these two should better 
be spent on porting the app.

Let us know when we have SSL

With the host-kit SSL can be added by the community.

The host of the hostkit can itself be a dll, and that dll could be 
designed to be loaded by R2.

Passing data between them would likely require serialization, just 
like with TCP, but it would be in-memory.

yes I have a client which would benefit from R3 within R2 specificaly 
to use PARSE..   as brian noted, I'd compile the R3 host as a dll 
and try to make a routine in R2 to access it.

any news on R3 GUI front? :-)

some refinements to the resizing model, by ladislav and cyphre as 
well as some documentation, so I can learn how it works. no new demos 
at this time.

What is the plan towards low-level of GUI? I mean - we now have new 
model - host-kit. My understanding is, that Carl created only few 
API functions, to get it running. So - how long will it take for 
VID being able to work upon new host-kit architecture?

Maybe my understanding is wrong, and all api is done already?

VID shouldn't be affected. The host-kit change with the low-level 
part: VID | VIew | Rebol Core | AGG | OS. We need to implement all 
DRAW commands yet.

From the API point-of-view, VID should not be affected, but - if 
you don't have all draw commands implemented yet, it can't work yet, 
no?

Yep, that's why we need to implement them now.