World: r3wp

barely ? lol

depends ...

ok.

old builds have draw, newer do not

But richtexts seem to work, as far i tested

on what build?

I mean the robert's one

for your IRC client?

see !REBOL Host kit

it's not an IRC client

Shad made a wrong guess

It's only some demo styles

ok ...

but maybe it will be a real GUI

SGUI ?

S for ?

oh !

Steeve ....

I guess it should be GUIdS since the noun follows in french

not bad :-)

GUIDuS

I found GuiMove but it''s already taken

it's sound like guimauve in french and it means marshmallow

hmm... tasty

I've created this function many times enough to think it should be 
standard:


; creates a string from a list of strings with human readable comma 
separation
string-list: func [blk /local out] [
	out: make string! 1000
	forall blk [
		append out form first blk

  unless tail? next blk [append out either tail? at blk 3 [" and "][", 
  "]]
	]
	out
]

string-list ["a" "b" "c"]
== "a, b and c"

feel free to optimize

Why is this R3?

works in R2 as well. feel free to add it to R2/Forward.

What's the setting?

what setting?

what input is causing you to create this output?

Are you creating sentences?

blocks of strings, usually created for dialogs or other human readable 
output

I'd think that it is just something that you do :)

I don't do this .. but I have code that processes a whole sentence 
and grammar fixes it including the above.

I've built similar funcs, but not often. Maybe it could be part of 
a formatting module, and I would give it a different name.

The output format is specific enough, and the name generic enough, 
that I wouldn't make it a standard func as is. It is useful though.

Could someone please add an A105 version to R3 Curecode? Thanks!

Done. And bug#1643 marked as fixed in it..

Thanks, Brian.

Just reading new roadmap - http://www.rebol.com/roadmap.html... 
what I don't understand is all the fuss about R3+. From the very 
beginning, I don't like the idea of putting some usefull stuff into 
additional module. E.g. - why some usefull mezzanines or protocols 
be part of the plus package? What I fear is - anything, that is optional, 
will not be a standard. I can understand that we can't include 100 
protocols probably, but talking about + package, where the only protocol 
we have is http, and even that is not fully functional, is a bit 
preliminary :-)


Interesting note about R3 DB - what is R3 DB port? Is Rebin, RIF, 
finally coming? Or did we decide to select one DB, e.g. SQLite engine, 
and include it into R3?


As for tasking - "Experiment: how far does the current R3 multitasking 
base take us?" - no experiments, please :-) Tasking/IPC is the last 
missing stone before we can claim R3 being a beta - it needs solid 
work, and I expect 1-2 months, and the same kind of impact, as Unicode 
transition, or Extension, Callbacks had :-)

Tasking/IPC is the last missing stone before we can claim R3 being 
a beta
 - disagreed

(with both "the last" as well as "missing")

these are just opinions

There is no definition of what constitutes a R3 beta

Nevertheless, I do not doubt Pekr will be proven wrong.

...even without a definition

Pekr, what part of "optional" means "non-standard"? It just means 
that it isn't loaded and taking up resources if you don't need it.

It's a plus for a lot of platforms to be able to build on a minimal 
base. For instance, I would have loved /Base on WinCE.

Everyone has different needs. I defined "my" needs for R3 beta in 
related document (wiki). The only thing I meant is, that I regard 
tasking/ipc being last "big" missing component. I have no problem 
being corrected or proven wrong ...