Hello, I am experiencing the same. There is a lack of examples. I am trying ckeditor 3, and I could not do anything. There is also no tutorial about 3.x versions. And i could not find a community to answer my questions. I thought that ckeditor, ex-fckeditor, was great as lots of people were talking about it, but i am very desapointed ! jujubre
- Starting with CKEditor is an easy task. Installation,and executing the samples, and following the "Developers Guide" is simple and straightforward. There are lots of samples distributed with the installation file.
- However, going one step beyond the basic setup is hard. After some hours, I have several problems that I a not able to solve from reading the documentation (all questions posted here in the forum). The only way to answering the questions myself would be to read the code and dive deeply into the subject.
sabr...
- "addStylesSet" being just a synonym for "stylesSet.add" is an interesting information. Where would I find such a piece of information? Or is it basic Javascript know how that I am missing?
- Why isn't the documentation for the API indexed? It is rather difficult to use CKEditor, if for example "addStylesSet" is mentioned exactly once in the Developers Guide and then no other place can be found where it is mentioned again.
Maybe the Developers' Guide should be changed. It might be better to describe CKEDITOR.stylesSet.add there.
At least for me, having a more detailed documentation would be better. I do not intend to read and understand the sources. I am not going to change the source, I just want to use what is offered.
Sabr, I am already using the samples. Sharespaces and divreplace works great! If my question is poor, why nobody say it, ask me to describe more, to provide you a screen shot or more code ? For me, no answer means nobody knows. php.net documentation, there are examples. jquery documentation, there are examples. mysql documentation, there are examples. I thought ckeditor would be the same, as it is widely used... but even in the documentation page, half of the index items are still not working. So where is the "Detailed documentation", the "Full documentation, from the basics to advanced features".
Ckeditor is great fast and all that. That is why i am ising it. I am pretty confident that a solution exists. Now, I am going to find it on ckeditor's source code.
I agree that their is a great deal of frustration in finding answers to questions one has on modifying things within ckeditor. The search function within the forum is horrible and commonly used terms display virtually nothing most times.
My main frustration though is not in ckeditors capabilities but in the countless hours one spends in searching for answers here. Simple things are often hidden deep within postings or documents.
What is lacking I think on the part of the developers in terms of the documentation is an understanding of its user base itself in a real world environment. The developers are obviously extremely good at coding, but lack the ability to translate things in terms or ways that the general average user can understand, what it is they are trying to explain. Bits of code do no good if you don't know what file to put them in or how they need to be properly placed within the file.
The other part of the issue here is the user of these support forums themselves. They ask questions in a posting and once they find the answers or solutions they rarely if ever return to post that solution so people see and other users become frustrated. Please users if you find an answer to your question return and reply back to your original posting with the solution and modify the subject with [Solved] at the beginning.
Most users here - myself included know just enough to get going and maybe do some slight modifications. All we really needed is good examples of how something is done to solve the issue.
I think that we all know that the documentation needs a lot of work, but the reality is that even if the current documentation is lacking info, it includes enough info to answer lots of questions and despite that you can see new posts asking things that makes me wonder what's on their minds.
I think that it isn't so hard to understand that when there are four forums, one for FCKeditor 2.x and other for support in CKFinder, questions related to those products should be placed on those forums, and also, those forums should be used only for those products, but nevertheless, people keeps asking FCKEditor or CKFinder questions in the CKEditor forums, and they also post CKEditor questions in the CKFinder forums. This is the first symptom that people doesn't care to read anything at all, they just want someone that answers their questions without taking care to read even the location of where they are placing their questions.
Something similar happens with questions related to Drupal, or any other specific CMS. Why are they posted here instead of searching the support site for whatever integration they are using? The funniest ones are those that say that they have tried to add the zip as an extension to their CMS and it fails because it isn't recognized as a valid extension.
Then we have those that needs an answer right now!, they feel that they must bump again their topic over and over again, they won't care to try to help anyone else, they just want someone to answer their questions. Reading other topics might help them to understand their problem, but they are here just to get the answers.
The fact is that many of the questions can be answered by following the links in the FAQ: check the samples, it's really incredible the number of people that ask questions that are just as easy as loading the samples and looking at how they work. If they can't be bothered to look at the files that they have in their own computer, why should they expect anyone else to answer their questions?
And all of them sum up to make the task of writing documentation a boring task, Should I really waste even a single minute to improve a doc, write a tutorial, create a sample if people is gonna ignore it? What's the sense about trying to improve the docs?
Previously the docs in FCKeditor was a wiki open for anyone to improve it, but the reality is that only spammers bothered to write anything there, so it was just a waste of time cleaning up all that crap. If you want to add some doc, write it in your blog and I'll link it in the FAQ. If you have some info that should be added to the FAQ just tell me and I'll add it. If you think that you can edit the wiki docs, then you can ask Wiktor to give you write priviledges, but I think that it would be better if you can write that content first in your own blog and that will make it easier for him to check that you really know what you are doing and he won't have to waste his time cleaning up whatever mistakes that you have added. Managing your own blog is easy, and can be an easy way to write things that can be helpful for other people.
I've said this many times, but everyone has a different base knowledge so something that it's easy for some people it's hard for people with a different skill. For example I've skipped the questions related to PHP in the FAQ because I don't know what are the best practices there and how they should be handled (questions to magic quotes mainly) and so you can see every now and then people that say that their images look like src="\"path or something like that. And that's not a question about CKEditor, it's a question about how they should code their CMS, but they lack that knowledge and think that these forums must give them the answers.
Re: Feedback about the documentation
I am experiencing the same. There is a lack of examples. I am trying ckeditor 3, and I could not do anything.
There is also no tutorial about 3.x versions. And i could not find a community to answer my questions.
I thought that ckeditor, ex-fckeditor, was great as lots of people were talking about it, but i am very desapointed !
jujubre
Re: Feedback about the documentation
http://docs.cksource.com/ckeditor_api/s ... .stylesSet
Re: Feedback about the documentation
jujubre, my opinion is a little bit different...
- Starting with CKEditor is an easy task. Installation,and executing the samples, and following the "Developers Guide" is simple and straightforward. There are lots of samples distributed with the installation file.
- However, going one step beyond the basic setup is hard. After some hours, I have several problems that I a not able to solve from reading the documentation (all questions posted here in the forum). The only way to answering the questions myself would be to read the code and dive deeply into the subject.
sabr...
- "addStylesSet" being just a synonym for "stylesSet.add" is an interesting information. Where would I find such a piece of information? Or is it basic Javascript know how that I am missing?
- Why isn't the documentation for the API indexed? It is rather difficult to use CKEditor, if for example "addStylesSet" is mentioned exactly once in the Developers Guide and then no other place can be found where it is mentioned again.
Michael
Re: Feedback about the documentation
Re: Feedback about the documentation
Maybe the Developers' Guide should be changed. It might be better to describe CKEDITOR.stylesSet.add there.
At least for me, having a more detailed documentation would be better. I do not intend to read and understand the sources. I am not going to change the source, I just want to use what is offered.
Michael
Re: Feedback about the documentation
For me, no answer means nobody knows.
php.net documentation, there are examples. jquery documentation, there are examples. mysql documentation, there are examples. I thought ckeditor would be the same, as it is widely used... but even in the documentation page, half of the index items are still not working.
So where is the "Detailed documentation", the "Full documentation, from the basics to advanced features".
Ckeditor is great fast and all that. That is why i am ising it. I am pretty confident that a solution exists. Now, I am going to find it on ckeditor's source code.
Thx for you poor answer.
Jujubre
Re: Feedback about the documentation
My main frustration though is not in ckeditors capabilities but in the countless hours one spends in searching for answers here. Simple things are often hidden deep within postings or documents.
What is lacking I think on the part of the developers in terms of the documentation is an understanding of its user base itself in a real world environment. The developers are obviously extremely good at coding, but lack the ability to translate things in terms or ways that the general average user can understand, what it is they are trying to explain. Bits of code do no good if you don't know what file to put them in or how they need to be properly placed within the file.
The other part of the issue here is the user of these support forums themselves. They ask questions in a posting and once they find the answers or solutions they rarely if ever return to post that solution so people see and other users become frustrated. Please users if you find an answer to your question return and reply back to your original posting with the solution and modify the subject with [Solved] at the beginning.
Most users here - myself included know just enough to get going and maybe do some slight modifications. All we really needed is good examples of how something is done to solve the issue.
Re: Feedback about the documentation
viewtopic.php?f=11&t=19843
Re: Feedback about the documentation
I think that it isn't so hard to understand that when there are four forums, one for FCKeditor 2.x and other for support in CKFinder, questions related to those products should be placed on those forums, and also, those forums should be used only for those products, but nevertheless, people keeps asking FCKEditor or CKFinder questions in the CKEditor forums, and they also post CKEditor questions in the CKFinder forums.
This is the first symptom that people doesn't care to read anything at all, they just want someone that answers their questions without taking care to read even the location of where they are placing their questions.
Something similar happens with questions related to Drupal, or any other specific CMS. Why are they posted here instead of searching the support site for whatever integration they are using?
The funniest ones are those that say that they have tried to add the zip as an extension to their CMS and it fails because it isn't recognized as a valid extension.
Then we have those that needs an answer right now!, they feel that they must bump again their topic over and over again, they won't care to try to help anyone else, they just want someone to answer their questions. Reading other topics might help them to understand their problem, but they are here just to get the answers.
The fact is that many of the questions can be answered by following the links in the FAQ: check the samples, it's really incredible the number of people that ask questions that are just as easy as loading the samples and looking at how they work.
If they can't be bothered to look at the files that they have in their own computer, why should they expect anyone else to answer their questions?
And all of them sum up to make the task of writing documentation a boring task, Should I really waste even a single minute to improve a doc, write a tutorial, create a sample if people is gonna ignore it?
What's the sense about trying to improve the docs?
Previously the docs in FCKeditor was a wiki open for anyone to improve it, but the reality is that only spammers bothered to write anything there, so it was just a waste of time cleaning up all that crap.
If you want to add some doc, write it in your blog and I'll link it in the FAQ. If you have some info that should be added to the FAQ just tell me and I'll add it.
If you think that you can edit the wiki docs, then you can ask Wiktor to give you write priviledges, but I think that it would be better if you can write that content first in your own blog and that will make it easier for him to check that you really know what you are doing and he won't have to waste his time cleaning up whatever mistakes that you have added. Managing your own blog is easy, and can be an easy way to write things that can be helpful for other people.
I've said this many times, but everyone has a different base knowledge so something that it's easy for some people it's hard for people with a different skill. For example I've skipped the questions related to PHP in the FAQ because I don't know what are the best practices there and how they should be handled (questions to magic quotes mainly) and so you can see every now and then people that say that their images look like src="\"path or something like that.
And that's not a question about CKEditor, it's a question about how they should code their CMS, but they lack that knowledge and think that these forums must give them the answers.
Re: Feedback about the documentation
http://docs.cksource.com/CKEditor_3.x/D ... de/Toolbar
Re: Feedback about the documentation
Re: Feedback about the documentation