World: r3wp

Sunanda: you can use tabs now to indent your code, they will be rendered 
as 4 spaces. Inserting <pre> tags is possible, I'm making a quick 
try at adding it right now.

Thanks.

Is tab the best choice? It's not easy/obvious how to type a tab in 
a webpage; though it's a good choice if you assume we are cutting'n'pasting 
from a text editor.

Right, the purpose was better support cut&pasting from a text editor.

Btw, HTML tags are allowed in comments. ;-)

Now, that's good!

But <pre> rendering doesn't look that good due to <br> tags insertion. 
I need to make the view encoding rules smarter.

Can you use 4 spaces directly to indent your code?

You mean in my own text editor?

No, I mean in code submissions in CureCode comments (rather than 
the example code section). I often type the code directly in the 
text field, and can't use tabs there because they are used for navigation.

I'm talking about output processing by CureCode itself.

Basically the same thing as "you can use tabs now to indent your 
code" but with spaces.

Ok, so your proposing to encode every 4 spaces sequences so that 
they are taken in account by the browser?

I don't know. Accepting pre tags in the input (with no attributes) 
would work too, I guess. I just know that I never post code from 
a text editor into CureCode comments. Instead, it is always written 
directly or copied from the console. In neither case are there tabs 
- all spaces.

Maybe you want to have <code> tags.

What tags are currently acceptible in the input for comments, with 
what restrictions?

I've got a weird bug in 0.9.8. I don't know if this has been fixed: 
When first selecting Main and then very quickly selecting Add Ticket, 
I get the Main page when selecting the Add Ticket page every time. 
It won't stop.

Could be a cache issue with Chrome... in the mouse over the add ticket 
link it shows add-ticket.rsp, but it loads index.rsp instead, when 
clicking on it.

One enhancement request - a check box, which would allow me to receive 
comments to particular bugs, or even state-changes, so that I am 
informed, that some bug got fixed. Would anyone else find it usefull?

yes, that would be pretty nice

an RSS feed per bug

Doc, could you make the Change Log page sort in numeric order based 
on the ticket number?

Brian - your selfless? func was added as a native :-)

Yay!

>> c: repeat i 1 ['i]
== i

>> selfless? 'i
== false

>> selfless? c
== true

Nevertheless, this is where the native SELFLESS? differs from the 
mezzanine one:

>> d: repeat self 1 ['self]
== self

>> selfless? d
== true

(and now, the question is, whether this behaviour is more useful, 
than the one of the mezzanine function.)

It surely is harder to document...

I wasn't aware SELFLESS? took a word argument at all. It works consistently 
with object arguments. We may have to report this.

>> d: repeat self 1 ['self]
== self

>> selfless? bind? d
== true

(the same result)

I do not see it as a bug, necessarily, it would be much harder to 
implement it this way as a mezzanine

Just tested, and the native works correctly in all cases, object 
and word. Your first test was correct too, since the 'i tested was 
a different 'i.

yes, I know that

, while the last test result differs from the result of the mezzanine

And it's the same as the mezzanine behavior, at least in my tests. 
In which case do you find the mezzanine to be different?

>> mezz-selfless? d
== false

>> mezz-selfless? bind? d
== false

How did you create d?

see above

selfless? bind? d == true looks good to me.

In other word, as `bind? d` is a selfless context which happens to 
contain a 'self word, I'd actually _expect_ `selfless? bind? d` to 
return true.

OK, got it, good point. I'll pt that note in the ticket.

One nice thing to be able to see is a graph of the  resolved issues 
vs the submitted issues

Chris' Google Chart API Dialect may be what you are looking for. 
 http://www.rebol.org/view-script.r?script=charts-api.r

Are there additional comments to #1631?

Comment added.

Could someone add a whole bunch of versions to CureCode for the latest 
host kit? Maybe also add some provisional ones for the next little 
while so that we don't need to do this with every release.

I guess a whole bunch and then some provisional ones is maybe too 
many ;-)

106 was only out for a day before being superceded

I guess you should have been more explicit ... is anyone using alpha 
18?