AltME groups: search

maybe you can use rename in the same way I used it to implement simple 
locking just before in DB Chat channel

Here's the source to the new 2.7.8 functions that were posted earlier 
today, for those who haven't seen it on chat. I'm posting one function 
per message so bear with me for a sec. Not posting them in !REBOL2 
because that is just for release discussion.

post it to RAMBO and I'll flag Carl on R3 chat

Ask in chat or CureCode, Carl won't see the request here.

re "ask in chat or CC" - I asked in chat, privately, but do not see 
any reaction yet, and I added a comment to CC #1571

Moving to "Chat"

Yup, same reason. There was a lot of blog/ticket-comment/chat about 
this recently for R3, and what was revealed applies to R2 as well. 
Though the precedences and rules have been tweaked for R3.

It's where all the mezzanine source and fixes go: R3 chat, aka DevBase.

humm ok I'll check how to browse R3 chat later, Now if you could 
paste a copy of extract here I would be very thankfull 8-)

Isn't Ashley making a Chat widget?

problems with tooltips

 ... note that since 11-Mar these and other problems have been solved 
 in the latest RebGUI Beta 2 builds.

Isn't Ashley making a Chat widget?

 ... chat, icon (SVG) and a simple tree widget (suitable for request-dir) 
 are in development.

RTF Style ... possible to use it in Rebgui

 ... RebGUI had this initially, but it was more trouble than it was 
 worth IMHO as (a year and a half ago) TMD (Text Markup Dialect) was 
 going to make it redundant. I believe R3 includes rich-text support.

http: ...

 ... I based my %render-rich-text2.r on this code but improved upon 
 it dramatically as we (shadwolf and I) were trying to use it to render 
 MD2 and MDP documents. Remember all the MDViewer and MDP-VIewer stuff 
 that was floating around a while back? ;)

In my chat client, I use Allen's parser to create active links for 
http/s ftp etc.

and in a chat screen, you don't normally need to scroll the text 
in the reply area ..

Build 78 uploaded to SVN. Includes the following additions:

1) New chat widget

	chat data ["Bob" none "Comment." yello 1-May-2007/10:00:00

2) New on-fkey handlers

	ctx-rebgui/on-fkey/f3: make function! [face] [...]


3) Soundex spellcheck logic replaced with new algorithm as discussed 
above


4) New, smaller, dictionaries (sans soundex codes) to be uploaded 
within the next few days

5) request-font enhanced (now has multiple refinements)

6) %tour.r updated


Note that the chat widget has a known display problem when it appears 
on a tab or is resized. The fix, adding a 'show in its feel/resize, 
appears to eat other widgets resize events. Not sure if this is a 
REBOL/View bug or not. Anyone who knows of a fix please speak up!

I'm getting this on the latest chat widget, and not on the old one.

make object! [
    code: 312
    type: 'script
    id: 'cannot-use
    arg1: 'add
    arg2: 'none!
    arg3: none
    near: [text: form any [row rows: rows + 1] 
        color:
    ]
    where: 'append-message
]

Is the chat error on initialization or when you try to add a message?

Does chat in %tour.r work OK for you (Static => Chat).

I'm only creating the chat widget, and then adding messages to it.

I wonder if chat widget etc. are more important than e.g. tree :-)

hmm, first clicking the Chat tab shows underlying Box tab content, 
distorted, even if I not clicked Box tab itself ...

it can be fixed by pressing another tab, then going back to Chat 
tab. But each first display of Chat tab seems to be incorrectly drawn 
to the screen ...

the problem with the chat widget is when I try to fill it in the 
do block of the display

>> display "" [ f: chat data [] do [ f/append-message "system" none 
"test" none 1-Jan-2007 ]] do-events
** Script Error: Cannot use add on none! value
** Where: append-message
** Near: text: form any [row rows: rows + 1]
color:
>>

If I resize a window containing a chat widget, it corrupts the widget. 
 Can I link to the resize event to do a show on the chat widget?

If you look at the source code for chat.r you'll see a commented 
out show face/pane/1 and show pane/1. Uncommenting either of these 
will fix all display problems for chat, BUT, subsequent widgets will 
not render correctly as the show "eats" subsequent resize events. 
You can see this with the following code:

	display "" [
		after 1
		button "One"
		chat #HW data ["a" none "b" none 1-Mar-2007/10:00:00]
		button "Two"
	]

where button 2 is not drawn correctly.

Graham - why e.g. Chat widget appeared? Do you use it? I will have 
to look, how it communicates :-) btw - why there is the distortion 
to initial display of the widget?

What I mean is, if I use the chat widget and build a window with 
it, I don't get the distortion.  I do if I use tour.r

spellcheck ... it's certainly something I miss in ALtME!
why e.g. Chat widget appeared?
 Carl asked for it first.


Graham, back to your modal windows and BEER compatibility issues 
... does this still happen with Beta 2? The reason I ask is that 
the initial modal window implementation was poor (in large part to 
get around REBOL/View limitations); but since REBOL/View 1.3 the 
View popup system has been completely rewritten (by Gabriele I think), 
and the RebGUI implementation is now simple and "standard" (in that 
it uses the same functions as VID). It may in fact have fixed the 
issues you were having.

I have an async routine that displays all the chat messages in table 
on a panel.  This triggers in the action field of the panel, but 
even though it is async, it takes a finite time, and so slows down 
the display of the panel.

The chat widget .. can we get it so that text is selectable?

re: chat widget. I'm waiting on R3's rich text enhancements before 
I do much more with this widget.

I want write a chat system. 

 RebGui provide me the client gui. Somebody knows a chat server with 
 history?
(synapse-chat server source code is not available)

A nice feature in altme is hyperlinks in chat. ( http://www.google.com
) 
Any way to get this feature en rebGui ?

Reichart: Microsoft - "Never require users to click an object to 
determine if it is clickable. Users must be able to determine clickability 
by visual inspection alone." Hahaha :-) That one is really nice. 
It is related to AltME group chat, where I wondered, how's that clicking 
radio-button brings you to entirely new sub-screen :-)

Don't worry, I've added it as an accessor func to tab-panel and will 
upload with the next build later tonight. I've also finally nailed 
the chat refresh bug as part of implementing a new action handler 
... on-resize.

I'm not 100% sure what Graham requests about the sliders, but it 
might be the same as a feature I wanted. I wrote alot of text to 
an area with a scroller, and I want to be able to remove text at 
the top and insert at the bottom - while keeping the horizontal scroller 
at the bottom (unless the user wants to scroll up ofcourse, in case 
the scroller should stay exactly where it is). In other words similar 
to a DOS prompt with some scrollback buffer.


Can't remeber exactly what problems I had with it, but it didn't 
work as intended :) Now I'm using a chat widget instead and it works 
pretty good. Not a bad feature to have though.

RebGUI v2 RC1 (build 200) uploaded to SVN

Focus of this version has been:
	* Make it look good (color scheme based on Windows 7)

 * Take into account OS sensibilities (different corner rounding, 
 window colors, system fonts)

 * Get rid of the cruft (removal of little-used widgets and options)
	* Improve tabbing
	* Make it load and run faster



Added
	icon
	get-fonts
	confirm
	request
	request-calc
	requesst-verify
	rebface/old-color
	rebface/over?



Reimplemented
	arrow
	calendar
	drop-list
	password
	slider
	tool-bar
	set-state
	set-color



Enhanced
	chat
	edit-list
	spinner
	table
	request-char
	request-font



Removed
	question
	request-ui
	pie-chart
	symbol
	options [info no-click]
	options [arrow options]


WIP
	A disable/enable function and layout option
	Rewrite of led widget
	Rewrite of tree widget

hmm, SVN says:

RebGUI v2 RC1

Added
	icon
	get-fonts
	confirm
	request
	request-calc
	requesst-verify
	rebface/old-color
	rebface/over?

Reimplemented
	arrow
	calendar
	drop-list
	password
	slider
	tool-bar
	set-state
	set-color

Enhanced
	chat
	edit-list
	spinner
	table
	request-char
	request-font

Removed
	question
	request-ui
	pie-chart
	symbol
	options [info no-click]
	options [arrow options]

WIP
	A disable/enable function and layout option
	Rewrite of led widget
	Rewrite of tree widget

Build 207
- Fixed slider bug (zero divide error when ratio = 1)
- Added find-key-face to needed funcs when not using view.r
- Added undisplay (does what unview/only does, but better)
- request-error now accepts string
- Removed gui-error (obsoleted by request-error)
- Removed find-face func
- Cosmetic changes to:
	- led
	- led-group
	- radio-group
	- chat
- Removed tip & over? attributes
- Made init, options & old-color attributes optional
- Made action & feel objects optional

- Replaced rebface, subface, gradface & btnface with baseface & gradface
- Added over? function
- icon changed to accept file name directly

- Added action/on-time event (used in conjunction with rate - see 
anim)
- Added table & text-list alternate row coloring

Just confirmed that btn and chat widgets are included in supplied 
%rebgui.r file but corresponding widgets files are missing in widgets 
directory. I'm sure Ashley will fix it one day. My custom widgets 
work ok now with 213.

Build 214
- updated toggle (2x2 edge on select)
- added missing btn widget
- added missing chat widget
- added flash requestor
- added request-about
- renamed request-password to request-pass

Flash is used as follows:

	...
	flash "message"
	...
	hide-popup
	wait []
	...

request-about is used as follows:


 request-about/url "MyProj" 0.0.1 "Copyright (c) MyCo" "www.site.com" 
 ; or a url!


Note the logo is located in ctx-rebgui/images/logo and defaults to 
the info icon ... replace with your own logo image as follows:

	ctx-rebgui/images/logo: load %my-logo.png

Yes good idea, and if I'm not asking too much, just a small documentaion 
explaining the basic concept of 2x RebGUI, to get people (me) started. 
Currently my only reference is RebDOC and tour.r and diff-ing with 
117. For example I wanted to bring the b117 panel style (no border, 
silver background) back, I looked for some hours, and give up. Even 
some short points in this AltMe thread would be helpful. For example 
I found out how to do append-widget in 2.x through searching in google 
and found the chat history in altme.

I just want to share my modifications of the chat widget in b177, 
I needed a slimmer chat. It should also fix the resize issue:
REBOL []
slim-chat: make baseface [
	options: {
		USAGE:

   chat2 120 data ["Bob" blue "My comment." yello 14-Apr-2007/10:58]

		DESCRIPTION:
			Three column chat display as found in IM apps such as AltME.
			Messages are appended, with those exceeding 'limit not shown.

		OPTIONS:

   [limit n] where n specifies number of messages to show (default 100)
			[id n] where n specifies id column width (default 10)
			[user n] where n specifies user column width (default 15)
			[date n] where n specifies date column width (default 25)
	}
	size: 200x100
	pane: []
	data: []
	edge: default-edge
	action: make default-action [
		on-resize: make function! [face] [

   poke face/pane/2/para/tabs 2 face/pane/1/size/x - sizes/slider - 
   (sizes/cell * any [select face/options 'date 25])
			face/redraw/no-show
		]
	]


 height: 0 ; actual pixel height of all messages (-1 ensures first 
 message is offset to hide it's edge
	rows: 0 ; number of messages
	limit: none ; last n messages to display

	append-message: make function! [
		user [string!]
		user-color [tuple! word! none!]
		msg [string!]
		msg-color [tuple! word! none!]
		date [date!]
		/no-show row
		/local p y t1 t2 t3
	] [
		;	cache current tab stops
		p: self
		t1: pick pane/2/para/tabs 1

  t2: pane/1/size/x - sizes/slider - (sizes/cell * any [select p/options 
  'date 25])

		p: self
		;	get height of message
		y: max sizes/line 4 + second size-text make baseface [
			size: as-pair p/size/x - sizes/slider + 1 10000
			text: msg
			font: default-font
			para: para-wrap
		]

		

		insert tail pane/1/pane reduce [
			make baseface [
				offset: as-pair -1 height - 1
				size: as-pair t2 21
				span: all [p/span find p/span #W #W]
				text: user
				edge: make default-edge [size: 0x1]

    font: make font-top [color: either word? user-color [get user-color] 
    [user-color] style: 'bold]
				color: either word? msg-color [get msg-color] [msg-color]
			]
			make baseface [
				offset: as-pair -1 height - 1 + 20
				size: as-pair p/size/x - sizes/slider + 1 y
				text: form msg
				color: either word? msg-color [get msg-color] [msg-color]
				edge: make default-edge [size: 0x1]
				font: default-font
				para: para-wrap
			]
			make baseface [
				offset: as-pair t2 - 1 height - 1

    size: as-pair (sizes/cell * any [select p/options 'date 25]) + sizes/slider 
    + 1 21
				span: all [p/span find p/span #W #X]

    text: form either now/date = date/date [date/time] [date/date]
				edge: make default-edge [size: 0x1]
				font: make font-top [style: 'bold align: 'right]
				color: either word? msg-color [get msg-color] [msg-color]
			]
		]
		height: height + y - 1 + 20
		if ((length? pane/1/pane) / 3) > limit [
			y: pane/1/pane/2/size/y + pane/1/pane/1/size/y - 2
			remove/part pane/1/pane 3
			foreach [u m d] pane/1/pane [
				u/offset/y: u/offset/y - y
				m/offset/y: m/offset/y - y
				d/offset/y: d/offset/y - y
			]
			height: height - y
		]
		unless no-show [
			insert tail data reduce [user user-color msg msg-color date]
			pane/1/size/y: height
			pane/3/ratio: pane/3/size/y / height
			show p
		]

  show pane/1 ; !!! this cleans up artifacts but "eats" other widgets 
  redraw events !!!
	]


 set-user-color: make function! [id [integer!] color [tuple! word! 
 none!] /local idx] [
		if any [zero? id id > rows] [exit]
		poke data id * 5 - 3 color
		if limit > (rows - id) [

   idx: either rows > limit [(id + limit - rows) * 3 - 2] [id * 3 - 
   2]

   pane/1/pane/:idx/font/color: either word? color [get color] [color]
			show pane/1/pane/:idx
		]
	]


 set-message-text: make function! [id [integer!] string [string!] 
 /local idx] [
		if any [zero? id id > rows] [exit]
		poke data id * 5 - 2 string
		if limit > (rows - id) [

   idx: either rows > limit [(id + limit - rows) * 3 - 1] [id * 3 - 
   1]
			insert clear pane/1/pane/:idx/text string
			redraw
		]
	]


 set-message-color: make function! [id [integer!] color [tuple! word! 
 none!] /local idx] [
		if any [zero? id id > rows] [exit]
		poke data id * 5 - 1 color
		if limit > (rows - id) [

   idx: either rows > limit [(id + limit - rows) * 3 - 1] [id * 3 - 
   1]
			pane/1/pane/:idx/color: either word? color [get color] [color]
			show pane/1/pane/:idx
		]
	]

	redraw: make function! [/no-show /local row] [
		clear pane/1/pane
		height: 0
		rows: (length? data) / 5
		row: max 0 rows - limit: any [select options 'limit 100]

  foreach [user user-color msg msg-color date] skip data row * 5 [

   append-message/no-show user user-color msg msg-color date row: row 
   + 1
		]
		pane/1/size/y: height
		pane/3/ratio: either zero? height [1] [pane/3/size/y / height]
		unless no-show [show self]
	]

	init: make function! [/local p] [
		unless options [options: copy []]
		p: self
		limit: any [select options 'limit 100]
		; chat pane (1)
		insert pane make baseface [
			offset: as-pair 0 sizes/line
			size: p/size - as-pair sizes/slider sizes/line
			span: all [p/span find p/span #W #W]
			pane: []
		]
		;	heading (2)
		insert tail pane make gradface [
			offset: -1x-1
			size: as-pair p/size/x sizes/line
			text: "Chat"
			span: all [p/span find p/span #W #W]
			font: make font-button [align: 'left]
			para: make default-para [tabs: [0 0]]
		]
		;	set header tabs

  poke pane/2/para/tabs 1 sizes/cell * (any [select options 'user 15])

  poke pane/2/para/tabs 2 size/x - sizes/slider - (sizes/cell * any 
  [select options 'date 25])
		;	vertical scroller
		insert tail pane make slider [
			offset: as-pair p/size/x - sizes/slider sizes/line - 2
			size: as-pair sizes/slider p/size/y - sizes/line + 2
			span: case [
				none? p/span [none]
				all [find p/span #H find p/span #W] [#XH]
				find p/span #H [#H]
				find p/span #W [#X]
			]
			action: make default-action [
				on-click: make function! [face] [
					if height > face/size/y [

      face/parent-face/pane/1/offset/y: (height - face/size/y * negate 
      face/data) + sizes/line
						show face/parent-face
					]
				]
			]
		]
		pane/3/init
		action/on-resize self
	]
]

And here is a screenshot: http://uploadpad.com/files/Chat.png

To use this, just save it as slim-chat in rebgui/widgets, and then 
do create-distribution.r. It's fully syntax-compatible with the existing 
chat widget.

I posted my reaction to rebdev chat too. I am missing some aproach 
to easily traverse gui:


- there is bog/pane, but not face/pane. There is face/faces e.g. 
for panel style. If it is the same concept, why name it differently?
- there is no face/parent-face to traverse backwards

- face/gob contains just one gob. It also seems to me, that it is 
not even a pointer to the gob, but not sure. Not sure if it would 
be usefull, but currently face can't be built from multiple unrelated 
gobs. You have to have one gob, and other ones in gob/pane

Maarten - I did agree with your POV and told Carl, that RebDev kills 
Altme. But - his reply made sense to me. We should not see it as 
a threat to Altme/web (yet), so let's suppose current RebDev is nothing 
more than CVS with ability to chat to whatever topic or file ...

I was against new system, but I am satisfied with Carl's explanation 
of his POV. He needed streamlined channels for chat, bugs, CVS, filesharing. 
New system, in comparison to AltME, gives us:

- threaded discussions
- ranking
- tagging
- threaded discussions
- message/topic moving
- versioning system
- document management. Docs posted anywhere to any message.
- console version


So far, the big minus is - no GUI client. But - that might be over 
in few months ... So - if we think of RebDev as nothing more than 
RT's supporting infrastructure, I am OK with it. It is just that 
for fast dev related chat, e.g. nowadays GUI related, it can't reach 
Altme comfort and speed in not more than 20%. Threading is very confusing 
now ...

we've got 100th user to ugly console rebdev chat :-) so - we are 
growing :-)

no I have so litle time to play with R3... I barely have time to 
chat here...  life, work, kids, music, glass, et al... life is full 
enough withough R3 yet  ' :-/

Well, this is one of those functions that *has* to be as bulletproof 
and efficient as possible. Even Carl defers to my judgement on LOAD. 
I try to make it easy to read, but there's no point about worrying 
about lost comments when the source is a CHAT 26 LF away.

You appear to be doing a very good job of it, overall, don't get 
me wrong. I wish you'd see my point of view with respect to other 
(future) users who will view the code in the console, not in some 
source file locatable somewhere if you're lucky and the RebDev chat 
server is still running.

Geomol - I have to object. Before complaining about the way the projects 
is run, please check the following:


 - do you really understand, how the project is being run at all? 
 Because quite frankly, you are not using fair arguments here imo. 
 I can agree, but only to some extent, that things are being done 
 in a chaotic way. But - being close to Carl and trying to listen 
 to him and COMMUNICATE with him, I can understand the aproach he 
 takes. 


- one of your false arguments is, that putting things into CureCode 
is not helpful - CureCode was chosen by Carl and the community as 
a streamlined channel for bug reporting. Now please don't tell me, 
that even some low level bugs are not reported? There is a changelog 
which simply proves you being wrong.


- Before some releases Carl asks BrianH to change CureCode items 
rating to fix most important stuff - so how comes that our aproach 
does not work? Please post bug reports, talk to Carl or BrianH to 
raise the importance - doesn't following section show we finally 
got our requested - release early, release often?
http://www.rebol.net/wiki/R3_Releases


- and to be honest - you are one of persons being added to the r3-gui 
world. Some time back Carl had to add even lamer like me to the list 
:-) - and you know why? Because he was not getting much of response. 
He nominated top community gurus to help with the GUI. Actually, 
the same happened during the Gab's VID3 project - only me, Henrik, 
and BrianH commented. It seems to me that some ppl prefer to chat 
about science and belief systems instead of helping to develop R3 
;-) (I am not dismissing anyone's right to come here to chat about 
anything - this place is really a rebol pub where we meet, but the 
other worlds were specialised, yet lacked the input from community, 
even if asked for help)


- in order to get more ppl involved in R3 development at native level, 
it is clear where do we need to get - we've got R3 chat to be base 
of new Altme, new BBS, new DevBase. In March plan Carl clearly outlined, 
that in order to get sources out, we need rebin, plugins. They are 
now postponed due to modules, security, but still a high priority. 
How do I know? Because I was not lazy and asked Carl the specific 
question.


- we also get improvements on other fronts - we have got new streamlined 
Docs. I suggested Carl to add community section, then also new R3 
section to rebol.com page and to produce detailed changelogs. These 
all are small steps, but steps which make a difference.


Now please tell me - how complaining here can make situation any 
better? How many bugs have you posted, how many rebdev messages you 
have asked to Carl? Why don't you talk about your concerns with Carl? 
He will respond to you, like to me or anyone else - either via chat, 
or via a Blog article.


As for me, I am quite fine with how R3 is progressing last few months. 
Yes, we are slow on the whole project, but we are still doing a good 
progress imo.

If you don't watch Chat, you probably also missed Carl's info - he 
is working on a list of items, which will turn R3 into beta.

Geomol - never mind, some old ppl left, some are not so much active 
anymore, some new are popping up. You also maybe don't understand 
current Carl's plan, which might look chaotic, but under the surface, 
there is very concrete plan. E.g. - some really important functionality 
moved into mezzanine level (load, codec system), and there are being 
added strong enhancements, which much improve REBOL's low level reflectivity 
and correct behaviour. BrianH puts lots of his energy into it. This 
is all cool stuff, you would just have to stop be worried about Chat 
console :-)

I attracted Bobik to R3 once again. He was waiting, and waiting, 
and then he went into pissed off mode. So I told him to concentrate 
upon R2 (he is now using RebGUI) and Python, and just take R3 as 
- "might be" a good thing in the future. We now have good chat about 
the progress, and there IS a progress, although it might seem to 
be slower than we might wish for ...

And the only thing more important to code organization than modules 
is a good developer communications infrastructure. It has been a 
real boon to have the new chat and DevBase.

Gabriele, a lot of the development process *is* open. Check chat/DevBase 
for details.

chat intergrated i found it complicated to use

Yes, chat is complex to use, though I find it more useful than AltME 
overall, even in text mode. When we get the GUI it won't even be 
harder to use. That's why we need modules - the code needs reorganization.

BrianH: thanks for doing fantastic work here - on every front - real 
developments, testing, prioritising, and explaining here ... Now 
it is even more clear to me, that ppl complaining about lack of development 
are not well informed about the project structure, but it is everybody's 
responsibility to try to be informed - it just needs log-in to Chat 
system, watching blogs, etc. I can understand, that ppl are busy 
with some other things, but then I really suggest to sit and wait, 
as those ppl that contribute, can't work any faster. As can be seen 
even from this single discussion - each developer has his own priorities 
for things to be fixed/finished first, but anyway - R3 is progressing 
well from Alpha to first beta being here in 2009, even if some things 
might be postponed for 3.1 ....

chat system is so complicated OMG ....

gee - what are you talking about now? Yes, there is Chat, which is 
more a unified replacement of some altme worlds and DevBase CVS, 
but - by info I also mean blogs, bugbase, detailed release notes, 
new docs with changelog, whole rebol.com R3 section, detailed month 
plan focus. I don't want to participate into this discussion anymore, 
as it is really rudiculous ....

ok, to get the protocol in a few steps: start r3, type "chat". type 
"more 3365"

PeterWood:R3/GUI/General>> more 3365

 ** Script error: submit-of? does not allow none! for its fid argument

 ** Where: case all submit-of? case what-file? more-file parse try 
 either either forever command-loop make context do catch applier 
 do try chat
** Near: case [

    is-submit? msg [msg]

    is-name? msg [submit-of?..
.

--- Note: unexpected error logged to error-log.txt

PeterWood, chat still segfaults here on OSX, so I can't test the 
bug.

Henrik. Try re-starting Rebol and then use chat. I have found that 
chat only segfaults once a certain amount of memory has been used.

Maybe once we have a usuable GUI wrapped around dev chat it might 
be easier to follow what is going on ... but it's a bit of a black 
box to me now.

Henrik. I only get the seg fault if I use a lot of memory or try 
to use a scheme before running chat.

Attaching Instruments to a running R3 works. But it shows no leaks 
when entering Chat.

PeterWood, I get a different crash from what you had before now. 
"N" when you are guest, right after starting chat.

Try this:

chat
3415
more 3365

shadwolf:R3/OS-Targets/OSX>> more 3365

** Script error: submit-of? does not allow none! for its fid argument

** Where: case all submit-of? case what-file? more-file parse try 
either either
forever command-loop make context do catch applier do try chat
** Near: case [
    is-submit? msg [msg]
    is-name? msg [submit-of?...

--- Note: unexpected error logged to error-log.txt

Don't worry, we all have the script. It is the error in the Rebol 
chat program we are discussing.

hmm... here's a fun one: decompress read http://www.rebol.com/r3/chat.r

Gobbles up memory and just hangs.

I think I have a fix for the guest N bug in chat.

The "more 3365" error in chat is because we are not under the correct 
topic, when trying to get that file. I will try to figure out how 
to fix that.

do http://rebol.hmkdesign.dk/files/chat.r

BrianH: do we post R3 beta item list somewhere here in non web-public 
group, or we keep the link in Chat only?

We're public now. If it is really important that it be quiet, use 
private chat here or in R3 chat.

Steeve - I posted read/text follow-up to codec Chat section. I really 
don't like it. I added even your question about ports. I think, that 
Carl is trying to make his life easier =  give me some whole C code 
for particular format, I will pack it with REBOL via tiny interface.

Then to be hones.. I use R3 chat every day, but don't know, where 
are the files:)

Anton, we are trying to come up with sensible defaults for all of 
the options. Get in on the conversation in R3 chat :)

R3 chat. No more R3-Alpha world.

james, we use the R3 chat built into R3 now.

Download R3. Copy it to a directory of your choosing. Run it. Enter 
the "chat" command.

I smell some problems towards Rebin :-( ... Carl points something 
in Chat ...

I would also like to ask about one Carl's Chat message, describing 
DELECT. Do I understand it correctly, that first Carl thought that 
DELECT might be used for some interfacing, but that DELECT is kind 
of functional/procedural aproach which does not fit the concept, 
and hence instead Carl is considering action! kind of aproach?

is Chat down again?

On the new R3 GUI document: I think the new guides and layers concept 
will work much better, but of course it depends on the implementation. 
I've asked a range of questions in Chat to get some more information.

Currently,  i have a crash  when i start the chat with r3-a48 under 
Vista.
Obviously, i can't see what is the bug, 

And when i try with the previous version i got  (a42)
i got this error: 
--- Note: checking for new messages

*** RebDev Error: server connection failed, is server down? (server-failed)
** Script error: cause-error-here has no value

** Where: error if unless request-serve if check-msgs check-new make 
context do
catch applier do try chat
** Near: error result


We have no way to return in a safe situation and can't guess what 
is the bug indeed.


Is Carl aware of that problem, i didn't see anything related to a 
crash of a48 when starting the chat ?

Ladislav, I've made the case for your FUNCTOR in R3 chat #3726. Join 
in on the discussion if you like.

now that we have FOREACH on objects, it could be a good time to ask 
on the blog or in chat.

The two biggest things blocking contributions:

1. We need to release the host code so people can fix platform-specific 
bugs.

2. The GUI infrastructure is just not in good enough shape to handle 
contributions, at least from a code organization standpoint.


There are people who won't participate at all because there is no 
GUI client for R3 chat (which sounds completely ridiculous to me), 
and in some cases we really need those people's help (ironically 
enough, not always for GUI work). For that and many other reasons, 
the GUI is a huge priority in the short term.


And we *really* need to release the host code, or platform-specific 
bug-fixes and enhancements won't happen.

There are people who won't participate at all because there is no 
GUI client for R3 chat (which sounds completely ridiculous to me), 
  

I'm suprised that so many people are happy to work with a non-gui 
client.  If one asks for volunteers to spend their time, and create 
a retro environment for them to work ... you're not going to get 
the optimal result.

Don't take it personally if something sounds ridiculous to me - I 
don't consider my opinion to be common.


We needed the infrastructure in place for collaborative development. 
What we were using before (AltMe, DevBase 2, traditional revision 
control systems) had failed us - we couldn't scale past about 5 developers 
before the process fell apart. That's why the R3-GUI AltMe world 
was created.


Even in text mode, R3 chat and DevBase 3 have been a huge success, 
as the many releases of R3 in the last few months have shown. We 
needed contributions to get R3 to the point where it is now.

I've asked on chat.

I just see little point in submitting bugs.


If you are talking about bugs in stuff that is mostly designed but 
not fully implemented (like money!, or maybe vector!) then they are 
worth reporting if they haven't been reported already - just don't 
expect an immediate fix, since we may not be working on those yet.


If you are talking about bugs in stuff that is still being designed 
(like the GUI) then reporting problems in R3 chat is better. 


If you are talking about bugs in stuff that hasn't been designed 
yet but may have a placeholder (like task! or utype!) then don't 
bother.

It would be good to probably ask Carl on Chat, no?

I have difficulcy to get Chat files. I do nf, to list new files, 
then I submit get * but nothing is synced. I try other aproach, going 
to e.g. R3 mezzanines section, and doing get * does either report, 
that there was no change to files, or that my local copy is changed, 
and hence it can't be synced. I am sure I did not do any local changes 
here ... So - how do you usually work with Chat file facility?