Most of us hate to write documentation, it's just much more fun to write code....I know this...
FCK is a really great tool, and the more I work with it the more I appreciate it. Great features, great stability. And congratulations on V2.
The thing I hate most about it as a developer is the amount if time i spend picking through code and the forums trying to figure out how to do the simplest things to extend or modify the functionality because of the lack of documentation. Almost no comments in the code doesn't help much either.
I noticed that the Development Roadmap has "complete documentation" at the bottom of the list. Pleeeeeaaase move it a bit further up the list. User docs would be nice eventually (even though a WYSIWYG is pretty intuitive on its own), but what FCK needs is just a basic API doc for developers. The full power of FCK won't be unleashed, until more of us suffering coders have a couple of pages to refer to to know what the important classes and methods, etc are. An API doc will also help the community because more people will be able to answer questions and contribute to the cause.
Anybody know what parameters FCKToolbarButton takes? I guess I'm just cross-eyed from grepping through the /editor code tree to find fragments of code...
The development roadmap also says it will be guided by community requests. I'm throwing in my 2 cents.....Pleeeeeeeaaase?
FCK is a really great tool, and the more I work with it the more I appreciate it. Great features, great stability. And congratulations on V2.
The thing I hate most about it as a developer is the amount if time i spend picking through code and the forums trying to figure out how to do the simplest things to extend or modify the functionality because of the lack of documentation. Almost no comments in the code doesn't help much either.
I noticed that the Development Roadmap has "complete documentation" at the bottom of the list. Pleeeeeaaase move it a bit further up the list. User docs would be nice eventually (even though a WYSIWYG is pretty intuitive on its own), but what FCK needs is just a basic API doc for developers. The full power of FCK won't be unleashed, until more of us suffering coders have a couple of pages to refer to to know what the important classes and methods, etc are. An API doc will also help the community because more people will be able to answer questions and contribute to the cause.
Anybody know what parameters FCKToolbarButton takes? I guess I'm just cross-eyed from grepping through the /editor code tree to find fragments of code...
The development roadmap also says it will be guided by community requests. I'm throwing in my 2 cents.....Pleeeeeeeaaase?