paul@6 | 1 | Introduction
|
paul@6 | 2 | ------------
|
paul@6 | 3 |
|
paul@6 | 4 | The EventAggregator macro for MoinMoin can be used to display event calendars
|
paul@6 | 5 | or listings which obtain their data from pages belonging to specific
|
paul@20 | 6 | categories (such as CategoryEvents). The start and end dates are read from the
|
paul@6 | 7 | page describing each event, and the calendar is automatically filled out with
|
paul@6 | 8 | the details of each event, colouring each event period in a specially
|
paul@6 | 9 | generated colour.
|
paul@6 | 10 |
|
paul@44 | 11 | The EventAggregatorSummary action can be used to provide iCalendar and RSS
|
paul@44 | 12 | summaries of event data based on pages belonging to specific categories, as
|
paul@44 | 13 | described above. The category, start and end parameters are read directly from
|
paul@44 | 14 | the request as URL or form parameters: these restrict the extent of each
|
paul@44 | 15 | generated summary.
|
paul@10 | 16 |
|
paul@47 | 17 | The EventAggregatorNewEvent action can be used to conveniently create new
|
paul@47 | 18 | event pages, displaying a simple form which can be filled out in order to
|
paul@47 | 19 | provide elementary event details such as the event title or summary, the
|
paul@47 | 20 | categories to which the page will be assigned, and the start and end dates of
|
paul@47 | 21 | the event.
|
paul@47 | 22 |
|
paul@88 | 23 | The eventfeed script can be used to import events from RSS feeds, inserting
|
paul@88 | 24 | new pages into a Wiki.
|
paul@88 | 25 |
|
paul@80 | 26 | Important Notices
|
paul@80 | 27 | -----------------
|
paul@80 | 28 |
|
paul@80 | 29 | In release 0.5, the "download this calendar" and "subscribe to this calendar"
|
paul@80 | 30 | links have been fixed to return only events within the specified period and to
|
paul@80 | 31 | work with day- and month-relative calendars. Users who have bookmarks in their
|
paul@80 | 32 | Web browser or feed reader should replace these bookmarks by visiting the
|
paul@88 | 33 | bookmarked page and acquiring new versions of these links, once
|
paul@88 | 34 | EventAggregator has been upgraded.
|
paul@80 | 35 |
|
paul@6 | 36 | Installation
|
paul@6 | 37 | ------------
|
paul@6 | 38 |
|
paul@90 | 39 | To install the support library and MoinMoin-related scripts, consider using
|
paul@90 | 40 | the setup.py script provided:
|
paul@10 | 41 |
|
paul@10 | 42 | python setup.py install
|
paul@10 | 43 |
|
paul@10 | 44 | You may wish to indicate a specific prefix if MoinMoin is not installed in the
|
paul@10 | 45 | traditional location:
|
paul@10 | 46 |
|
paul@10 | 47 | python setup.py install --prefix=path-to-moin-prefix
|
paul@10 | 48 |
|
paul@6 | 49 | To install the macro in a Wiki, consider using the instmacros script provided:
|
paul@6 | 50 |
|
paul@6 | 51 | ./instmacros path-to-wiki
|
paul@6 | 52 |
|
paul@6 | 53 | On non-UNIX platforms, it is necessary to manually copy the contents of the
|
paul@6 | 54 | macros directory in this distribution into the macros directory of your Wiki.
|
paul@6 | 55 |
|
paul@10 | 56 | It is highly recommended that the tables and listings be styled according to
|
paul@10 | 57 | the stylesheet provided, and you can use this file as a starting point for
|
paul@10 | 58 | your own modifications. To install the stylesheet, consider using the
|
paul@10 | 59 | insttheme script provided:
|
paul@10 | 60 |
|
paul@10 | 61 | ./insttheme path-to-wiki theme-name
|
paul@10 | 62 |
|
paul@10 | 63 | Again, on non-UNIX platforms, it is necessary to manually copy the files. In
|
paul@10 | 64 | this case, just copy the contents of the css directory into the css directory
|
paul@10 | 65 | of themes which will support styling of event calendars and listings.
|
paul@10 | 66 |
|
paul@10 | 67 | To activate the styles provided by the stylesheet in the css directory, you
|
paul@10 | 68 | will need to edit the screen.css file in each affected theme's css directory,
|
paul@10 | 69 | adding the following before any style rules:
|
paul@10 | 70 |
|
paul@10 | 71 | /* Event aggregation... */
|
paul@10 | 72 |
|
paul@10 | 73 | @import "event-aggregator.css";
|
paul@10 | 74 |
|
paul@82 | 75 | This ensures that the styles are made available to the browser. Additionally,
|
paul@82 | 76 | to make sure that printed pages are correctly styled, the following also needs
|
paul@82 | 77 | to be added to the print.css file in each affected theme's css directory:
|
paul@82 | 78 |
|
paul@82 | 79 | /* Event aggregation... */
|
paul@82 | 80 |
|
paul@82 | 81 | @import "event-aggregator-print.css";
|
paul@82 | 82 | @import "event-aggregator.css";
|
paul@10 | 83 |
|
paul@88 | 84 | To install the actions in a Wiki, consider using the instactions script
|
paul@88 | 85 | provided:
|
paul@10 | 86 |
|
paul@10 | 87 | ./instactions path-to-wiki
|
paul@10 | 88 |
|
paul@10 | 89 | On non-UNIX platforms, it is necessary to manually copy the contents of the
|
paul@88 | 90 | actions directory in this distribution into the actions directory of your
|
paul@88 | 91 | Wiki.
|
paul@88 | 92 |
|
paul@27 | 93 | Useful Pages
|
paul@27 | 94 | ------------
|
paul@27 | 95 |
|
paul@27 | 96 | The pages directory contains a selection of useful pages using a syntax
|
paul@27 | 97 | appropriate for use with MoinMoin 1.6 or later. These pages can be created
|
paul@27 | 98 | through the Wiki and their contents copied in from each of the files.
|
paul@27 | 99 |
|
paul@10 | 100 | Using the Macro
|
paul@10 | 101 | ---------------
|
paul@10 | 102 |
|
paul@6 | 103 | It should now be possible to edit pages and use the macro as follows. For
|
paul@6 | 104 | MoinMoin 1.5:
|
paul@6 | 105 |
|
paul@20 | 106 | [[EventAggregator(CategoryEvents)]]
|
paul@6 | 107 |
|
paul@6 | 108 | For MoinMoin 1.6 and above:
|
paul@6 | 109 |
|
paul@20 | 110 | <<EventAggregator(CategoryEvents)>>
|
paul@6 | 111 |
|
paul@6 | 112 | As arguments to the macro, you must indicate a comma-separated list of
|
paul@6 | 113 | categories to be inspected for event data. For example:
|
paul@6 | 114 |
|
paul@20 | 115 | <<EventAggregator(CategoryEvents,CategoryTraining)>>
|
paul@6 | 116 |
|
paul@6 | 117 | By default, this should display a calendar in a collection of tables, one for
|
paul@6 | 118 | each month containing events. To show a collection of month-by-month listings,
|
paul@6 | 119 | use the 'mode' argument as follows:
|
paul@6 | 120 |
|
paul@20 | 121 | <<EventAggregator(CategoryEvents,mode=list)>>
|
paul@20 | 122 |
|
paul@20 | 123 | See pages/HelpOnEventAggregator for more detailed information.
|
paul@6 | 124 |
|
paul@47 | 125 | Using the Actions
|
paul@47 | 126 | -----------------
|
paul@6 | 127 |
|
paul@20 | 128 | To obtain an iCalendar summary, the EventAggregatorSummary action can be
|
paul@20 | 129 | selected from the actions menu on any page. Alternatively, a collection of
|
paul@24 | 130 | parameters can be specified in the URL of any Wiki page.
|
paul@6 | 131 |
|
paul@24 | 132 | See pages/HelpOnEventAggregatorSummary for more detailed information.
|
paul@6 | 133 |
|
paul@47 | 134 | To create new events using the EventAggregatorNewEvent action, the appropriate
|
paul@47 | 135 | menu entry can be selected in the actions menu. Alternatively, clicking on a
|
paul@47 | 136 | day number in a calendar view will invoke the action and pre-fill the form
|
paul@47 | 137 | with the start date set to the selected day from the calendar.
|
paul@47 | 138 |
|
paul@47 | 139 | See pages/HelpOnEventAggregatorNewEvent for more detailed information.
|
paul@47 | 140 |
|
paul@88 | 141 | Running the Scripts
|
paul@88 | 142 | -------------------
|
paul@88 | 143 |
|
paul@88 | 144 | To import events from an RSS feed, the eventfeed script integrated with the
|
paul@88 | 145 | moin program can be used as follows:
|
paul@88 | 146 |
|
paul@88 | 147 | moin --config-dir=path-to-wiki --wiki-url=example.com/ \
|
paul@88 | 148 | import eventfeed --url=url-of-events-feed
|
paul@88 | 149 |
|
paul@88 | 150 | Thus, to import events from the FSFE events RSS feed, the following command
|
paul@88 | 151 | could be used:
|
paul@88 | 152 |
|
paul@88 | 153 | moin --config-dir=path-to-wiki --wiki-url=example.com/ \
|
paul@88 | 154 | import eventfeed --url=http://www.fsfe.org/events/events.en.rss
|
paul@88 | 155 |
|
paul@88 | 156 | If this command is being used with sudo, make sure to use the -u option so
|
paul@88 | 157 | that the script can operate as the appropriate user. For example:
|
paul@88 | 158 |
|
paul@88 | 159 | sudo -u www-data moin --config-dir=path-to-wiki --wiki-url=example.com/ \
|
paul@88 | 160 | import eventfeed --url=http://www.fsfe.org/events/events.en.rss
|
paul@88 | 161 |
|
paul@88 | 162 | It may also be necessary to set PYTHONPATH directly before the moin program
|
paul@88 | 163 | name and even to explicitly use the path to that program.
|
paul@88 | 164 |
|
paul@6 | 165 | Recommended Software
|
paul@6 | 166 | --------------------
|
paul@6 | 167 |
|
paul@6 | 168 | The Xapian search software is highly recommended, if not technically
|
paul@6 | 169 | essential, for the acceptable performance of the EventAggregator macro since
|
paul@6 | 170 | the macro makes use of search routines in MoinMoin that can dominate the time
|
paul@6 | 171 | spent processing requests.
|
paul@6 | 172 |
|
paul@6 | 173 | See the following page for information on Xapian and MoinMoin:
|
paul@6 | 174 |
|
paul@6 | 175 | http://moinmo.in/HelpOnXapian
|
paul@6 | 176 |
|
paul@6 | 177 | Troubleshooting
|
paul@6 | 178 | ---------------
|
paul@6 | 179 |
|
paul@6 | 180 | See here for a bug related to category recognition:
|
paul@6 | 181 |
|
paul@6 | 182 | http://moinmo.in/MoinMoinBugs/1.7TemplatesNotAppearing
|
paul@6 | 183 |
|
paul@6 | 184 | This affects installations where migrations between versions have occurred,
|
paul@6 | 185 | yet the Wiki configuration retains old regular expression details.
|
paul@6 | 186 |
|
paul@6 | 187 | Contact, Copyright and Licence Information
|
paul@6 | 188 | ------------------------------------------
|
paul@6 | 189 |
|
paul@10 | 190 | See the following Web pages for more information about this work:
|
paul@6 | 191 |
|
paul@6 | 192 | http://moinmo.in/MacroMarket/EventAggregator
|
paul@10 | 193 | http://moinmo.in/ActionMarket/EventAggregator
|
paul@6 | 194 |
|
paul@6 | 195 | The author can be contacted at the following e-mail address:
|
paul@6 | 196 |
|
paul@6 | 197 | paul@boddie.org.uk
|
paul@6 | 198 |
|
paul@6 | 199 | Copyright and licence information can be found in the docs directory - see
|
paul@6 | 200 | docs/COPYING.txt and docs/LICENCE.txt for more information.
|
paul@6 | 201 |
|
paul@82 | 202 | New in EventAggregator 0.6 (Changes since EventAggregator 0.5)
|
paul@82 | 203 | --------------------------------------------------------------
|
paul@82 | 204 |
|
paul@82 | 205 | * Added print stylesheet rules in order to improve the printed versions of
|
paul@82 | 206 | calendars.
|
paul@84 | 207 | * Fixed definition list parsing to handle completely empty definitions
|
paul@84 | 208 | (having no space after the "::" token) which previously captured text from
|
paul@84 | 209 | subsequent lines, and merely empty definitions which previously would have
|
paul@84 | 210 | produced a single empty value for definitions providing lists of values.
|
paul@88 | 211 | * Added a script to import events from RSS feeds.
|
paul@88 | 212 | * Added support for a link entry in event pages, although this does not
|
paul@88 | 213 | replace the link information provided by the RSS and iCalendar summaries.
|
paul@89 | 214 | * Fixed the production of the summaries when pages with no available edit
|
paul@89 | 215 | log information are to be included.
|
paul@82 | 216 |
|
paul@65 | 217 | New in EventAggregator 0.5 (Changes since EventAggregator 0.4)
|
paul@65 | 218 | --------------------------------------------------------------
|
paul@65 | 219 |
|
paul@65 | 220 | * Changed the EventAggregatorNewEvent action to substitute only the stated
|
paul@65 | 221 | title, not the full page title, into the new page.
|
paul@66 | 222 | * Changed event colouring to use the event summary as the basis for
|
paul@66 | 223 | calculating the colour used in the calendar. This means that related
|
paul@66 | 224 | events can be coloured identically if their summaries are the same.
|
paul@71 | 225 | * Added support for multiple events on a single event page.
|
paul@71 | 226 | * Introduced EventPage and Event abstractions in order to better support new
|
paul@71 | 227 | features.
|
paul@78 | 228 | * Introduced basic and advanced modes to the EventAggregatorNewEvent action,
|
paul@78 | 229 | along with date swapping to correct cases where the start is given as
|
paul@78 | 230 | being later than the end of an event.
|
paul@77 | 231 | * Fixed the "download this calendar" and "subscribe to this calendar" links
|
paul@77 | 232 | by propagating the "raw" calendar start and end values within the macro.
|
paul@77 | 233 | These links should yield events only within the period defined for a
|
paul@77 | 234 | calendar, not all events in a calendar's categories. This fix also ensures
|
paul@77 | 235 | that the links for year- and month-relative calendars are correct, rather
|
paul@77 | 236 | than the specific links generated previously. Thus, a "this year's events"
|
paul@77 | 237 | link will now continue to produce a resource with the current year's
|
paul@77 | 238 | events, rather than the events from the year when the link was generated.
|
paul@65 | 239 |
|
paul@51 | 240 | New in EventAggregator 0.4 (Changes since EventAggregator 0.3)
|
paul@51 | 241 | --------------------------------------------------------------
|
paul@51 | 242 |
|
paul@51 | 243 | * Added a table view in the macro, using special topic/category styles to
|
paul@51 | 244 | provide background colours for events.
|
paul@56 | 245 | * Added category propagation from calendars to the new event form provided
|
paul@56 | 246 | by the EventAggregatorNewEvent action.
|
paul@56 | 247 | * Added a default template parameter to the macro, employed by the new event
|
paul@56 | 248 | form.
|
paul@56 | 249 | * Added a parent page parameter which is used by the new event form to place
|
paul@56 | 250 | new event pages in a particular location specific to a calendar or
|
paul@56 | 251 | collection of events.
|
paul@56 | 252 | * Improved the presentation of pop-up event information elements.
|
paul@59 | 253 | * Added navigation between display modes (calendar, list and table views).
|
paul@59 | 254 | * Ensured that calendar settings are retained when creating new events for a
|
paul@59 | 255 | calendar.
|
paul@59 | 256 | * Fixed various problems with events not having topics.
|
paul@51 | 257 |
|
paul@45 | 258 | New in EventAggregator 0.3 (Changes since EventAggregator 0.2)
|
paul@45 | 259 | --------------------------------------------------------------
|
paul@45 | 260 |
|
paul@45 | 261 | * Added a parameter to the EventAggregatorSummary action to select the
|
paul@45 | 262 | source of event descriptions for the RSS feed.
|
paul@45 | 263 | * Updated the documentation to cover the RSS support.
|
paul@47 | 264 | * Added the EventAggregatorNewEvent action.
|
paul@45 | 265 |
|
paul@41 | 266 | New in EventAggregator 0.2 (Changes since EventAggregator 0.1)
|
paul@41 | 267 | --------------------------------------------------------------
|
paul@41 | 268 |
|
paul@41 | 269 | * Improved the calendar view in the macro to use the fixed table layout
|
paul@41 | 270 | algorithm and to provide cells spanning potentially many columns for
|
paul@41 | 271 | continuing events. Introduced pop-up elements in order to show truncated
|
paul@41 | 272 | event names.
|
paul@41 | 273 | * Made the "weekly" naming policy the default in the calendar view.
|
paul@41 | 274 | * Improved the list view in the macro.
|
paul@41 | 275 | * Introduced RSS 2.0 feed support.
|
paul@41 | 276 | * Improved the help pages.
|
paul@41 | 277 |
|
paul@6 | 278 | Release Procedures
|
paul@6 | 279 | ------------------
|
paul@6 | 280 |
|
paul@18 | 281 | Update the EventAggregatorSupport.py __version__ attribute and the setup.py
|
paul@18 | 282 | version details.
|
paul@6 | 283 | Change the version number and package filename/directory in the documentation.
|
paul@51 | 284 | Update the setup.py and PKG-INFO files.
|
paul@6 | 285 | Update the release notes (see above).
|
paul@6 | 286 | Tag, export.
|
paul@6 | 287 | Archive, upload.
|
paul@10 | 288 | Update the MacroMarket and ActionMarket (see above for the URLs).
|