World: r3wp

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 :)

Thanks to the new CSS, the look is now consistent across Chrome / 
FF / IE7, but I gave up on trying to hack the CSS to make IE8 render 
pages as the others. The time spent in making all browser render 
the same way is quite insane.

Hey Doc, is this picture of CureCode schema still current ?
http://softinnov.org/dl/DB-schema.png

nice, what's this "drawn" in?

Doc said 27-Aug-2008 in this group "Microsoft Visio"

Nope, the schema was changed a little for R3 specific needs.

I didn't had the time yet to update the picture.

I'm interested in the "logs" table. It records changes to tickets 
once they are created, right?

Right, it records every event for each ticket (including creation).

If a new project is created, does that go into the logs table?

(as an example).

In the "tickets" table, there are several foreign key fields of INT(8) 
which link to tables with ids of INT(16), eg. severities.
Is that just an oversight?

New project => not logged, only tickets info are logged.

That's a typo, it should be INT(16).

Ok, that makes sense. So does the "field" field of the logs table 
tell which field of the tickets table was changed?

If so, then when several fields of a ticket are changed at once, 
does that generate several log entries in the logs table?

That is what the log at the bottom of the ticket shows, Anton.