Skip to content
This repository

Google Calendar in GNOME Shell

branch: master

This branch is 0 commits ahead and 0 commits behind master

Merge pull request #36 from jayr0d/master

Where an exception object is used, uses the string representation of it.  Where not used, does not initialize one.
latest commit 0fa6c396b3
vintitres authored
Octocat-spinner-32 .gitignore PEP8 fixes February 18, 2012
Octocat-spinner-32 README Update master June 12, 2012
Octocat-spinner-32 config.py PEP8 fixes February 18, 2012
Octocat-spinner-32 excludes-example Adding support to exclude specific calendars that are specified in an… December 16, 2011
Octocat-spinner-32 gnome-shell-google-calendar.py Where an exception object is used, uses the string representation of it. December 08, 2012
Octocat-spinner-32 keyring.py PEP8 fixes February 18, 2012
Octocat-spinner-32 oauth.py PEP8 fixes February 18, 2012
Octocat-spinner-32 test PEP8 fixes February 18, 2012
README
                          gnome-shell-google-calendar

                         Google Calendar in GNOME Shell


    ~ What is it?

      A D-Bus service that fetches events from Google Calendar and makes them
      available for GNOME Shell to display.

    ~ What do I need?

      Python 2.6+ with the following modules:
        gtk
        dbus
        gdata
        iso8601

      Packages:
        gtk-engines
        gtk-engine-murrine
        gtk-engine-equinox

    ~ Usage

      Run the daemon like so:

        ./gnome-shell-google-calendar.py

      You will be prompted for your Google Calendar email the
      first time. A password is not neccesary, as gnome-online-accounts is used.

      Once logged in, events from all your calendars should appear in
      GNOME Shell's calendar.

      To exclude calendars, create a file named "excludes" in the directory
      you run "gnome-shell-google-calendar" from, or a file named
      ".gnome-shell-google-calendar-excludes" in your home directory.
      List the title of each calendar you want to exclude on a separate
      line.

Something went wrong with that request. Please try again.