World: r3wp

http://www.rebol.net/wiki/RebTalk_Forum

First client prototype (30-Nov-2008) 8.1 KB in size, and first server, 
4.6 KB. Written by Carl Sassenrath.
 :)

and very busy already 

data: [
]
[command-error]

Now how to force a client update each time you change some functionality?

Perhaps the client should download the source each time ...

DevBase does that (though it caches locally in the R2 version).

My vidwiki client downloaded a new layout for each page ....

ie. emulating what browser clients did ( sort of )

You would only need to download a changed version. This looks like 
a good job for a REBOL browser reblet.

Using it already, though it has some bugs to work out. These are 
R3 bugs which then get fixed :)

OK, if Carl wants to make a release now, then it will be without 
my skin (untested, not merged), so enjoy the colors. :-)

Has he made a general release???

I don't think so, but he did say "a few hours".

(I would translate that to "about 2 weeks") :-)

We've already done the translation!

iicari, I have a working solution from DideC now.Thanks for helping.

:)

generic calendar module for R2 / R3 use can be found at http://rebol.mustard.co.nz/calendar.r
- this assumes a minimal amount of data necessary to build a monthly 
calendar with optional first-day-of-weeks (rather than REBOLs default 
Monday..)

quite small. I will look into it. Thanks.

Has the functionality that resided in the system object in R2 been 
moved to its new home in R3 yet?

Now, there is in fact a part of the R3 GUI I want to release for 
testing and that is the color conversion functions.

PeterWood, the system object is still there it seems.

So is this no longer valid? http://www.rebol.net/r3blogs/0020.html

I think the existence of the system object is tightly coupled with 
modules which Carl has not been working on yet. BrianH knows more 
about it than me.

I'm moving the color test discussion to r3-alpha.

Conclusion of test: Color conversion functions require latest alpha. 
:-)

But for those interested in reading the source code:

http://www.hmkdesign.dk/rebol/r3/g-color.r

My webserver is now running again (temporarily on a laptop)

One step forward -- a demo/teaser for the REbtalk forum:
http://www.rebol.net/r3blogs/0157.html

Doesn't look like a way to choose unread threads

Now what is that once again? It once again looks as missorganised 
effort. Give me a break, please. This one is really not going to 
be better than Atlme, far from that. I thought, that when we were 
talking about REBOL forum, we were not talking REBOL based GUI?

Hopefully someone will quickly write a browser client

If we want to have something cool, we should not aim anything less 
than IOS NG, based upon rebservices. As for me, I regard this client 
being only usefull for testing purposes, but I refuse to think in 
feature set it offers.

Well, at least we found a couple of bugs that need to be fixed anyway, 
so the effort wasn't entirely wasted.

Please post the source ... so we can write a Rebol plugin client

Carl makes R3 usable the only way you can... create a test application 
that has enough real world charateristics to be representative of 
real life work being done in R3.

Look closer, you see:
- server
- async web network client 
- GUI
- local and remote data storage

 and so on.

Nothing as goof as a real user

*goof=good

Pekr, do you really think that you may write complex apps without 
making simple one first?

No, but you could come up with any app. This plan to use it as a 
basis for the discussion is pretty much FLAWED. If used, it will 
distract us from altme, as well as it WILL NOT cover what the group 
was asking for - having the web forum.

I don't think this can be used for a web forum (with heavy trafic), 
but it's useful to find out what needs to be changed in the R3 design. 
That's the reason why Carl limit's access to releases. He does not 
want to confuse too many people as the design changes too fast. I 
guess, I'm not in the same group as Henrik.

For me it would be enough, if unicode is already possible in the 
text areas of the new GUI.

What's worse ... using php ( as we already do with mediawiki ), or 
your own BBS that can't handle loads?

Carl states in the blog, that he is considering to use it for developer's 
discussions, and I don't agree to that, unless I can see, that the 
plan is really well though out. It will not be forum, it will be 
still worse than altme, it will not be searchable, etc.

If we state that it is some kind of typical communication test-bed, 
then I am ok with it. But then it belongs to trashcan.

then = after it fulfills its testing purposes

So, we still lack a forum for the new users

Carl is seeking a solution to HIS communication needs. Not the USERS' 
communication needs. It seems to be a common pattern: That he starts 
developing something himself, because his needs are misunderstood.

I would not call it trashcan, but "how to" category

Henrik - wake me up, when after 3 months or half a year we found 
ourselves with another unfinished system, semi functional ...