another thing to consider is when to write something yourself in your extension versus use what has already been written in another extension.
for example, forecasting. you could easily make queries to wu or other forecast service in the weewx-wx34 extension. or you could make the weewx-wx34 extension use the forecast variables in the weewx-forecast extension. which do you do? i depends how much you want to duplicate effort, and how how much of the functionality from another extension that you need. for example, the weewx-forecast extension works with many different forecasting services, and it provides a unified way to query and display forecast information. that could make your work easier in weewx-wx34, and it could make life easier for users of weewx-wx34 (e.g., if a user cannot access the forecast service you hard-coded into weewx-wx34, or if a user wants to extend weewx-wx34 forecasting in a 'standard' way) many of the lower-level extensions do not have to worry about this kind of tradeoff, but almost any skin/template extension will. another example: the seasons skin. in that skin we did not provide explicit support for air quality or forecasting or many other useful extensions. but we did provide a structure that makes it trivially simple to add sections to the seasons skin, without breaking the original implementation. if you want to make your system modular and easily customized, spend some time on that aspect of the design. (you may not be able to do that much with wx34 - it strikes me as a rather monolithic design and implementation. modularity might not be possible unless you do a complete fork, or get the upstream to accept significant changes.) m -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/0509b343-0e11-4ef2-b87b-3664a713a19a%40googlegroups.com.
