On Wednesday, August 10, 2016 at 2:51:01 PM UTC-4, Vince Skahan wrote: > > On Wednesday, August 10, 2016 at 10:20:25 AM UTC-7, mwall wrote: >> >> stuff on the wiki is 'officially' released and should work with the >> latest version of weewx. stuff in my github space, that is not listed in >> the wiki, may or may not work. detailed comments are in the code. i have >> some 3-year-old updates to the weewx plotting system in an svn repo >> somewhere. maybe i'll get those applied before someone makes a nice d3 (or >> derivative) based skin for weewx :) >> > > >> what is a roadmap? ;) >> > >> > Yup - certainly. > > v3 big thing was I guess separate databases and perhaps the extension > installer (?) > > Is there any kind of plan for a v4 next big change/improvement/enhancement > looking forward ? >
i'm not sure what tom has in mind for v4, but we're talking about a 3.6 going out real soon now. here are some things i'd like to do, some of which would be v4-ish: - a separate, dependent deb package with a web-based front-end for managing one or more weewx instances. the ui would take care of all the basic configuration options, let you start/stop/monitor weewx, and would understand the extension mechanism for (at least) skins and drivers. - automate the deb repo updates - do a final (?) fix for the weewx plotting system with second y axis and some of the other features we prototyped about 3 years ago - switch to a weewx schema that is a superset of the wview schema - push some c3 code i have sitting around into a new skin for weewx - replace StandardReport with something cleaner but still using png, html, and css (no javascript or jquery or dependencies) - get some time to finish up the forecast comparisons the weewx issue list has more requested features and details. i cannot speak for tom, but i have not had time to put things into a roadmap - basically you see code from me when i need to scratch an itch. maybe you'd like to start a thread in weewx-user that asks people what features they would like to see? m
