In the process, I wanted to share a tip to simplify getting any existing weather skins working again.
The process of adding files and @include statements is readily available in other posts, so this is a tip on repairing original skins using those techniques. You can read JSMorley's help on those include files here.
Once you have the files in '@Resources' and added the @include statements, now you need to get that information into the old skin.
That is the daunting part, but can be made much easier with the process described here.
1.) The skin already has a main weather webparser measure that must be removed or commented out.
Note: The child weather measures are being used by the skin, DO NOT REMOVE THE CHILD MEASURES! The child measures can be modified to return correct values; which is all that is usually needed to get the skin working again.
2.) Change all the webparser child measures to STRING measures, and set the 'String=value' to the corresponding Section Variable from the included weather measures file. Because we are using Section Variables, you will need to add 'DynamicVariables=1' to the measures. Replace only the lines that relate to the parent Webparser measure; other lines such as 'Substitute=', 'IfMatch=...', etc. should not be changed. Determining what value the old child measures should return is usually pretty straight forward if the original author named them in a logical way.
Here's and example original Child measure
Code: Select all
[MeasureTemp] Measure=Plugin Plugin=Webparser.dll Parent=[MainWeather] StringIndex=7 Substitute="":"na"
Code: Select all
[MeasureTemp] Measure=String String=[MeasureTemperature] DynamicVariables=1 Substitute="":"na"
Because you used the old child measures, very little else should be needed to have a working weather skin.
Feel free to comment or show me another method.