Dave Rexel
|
| Posted: 04/23/2004, 5:31 PM |
|
::
Yes... Textbook example of successfull transition from shareware roots to
preferred enterprise-wide development IDE.
Yes, Code Charge Studio is good and cross-platform, openly extendable as the
code is generated before our very eyes. However, what is frustrating as an
intermediate Code Charge Studio user is the lack of easy to use information
on how to extend this excellent IDE to reproduce our specialised objects
(Actions, IDE controls, pages or entire sites).
What??? say what!!! Dave you're over the top as usual. But, yes.... Once
we've tweaked a basic site design and logic we'd like a quick way as
businessmen to sell the same solution to several customers and be able to
redesign and update these installations from a core implementation. I will
not elaborate on the programs current inherent weaknesses regarding dynamic
skinning or multi-language here as this analysis is about the lack of
intermediate information on the APIs.
At a glance any major player has well documented APIs so our senior
programmers can serve up in-house Dreamweaver, Photoshop, Maya or Renderman
scripts that will initialise our specialised frameworks and we can use the
time saved to adopt the customers requirements to a greater degree. So what
of Code Charge Studio?
Brilliant and intrepid Code Charge Studio users such as Sixto Luis Santos
and Bill Noble have bravely probed the depths of the as yet undocumented CCS
API and published excellent proof of concept examples. While learning much
from the published code provided by these generous developers we still lack
an official SDK to hand to our senior programmers and thus this Code Charge
Studio is not acccepted by the very talented coders in our organisation.
Yes... the entire Code Charge Studio user-base would benefit immensely from
the release of API documentation and a plug-in development SDK. All the
major players have realised considerable advancement through the work of 3rd
parties and Code Charge Studio would not be an exception.
As a staunch supporter of Code Charge Studio since its beginning, this is
an open appeal to the Code Charge Studio producers : "We want to make and
sell them bells and whistles"... please, your APIs need to be open, and
published preferrably as an SDK.
Greetings
Dave
http://ccs.ath.cx/~ccs/Default.php
Free membership is required to view Code Charge Studio Tutorials & Examples.
|
|
|
 |
Robert Rodgers
|
| Posted: 04/24/2004, 6:11 AM |
|
Dave,
Great post. I hope that Yes Software will study it and seriously consider the actions you suggest. A lot of developers I
work with judge tools by several criteria, one is available 3rd party tools. You can get a feel for how mature and widely
accepted a tool is by the number and the quality of 3rd party tools.
rob
"Dave Rexel" <therex_spamenot@hotmail.com> wrote in messagenews:c6cch6$n2i$1@news.codecharge.com...
> ::
> Yes... Textbook example of successfull transition from shareware roots to
> preferred enterprise-wide development IDE.
>
> Yes, Code Charge Studio is good and cross-platform, openly extendable as the
> code is generated before our very eyes. However, what is frustrating as an
> intermediate Code Charge Studio user is the lack of easy to use information
> on how to extend this excellent IDE to reproduce our specialised objects
> (Actions, IDE controls, pages or entire sites).
>
> What??? say what!!! Dave you're over the top as usual. But, yes.... Once
> we've tweaked a basic site design and logic we'd like a quick way as
> businessmen to sell the same solution to several customers and be able to
> redesign and update these installations from a core implementation. I will
> not elaborate on the programs current inherent weaknesses regarding dynamic
> skinning or multi-language here as this analysis is about the lack of
> intermediate information on the APIs.
>
> At a glance any major player has well documented APIs so our senior
> programmers can serve up in-house Dreamweaver, Photoshop, Maya or Renderman
> scripts that will initialise our specialised frameworks and we can use the
> time saved to adopt the customers requirements to a greater degree. So what
> of Code Charge Studio?
>
> Brilliant and intrepid Code Charge Studio users such as Sixto Luis Santos
> and Bill Noble have bravely probed the depths of the as yet undocumented CCS
> API and published excellent proof of concept examples. While learning much
> from the published code provided by these generous developers we still lack
> an official SDK to hand to our senior programmers and thus this Code Charge
> Studio is not acccepted by the very talented coders in our organisation.
>
> Yes... the entire Code Charge Studio user-base would benefit immensely from
> the release of API documentation and a plug-in development SDK. All the
> major players have realised considerable advancement through the work of 3rd
> parties and Code Charge Studio would not be an exception.
>
> As a staunch supporter of Code Charge Studio since its beginning, this is
> an open appeal to the Code Charge Studio producers : "We want to make and
> sell them bells and whistles"... please, your APIs need to be open, and
> published preferrably as an SDK.
>
> Greetings
> Dave
>
> http://ccs.ath.cx/~ccs/Default.php
>
> Free membership is required to view Code Charge Studio Tutorials & Examples.
>
>
>
|
|
|
|
|
