It seems to me that you are only removing some items from the toolbar at creation time. Wouldn't it be easier to set up two toolbar configs in the fckconfig.js file and then when you create the editor choose the right one? or use different custom config.js files for each group of users?
Yes you are correct and also there is a point of scalability,but think like how many of the configurations we have to set and the count will increase as the user group increases and also the worst case would be sometimes we will need to remove only one or two items so for that, we have to write a separate toolbar and in this case maintanence is also going to cost in anyway , so I thought the neat solution would be to give the list of items that has to be removed while startup,and there will be a single toolbar specification to make the maintanence cheaper.
Hope this helps and also thanks for your comments Alfonso.
In my apps, I have found some variations are easy to define, i.e. some of the buttons tend to cluster and can be treated as a group, reducing the number of options that have to be porvided. My basic groupings, each of which represents a custom toolbar configuration, are font formatting, text formatting and paragraph formatting.
My app supports bibliographies (among other similar types of data)
The first level, font formatting, is used for author's names etc. where I need special characters only (plus the basics like Source) -- and where I especially do not want to support anything to do with paragraphs.
The second, text formatting, supports changing the appearance of the entered text, typically for titles: bold, italics, super and subscripts, etc. plus everything from the first. Again the assumption is. that the character string is a single line (even if wrapped)
The third, paragraph formatting, adds support for lists, indenting, etc. useful for annotations.
This covers most situations, although some other apps of mine do have a special configuration for a specific need.
So I have been able to avoid managing switches on every possible combination -- what I would like to see, however, is a way to preserve these toolbar definitions in an outside file that gets included into the config file so I don't have to copy and paste with every new release. That would be a great help.
Thanks for the comments , I liked the JSON serializing of the toolbarsets and I have planned to implement that.Then I have some features to implement in the Image browser too,like we have some private folders and shared folders so is there any plugin available to move the files between folders?? or I have to implement that??.That would be a great help for me , thanks in advance.
You can check the patches and plugins section. Depending on your server languages and the features that you want you might find something that fits your needs.
RE: Dynamiclly Add and Remove FCK Toolbar ite
Wouldn't it be easier to set up two toolbar configs in the fckconfig.js file and then when you create the editor choose the right one? or use different custom config.js files for each group of users?
RE: Dynamiclly Add and Remove FCK Toolbar ite
Hope this helps and also thanks for your comments Alfonso.
regards,
Mehmood
RE: Dynamiclly Add and Remove FCK Toolbar ite
My app supports bibliographies (among other similar types of data)
The first level, font formatting, is used for author's names etc. where I need special characters only (plus the basics like Source) -- and where I especially do not want to support anything to do with paragraphs.
The second, text formatting, supports changing the appearance of the entered text, typically for titles: bold, italics, super and subscripts, etc. plus everything from the first. Again the assumption is. that the character string is a single line (even if wrapped)
The third, paragraph formatting, adds support for lists, indenting, etc. useful for annotations.
This covers most situations, although some other apps of mine do have a special configuration for a specific need.
So I have been able to avoid managing switches on every possible combination -- what I would like to see, however, is a way to preserve these toolbar definitions in an outside file that gets included into the config file so I don't have to copy and paste with every new release. That would be a great help.
Reg
RE: Dynamiclly Add and Remove FCK Toolbar ite
http://wiki.fckeditor.net/Developer%27s ... tions_File
RE: Dynamiclly Add and Remove FCK Toolbar ite
https://sourceforge.net/tracker/index.p ... tid=543655
https://sourceforge.net/tracker/index.p ... tid=543655
https://sourceforge.net/tracker/index.p ... tid=543655
https://sourceforge.net/tracker/index.p ... tid=543655
RE: Dynamiclly Add and Remove FCK Toolbar items
Thanks for the tip about the CustomConfiguration file -- I had overlooked that feature, but now I am using it and it works just fine.
Reg
RE: Dynamiclly Add and Remove FCK Toolbar ite
Thanks for the comments , I liked the JSON serializing of the toolbarsets and I have planned to implement that.Then I have some features to implement in the Image browser too,like we have some private folders and shared folders so is there any plugin available to move the files between folders?? or I have to implement that??.That would be a great help for me , thanks in advance.
regards,
Mehmood
RE: Dynamiclly Add and Remove FCK Toolbar ite
RE: Dynamiclly Add and Remove FCK Toolbar ite
https://sourceforge.net/forum/forum.php ... _id=257180