World: r3wp

Are we going to see an sctp implementation soon?

well, I won't be making it. :-) I think these questions are better 
suited for later. I need to have a better look at devbase. I suspect 
(sorry, Terry) that it will be a 3rd party job.

actually those questions have been answered already, but some people 
like to pretend they didn't notice. R3 will not be sold. RT makes 
money in other ways. (eg AltMe 3)

http://hmkdesign.dk/rebol/files/f5ab092787305f43a01d825826a9eb51-87.html
<--- small FAQ posted here.

henrik, some bugs in your former blog, it might confuse ppl:


1) "Knowing FOREACH from R2, you can assign a word to each of those 
4 elements " .... while your block shows only [a b c]
2) >> a: [1 2 3 4 5 6 7 8 9]
== [1 2 3 4 5 6]

...is wrong too - you miss 7 8 in the ==[] block returned from console 
...

fixed

What a great faq Henrik. Thanks.

Hey, I was just wondering. How big is Rebol3 now (in MB)? Not that 
it matters to me that much but I am curious.

MB? :-)

rebhost.exe - 360KB, rebol.dll - 298KB

Ohh, sorry : ) Wasn't thinking straight. (I am working on a PC, you 
know)

some things are still outside of the R3 distribution, so it might 
balloon a few more kb.

Still incredible, don't you think? So this thing might really work 
on a cellphone/pda?

easily.

Henrik, you know I am a big PS3 fan. How big of a deal would it be 
to port?

I don't know yet much about the porting process, but so far it looks 
like a "fill in the blanks" process, where you need to provide functionality 
for events, timers, threads, etc. That and the documentation for 
whatever OS runs on the PS3. If Linux can run on it, R3 should work 
fine.

It does so I hope that means my next "Amiga" will be a PS3.

The executable size of all versions of REBOL is absolutely tiny.
But the memory footprint when loaded runs into megabytes.

That used to be a showstopper for memory-limited devices such as 
phones/pdas.

It may no longer be if the minimum hardware has caught up with REBOL's 
memory requirements.

R3 typically uses half the memory of R2 right now. Perhaps much less 
on graphics intensive apps.

The cows demo shows that spectacularly.

That's a very promising statistic!

Sure is.

I don't know how much memory an R2 face takes, but a single empty 
GOB in R3 takes 64 bytes.

Well, the proof will be in the pudding. When we get to the point 
where we can run R3 on a Nokia device, we'll know.

I don't do many benchmarks either right now, because my only windows 
box is a 192 MB Celeron 500 that will only boot in fail safe mode 
without graphics acceleration. However it probably is a good thing, 
since it really shows that graphics are noticably faster. That will 
help lowering the system requirements.

>> stats
Series Memory Info:
  node   size = 16
  series size = 20
       5 segs =  409640 bytes (header space)
   11259 blks = 1295568 bytes (blocks used)
    1213 strs =   85112 bytes (strings used)
       3 odds =   73792 bytes (odd series used)
   12475 used = 1454472 bytes (total used)
       0 free /    8005 bytes (free headers / nodespace)

Pool[ 0]    8B   173/  512: 256 (33%)  2 segs,    4112 total
Pool[ 1]   16B   487/  768: 256 (63%)  3 segs,   12312 total
Pool[ 2]   32B  1326/ 2048: 512 (64%)  4 segs,   65568 total
Pool[ 3]   48B  4621/ 8192:1024 (56%)  8 segs,  393280 total
Pool[ 4]   64B  2414/ 3584: 512 (67%)  7 segs,  229432 total
Pool[ 5]   80B  1182/ 1792: 256 (65%)  7 segs,  143416 total
Pool[ 6]   96B   544/  896: 128 (60%)  7 segs,   86072 total
Pool[ 7]  112B   342/  512: 128 (66%)  4 segs,   57376 total
Pool[ 8]  128B   228/  320:  64 (71%)  5 segs,   41000 total
Pool[ 9]  144B   182/  320:  64 (56%)  5 segs,   46120 total
Pool[10]  160B   144/  256:  64 (56%)  4 segs,   40992 total
Pool[11]  176B   137/  224:  32 (61%)  7 segs,   39480 total
Pool[12]  192B   121/  192:  32 (63%)  6 segs,   36912 total
Pool[13]  208B    89/  160:  32 (55%)  5 segs,   33320 total
Pool[14]  224B    77/  128:  32 (60%)  4 segs,   28704 total
Pool[15]  240B    28/   64:  32 (43%)  2 segs,   15376 total
Pool[16]  256B    39/   64:  64 (60%)  1 segs,   16392 total
Pool[17]  320B   170/  256:  32 (66%)  8 segs,   81984 total
Pool[18]  384B    49/   96:  16 (51%)  6 segs,   36912 total
Pool[19]  448B    21/   48:  16 (43%)  3 segs,   21528 total
Pool[20]  512B    14/   32:   8 (43%)  4 segs,   16416 total
Pool[21] 1024B    62/  128:  16 (48%)  8 segs,  131136 total
Pool[22] 2048B    13/   24:   8 (54%)  3 segs,   49176 total
Pool[23] 3072B     0/    4:   4 ( 0%)  1 segs,   12296 total
Pool[24] 4096B     0/    4:   4 ( 0%)  1 segs,   16392 total
Pool[25]   20B 12475/20480:4096 (60%)  5 segs,  409640 total
Pool[26]   64B     1/  128: 128 ( 0%)  1 segs,    8200 total
Pools used 1220708 of 2073544 (58%)
System pool used 483328
== 1454472

(in a new R3 session)

in R2 I have == 6145092

FlashPlayer has same or bigger memory footprint and is on pdas so 
why not R3

Don't know if this is the right place to ask but.. Will there be 
some easy way to access USB devices in Rebol3?

no ....

But if your USB device supports mass storage - most usefull do, then 
what is the problem? You treat is as simply another drive ...

I suppose you go through the OS for that.

R3 is going to have specific access to usb devices

If you need more, you could use the libusb library on Unixy platforms

I'm on Windows.. I've managed to make a small program that communicates 
with the device (it's a small OLED display on my laptop) in C++, 
but it would be much more fun to write it all in Rebol

if you know what DLLs to use, you probably can.

at 4:12 my local time DevBase went online

at 4:57 my local time the first change was carried through in the 
source tree

i need Encap rebview1350042.tar.gz ( rebcode)  - I can buy

Henrik, so R3 is not far behind, eh?

still some bugs to iron out.

any Screenshots of DevBase ?

we want to see...

posting some soon

pictures on my blog at: http://www.hmkdesign.dk/rebol/

thx

:-)

Henrik, I spy a little list-view there!  : ) Very nice.

You know, that devbase seems like a very useful tool for personal 
application development as well. Any plans for releasing it for that 
reason? I imagine it tracks uploaded files