Hi,
Is it possible to hide the CSS-classes label and dropdown that appears on dialogs (i.e. on image manager/properties, hyperlink manager). Alternatively, how can I set the data source for the css-classes dropdown. Currently it loads all the application's styles and the result is awkward. The application in question cannot use styles so it is not needed. I prefer to hide it but if not possible, than set it to an empty data source.
BR,
eyal
Is it possible to hide the CSS-classes label and dropdown that appears on dialogs (i.e. on image manager/properties, hyperlink manager). Alternatively, how can I set the data source for the css-classes dropdown. Currently it loads all the application's styles and the result is awkward. The application in question cannot use styles so it is not needed. I prefer to hide it but if not possible, than set it to an empty data source.
BR,
eyal
7 Answers, 1 is accepted
0
eyal
Top achievements
Rank 1
Rank 1
answered on 16 Nov 2009, 02:11 PM
I've managed to empty the css-classes dropdown using the documentation for external css files.
Please let me know in case it is still possible to hide the property selection altogether.
br,
eyal
Please let me know in case it is still possible to hide the property selection altogether.
br,
eyal
0
Hi Eyal,
You can learn how to customize the editor's dialogs and hide elements in them in this live example: Customize Built-in Dialogs.
Greetings,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
You can learn how to customize the editor's dialogs and hide elements in them in this live example: Customize Built-in Dialogs.
Greetings,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
Rank 1
answered on 18 Nov 2009, 03:07 PM
Hi Rumen,
I know it is possible to locally customize the editor dialogs, but I rather check first if there is a simpler way to implement it. Coping the EditorDialogs folder and start modifying all the dialogs would create over maintenance work. It means that the dialogs would have to be modified again with each update release. Unfortunately, I have bad experience with this same modifying method while using other web components.
Telerik's editor dialogs attempt to provide all the possible properties of an element (which is great of course). Though, I believe that many clients in many type of applications does not need or know half of the properties (you can even stick to the 80-20 rule = 80% of clients need 20% of functionality). I also saw quite many messages about it in this forum. My suggestion is to show all properties by default, but allow developers to locally set the dialog properties they don't need (visible=false) in the same way you set other properties of a dialog. In this way, you would not have to bother modifying locally the dialogs every new release.
br,
eyal
I know it is possible to locally customize the editor dialogs, but I rather check first if there is a simpler way to implement it. Coping the EditorDialogs folder and start modifying all the dialogs would create over maintenance work. It means that the dialogs would have to be modified again with each update release. Unfortunately, I have bad experience with this same modifying method while using other web components.
Telerik's editor dialogs attempt to provide all the possible properties of an element (which is great of course). Though, I believe that many clients in many type of applications does not need or know half of the properties (you can even stick to the 80-20 rule = 80% of clients need 20% of functionality). I also saw quite many messages about it in this forum. My suggestion is to show all properties by default, but allow developers to locally set the dialog properties they don't need (visible=false) in the same way you set other properties of a dialog. In this way, you would not have to bother modifying locally the dialogs every new release.
br,
eyal
0
Hi Eyal,
If we provide properties to show and hide the tools in the dialog this will make the configuration of the editor very hard. Our goal is to make the RadEditor control as much as easy for configuration and for that reason we removed a lot of non frequently used properties in the classic editor when we developed the new AJAX editor.
Our plans for the near future is to provide a lite version of the Image manager and Hyperlink manager dialogs that will be loaded faster and will not contain so many features as the current version of these dialogs.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
If we provide properties to show and hide the tools in the dialog this will make the configuration of the editor very hard. Our goal is to make the RadEditor control as much as easy for configuration and for that reason we removed a lot of non frequently used properties in the classic editor when we developed the new AJAX editor.
Our plans for the near future is to provide a lite version of the Image manager and Hyperlink manager dialogs that will be loaded faster and will not contain so many features as the current version of these dialogs.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2009, 07:39 AM
Thank you Rumen for your answer.
I don't quite understand how it will make the configuration of the editor, or actually the dialogs, very hard (or harder than the current approach).
For instance, let's say I want to hide some properties in the hyperlink manager. Currently I have to copy the EditorDialogs folder, modify the dialogs, and set the editor to load them locally. Once you have a new release, I may need again to copy the EditorDialogs and modify the dialogs. Most likely, it would also cause Telerik more support work answering questions such as 'why my x dialog behaves strangely with the new release'. Alternatively, if a show/hide property is provided for the optional properties of the hyperlink dialog, then you set it once and that's it. By default all the properties are visible, which does not cause any more work than the current situation. Certainly, modifying dialogs is not only about showing/hiding properties, but the showing/hiding request seems to be quite common in this forum.
Of course, some of the dialogs are abounded with properties. In this case I agree with your argument. But a quick review of this forum can reveal those properties that tends to be unnecessary in most cases.
br,
eyal
I don't quite understand how it will make the configuration of the editor, or actually the dialogs, very hard (or harder than the current approach).
For instance, let's say I want to hide some properties in the hyperlink manager. Currently I have to copy the EditorDialogs folder, modify the dialogs, and set the editor to load them locally. Once you have a new release, I may need again to copy the EditorDialogs and modify the dialogs. Most likely, it would also cause Telerik more support work answering questions such as 'why my x dialog behaves strangely with the new release'. Alternatively, if a show/hide property is provided for the optional properties of the hyperlink dialog, then you set it once and that's it. By default all the properties are visible, which does not cause any more work than the current situation. Certainly, modifying dialogs is not only about showing/hiding properties, but the showing/hiding request seems to be quite common in this forum.
Of course, some of the dialogs are abounded with properties. In this case I agree with your argument. But a quick review of this forum can reveal those properties that tends to be unnecessary in most cases.
br,
eyal
0
Hi Eyal,
Thank you for the very detailed feedback and explanation of your feature request. We will consider its implementation for some next major release, but I cannot promise that such properties will be implemented.
What you can expect for sure for the for Q1 2010 release are the lite versions of some of the editor dialogs (link, image).
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Thank you for the very detailed feedback and explanation of your feature request. We will consider its implementation for some next major release, but I cannot promise that such properties will be implemented.
What you can expect for sure for the for Q1 2010 release are the lite versions of some of the editor dialogs (link, image).
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
Rank 1
answered on 25 Nov 2009, 02:06 PM
Thank you Rumen.
I do wait to see the lite versions, but I'm afraid they would bring you similar requests as the full versions. Albeit, to the other direction - such as to extend the lite version with one property or another (something in between the versions).
Go lite :)
br,
eyal
I do wait to see the lite versions, but I'm afraid they would bring you similar requests as the full versions. Albeit, to the other direction - such as to extend the lite version with one property or another (something in between the versions).
Go lite :)
br,
eyal