home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
WorldWeather Lite
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Micropolis" data-source="post: 954197" data-attributes="member: 96567"><p>Hi Dadeo,</p><p>thanks for your feedback.</p><p></p><p>Sure, I don't need more than 30min. for development and test. This option was removed to dissolve the dependency to the skin path media\worldweather\provider. Do we want use the same location here or the media folder? Personally I prefer the first solution, because it makes no sense to save the same images (for WorldWeather Lite and WorldWeather) in different locations.</p><p> </p><p></p><p>That's a good point. The API return values of supported weather providers follow different standards (e.g. international weather code or Where On Earth ID), the next provider require the country name, another the city name in a special style (see provider comparison sheet and required input parameters). WorldWeather doesn't have the chance to solve this problem completely. Unfortunately, this can of course lead to the described problems. Let me give a overview of my best practice rules:</p><ul> <li data-xf-list-type="ul">always try to take the English place names without country code abbreviations</li> <li data-xf-list-type="ul">primarily use the international codes (e.g. CAXX0165 from your example)</li> <li data-xf-list-type="ul">use country names, which you can select in the combobox of the configuration dialog (in case entries should be missing, please send me information)</li> <li data-xf-list-type="ul">fill longitude/latitude values, if the parameters cannot be determined automatically</li> </ul><p></p><p></p><p>I can check your example at weekend, currently I do not have access to my development machine and/or HTPC.</p><p> </p><p></p><p>"Correct" is not the right word, here it is more the problem that each provider makes it a little bit different. But these small differences can lead to problems in the sum.</p><p> </p><p>Cheers, Micropolis</p></blockquote><p></p>
[QUOTE="Micropolis, post: 954197, member: 96567"] Hi Dadeo, thanks for your feedback. Sure, I don't need more than 30min. for development and test. This option was removed to dissolve the dependency to the skin path media\worldweather\provider. Do we want use the same location here or the media folder? Personally I prefer the first solution, because it makes no sense to save the same images (for WorldWeather Lite and WorldWeather) in different locations. That's a good point. The API return values of supported weather providers follow different standards (e.g. international weather code or Where On Earth ID), the next provider require the country name, another the city name in a special style (see provider comparison sheet and required input parameters). WorldWeather doesn't have the chance to solve this problem completely. Unfortunately, this can of course lead to the described problems. Let me give a overview of my best practice rules: [LIST] [*]always try to take the English place names without country code abbreviations [*]primarily use the international codes (e.g. CAXX0165 from your example) [*]use country names, which you can select in the combobox of the configuration dialog (in case entries should be missing, please send me information) [*]fill longitude/latitude values, if the parameters cannot be determined automatically [/LIST] I can check your example at weekend, currently I do not have access to my development machine and/or HTPC. "Correct" is not the right word, here it is more the problem that each provider makes it a little bit different. But these small differences can lead to problems in the sum. Cheers, Micropolis [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
WorldWeather Lite
Contact us
RSS
Top
Bottom