collective.weather 1.0a4

Installation

To enable this package on a buildout-based installation:

1. Edit your buildout.cfg and add collective.weather to the list of eggs to install:

   [buildout]
   ...
   eggs =
       collective.weather

2. If you are using Plone 4.1, you may need to extend a Dexterity known good set (KGS) to make sure that you get the right versions of the packages that make up Dexterity:

   [buildout]
   ...
   extends =
       https://good-py.appspot.com/release/dexterity/1.2.1?plone=4.1.6

After updating the configuration you need to run ‘’bin/buildout’’, which will take care of updating your system.

Go to the ‘Site Setup’ page in a Plone site and click on the ‘Add-ons’ link.

Check the box next to ‘’collective.weather’’ and click the ‘Activate’ button.

Usage

Go to Site Setup and select ‘Weather’.

Enter the list of locations that are going to be available on the site in the following format:

location_id|name

Where location_id should be a unique value and not repeated among any of the locations; name is the name to be shown in the drop down (this doesn’t need to be unique). Some examples could be:

455827|São Paulo (for Yahoo! Weather)
-23.548871,-46.638814|São Paulo (for Forecast.io and Weather Underground)

Select the sistem of units: Metric or Imperial. Metric system uses degrees Celsius. Imperial system uses degrees Fahrenheit.

Finding locations

Different weather service providers need different location ids to get weather conditions.

You’ll have to change the Available locations setting depending on your selection. Please, refer to providers documentation for more information:

• Yahoo Weather needs a WOEID. There’s a convenient online tool to get WOEID.

• Forecast.io API just needs a latitude, longitude coordinate.

• Weather Underground accepts many options (check the query option).

Portlet

The package includes a portlet that you can add in your site.

• Open the ‘Manage portlets’ screen and select ‘Weather portlet’

• Set the title of the portlet

• Select a city from the list

Viewlet

The package also includes a viewlet that will display the weather in one of the locations defined in the settings. The viewlet will be displayed on top of the site inside the IPortalHeader viewlet manager.

To use the viewlet you need to activate it: go to Site Setup and select ‘Weather’ again. Select the ‘Show weather viewlet?’ box.

The user will be able to select from one of the locations (this information will be stored inside a cookie to show this location the next time the user visits the site).

The current weather condition of the selected location will be displayed at the viewlet.

Extending the package with new weather providers

In case you want to contribute with new weather providers for this package or if you want to add a new one in a custom package for your site you’ll just need to create a new named utility that should implement collective.weather.interfaces.IWeatherInfo.

Weather control panel will automatically learn about the new utility and it will be listed as an option in the provider’s drop-down.

This package already comes with some utilities you can check to get a quick idea of how to create yours:

• yahoo

• forecast.io

• wunderground

The API for this utility is very simple.

In case your utility needs an API key you can pass it on initialization.

Here’s and example you can copy and paste to start your custom utility:

"""Example of a named utility for IWeatherInfo.
"""
from collective.weather.interfaces import IWeatherInfo
from zope.interface import implements


class DummyProvider(object):
    """Dummy weather implementation of IWeatherInfo
    """
    implements(IWeatherInfo)

    def __init__(self, key=None):
        self.key = key

    def getWeatherInfo(self, location, units='metric', lang='en'):
        """Dummy implementation of getWeatherInfo as an example
        """
        return {
            'summary': u'What a lovely day!',
            'temperature': 20,
            'icon': u'lovely-day-icon.png',
        }

1.0a4 (2014-04-11)

• Update package documentation. [marcosfromero, hvelarde]

• Spanish and Brazilian Portuguese translations were updated. [hvelarde]

• Refactor weather_utility to use location_id as key. (closes #36). [marcosfromero]

• Depend on plone.api and remove dependency on pywapi. [hvelarde]

• New named utilities for Forecast.io and Weather Underground (closes #18). [marcosfromero]

• New API for named utilities and Yahoo! Weather implementation. [marcosfromero]

• The weather portlet is now configurable. [marcosfromero]

1.0a3 (2013-10-29)

• Spanish and Brazilian Portuguese translations were updated. [hvelarde]

• Package documentation was updated. [hvelarde]

• A new option to define whether or not the weather viewlet is visible was added; by default the viewlet is hidden (closes #14). [hvelarde]

• Control panel configlet was simplified; now all package settings are defined in one screen (closes #19). [hvelarde]

• WeatherUtility is now registered as a global utility as we have no data to persist on it (closes #7). If you’re still stock with a TypeError: ('object.new(WeatherUtility) is not safe... error, keep calm an read the section dedicated to componentregistry.xml on How to make your Plone add-on products uninstall cleanly. May the Force be with you. [hvelarde]

• Add weather portlet that displays weather conditions of current city (closes #9). [marcosfromero]

• Remove all Google Weather related code. [marcosfromero]

• Weather conditions moved to title tag. [flecox]

1.0a2 (2012-09-14)

• Made the code to be more resistent to invalid data from the weather server. [frapell]

• Major refactoring to allow updates and city changes through AJAX calls (fixes #6). [frapell]

• Implemented Yahoo! Weather. [frapell]

1.0a1 (2012-08-01)

• Initial release.