World: r3wp

yes tagging is an even better solution. it could even replace much 
of the current fields, if done associatively, using a two column 
tag -> id  table..

three columns if you want to store the date at which the tag was 
set.

Updating Cheyenne version on CureCode server, all sessions will be 
closed.

Upgrade done.

Doc, could you sort the change log lists by ticket ID? They seem 
to be random now.

BrianH: I'll add that. I'm working on fixing a few UI issues on CureCode 
(mainly on stats page).

I miss very simple graph on the main page, exactly the one showing 
what RT's blog shows - showing completed, opened and waiting tickets. 
Current graphs are nice, but it takes longer time for me to understand 
it. E.g. why are not dismissed tickets part of completed tickets? 
I know that it would mean double categorisation, but then I propose 
dividing table into 3 sections, waiting, opened, closed, or at least 
two sections - opened, closed ... and part of the closed would be 
- complete, dismissed, tested, and their subtotal. What do you think?

I want the more detail - the distinction between dismissed and complete 
matters.

there are graphs in curecode now?

Yeah, check the Main page.

neat. never saw that before.

are they generated with AGG? the fonts are really nice looking.

Probably :)

BrianH: noone wants distinction between dismissed and completed being 
removed, it could be subgrouped. But that way, it is a bit difficult 
to quickly get clear view, of how many tickets are being regarded 
being finished, and with how many tickets there is a chance someone 
will look at them, correct or implement. Simply put - when I looked 
at Carl't graph, it gave me clear status of overall R3 development. 
6 months CureCode status is no clear indication about the concrete 
state of the project.

People still review the completed/dismissed tickets - not as often, 
but it happens.

I agree with Pekr about the need of a simple and global graph.

Graphs are currently generated using Google Charts API.

They look nice :)

Weirdness on http://curecode.org/rebol3/: Twice today I have noticed 
people changing descriptions of tickets after they were reviewed 
or tested, people who don't have admin privileges, afaik. Has there 
been a change to CureCode recently, or have new admins been added?

No changes recently. Can you give me the changed tickets ID?

Hmm, the stats page has been removed a week ago waiting for fixes. 
That's the only change done recently.

I've done a lot of fixes and improvements on the stats page so I'll 
put it back online tomorrow. I've also pulled CureCode out of the 
quirk rendering mode, so a lot of CSS have been changed to keep the 
look as it should be. The result is an improved CSS support for Gecko 
and Webkit, but I gave up on IE8 (can't fix table inner borders).

It looks to me that the only way for proper table border rendering 
in a cross-browser way is replacing them with DIV tags.

I would like to propose some enhancements:


- having to manually always select particular ticket-view category 
and project name in changelog section, becomes kind of denerving, 
once you have to do it several times a day

- hence I propose to extend user-profile settings, where we can preselect 
such things. If it is more complicated effort, I vote to change default 
ticket view from "my tickets" to "most recent reports" one

The default ticket view for anonymous login shows up as Most Recent 
Reports in the dropdown box, but is actually Recent Changes. The 
first thing I check when going in anonymously is Recent Changes, 
but either default would be fine if the dropdown and display matched.

BrianH: Ok, issue fixed in the new version (not yet released).

In case you were curious, the reason I go in anonymously is to check 
to see if there has been any changes. Only if there is something 
that needs some action on my part do I log in.

Pekr: I'm looking at thoses features to see if I can add it easily 
now (or postpone it in a future release).

BrianH: that's how it supposed to be used. ;-)

I've been trying to add categories, but keep getting hampered by 
problems with rearranging the categories in the dropdown when more 
data leads to more categories. I've had to clear the category list 
in whole or in part several simes, then recategorize tickets.

I noticed that the first category in the list gets selected by default, 
so I cleared the list and added an Uncategorized category first then 
readded the rest of the categories back. Later I came up with more 
categories to add in the middle. Eventually I had to give up for 
a while - too much work.

It would be easier if the order in the dropdown list was a separate 
field from the order added, then add little up/down arrows or something 
to the management page. That way you can rearrange the dropdown list 
without needing to recategorize tickets.

Having a default Uncategorized category (however you want to name 
it) would help too.

I agree. I'll look into that too to see how much work it would require.

That kind of thing wasn't hard the last ttime I did it for another 
site :)

looks like the charts aren't working?

They are not back, I didn't released the new version yet. I'm still 
implementing the features asked by Pekr and Brian.

Changelog : 0.9.9 - 26/07/2009

	o FEAT: Prefered filters and project can now be user-defined.
	o FEAT: Categories order can now be set by admin.
	
	o FIX:   Stats charts are now correct.
	o FIX:  Default filter in anonymous mode works now correctly.
	o FIX:  Switched from HTML quirk mode to correct doctype.
	
	o LOOK: Fixed borders issues in CSS (except for IE8)

CureCode will be down for a few minutes from now for upgrading files 
and the database.

Upgrade done. If you had a previously opened session on CureCode, 
you have to close it and log again.

Pekr: you can now save your filter and project settings using the 
new button in "Profile" page. On new session, you'll get back your 
last saved settings.

Brian: You can now play with the new ordering buttons for categories. 
;-)

For a long while, "Most Recent Reports" and "Recent Changes" produced 
identical results here, but works properly now. Is that part of the 
fixes above?

It's not in my Changelog, so maybe I did the fix but forgot to note 
it.

As this release marks the end of the "quirk mode" era for CureCode, 
you may found some minor rendering issues here and there. If you 
think that it has to be fixed, please report it here.

is there a status on the API?

The API hasn't changed since the first release. I guess that no one 
is using it.

I might give it a shot at some point. We also need an R3 native client 
to connect to it eventually, so I might want some practice.

Category order setting works great. The new layout has more padding 
on Chrome than it did before (I may be wrong about that), but looks 
good to me. Great stuff! :)

Today, CureCode on Chrome looks like it does on Firefox: No extra 
padding, white grid separators, nice. Must have been a cache issue 
yesterday. Good work, Doc :)