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@253 | 6 | categories (such as CategoryEvents) or from remote event sources. The start
|
paul@253 | 7 | and end dates are read from the page describing each event, and the calendar
|
paul@253 | 8 | is automatically filled out with the details of each event, colouring each
|
paul@253 | 9 | event period in a specially generated colour. Maps showing event locations are
|
paul@253 | 10 | also supported, given the availability of appropriate map images and location
|
paul@253 | 11 | information.
|
paul@6 | 12 |
|
paul@44 | 13 | The EventAggregatorSummary action can be used to provide iCalendar and RSS
|
paul@44 | 14 | summaries of event data based on pages belonging to specific categories, as
|
paul@44 | 15 | described above. The category, start and end parameters are read directly from
|
paul@44 | 16 | the request as URL or form parameters: these restrict the extent of each
|
paul@44 | 17 | generated summary.
|
paul@10 | 18 |
|
paul@47 | 19 | The EventAggregatorNewEvent action can be used to conveniently create new
|
paul@47 | 20 | event pages, displaying a simple form which can be filled out in order to
|
paul@47 | 21 | provide elementary event details such as the event title or summary, the
|
paul@47 | 22 | categories to which the page will be assigned, and the start and end dates of
|
paul@47 | 23 | the event.
|
paul@47 | 24 |
|
paul@88 | 25 | The eventfeed script can be used to import events from RSS feeds, inserting
|
paul@88 | 26 | new pages into a Wiki.
|
paul@88 | 27 |
|
paul@80 | 28 | Important Notices
|
paul@80 | 29 | -----------------
|
paul@80 | 30 |
|
paul@277 | 31 | In release 0.9, much of the common support code has been moved to the
|
paul@277 | 32 | MoinSupport distribution, thus introducing that distribution as a dependency
|
paul@277 | 33 | which must be installed for EventAggregator to work. See the documentation
|
paul@277 | 34 | regarding dependencies for further details.
|
paul@277 | 35 |
|
paul@320 | 36 | Release 0.8.4 fixes time zone offset calculations for time regimes west of the
|
paul@320 | 37 | prime meridian.
|
paul@320 | 38 |
|
paul@287 | 39 | Release 0.8.3 fixes end dates in events aggregated from remote iCalendar
|
paul@287 | 40 | sources.
|
paul@287 | 41 |
|
paul@234 | 42 | Release 0.7.1 restores MoinMoin 1.9.x compatibility which was accidentally
|
paul@234 | 43 | lost in the 0.7 release.
|
paul@234 | 44 |
|
paul@148 | 45 | Release 0.6.2 fixes various bugs in HTML production done by the actions. It is
|
paul@153 | 46 | strongly recommended to upgrade from earlier versions to this or a later
|
paul@153 | 47 | release.
|
paul@137 | 48 |
|
paul@148 | 49 | In release 0.6.2, support for MoinMoin 1.5.x has been dropped. Since usage of
|
paul@117 | 50 | the Xapian search software is practically a necessary part of deploying this
|
paul@117 | 51 | solution, and yet Xapian only became integrated with MoinMoin from version 1.6
|
paul@117 | 52 | onwards, few deployments should have involved MoinMoin 1.5.x.
|
paul@117 | 53 |
|
paul@102 | 54 | In release 0.6, support for event times has been introduced. Due to the
|
paul@102 | 55 | complicated nature of times, time zones, time regimes, and so on, the
|
paul@102 | 56 | behaviour of the software may change in future versions to support common
|
paul@102 | 57 | use-cases in a more convenient fashion. Please be aware that implicitly chosen
|
paul@102 | 58 | or generated time or time zone information may change for events, particularly
|
paul@106 | 59 | those whose times are ambiguous or ill-defined. It is highly recommended that
|
paul@106 | 60 | the pytz library be installed - see the documentation regarding dependencies
|
paul@106 | 61 | for more information.
|
paul@102 | 62 |
|
paul@80 | 63 | In release 0.5, the "download this calendar" and "subscribe to this calendar"
|
paul@80 | 64 | links have been fixed to return only events within the specified period and to
|
paul@80 | 65 | work with day- and month-relative calendars. Users who have bookmarks in their
|
paul@80 | 66 | Web browser or feed reader should replace these bookmarks by visiting the
|
paul@88 | 67 | bookmarked page and acquiring new versions of these links, once
|
paul@88 | 68 | EventAggregator has been upgraded.
|
paul@80 | 69 |
|
paul@6 | 70 | Installation
|
paul@6 | 71 | ------------
|
paul@6 | 72 |
|
paul@90 | 73 | To install the support library and MoinMoin-related scripts, consider using
|
paul@144 | 74 | the moinsetup tool. See the "Recommended Software" section below for more
|
paul@144 | 75 | information.
|
paul@144 | 76 |
|
paul@144 | 77 | With moinsetup and a suitable configuration file, the installation is done as
|
paul@144 | 78 | follows with $EADIR referring to the EventAggregator distribution directory
|
paul@144 | 79 | containing this README.txt file:
|
paul@10 | 80 |
|
paul@247 | 81 | python moinsetup.py -f moinsetup.cfg -m install_extension_package $EADIR
|
paul@247 | 82 | python moinsetup.py -f moinsetup.cfg -m install_actions $EADIR/actions
|
paul@247 | 83 | python moinsetup.py -f moinsetup.cfg -m install_macros $EADIR/macros
|
paul@247 | 84 | python moinsetup.py -f moinsetup.cfg -m install_theme_resources $EADIR
|
paul@247 | 85 | python moinsetup.py -f moinsetup.cfg -m edit_theme_stylesheet screen.css event-aggregator.css
|
paul@247 | 86 | python moinsetup.py -f moinsetup.cfg -m edit_theme_stylesheet print.css event-aggregator.css
|
paul@247 | 87 | python moinsetup.py -f moinsetup.cfg -m edit_theme_stylesheet print.css event-aggregator-print.css
|
paul@10 | 88 |
|
paul@144 | 89 | The first command above uses the setup.py script provided as follows:
|
paul@10 | 90 |
|
paul@10 | 91 | python setup.py install --prefix=path-to-moin-prefix
|
paul@10 | 92 |
|
paul@144 | 93 | The second and third commands install the actions and macros respectively.
|
paul@6 | 94 |
|
paul@144 | 95 | The fourth command installs the theme resources in the available theme
|
paul@144 | 96 | directories.
|
paul@10 | 97 |
|
paul@144 | 98 | The remaining commands activate the styles provided by EventAggregator by
|
paul@144 | 99 | editing the screen.css and print.css files which are typically provided by
|
paul@144 | 100 | themes. These commands add imports of the following form to the theme
|
paul@144 | 101 | stylesheets:
|
paul@10 | 102 |
|
paul@10 | 103 | @import "event-aggregator.css";
|
paul@10 | 104 |
|
paul@238 | 105 | Optional Installation Tasks
|
paul@238 | 106 | ---------------------------
|
paul@238 | 107 |
|
paul@238 | 108 | To add the capability of aggregating iCalendar format event sources, the
|
paul@238 | 109 | vContent software needs to be obtained and installed. See the "Recommended
|
paul@238 | 110 | Software" section below for details.
|
paul@238 | 111 |
|
paul@238 | 112 | The following command can be run with $VCDIR referring to the vContent
|
paul@238 | 113 | distribution directory:
|
paul@238 | 114 |
|
paul@247 | 115 | python moinsetup.py -f moinsetup.cfg -m install_extension_package $VCDIR
|
paul@238 | 116 |
|
paul@238 | 117 | This merely runs the setup.py script provided by that software, installing
|
paul@238 | 118 | the software under the configured installation "prefix".
|
paul@238 | 119 |
|
paul@27 | 120 | Useful Pages
|
paul@27 | 121 | ------------
|
paul@27 | 122 |
|
paul@27 | 123 | The pages directory contains a selection of useful pages using a syntax
|
paul@27 | 124 | appropriate for use with MoinMoin 1.6 or later. These pages can be created
|
paul@144 | 125 | through the Wiki and their contents copied in from each of the files. An
|
paul@144 | 126 | easier installation method is to issue the following commands:
|
paul@144 | 127 |
|
paul@247 | 128 | python moinsetup.py -f moinsetup.cfg -m make_page_package $EADIR/pages pages.zip
|
paul@247 | 129 | python moinsetup.py -f moinsetup.cfg -m install_page_package pages.zip
|
paul@144 | 130 |
|
paul@144 | 131 | You may need to switch user in order to have sufficient privileges to copy the
|
paul@238 | 132 | page package into the Wiki. For example:
|
paul@238 | 133 |
|
paul@247 | 134 | sudo -u www-data python moinsetup.py -f moinsetup.cfg -m install_page_package pages.zip
|
paul@27 | 135 |
|
paul@203 | 136 | Resource Pages
|
paul@203 | 137 | --------------
|
paul@203 | 138 |
|
paul@203 | 139 | For the map view, some resource pages are provided with EventAggregator.
|
paul@203 | 140 | Unlike the help pages which are most likely to be left unedited, the resource
|
paul@203 | 141 | pages should be modified and updated with additional map and place details.
|
paul@203 | 142 | Consequently, upgrading these pages is not necessarily desirable when new
|
paul@203 | 143 | releases of EventAggregator are made available, and thus these pages are kept
|
paul@203 | 144 | separate from the help pages.
|
paul@203 | 145 |
|
paul@203 | 146 | To install the resource pages, use the following commands:
|
paul@203 | 147 |
|
paul@247 | 148 | python moinsetup.py -f moinsetup.cfg -m make_page_package $EADIR/resource_pages resource_pages.zip
|
paul@247 | 149 | python moinsetup.py -f moinsetup.cfg -m install_page_package resource_pages.zip
|
paul@203 | 150 |
|
paul@203 | 151 | You may need to switch user in order to have sufficient privileges to copy the
|
paul@238 | 152 | page package into the Wiki. For example:
|
paul@238 | 153 |
|
paul@247 | 154 | sudo -u www-data python moinsetup.py -f moinsetup.cfg -m install_page_package resource_pages.zip
|
paul@203 | 155 |
|
paul@10 | 156 | Using the Macro
|
paul@10 | 157 | ---------------
|
paul@10 | 158 |
|
paul@117 | 159 | It should now be possible to edit pages and use the macro as follows:
|
paul@6 | 160 |
|
paul@20 | 161 | <<EventAggregator(CategoryEvents)>>
|
paul@6 | 162 |
|
paul@6 | 163 | As arguments to the macro, you must indicate a comma-separated list of
|
paul@6 | 164 | categories to be inspected for event data. For example:
|
paul@6 | 165 |
|
paul@20 | 166 | <<EventAggregator(CategoryEvents,CategoryTraining)>>
|
paul@6 | 167 |
|
paul@6 | 168 | By default, this should display a calendar in a collection of tables, one for
|
paul@6 | 169 | each month containing events. To show a collection of month-by-month listings,
|
paul@6 | 170 | use the 'mode' argument as follows:
|
paul@6 | 171 |
|
paul@20 | 172 | <<EventAggregator(CategoryEvents,mode=list)>>
|
paul@20 | 173 |
|
paul@253 | 174 | To use remote event sources instead of categories in the Wiki, specify each
|
paul@253 | 175 | source using explicit source parameters:
|
paul@253 | 176 |
|
paul@253 | 177 | <<EventAggregator(source=GriCal,source=FSFE)>>
|
paul@253 | 178 |
|
paul@253 | 179 | This will aggregate events from the GriCal and FSFE calendars residing on
|
paul@253 | 180 | remote Web sites, provided that these sources have been defined in the event
|
paul@253 | 181 | sources dictionary.
|
paul@253 | 182 |
|
paul@330 | 183 | To use a search pattern, use the search parameter and specify the search
|
paul@330 | 184 | criteria just as you would when using the standard search macros:
|
paul@330 | 185 |
|
paul@330 | 186 | <<EventAggregator(search="title:MonthCalendarEvents/")>>
|
paul@330 | 187 |
|
paul@330 | 188 | This will aggregate events found on subpages of the MonthCalendarEvents page.
|
paul@330 | 189 |
|
paul@20 | 190 | See pages/HelpOnEventAggregator for more detailed information.
|
paul@6 | 191 |
|
paul@47 | 192 | Using the Actions
|
paul@47 | 193 | -----------------
|
paul@6 | 194 |
|
paul@20 | 195 | To obtain an iCalendar summary, the EventAggregatorSummary action can be
|
paul@20 | 196 | selected from the actions menu on any page. Alternatively, a collection of
|
paul@24 | 197 | parameters can be specified in the URL of any Wiki page.
|
paul@6 | 198 |
|
paul@24 | 199 | See pages/HelpOnEventAggregatorSummary for more detailed information.
|
paul@6 | 200 |
|
paul@47 | 201 | To create new events using the EventAggregatorNewEvent action, the appropriate
|
paul@47 | 202 | menu entry can be selected in the actions menu. Alternatively, clicking on a
|
paul@47 | 203 | day number in a calendar view will invoke the action and pre-fill the form
|
paul@47 | 204 | with the start date set to the selected day from the calendar.
|
paul@47 | 205 |
|
paul@47 | 206 | See pages/HelpOnEventAggregatorNewEvent for more detailed information.
|
paul@47 | 207 |
|
paul@88 | 208 | Running the Scripts
|
paul@88 | 209 | -------------------
|
paul@88 | 210 |
|
paul@238 | 211 | Note that remote event sources are likely to be more useful than the scripts
|
paul@238 | 212 | described below. However, these scripts may be useful for certain kinds of
|
paul@238 | 213 | application.
|
paul@238 | 214 |
|
paul@88 | 215 | To import events from an RSS feed, the eventfeed script integrated with the
|
paul@88 | 216 | moin program can be used as follows:
|
paul@88 | 217 |
|
paul@88 | 218 | moin --config-dir=path-to-wiki --wiki-url=example.com/ \
|
paul@88 | 219 | import eventfeed --url=url-of-events-feed
|
paul@88 | 220 |
|
paul@88 | 221 | Thus, to import events from the FSFE events RSS feed, the following command
|
paul@88 | 222 | could be used:
|
paul@88 | 223 |
|
paul@88 | 224 | moin --config-dir=path-to-wiki --wiki-url=example.com/ \
|
paul@88 | 225 | import eventfeed --url=http://www.fsfe.org/events/events.en.rss
|
paul@88 | 226 |
|
paul@88 | 227 | If this command is being used with sudo, make sure to use the -u option so
|
paul@88 | 228 | that the script can operate as the appropriate user. For example:
|
paul@88 | 229 |
|
paul@88 | 230 | sudo -u www-data moin --config-dir=path-to-wiki --wiki-url=example.com/ \
|
paul@88 | 231 | import eventfeed --url=http://www.fsfe.org/events/events.en.rss
|
paul@88 | 232 |
|
paul@88 | 233 | It may also be necessary to set PYTHONPATH directly before the moin program
|
paul@88 | 234 | name and even to explicitly use the path to that program.
|
paul@88 | 235 |
|
paul@6 | 236 | Recommended Software
|
paul@6 | 237 | --------------------
|
paul@6 | 238 |
|
paul@249 | 239 | See the "Dependencies" section below for essential software.
|
paul@249 | 240 |
|
paul@144 | 241 | The moinsetup tool is recommended for installation since it aims to support
|
paul@144 | 242 | all versions of MoinMoin that are supported for use with this software.
|
paul@144 | 243 |
|
paul@144 | 244 | See the following page for information on moinsetup:
|
paul@144 | 245 |
|
paul@144 | 246 | http://moinmo.in/ScriptMarket/moinsetup
|
paul@144 | 247 |
|
paul@6 | 248 | The Xapian search software is highly recommended, if not technically
|
paul@6 | 249 | essential, for the acceptable performance of the EventAggregator macro since
|
paul@6 | 250 | the macro makes use of search routines in MoinMoin that can dominate the time
|
paul@6 | 251 | spent processing requests.
|
paul@6 | 252 |
|
paul@6 | 253 | See the following page for information on Xapian and MoinMoin:
|
paul@6 | 254 |
|
paul@6 | 255 | http://moinmo.in/HelpOnXapian
|
paul@6 | 256 |
|
paul@238 | 257 | The vContent software is required for the parsing of iCalendar information
|
paul@238 | 258 | from remote event sources.
|
paul@238 | 259 |
|
paul@238 | 260 | See the following page for information on vContent:
|
paul@238 | 261 |
|
paul@238 | 262 | https://hg.boddie.org.uk/vContent
|
paul@238 | 263 |
|
paul@338 | 264 | Troubleshooting: Categories
|
paul@338 | 265 | ---------------------------
|
paul@6 | 266 |
|
paul@6 | 267 | See here for a bug related to category recognition:
|
paul@6 | 268 |
|
paul@6 | 269 | http://moinmo.in/MoinMoinBugs/1.7TemplatesNotAppearing
|
paul@6 | 270 |
|
paul@6 | 271 | This affects installations where migrations between versions have occurred,
|
paul@6 | 272 | yet the Wiki configuration retains old regular expression details.
|
paul@6 | 273 |
|
paul@338 | 274 | Troubleshooting: Xapian
|
paul@338 | 275 | -----------------------
|
paul@338 | 276 |
|
paul@208 | 277 | Xapian can be troublesome, especially where file permissions are concerned: if
|
paul@208 | 278 | something acquires a lock on the index (for example, the moin script, possibly
|
paul@208 | 279 | invoked via moinsetup) nothing else will be able to modify the index, and this
|
paul@208 | 280 | may cause pages to become detached from their categories in the index.
|
paul@208 | 281 |
|
paul@208 | 282 | To resolve index issues, try and run the following command (with the appropriate
|
paul@208 | 283 | options):
|
paul@208 | 284 |
|
paul@208 | 285 | moin --config-dir=path-to-wiki --wiki-url=example.com/ index build --mode=rebuild
|
paul@208 | 286 |
|
paul@208 | 287 | It may be necessary to manually remove locks. This can be done as follows:
|
paul@208 | 288 |
|
paul@208 | 289 | find path-to-wiki/data/cache/xapian -depth -name "*-lock" -type d -exec rmdir '{}' \;
|
paul@208 | 290 |
|
paul@338 | 291 | Troubleshooting: Plain Text Formatting
|
paul@338 | 292 | --------------------------------------
|
paul@338 | 293 |
|
paul@338 | 294 | Plain text formatting is used in certain places in EventAggregator, but the
|
paul@338 | 295 | formatter is rather broken in MoinMoin 1.8 and in previous releases. See the
|
paul@338 | 296 | following page for a summary:
|
paul@338 | 297 |
|
paul@338 | 298 | http://moinmo.in/FeatureRequests/TextPlainFormatterRewrite
|
paul@338 | 299 |
|
paul@338 | 300 | A patch is supplied in the patches directory to fix link formatting in the
|
paul@338 | 301 | plain text formatter, and once copied into the root directory of the MoinMoin
|
paul@338 | 302 | 1.8 sources it can be applied as follows:
|
paul@338 | 303 |
|
paul@338 | 304 | patch -p1 < patch-plain-text-link-formatting-1.8.diff
|
paul@338 | 305 |
|
paul@6 | 306 | Contact, Copyright and Licence Information
|
paul@6 | 307 | ------------------------------------------
|
paul@6 | 308 |
|
paul@10 | 309 | See the following Web pages for more information about this work:
|
paul@6 | 310 |
|
paul@6 | 311 | http://moinmo.in/MacroMarket/EventAggregator
|
paul@10 | 312 | http://moinmo.in/ActionMarket/EventAggregator
|
paul@6 | 313 |
|
paul@6 | 314 | The author can be contacted at the following e-mail address:
|
paul@6 | 315 |
|
paul@6 | 316 | paul@boddie.org.uk
|
paul@6 | 317 |
|
paul@6 | 318 | Copyright and licence information can be found in the docs directory - see
|
paul@6 | 319 | docs/COPYING.txt and docs/LICENCE.txt for more information.
|
paul@6 | 320 |
|
paul@106 | 321 | Dependencies
|
paul@106 | 322 | ------------
|
paul@106 | 323 |
|
paul@106 | 324 | EventAggregator has the following basic dependencies:
|
paul@106 | 325 |
|
paul@106 | 326 | Packages Release Information
|
paul@106 | 327 | -------- -------------------
|
paul@106 | 328 |
|
paul@306 | 329 | MoinSupport Tested with 0.2
|
paul@277 | 330 | Source: http://hgweb.boddie.org.uk/MoinSupport
|
paul@277 | 331 |
|
paul@106 | 332 | pytz Tested with 2007k (specifically 2007k-0ubuntu2)
|
paul@106 | 333 | Source: http://pytz.sourceforge.net/
|
paul@106 | 334 |
|
paul@106 | 335 | If time zone handling is not required, pytz need not be installed, but this
|
paul@106 | 336 | may result in iCalendar summaries being produced that provide insufficient
|
paul@106 | 337 | time zone information for the correct interpretation of time information in
|
paul@106 | 338 | those summaries. Thus, it is highly recommended that pytz be installed.
|
paul@106 | 339 |
|
paul@320 | 340 | New in EventAggregator 0.9 (Changes since EventAggregator 0.8.5)
|
paul@277 | 341 | ----------------------------------------------------------------
|
paul@277 | 342 |
|
paul@277 | 343 | * Moved much of the support library to the MoinSupport distribution, thus
|
paul@277 | 344 | introducing a dependency on that software.
|
paul@294 | 345 | * Added support for in-page updates of the event views so that navigation
|
paul@294 | 346 | between days, months and different views does not cause a full-page
|
paul@294 | 347 | reload if JavaScript is enabled.
|
paul@294 | 348 | * Tidied up the new event form, showing a list of known locations for
|
paul@294 | 349 | selection, making the event location affect the chosen time zone/regime if
|
paul@294 | 350 | the location is known, and hiding latitude and longitude fields unless an
|
paul@294 | 351 | unknown location is to be specified.
|
paul@294 | 352 | * The EventLocationsDict or equivalent can now retain time zone/regime
|
paul@294 | 353 | information about each location.
|
paul@312 | 354 | * Added an event parser that can format special page regions in different
|
paul@323 | 355 | ways and support links directly to such regions.
|
paul@323 | 356 | * Permitted Wiki markup in the description and location metadata.
|
paul@330 | 357 | * Added support for search patterns so that event pages can be obtained
|
paul@330 | 358 | through arbitrary searches and do not have to belong to particular
|
paul@330 | 359 | categories.
|
paul@337 | 360 | * Encoded map location pop-up headings as plain text in order to handle
|
paul@337 | 361 | locations specified using Wiki formatting.
|
paul@339 | 362 | * Improved navigation between months and days, and between view modes for
|
paul@339 | 363 | both levels of calendar view.
|
paul@277 | 364 |
|
paul@320 | 365 | New in EventAggregator 0.8.5 (Changes since EventAggregator 0.8.4)
|
paul@320 | 366 | ------------------------------------------------------------------
|
paul@320 | 367 |
|
paul@320 | 368 | * Fixed iCalendar quoting for newlines in calendar data.
|
paul@320 | 369 |
|
paul@320 | 370 | New in EventAggregator 0.8.4 (Changes since EventAggregator 0.8.3)
|
paul@320 | 371 | ------------------------------------------------------------------
|
paul@320 | 372 |
|
paul@320 | 373 | * The calculation of hour and minute offsets for time regimes west of the
|
paul@320 | 374 | prime meridian was not producing correct results since the day offset
|
paul@320 | 375 | provided by pytz was not being considered in the calculation. Such regimes
|
paul@320 | 376 | should now produce the expected (hour, minute) offsets such that events
|
paul@320 | 377 | employing these regimes can be positioned correctly on a UTC timescale.
|
paul@320 | 378 |
|
paul@287 | 379 | New in EventAggregator 0.8.3 (Changes since EventAggregator 0.8.2)
|
paul@287 | 380 | ------------------------------------------------------------------
|
paul@287 | 381 |
|
paul@287 | 382 | * The end dates defined in events from remote iCalendar event sources were
|
paul@287 | 383 | not correctly adjusted when aggregating such events. Thus, events with a
|
paul@287 | 384 | day-level resolution will have appeared one day longer in calendars and
|
paul@287 | 385 | summaries than was actually specified in the source data. This adjustment
|
paul@287 | 386 | has now been introduced.
|
paul@287 | 387 |
|
paul@265 | 388 | New in EventAggregator 0.8.2 (Changes since EventAggregator 0.8.1)
|
paul@265 | 389 | ------------------------------------------------------------------
|
paul@265 | 390 |
|
paul@265 | 391 | * Improved the error handling around remote event source data retrieval,
|
paul@265 | 392 | introducing handling of missing resources and unsupported content types.
|
paul@275 | 393 | * Improved the presentation of download and subscription links, adding
|
paul@275 | 394 | webcal: URL links for suitable calendar clients.
|
paul@265 | 395 |
|
paul@255 | 396 | New in EventAggregator 0.8.1 (Changes since EventAggregator 0.8)
|
paul@255 | 397 | ----------------------------------------------------------------
|
paul@255 | 398 |
|
paul@255 | 399 | * Changed the EventAggregatorNewEvent action to not save new event pages
|
paul@255 | 400 | directly, instead invoking the textual page editor for the page so that
|
paul@255 | 401 | the page text can be changed and the page saved without a redundant
|
paul@255 | 402 | initial version being created. Cancelling the editing operation will also
|
paul@255 | 403 | avoid the creation of unwanted event pages.
|
paul@256 | 404 | * Added a page break before each map in the print view, adding a page break
|
paul@256 | 405 | after each map to fully isolate unpositioned events on separate pages.
|
paul@260 | 406 | * Fixed errors where empty location fields were given in vCalendar events.
|
paul@260 | 407 | * Reintroduced event sorting in the list and table views.
|
paul@262 | 408 | * Fixed location positioning where some events employing an unknown location
|
paul@262 | 409 | do not position that location whereas others do (using "geo" information).
|
paul@255 | 410 |
|
paul@236 | 411 | New in EventAggregator 0.8 (Changes since EventAggregator 0.7.1)
|
paul@236 | 412 | ----------------------------------------------------------------
|
paul@230 | 413 |
|
paul@230 | 414 | * Added remote event aggregation with support for iCalendar event sources.
|
paul@230 | 415 | * Added support for explicit latitude and longitude event properties.
|
paul@230 | 416 | * Added support for decimal latitude and longitude values.
|
paul@238 | 417 | * Introduced in-page updates of the new event form, avoiding full-page
|
paul@238 | 418 | reloads when editing the initial details of an event.
|
paul@230 | 419 |
|
paul@234 | 420 | New in EventAggregator 0.7.1 (Changes since EventAggregator 0.7)
|
paul@234 | 421 | ----------------------------------------------------------------
|
paul@234 | 422 |
|
paul@234 | 423 | * Restored MoinMoin 1.9.x compatibility around WikiDict access.
|
paul@234 | 424 |
|
paul@180 | 425 | New in EventAggregator 0.7 (Changes since EventAggregator 0.6.4)
|
paul@153 | 426 | ----------------------------------------------------------------
|
paul@153 | 427 |
|
paul@153 | 428 | * Added a day view which shows events ordered according to their timespans
|
paul@153 | 429 | within each day.
|
paul@192 | 430 | * Added a map view which shows events according to their location. This
|
paul@192 | 431 | requires map images to be uploaded to a designated page, and map locations
|
paul@192 | 432 | to be defined on a designated page.
|
paul@153 | 433 | * Switched to using moinsetup for the installation procedure.
|
paul@180 | 434 | * Introduced formatting of description, location and topic information in
|
paul@180 | 435 | the list and table views and in RSS format summaries.
|
paul@214 | 436 | * Introduced support for days as calendar period units in the list view.
|
paul@214 | 437 | * Added "Help" and "New event" links alongside the calendar view controls,
|
paul@214 | 438 | giving the download and view controls centre alignment.
|
paul@180 | 439 |
|
paul@180 | 440 | New in EventAggregator 0.6.4 (Changes since EventAggregator 0.6.3)
|
paul@180 | 441 | ------------------------------------------------------------------
|
paul@180 | 442 |
|
paul@180 | 443 | * Fixed pop-up element labels where one limit of a calendar has not been
|
paul@180 | 444 | specified.
|
paul@180 | 445 |
|
paul@180 | 446 | New in EventAggregator 0.6.3 (Changes since EventAggregator 0.6.2)
|
paul@180 | 447 | ------------------------------------------------------------------
|
paul@180 | 448 |
|
paul@180 | 449 | * Fixed category membership parsing.
|
paul@180 | 450 | * Fixed open-ended calendars and their pop-up summaries.
|
paul@153 | 451 |
|
paul@148 | 452 | New in EventAggregator 0.6.2 (Changes since EventAggregator 0.6.1)
|
paul@148 | 453 | ------------------------------------------------------------------
|
paul@109 | 454 |
|
paul@136 | 455 | * Fixed HTML encoding in the forms generated by the actions.
|
paul@117 | 456 | * Dropped MoinMoin 1.5.x support, since Xapian search is not available for
|
paul@117 | 457 | that version and is virtually a necessity.
|
paul@109 | 458 | * Fixed form handling to be compatible with MoinMoin 1.9.x, since that
|
paul@109 | 459 | particular release series introduced an incompatible request API that
|
paul@109 | 460 | breaks existing code (no longer providing access to query string
|
paul@109 | 461 | parameters via the form attribute, and only returning single values
|
paul@109 | 462 | unless the new getlist method on form-like objects is used).
|
paul@110 | 463 | * Fixed the direct writing of requests to be compatible with MoinMoin 1.9.
|
paul@113 | 464 | * Added pop-up elements showing information about the calendar/view
|
paul@113 | 465 | resources available for download or subscription.
|
paul@113 | 466 | * Added download/subscription links which open the form associated with the
|
paul@113 | 467 | EventAggregatorSummary action and permit editing of the supplied values.
|
paul@109 | 468 |
|
paul@137 | 469 | New in EventAggregator 0.6.1 (Changes since EventAggregator 0.6)
|
paul@137 | 470 | ----------------------------------------------------------------
|
paul@137 | 471 |
|
paul@137 | 472 | * Fixed HTML encoding in the forms generated by the actions.
|
paul@137 | 473 |
|
paul@82 | 474 | New in EventAggregator 0.6 (Changes since EventAggregator 0.5)
|
paul@82 | 475 | --------------------------------------------------------------
|
paul@82 | 476 |
|
paul@82 | 477 | * Added print stylesheet rules in order to improve the printed versions of
|
paul@82 | 478 | calendars.
|
paul@84 | 479 | * Fixed definition list parsing to handle completely empty definitions
|
paul@84 | 480 | (having no space after the "::" token) which previously captured text from
|
paul@84 | 481 | subsequent lines, and merely empty definitions which previously would have
|
paul@84 | 482 | produced a single empty value for definitions providing lists of values.
|
paul@88 | 483 | * Added a script to import events from RSS feeds.
|
paul@88 | 484 | * Added support for a link entry in event pages, although this does not
|
paul@88 | 485 | replace the link information provided by the RSS and iCalendar summaries.
|
paul@89 | 486 | * Fixed the production of the summaries when pages with no available edit
|
paul@89 | 487 | log information are to be included.
|
paul@102 | 488 | * Added support for event times and time zone/regime information. This is
|
paul@102 | 489 | subject to revision.
|
paul@82 | 490 |
|
paul@65 | 491 | New in EventAggregator 0.5 (Changes since EventAggregator 0.4)
|
paul@65 | 492 | --------------------------------------------------------------
|
paul@65 | 493 |
|
paul@65 | 494 | * Changed the EventAggregatorNewEvent action to substitute only the stated
|
paul@65 | 495 | title, not the full page title, into the new page.
|
paul@66 | 496 | * Changed event colouring to use the event summary as the basis for
|
paul@66 | 497 | calculating the colour used in the calendar. This means that related
|
paul@66 | 498 | events can be coloured identically if their summaries are the same.
|
paul@71 | 499 | * Added support for multiple events on a single event page.
|
paul@71 | 500 | * Introduced EventPage and Event abstractions in order to better support new
|
paul@71 | 501 | features.
|
paul@78 | 502 | * Introduced basic and advanced modes to the EventAggregatorNewEvent action,
|
paul@78 | 503 | along with date swapping to correct cases where the start is given as
|
paul@78 | 504 | being later than the end of an event.
|
paul@77 | 505 | * Fixed the "download this calendar" and "subscribe to this calendar" links
|
paul@77 | 506 | by propagating the "raw" calendar start and end values within the macro.
|
paul@77 | 507 | These links should yield events only within the period defined for a
|
paul@77 | 508 | calendar, not all events in a calendar's categories. This fix also ensures
|
paul@77 | 509 | that the links for year- and month-relative calendars are correct, rather
|
paul@77 | 510 | than the specific links generated previously. Thus, a "this year's events"
|
paul@77 | 511 | link will now continue to produce a resource with the current year's
|
paul@77 | 512 | events, rather than the events from the year when the link was generated.
|
paul@65 | 513 |
|
paul@51 | 514 | New in EventAggregator 0.4 (Changes since EventAggregator 0.3)
|
paul@51 | 515 | --------------------------------------------------------------
|
paul@51 | 516 |
|
paul@51 | 517 | * Added a table view in the macro, using special topic/category styles to
|
paul@51 | 518 | provide background colours for events.
|
paul@56 | 519 | * Added category propagation from calendars to the new event form provided
|
paul@56 | 520 | by the EventAggregatorNewEvent action.
|
paul@56 | 521 | * Added a default template parameter to the macro, employed by the new event
|
paul@56 | 522 | form.
|
paul@56 | 523 | * Added a parent page parameter which is used by the new event form to place
|
paul@56 | 524 | new event pages in a particular location specific to a calendar or
|
paul@56 | 525 | collection of events.
|
paul@56 | 526 | * Improved the presentation of pop-up event information elements.
|
paul@59 | 527 | * Added navigation between display modes (calendar, list and table views).
|
paul@59 | 528 | * Ensured that calendar settings are retained when creating new events for a
|
paul@59 | 529 | calendar.
|
paul@59 | 530 | * Fixed various problems with events not having topics.
|
paul@51 | 531 |
|
paul@45 | 532 | New in EventAggregator 0.3 (Changes since EventAggregator 0.2)
|
paul@45 | 533 | --------------------------------------------------------------
|
paul@45 | 534 |
|
paul@45 | 535 | * Added a parameter to the EventAggregatorSummary action to select the
|
paul@45 | 536 | source of event descriptions for the RSS feed.
|
paul@45 | 537 | * Updated the documentation to cover the RSS support.
|
paul@47 | 538 | * Added the EventAggregatorNewEvent action.
|
paul@45 | 539 |
|
paul@41 | 540 | New in EventAggregator 0.2 (Changes since EventAggregator 0.1)
|
paul@41 | 541 | --------------------------------------------------------------
|
paul@41 | 542 |
|
paul@41 | 543 | * Improved the calendar view in the macro to use the fixed table layout
|
paul@41 | 544 | algorithm and to provide cells spanning potentially many columns for
|
paul@41 | 545 | continuing events. Introduced pop-up elements in order to show truncated
|
paul@41 | 546 | event names.
|
paul@41 | 547 | * Made the "weekly" naming policy the default in the calendar view.
|
paul@41 | 548 | * Improved the list view in the macro.
|
paul@41 | 549 | * Introduced RSS 2.0 feed support.
|
paul@41 | 550 | * Improved the help pages.
|
paul@41 | 551 |
|
paul@6 | 552 | Release Procedures
|
paul@6 | 553 | ------------------
|
paul@6 | 554 |
|
paul@18 | 555 | Update the EventAggregatorSupport.py __version__ attribute and the setup.py
|
paul@18 | 556 | version details.
|
paul@6 | 557 | Change the version number and package filename/directory in the documentation.
|
paul@51 | 558 | Update the setup.py and PKG-INFO files.
|
paul@6 | 559 | Update the release notes (see above).
|
paul@6 | 560 | Tag, export.
|
paul@6 | 561 | Archive, upload.
|
paul@10 | 562 | Update the MacroMarket and ActionMarket (see above for the URLs).
|