wview compatibility - time to cut the cord ?

[Vince Skahan]

A couple recent questions on the -users group got me thinking about how often people ask questions that require answers along the lines of "the default archive schema matches wview but you can procedurally extend it if you follow these reasonably detailed steps....."

I seem to recall somebody (Matthew?) cooking up an alternate significantly extended schema that seemed intended to be able to include a 'lot' of the things folks ask for frequently, but at the cost of breaking wview compatibility of course.

I know v4 is essentially a 'get to python3' major release that's real-close-now, and that'll take time to work through of course as more configurations start to use v4 in the field, but is there any notional roadmap currently re: extending the default schema ?

Perhaps something like:

• 4.0 = python3 (main goal) plus bug fixes and whatever cool features I can't recall were added
• 4.0.x = fixes for python3 'adventures' discovered as v4 hits the streets more widely
• 4.x = start adding features again (???)

wview's website no longer works.  The last commit was 5+ years ago.  Time to schedule cutting the cord ???

[Thomas Keffer]

I agree completely that anyone who is coming over from wview has come over.

Issue #115 discusses this a bit.

I like your generic timeline, although if someone is willing to work on this, I don't see any reason why we can't include an expanded schema in V4.

Let's continue the discussion under the issue...

-tk

--
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 weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/da0db14a-d6c9-4f8e-b9f7-27ea4b1ea950%40googlegroups.com.