Hello,
I'm working on a custom skin and just getting started. The concept is pretty straight forward but I'm wondering why if I edit any of the CSS or image files in any of the pre-defined skins there is no change in the application of the skin. For example, if I edit an image and keep it in the original directory (for example, change the background color in the ButtonSprites.gif to pink) then refresh the browser the original image still appears. What is keeping the image from being updated in the browser?
Also, I'm wondering when making a new skin why the contents of the new skin have to be copied to the project directory, is it not possible to just keep it with the pre-defined and just somehow add it to the list of available skins in the pulldown in the properties to assign it to a tool instead of having to register it manually?
Can I add styles to a skin's CSS file? For example, the form decorator has h4, h5, and h6. Can I add a style for h3 or do I need to create a separate CSS file to place it in?
Using Q3 2008 tools.
Thanks,
Bob
I'm working on a custom skin and just getting started. The concept is pretty straight forward but I'm wondering why if I edit any of the CSS or image files in any of the pre-defined skins there is no change in the application of the skin. For example, if I edit an image and keep it in the original directory (for example, change the background color in the ButtonSprites.gif to pink) then refresh the browser the original image still appears. What is keeping the image from being updated in the browser?
Also, I'm wondering when making a new skin why the contents of the new skin have to be copied to the project directory, is it not possible to just keep it with the pre-defined and just somehow add it to the list of available skins in the pulldown in the properties to assign it to a tool instead of having to register it manually?
Can I add styles to a skin's CSS file? For example, the form decorator has h4, h5, and h6. Can I add a style for h3 or do I need to create a separate CSS file to place it in?
Using Q3 2008 tools.
Thanks,
Bob
7 Answers, 1 is accepted
0
-DJ-
Top achievements
Rank 1
Rank 1
answered on 20 Mar 2009, 11:54 AM
Hi Robert,
You don't see any change when editing an official skin because it doesn't use the resources you are editing. Everything is in the dll.
So you need to start by renaming the skin and edit from there.
You cannot add your own skins to the dll, but there is nothing (I think) that stops you from making your own skin dll if you prefer.
You can add new classes to your skins css file.
Regards,
-DJ-
You don't see any change when editing an official skin because it doesn't use the resources you are editing. Everything is in the dll.
So you need to start by renaming the skin and edit from there.
You cannot add your own skins to the dll, but there is nothing (I think) that stops you from making your own skin dll if you prefer.
You can add new classes to your skins css file.
Regards,
-DJ-
0
Robert
Top achievements
Rank 1
Rank 1
answered on 20 Mar 2009, 12:03 PM
Hi DJ,
Thank you for the repsonse.
OK, so the image and CSS files associated with the official skins is supplied only to provide a base for creating a new skin?
Bob
Thank you for the repsonse.
OK, so the image and CSS files associated with the official skins is supplied only to provide a base for creating a new skin?
Bob
0
-DJ-
Top achievements
Rank 1
Rank 1
answered on 20 Mar 2009, 12:27 PM
Hi Bob,
Yes basically I think that's the idea.
A sidenote for you: If you plan to upgrade to Q1 2009 soon, you shouldn't spend much time on skinning the Q3 2008 version controls, as the new skinning mechanism has changed quite a bit, and skins from 2008 have to be remade.
Regards,
-DJ-
Yes basically I think that's the idea.
A sidenote for you: If you plan to upgrade to Q1 2009 soon, you shouldn't spend much time on skinning the Q3 2008 version controls, as the new skinning mechanism has changed quite a bit, and skins from 2008 have to be remade.
Regards,
-DJ-
0
Robert
Top achievements
Rank 1
Rank 1
answered on 20 Mar 2009, 12:41 PM
Hi DJ,
Yes, I'm aware of the new version. We're discussing the pros and cons. Ideally I would like to jump to the updated version before I create multiple custom skins but there are a lot of moving parts already in motion in the project I'm working on and upgrading now may slow down another part of the process. Perhaps you can shed some light on how much work it would be (if any) to update an application that is currently using the Q3 version. Make note I'm responsible for creating new skins that the developers will apply to the Telerik tools that are already part of the application we're building so I'm unsure of the complexity that goes on behind the scenes in applying the Telerik tools to work as needed. I suppose that's a question for our developers but I was wondering what your opinion might be.
Thanks for the help!
Bob
Yes, I'm aware of the new version. We're discussing the pros and cons. Ideally I would like to jump to the updated version before I create multiple custom skins but there are a lot of moving parts already in motion in the project I'm working on and upgrading now may slow down another part of the process. Perhaps you can shed some light on how much work it would be (if any) to update an application that is currently using the Q3 version. Make note I'm responsible for creating new skins that the developers will apply to the Telerik tools that are already part of the application we're building so I'm unsure of the complexity that goes on behind the scenes in applying the Telerik tools to work as needed. I suppose that's a question for our developers but I was wondering what your opinion might be.
Thanks for the help!
Bob
0
-DJ-
Top achievements
Rank 1
Rank 1
answered on 20 Mar 2009, 01:19 PM
Hi Bob,
Apart from the skinning, the upgrade shouldn't be much of a slowdown in my opinion. I also upgraded in the middle of a few projects and the only setback was the look & feel of the projects, I didn't have to change much code.
The ideal approach would probably be for you to start on the skins for Q1 2009, and then upgrade the project at the dev teams end once you have your skins ready. Any time you spend on skinning the Q3 2008 controls is simply lost.
Regards,
-DJ-
Apart from the skinning, the upgrade shouldn't be much of a slowdown in my opinion. I also upgraded in the middle of a few projects and the only setback was the look & feel of the projects, I didn't have to change much code.
The ideal approach would probably be for you to start on the skins for Q1 2009, and then upgrade the project at the dev teams end once you have your skins ready. Any time you spend on skinning the Q3 2008 controls is simply lost.
Regards,
-DJ-
0
Hello Bob,
Daniel is absolutely right (and the points I'm sending his way are well deserved!). The skinning is the most breaking change in the Q1 release, as many CSS classes have been renamed, and many properties were moved to the "base" stylesheet for each control.
Regarding the development effort required for the upgrade, it would be minimal compared to the cost of the skin upgrade from 2008.Q3 to 2009.Q1.
Kind regards,
Alex
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.
Daniel is absolutely right (and the points I'm sending his way are well deserved!). The skinning is the most breaking change in the Q1 release, as many CSS classes have been renamed, and many properties were moved to the "base" stylesheet for each control.
Regarding the development effort required for the upgrade, it would be minimal compared to the cost of the skin upgrade from 2008.Q3 to 2009.Q1.
Kind regards,
Alex
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.
0
Robert
Top achievements
Rank 1
Rank 1
answered on 20 Mar 2009, 04:16 PM
Hi Alex,
We've decided to jumb to the most recent version and proceed. I'm getting the update now and looking forward to working with the new stuff. I also think that moving many of the properties to the base stylesheet is a step in the right direction.
Thanks for all your help.
Bob
We've decided to jumb to the most recent version and proceed. I'm getting the update now and looking forward to working with the new stuff. I also think that moving many of the properties to the base stylesheet is a step in the right direction.
Thanks for all your help.
Bob