World: r3wp

CureCode also requires a DB backend (currently MySQL). It could be 
adapted to other DB engines, there's just one file to adapt (%private/db-abstract.r)

The Test project is filled with 10'000 fake tickets (generated by 
a rebol script included in the archive).

would be nice to go rebDB or similar.

what is the license?

see line 2 ;-)

are you planning a VID frontend?

I'm not sure it could work with rebDB because it requires a DB engine 
being able to work with several clients in different processes (a 
DB server engine). AFAIK, rebDB is not suited for that job..anyone 
can confirm or not ?

yes, rebdb is is single process ready only. No server mode ...

VID frontend : well I'm planning a modular kernel for CureCode allowing 
exposition of services (web or reb-services), so that anyone could 
integrate it partially or completely in any app (Web,View, console, 
etc...). But not in the short-term, I'd like to make a generic framework 
to support such features.

that would be so nice. I was working on a VID based bugtracker once, 
but it was poorly done and caused more trouble than good. I'll be 
sure to test this when I get more time as I really need a bugtracker 
for my projects.

There's still several important features missing (like full-text 
search), but it's already usable for real projects.

I'll test CureCode online a few days before using it to track Cheyenne 
and my other projects bugs.

In the meantime, I'll add the most important missing features.

Hi Doc,    Very nice. And fast!        From first look here are some 
questions:

1. Is it possible that an option is don't allow comment editting 
or delete since this is the full audit path for resolution?

2. Can it add journal items to record who changed what when they 
use "Edit Ticket"?

Hi MikeL, thanks for your feedback.


1: Only the author of a comment can edit/delete its comment, no one 
else can. See http://softinnov.org:8000/curecode/ticket.rsp?id=10005#comments


2: Definitely a useful feature that I would like to add asap. (added 
as a feature request in CureCode project).

So,this is a bugtracker for itself or for Cheyenne?

Ok, just scrolled down ...

it's a standalone product that needs Cheyenne and MySQL to run. Maybe 
one of the future flagship product for spreading Cheyenne...;-)

Easy enough to change to postsgresql ?

For an SQL expert, it shouldn't take more than one hour, I guess. 
Maybe even less, I didn't counted how much MySQL specific syntax 
or functions are used.

I'll give it a try tomorrow, I've finally got my new linux virtual 
box working with postgresql.

I'd like also to support sqlite in the future. It would be easier 
and smaller when I'll need to package Cheyenne and Curecode together 
;-)

you can download linux vmware with postgresql working ...

Tried to register and got this:

> RSP Error Trapped<

Error Code : 	303
Description : 	script error !
answer? expected reference argument of type: string

Near : 	[if not denied?: any [ all [ params/pass <> params/pass2 
"Both passwords don't match" ] all [ "Unknown user" <> identify-user 
params {This Login ID already exists, please choose another} ] all 
[ not find params/email #"@" "Invalid email address" ] all [ not 
captcha/answer? params/code session/content/captcha-text "Wrong Captcha 
code, please try again" ] ]]
Where : 	protected-exec

btw, this is a nice effort doc.  :-)

Gregg: strange error, never got it before. It's like you went to 
the registering page and waited 20minutes for the session to expire, 
then submited the form...Could you please try to register again ?

Graham: thanks for the info.

I didn't have cookies on for softinnov, but turned them on, and still 
get the error.

Browser is FF 1.5.

Fired up a fresh instance of FF, and it worked there.

Please add a ticket about that error in CureCode, I'll try to find 
a FF v1.5 to try to reproduce it.

I registered okay, FF 2004

.

Curecode new release : 0.9.1 - http://softinnov.org:8000/curecode/

Changelog:

	o Localization framework (english and french catalogs provided).
	o ChangeLog page added.
	o Ticket history added.
	o Tickets list sorting added.
	o Numerous bugfixes (see CureCode project)
	
Needs Cheyenne 0.9.16 (to be released soon).

Package download URL : http://softinnov.org/dl/curecode-r091.zip

Looks like there's some bugs in the online version with localization 
(french browsers get a mix of french and english).

Seems to be ok now after a reboot.

Looks nice.  I noticed that on column sorting, depending on the sort, 
columns resize differently.

I'm far better at REBOL coding than at CSS, at least, with REBOL 
(or any decent language), I can predict the behaviour...;-) If anyone 
knows how to fix such things in a cross-browser manner, I'll be happy 
to know.

If you want to see the french translation of CureCode, just add french 
language in your browser language options (and ensure that it appears 
first in the list), or...just use a french browser version ;-). By 
default, the lang is controlled by the browser, but it can be overloaded 
by the application if required (next release will add a language 
option in user profile).

Curecode needs new Cheyenne ?

ie. unreleased version?

Nenad, why build this, as opposed to use Trac, or RAMBO?


(sometimes people think I'm being sarcastic when I ask such questions, 
but I'm genuinely curious what your logic is).

It's a demonstration of Cheyenne

Hmmm. teach me...how does this demo Cheyenne, I'm missing the connection...

Needs Cheyenne 0.9.16 (to be released soon).

Graham: yes, the localization framework has been added to 0.9.16, 
so CureCode won't work on 0.9.15.

CureCode is built using the RSP engine provided by Cheyenne.

Reichart, it's a good and logical question. There're several reasons 
:


1) To have a real application to test the concepts and implementation 
of Cheyenne's RSP engine. It has proved to be really useful in helping 
me see the gaps and find bugs in RSP engine.


2) To demo the features of RSP framework and Cheyenne's performances. 
(CureCode is really fast !)


3) RAMBO is very limited (able to handle only one project), the bugtracking 
part of Trac is quite limited too (compared to more popular products 
like Mantis or Bugzilla). Mantis was my favourite one but it's badly 
coded and failed once loosing all my tickets! So CureCode will gave 
me a lightweight Mantis-like solution for all our bugtracking needs.


4) I want to be able to build such kind of web application in just 
a few days. So I need to study each steps of the full creation process 
to see how some parts could be automated by a smart framework.

Good reasons, and I agree, the best way to do this.
We nee da universal XML export import with ID compare.  



In other words, CureCode needs to be able to export itself as XML 
(Easy).
It needs to import XML (Easy)


It needs to import XML and update the old XML keying on some ID value. 
 Not so easy.


Once done, building things like RSS feeds with just the top 10 recent 
changes becomes easy.


Also, then we can sync Qtask and CureCode.  There are a lot of cool 
side effects though…


-	We have an integrated file share, so you can link to screen shots.
-	Qtask has the ability to have conversation about each issue.
-	You can throw your issues onto a calendar view.


I know this is not your concern right now, but this is the direction 
we are going in, and need to learn how to best allow this type of 
integration.  Much as you have made one thing to test another, we 
have the same problem constantly.

R: if both QTask and CureCode are Rebol, why the need for the XML 
middle man?  Especially when Rebol exchange data is more versatile 
than XML.