Social_Quotient
Top achievements
Rank 1
Rank 1
Social_Quotient
asked on 05 Jan 2008, 05:15 AM
In rad there was a way to set a property for each of the controls to useembedscripts= false. I cannot find where to set this in the new prometheus controls. Is there a way to set this. I prefer to have external js, css, and images etc...
Thanks
John
Thanks
John
3 Answers, 1 is accepted
0
Hi John,
UseEmbeddedScripts is not available with "Prometheus" controls. Currently, scripts are only available as embedded resources.
Could you please provide some further details on your scenario? Why do you need external JavaScript files? We strongly recommend using the embedded scripts only.
Regards,
Ivo
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
UseEmbeddedScripts is not available with "Prometheus" controls. Currently, scripts are only available as embedded resources.
Could you please provide some further details on your scenario? Why do you need external JavaScript files? We strongly recommend using the embedded scripts only.
Regards,
Ivo
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Social_Quotient
Top achievements
Rank 1
Rank 1
answered on 15 Jan 2008, 11:40 PM
Ivo,
From a not so technical perspective here is my answer.
I like to be able to see the actual items that are loading on the page and when. Using things like firebug allow me to debug and make changes on the fly to css and other things. It is easy to try things, then edit the css and then upload without touching the code of the application.
From a page profiling perspective it is nice to be able to have our asp.net pages look and act like other non.net pages in terms of comparing and looking at the profile of the page.
In the caching app that we use I like to be able to state specifically what to cache and then set expires headers accordingly without much hassle and I feel like it is tougher to mess with axd's than just css and js. I also don't like not being able to clearly see images from the skins, since they are embedded.
Overall we loose the ability to turn the asp.net styles over to a non compiling coder whereby they would normally just work in the css, js and images directly
From a not so technical perspective here is my answer.
I like to be able to see the actual items that are loading on the page and when. Using things like firebug allow me to debug and make changes on the fly to css and other things. It is easy to try things, then edit the css and then upload without touching the code of the application.
From a page profiling perspective it is nice to be able to have our asp.net pages look and act like other non.net pages in terms of comparing and looking at the profile of the page.
In the caching app that we use I like to be able to state specifically what to cache and then set expires headers accordingly without much hassle and I feel like it is tougher to mess with axd's than just css and js. I also don't like not being able to clearly see images from the skins, since they are embedded.
Overall we loose the ability to turn the asp.net styles over to a non compiling coder whereby they would normally just work in the css, js and images directly
0
Hello strategic coder,
The prometheus controls provide abilities to turn the embedded skins off. If you set the EnableEmbeddedSkins property to false no embedded skin CSS would be rendered by our controls. If you you set the EnableEmbeddedBaseStylesheet property to false no stylesheet will be rendered by our controls. We call "base" the CSS files which define the common appearance of our controls. Keep in mind not every control has a base stylesheet. Here is a quick example - if you are using the Default skin of RadTreeView it would register two CSS files - the skin stylesheet and the base stylesheet. If you set the aforementioned properties to false - no stylesheets will be registered - you should register them by hand in order the treeview to look right. We install all the skins and base CSS files in the Skins folder within the Prometheus installation location.
At the time being we don't provide means to turn of embedded JavaScript though as we are currently not shipping them. However you bring up a good point so we will consider implementing such capabilities and shipping the JavaScript files as external resources.
Regards,
Albert
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The prometheus controls provide abilities to turn the embedded skins off. If you set the EnableEmbeddedSkins property to false no embedded skin CSS would be rendered by our controls. If you you set the EnableEmbeddedBaseStylesheet property to false no stylesheet will be rendered by our controls. We call "base" the CSS files which define the common appearance of our controls. Keep in mind not every control has a base stylesheet. Here is a quick example - if you are using the Default skin of RadTreeView it would register two CSS files - the skin stylesheet and the base stylesheet. If you set the aforementioned properties to false - no stylesheets will be registered - you should register them by hand in order the treeview to look right. We install all the skins and base CSS files in the Skins folder within the Prometheus installation location.
At the time being we don't provide means to turn of embedded JavaScript though as we are currently not shipping them. However you bring up a good point so we will consider implementing such capabilities and shipping the JavaScript files as external resources.
Regards,
Albert
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center