I am hoping that someone from the "FCKeditor Team" reads this.
1) I have posted several messages on this forum but no one ever responds.
2) The documentation provided at the FCKeditor wiki page is a joke. In reality there IS NO DOCUMENTATION.
3) The official website states that they want $175 in order to respond to any email.
4) There is no mechanism for reporting genuine bugs (as opposed to 'requests for help').
QUESTION: Is the lack of documentation and resusal to respond to posts on this forum a deliberate strategy to encourage me to pay pay some money?
If so, then you you should have the decency to state that in a bold heading at the top of the forum.
---------------------
In case anyone does bother to read this, I will repeat the postI made several weeks ago.
Actually this is a BUG REPORT:
In FCKeditor 2.2 distribution there is a test case ( 010.html ) which uses code to reset the toolbar.
I have used this code, but there is a bug.
If you switch from Default to Basic, then back to Default again, the drop-down menus (Style, Format, Font, Size) no longer work. It seems that the selection is lost.
Note: this bug only occurs if you switch toolbar sets from Default to Basic and then back to Default.
code follows:
----------------------------------------
function SetToolbar( toolbarName )
{
// Get the editor instance that we want to interact with.
var oEditor = FCKeditorAPI.GetInstance('FCKeditor1') ;
var oToolbarSet = oEditor.ToolbarSet ;
// Reset the state of all items in the current toolbar.
for ( var i = 0 ; i < oToolbarSet.Toolbars.length ; i++ )
{
if ( oToolbarSet.Toolbars[i].Items )
{
for ( var j = 0 ; j < oToolbarSet.Toolbars[i].Items.length ; j++ )
oToolbarSet.Toolbars[i].Items[j].State = FCK_UNKNOWN ;
}
}
// Reset the array of toolbat items that are active only on WYSIWYG mode.
oToolbarSet.ItemsWysiwygOnly = new Array() ;
// Reset the array of toolbar items that are sensitive to the cursor position.
oToolbarSet.ItemsContextSensitive = new Array() ;
// Remove all items from the DOM.
oToolbarSet.DOMElement.innerHTML = '' ;
// Load the new toolbar.
oToolbarSet.Name = toolbarName ;
oToolbarSet.Load( toolbarName ) ;
}
1) I have posted several messages on this forum but no one ever responds.
2) The documentation provided at the FCKeditor wiki page is a joke. In reality there IS NO DOCUMENTATION.
3) The official website states that they want $175 in order to respond to any email.
4) There is no mechanism for reporting genuine bugs (as opposed to 'requests for help').
QUESTION: Is the lack of documentation and resusal to respond to posts on this forum a deliberate strategy to encourage me to pay pay some money?
If so, then you you should have the decency to state that in a bold heading at the top of the forum.
---------------------
In case anyone does bother to read this, I will repeat the postI made several weeks ago.
Actually this is a BUG REPORT:
In FCKeditor 2.2 distribution there is a test case ( 010.html ) which uses code to reset the toolbar.
I have used this code, but there is a bug.
If you switch from Default to Basic, then back to Default again, the drop-down menus (Style, Format, Font, Size) no longer work. It seems that the selection is lost.
Note: this bug only occurs if you switch toolbar sets from Default to Basic and then back to Default.
code follows:
----------------------------------------
function SetToolbar( toolbarName )
{
// Get the editor instance that we want to interact with.
var oEditor = FCKeditorAPI.GetInstance('FCKeditor1') ;
var oToolbarSet = oEditor.ToolbarSet ;
// Reset the state of all items in the current toolbar.
for ( var i = 0 ; i < oToolbarSet.Toolbars.length ; i++ )
{
if ( oToolbarSet.Toolbars[i].Items )
{
for ( var j = 0 ; j < oToolbarSet.Toolbars[i].Items.length ; j++ )
oToolbarSet.Toolbars[i].Items[j].State = FCK_UNKNOWN ;
}
}
// Reset the array of toolbat items that are active only on WYSIWYG mode.
oToolbarSet.ItemsWysiwygOnly = new Array() ;
// Reset the array of toolbar items that are sensitive to the cursor position.
oToolbarSet.ItemsContextSensitive = new Array() ;
// Remove all items from the DOM.
oToolbarSet.DOMElement.innerHTML = '' ;
// Load the new toolbar.
oToolbarSet.Name = toolbarName ;
oToolbarSet.Load( toolbarName ) ;
}
RE: I am really DESPERATE for some assistance
1) anyone can reply to any question in the forum, I try to reply to those messages that I can, but not always I want to spend some time in the forum when the people doesn't bother to come back and say thank you or help other people.
2) if you find it that the documentation can be improved then go ahead and do it, it is a wiki so you can add your experience so other people can learn.
3) I can understand that if you want personal treatment then you must pay for it. Developers don't eat air.
4) Yes, look up there in the "bugs" link.
With regards to your problem, I have tested it right now and it works for me, so I can't help you anymore. Maybe it is a problem with your browser, your setup or something else that it isn't in your steps to reproduce, but I prefer to use a static toolbar so you might have better luck if someone else has tried that code (that by the way it is marked as "This is not a supported feature but this page shows how to do the trick")
RE: I am really DESPERATE for some assistance...
RE: I am really DESPERATE for some assistance...
----------------------------
It is not so much a case of "improving" the documentation as providing it in the first place. For example, the section on the FCKeditor API has a list of functions ... and that's it! There's no syntax or examples for 90% of it.
... I don't think I'm very well positioned to author this documentation at this stage do you? Anything I would add would be pure fantasy.
Would you like me to add my fantasies to the wiki? I don't think so.
That's why I need the documentation.
I find your suggestion that I should effectively write the missing documentation kind of bizarre ...