World: r3wp

Both Chrome and Chromium installers put their application files in 
a directory next to the user data directory under the user's local 
settings directory. Non-admin install, no registry access except 
for setting the file associations if you like.

Try here: http://dirhael.dcmembers.com/cnu

Doc, is the CureCode "feature" severity meant ironically, as in "It's 
not a bug, it's a feature!"? If so, it would explain why that severity 
is not available on the Add Ticket page, and I would have to rereview 
every ticket I put that severity on thinking it meant "request for 
a feature". I've been marking non-bugs as dismissed so far.

I've removed it from "Add Ticket" list from the beginning because 
we already had Type->Wish for feature requests. For the severity 
field in the filters or in the ticket, I can remove it too, or we 
can keep it for marking tickets as "it's not a bug, it's a feature". 
As you like.

Rename it "By feature" or something not ambigious

Please rename the "feature" severity to "not a bug", and I will review 
the tickets accordingly. I need a way to mark tickets where people 
are reporting as bugs deliberate changes in the semantics of REBOL 
from R2 to R3. We are trying to fix design flaws in R2, so some incompatibility 
is *intended* to happen.

The "not a bug" phrasing will let people fill in the rest of the 
phrase in their heads :)

BrianH: done.

Didec: if you can think of a better (and shorter) french translation 
than "pas une anomalie", I would take it.

Thanks. Affected tickets modified accordingly. Here's the new criteria 
for applying the "not a bug" severity:

- If the ticket is a Bug or Issue and the behavior is by design and 
intention, it gets marked as "not a bug" and dismissed.

- If there is some question, comments are added saying so and the 
ticket is marked as "waiting" or "problem", depending on whether 
the question is more of a group thing or a Carl thing, with some 
leeway either way.

- If the ticket isn't deep enough it will be rewritten to reflect 
the real problem, or maybe a new ticket will be made.

- If the ticket is too broad or general, it will be marked "problem" 
and split into multiple narrower tickets.

Once a ticket is dismissed, what is the proces for it getting to 
closed?

There are a number of dismissed tickets in the REBOL3 tracker. I 
presume no further work is being done on them. The statistics on 
the main page would look much better if they were counted as closed.

I think it would be better to exclude "wishes" from the front-page 
stats too. There are a growing number of them and as they are included 
in the stats they give the impression that there are mire bugs than 
there are.

The stats needs to be fully refactored to better fit CC/R3 specific 
status list.

Anything I can do to help?

Once a ticket is dismissed, what is the proces for it getting to 
closed?
 I have been wondering that same thing (I'm the reviewer).

Carl and been in a hole generating R3 documentation so he hasn't 
been available to make policy decisions, but that would be the job 
of Carl and the reviewers (just me right now, want to volunteer?). 
However, I think "dismissed" should be removed from the stats and 
current list just like "closed", since it is useful to make the distinction 
between them for documentation purposes.

I think it would be better to exclude 

wishes" from the front-page stats too" Please don't. All requests 
for new functions or options are marked as wishes, so we need to 
keep track of those too if they aren't dismissed.

Missing functionality is a bug too, though less severe.

I entered a bug report into the Rebol3 tracker and it got duplicated 
- #645 & #646. I don't think I clicked "submit ticket" twice though 
I may have accidentally double-clicked on it.


I tried to delete #645 and followed the sequence "edit ticket"->"delete 
ticket"->"confirm ticket" but it wasn't deleted.

Doc, two requests:

- Remove the value="" attributes from the username and password input 
tags on the login page.

- Filter out tickets with dismissed status from the "Active Priorities" 
and "Worst Severity" preset filters.
Dismissed should be considered complete - rejected, but complete.

Noted. I'll make these modifications this weekend.

Is the value="" removal request related to an issue you've experienced 
with Chrome?

The value="" disables saved passwords. I don't want to have to load 
up my password database if I am on a trusted computer that I can 
just let the browser track my passwords.

Good to know. Your fixes are built on my CC developer instance. I'm 
currently adding a few more feature/fixes before releasing.

BrianH, on 21-Jan 11:16 PM you said : "Do a server-side redirect 
to a get page when you go into edit mode on a ticket or comment update."


I'm not sure to understand the "server-side redirect to a get page" 
part. When you click on a ticket ID or comment [Edit] button, you 
enter in edit mode using a GET request. What would a redirect improve 
here? Is it related to the browser Back button and client cache management?

New CureCode version released. Changelog : 0.9.7 - 11/04/2009


 o FEAT: Dismissed tickets are now filtered out from "Active Priorities" 
 and "Worst Severity" filters
	o FEAT: Current project name added to "Add Ticket" form.

 o FEAT: Reversed sort order for Versions and Categories lists in 
 admin page.

 o FEAT: Added an experimental API for getting tickets in REBOL format.

	o FIX:	Front page stats now count "dismissed" tickets as closed.

 o FIX:	Message "n ticket(s) found" fixed for localization, now translates 
 correctly in french.

CureCode API documented here : http://rebol.net/wiki/CureCode#API_documentation

Let me know if there's any bug or regression.

Source code package for 0.9.7 available at : http://curecode.org

I've started working on the "POST data lost when session times out" 
issue, but that requires some deep changes in the RSP engine, so 
this enhancement is currently postponed.

Great.

Dockimbel -- could we have some way of searching (or sorting results) 
according to Submitter name?

I just tried to have a quick scan of all my contributions to the 
R3 bugs (see discussion in REBOL3 group).
It was not easy.

I'd especially like an easy way to find FIXed bugs by submitter name......That'd 
remind and encourage me to test the ones I'd raised.

Good point, the "By submitter" filter is not fully implemented yet, 
so not really working. I've added that in my Todo list and will see 
next week if I can improve that quickly.

thanks!

Did anyone tried to play with CureCode's API yet? Should be fairly 
easy to make a VID-based popup notifier for new or modified tickets.

Looks interesting.

Should be also easy to integrate in RebDev, so you could see a ticket 
content without going in the browser. Or maybe just by extending 
the 'bugs function to accept an issue! ID and display the ticket 
in console...

We could write an example client to show how it would work?

I thought about doing that for the last release, but didn't had the 
time. I should be able to work a little on that next weekend. IIRC 
Gabriele wrote a small popup notifier app in View (was it for incoming 
emails?) with a nice slide in effect.

we still don't have an API for writing bots for Rebdev, though.

does anyone think it would be even remotely possible to write a one-time 
exporter from bugzilla to curecode?

I have a question for CureCode users : do you think that adding a 
rich text editor for Description and Comment editing areas would 
be a usefull addition? See an example of such integrated rich text 
editor in the bottom of the page there : http://www.cheyenne-server.org/blog.rsp?view=19&cmt=on

One drawback of such change would be that these fields would be stored 
as HTML in the database making them less easily usable for external 
non-HTML renderers (like making a View-based client, or integrating 
in a IDE).

HMTL can always be stripped out.

I'd rather see a possibility for wrapping code in preformatting tags. 
Rich text is not important in comments.

I don't think that rich text descriptions and comments will add much 
value. 


I agree with Henrik that  pre-formatted code (and console sessions) 
would be helpful especially if they were  displayed in "boxes".

Don't think so too.

I don't think rich text will add much value.

me to.. maybe bold and italic.. to emphasise something but not much 
beyond that

I sometimes use a few HTML tags for CureCode tickets like : <B>, 
<U>, <I> and <A>, but not much more. Having to type HTML code inside 
text areas is not a clean method, that's why I proposed an integrated 
WYSIWYG editor. But it seems not adequate to R3 users. I might add 
it as an option for our customers in a future CureCode version, thought.

yes, for links it's also helpfull.. I agree that <a href=...> or 
other html stuff inside of comments field is not that great

Doc, did you ever notice that Cure is one letter away from Curse? 
 ;-)