Hi there,
I am looking for some advice on the best way to go forward with adding a new custom skin to our project. We are looking to modify the built-in bootstrap skin to match our bootstrap customisation. We would like to be able to:
- Build from scss - so we can use the same scss variables etc we use for our bootstrap customisation
- Have a good way to merge updates to the built-in bootstrap skin into our custom skin so that if controls are added or changed we can easily keep our skin up to date
So far we have come up with the following workflow:
- Create a new skin repository containing the Bootstrap and Common folders from the Telerik Skin Source
- Create a branch off that repository and rename and modify the Bootstrap with our customisations
- Add a build task to compile the sass and place in zip along with the image folders in the Bootstrap folders
- Pass through the skins assembly builder to create a dll to include in our web application
This approach means when there is an update to the telerik controls we can update the master of the skin repository with the changes, and then merge out to the skin branch and resolve any conflicts.
The issue we are running into is that the compiled SASS from the telerik source has already subbed out the image url references with WebResource tags, so we cannot then pass through the Skin's Assembly builder without error.
We are looking for some advice on this, so far the ideas we have come up with are:
1. Updated our scss build task to add a job to revert the WebResource entries back to their url counterparts (so they can then be converted back in the Skin's Assembly Builder)
2. Obtain the source of the Skin's Assembly Builder and remove the parts that sub out the urls with WebResource entries.
The second option is the preferred and we had a look at the source provided by Alain in this post: http://www.telerik.com/forums/tool-for-embedding-custom-skins-into-an-assembly
Unfortunately it does not seem to be up to date as even running output through it straight from the Visual Style Builder does not produce valid css in the dll.
Is there another obvious way to carry out a task such as this? and is the source for the Skin's Assembly Builder available anywhere?
Kind Regards,
Daniel
I am looking for some advice on the best way to go forward with adding a new custom skin to our project. We are looking to modify the built-in bootstrap skin to match our bootstrap customisation. We would like to be able to:
- Build from scss - so we can use the same scss variables etc we use for our bootstrap customisation
- Have a good way to merge updates to the built-in bootstrap skin into our custom skin so that if controls are added or changed we can easily keep our skin up to date
So far we have come up with the following workflow:
- Create a new skin repository containing the Bootstrap and Common folders from the Telerik Skin Source
- Create a branch off that repository and rename and modify the Bootstrap with our customisations
- Add a build task to compile the sass and place in zip along with the image folders in the Bootstrap folders
- Pass through the skins assembly builder to create a dll to include in our web application
This approach means when there is an update to the telerik controls we can update the master of the skin repository with the changes, and then merge out to the skin branch and resolve any conflicts.
The issue we are running into is that the compiled SASS from the telerik source has already subbed out the image url references with WebResource tags, so we cannot then pass through the Skin's Assembly builder without error.
We are looking for some advice on this, so far the ideas we have come up with are:
1. Updated our scss build task to add a job to revert the WebResource entries back to their url counterparts (so they can then be converted back in the Skin's Assembly Builder)
2. Obtain the source of the Skin's Assembly Builder and remove the parts that sub out the urls with WebResource entries.
The second option is the preferred and we had a look at the source provided by Alain in this post: http://www.telerik.com/forums/tool-for-embedding-custom-skins-into-an-assembly
Unfortunately it does not seem to be up to date as even running output through it straight from the Visual Style Builder does not produce valid css in the dll.
Is there another obvious way to carry out a task such as this? and is the source for the Skin's Assembly Builder available anywhere?
Kind Regards,
Daniel