[dev] Weather/Metar Block

[Rick Emery]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Rick Emery <rick at emery.homelinux.net>:
>
> > I understand. I'm torn, though, on which way to go. Metars provide good
> > current information and display the dew point and cloud accumulation at
> > various altitudes (good for pilots; too specialized, maybe?). EJSE (and
> > InterceptVector before it) provides an extended forecast, with high/low
> > temperatures and pretty graphics for anticipated weather conditions. I
> have
> > working implementations of both, and have both displayed on my portal
> page.
> > If I had to choose, I'm not sure which I would prefer.
> >
> > I was just about to submit the EJSE block to the list. Should I scrap it,
> or
> > post it and see what the consensus of the core developers is?
>
> Your explanation makes a lot of sense to me. How about we keep the METAR
> block
> for detailed current info, and then have a forecast block, ideally just one
> with multiple backends (or all done through Services_Weather).
>
> How's that sound?
>
> -chuck
>
> --
> Charles Hagenbuch, <chuck at horde.org>
> "I'm really... I'm not too fascinated by green food." - Average Joe

Sounds great to me. And I plan to work on a forecast block using
Services_Weather as soon as I figure out why my registration at weather.com
didn't go through.

So as not to confuse the issue, I'll just scrap my EJSE block (since I only
intended it to be temporary anyway).

Thanks!

--
Rick Emery

"When once you have tasted flight, you will forever walk the Earth
 with your eyes turned skyward, for there you have been, and there
 you will always long to return"
                                              -- Leonardo Da Vinci