Cool-Cat
Posts: 9
|
| Posted: 11/16/2007, 12:33 AM |
|
CCS, for me, has a reputation of lack of depth in testing. Considering the complexity of a general purpose tool CCS needs much more structured testing. I find that I can not update from 3.1 to 3.2 of any version due to style sheet conversion problems.
This, in my book , is a big blunder by CCS ref their testing methodology.
The CCS product, when stable, is still the best but I have always thought that the weakness lay in the complexity and depth of their testing.
This style sheet conversion problem appears unresolved and attention is drawn away from resolving these problems with the release of CCS4. How can I justify CCS4 when issues are not resolved with 3.x?
New projects have to start with the old 3.1 version but this leaves a project conversion risk.
Due to current conversion scripting bugs in style sheets I have to avoid ALL custom CSS changes else I find Font_User.xml errors with buttons and custom font sizes. BTW: Alt+C for Cancel, while clicking the 'contact support' dialogue OK button, gets you out of the eternal loop in the scheme designer.
It appears as if the numerous increase in issues raised with style sheets is being ignored during CCS4 development.
Now, I don't mind sharing my project detail to resolve this but I do have serious concerns over commitment to resolve real bugs and problems with the IDE/GUI generator code.
I have commercial justification to get this resolved.
Let's not get exited over CCS4 because it will probably introduce only more unresolved issues.
IMO, this is a tragic error of judgement.
I do not bother with purchasing support to resolve CCS's own problems. I have full multiple backup methods and will downgrade to 3.1 and not use 3.202, 3.2.04 or 4.x.
Living in hope for better structured testing.
Anton Hinxman
_________________
A consultant contractor with 20+ years service now breathing life into legacy applications with CodeCharge Studio. You won't find better or simpler than CCS ? |
 |
 |
|
