2- Offer a configuration option to tell the editor not to use the image upload feature. This would hide or show the 'image upload' button in the toolbar.
Something like:
oFCKeditor.WithImage = true/false;
3- Offer a configuration option to tell the editor not to offer the 'server browsing' support in the image upload popup window. This would prevent the end user from browsing the server directories, and also, from creating sub directories. No 'Create a sub directory' button would be displayed. The user would only be able to upload images in a directory specified by the developer.
Something like:
oFCKeditor.WithImageServerBrowsing = true/false;
4- Offer a configuration option to tell the editor which toolbar buttons to hide. This would display all the buttons of the current toolbar, except the ones listed in this array. Often, one is satisfied with the default toolbar, but just wants to remove one or two buttons from the toolbar. It would make it easier than to have to redefine a complete toolbar.
Something like:
oFCKeditor.HideButtons = new Array('Source', 'Save');
5- Offer an 'Internal link' button. This button would open a popup window in which the end user could select the link href value from an html select list. It is a very usefull feature to prevent the end users from manually typing in the value of links pointing to pages stored on the same server.
Something like:
oFCKeditor.UseInternalLink = true/false;
oFCKeditor.InternalLinkList = new Array(
new Array('Home', 'relative/url/to/home.php'),
new Array('Contact', 'relative/url/to/contact.php')
);
6- Offer a 'Resource' button. This button would open a popup window in which the end user could select a resource file like a Flash .swf file sitting on the server. Something that would work like the image upload feature.
Something like:
oFCKeditor.UseAsset = true/false;
Something like:
oFCKeditor.WithImage = true/false;
3- Offer a configuration option to tell the editor not to offer the 'server browsing' support in the image upload popup window. This would prevent the end user from browsing the server directories, and also, from creating sub directories. No 'Create a sub directory' button would be displayed. The user would only be able to upload images in a directory specified by the developer.
Something like:
oFCKeditor.WithImageServerBrowsing = true/false;
4- Offer a configuration option to tell the editor which toolbar buttons to hide. This would display all the buttons of the current toolbar, except the ones listed in this array. Often, one is satisfied with the default toolbar, but just wants to remove one or two buttons from the toolbar. It would make it easier than to have to redefine a complete toolbar.
Something like:
oFCKeditor.HideButtons = new Array('Source', 'Save');
5- Offer an 'Internal link' button. This button would open a popup window in which the end user could select the link href value from an html select list. It is a very usefull feature to prevent the end users from manually typing in the value of links pointing to pages stored on the same server.
Something like:
oFCKeditor.UseInternalLink = true/false;
oFCKeditor.InternalLinkList = new Array(
new Array('Home', 'relative/url/to/home.php'),
new Array('Contact', 'relative/url/to/contact.php')
);
6- Offer a 'Resource' button. This button would open a popup window in which the end user could select a resource file like a Flash .swf file sitting on the server. Something that would work like the image upload feature.
Something like:
oFCKeditor.UseAsset = true/false;
RE: A few suggestions for improvement
3- : dito. option available : FCKConfig.ImageBrowser = false ; (config.js)
4- : just remove the unwanted buttons from the config.js file.
5- : just modify the link dialog page
6- : flash support is being planned for RC3 / FC