The roadmap

Instead of keeping this ancient to-do list, originally made around 0.2 beta (as a way to keep track of what's to come and what was finished), I thought I'd make a nice roadmap laying out the future of PyWeather.

The initial implementation

The initial implementation. It's the stage where I get whatever I think of coded. It may not look pretty, or be efficient, but it works.

There's still lots left to do, as I constantly create new ideas for PyWeather. At this stage, here's a few of the big things I'd like to get implemented into PyWeather.

• Alerts information - Coming in 0.6 beta
• Radar/satellite loops (using gif files) - Coming in 0.6 beta
• Configuration script - Coming in 0.6 beta (or 0.6.1)
• PWS mode (for displaying information from a Personal Weather Station) - Coming in 0.7 beta
• Hurricane/tide data - Coming in 0.7 beta
• "Quick Weather", basically a slow-typing weather summary - Coming in 0.8 beta

This should all be implemented in the next few betas, along with some other features. This stage should cap off at the end of August 2017, but that's really a rough estimate.

The cleanup phase

For a solid month or two, I'll be working on cleaning up code, and finding some more efficient/clean ways to do what PyWeather does. I've started to do some cleanup, but it'll mainly happen after the initial implementation. This basically entails doing two things:

• Cleaning up all multi-line prints.
• Making sure all scripts have code that doesn't exceed 79 characters.

This should cap off by the end of 2017. At that point, 1.0 would get released.

Working towards more efficient means of coding

Past the cleanup phase, I'd like to explore new areas of Python, object-oriented programming (something like http://www.python-course.eu/object_oriented_programming.php), that kind of stuff.

I'd probably make a whole new OOP branch for PyWeather (to keep the main branch in-tact). Doing OOP would hopefully entail doing something like:

currentforecast = pyweather_oop.currentforecast
print(currentforecast.tempf)```

And even more challenging:
```import pyweather_oop
dailyforecast = pyweather_oop.currentforecast(day=2)
print(dailyforecast.conditions)```

This would be pretty experimental, and I would do this at my own discretion.

## Implementing a good front-end
I'm starting to set sights past 2018 on doing front-end coding, basically interfacing my existing Python code for PyWeather with a pretty GUI, or front end. Be it a website, app, whatever, I'd like to explore implementing front-ends. This phase should end up lasting well into 2019.

## And beyond...
Well, I don't know! I guess we'll see...