This is a record of pre v0.98 Bugs and Disussion for EventCalendar, moved from the original page to make that somewhat clearer.

Contents

  1. Bugs
    1. v0.98
    2. v0.94
  2. Discussion
    1. v0.98
      1. Commented data
    2. v0.94 ~ v0.96
      1. Background Color for days with events in simple view
      2. What to do with eventcal.css
    3. discussions for older versions than v0.94
    4. Event Name

Bugs

v0.98

v0.94

Discussion

v0.98

Commented data

I really love the event calendar and I think it's one of the best macros (if not the best) for Moin. What I would like to be able to do is comment the part where actual event calendar data is shown, something like: 

= Event1 =
## start:: 2006-06-10
## end:: 2006-06-11
## description:: some description

description which will be shown on the page...

It works if I take the comments off. Could parser be fixed somehow to include commented lines? Or is there any other way to acomplish this?

v0.94 ~ v0.96

Background Color for days with events in simple view

I can see that in your example page, the simpleview of the calendar has distictive colors for days with events (palid blue) and days without them (white). How can I get this behaviour?

Cheers and thanks for the good work :) -- Offray

What to do with eventcal.css

Hi all, I have a newbie question and a request to describe this thing better in the installation guide: Where must I add the eventcal.css? Is there a way to import the *.css or must I copy whole eventcal.css in the right common.css? I wish for some more information in the installation guide at this place. Thx, for help. -- Stephan, 24.04.2006

very nice, but one page for one day is much easier to handle and more secure. -- GSB 2006-01-30 17:42:28

hi, great addition to MoinMoin, but with the latest versions for 1.5 i've a problem: events from one page are displayed correctly, but only some events from another page are listed -- RiBeZ 2006-02-23 22:38:23

Hi, if the list of events gets longer (e.g. after one year...), the "List"-view will be very long, because it shows all events regardless if they are already expired or not.
My idea would be something like "previous 100 events"+"next 100 events", or other ways to make the list shorter.
Thanks a lot for the good work! -- ChristianNass 2006-03-01

Another thing that I thought about: I would prefer some kind of coloring schemes for the events. Instead of (or as an alternative option) giving an event a specified color code, events should get a "color label", like "important" or "holiday" or the like. And on a additional page, also referenced by the category, these color codes will be resolved.
Or more general, there could be global definitions like 

ColorCode(importang):: #ff0000

so it is not important if this appears on an extra page or in the page itself.
Thank you, Christian -- ChristianNass 2006-03-01

discussions for older versions than v0.94

Of course XML suck for data entry. But you may use wiki markup, for example: 

== Event Name ==
Event description...
 start:: 2005-10-25 14:00
 end:: 2005-10-28 20:00
 foo:: bar

This markup is automatically rendered in a meaningful way:

Event Name

Event description...

start
2005-10-25 14:00
end
2005-10-28 20:00
foo
bar

You can parse this data using a special event formatter, that ignore everything but heading level 1, paragraph, text and definition list. When you format you page with such formatter, it can produce a list of events objects, each with name, start, end, foo and description. Check how MoinMoin/formatter/pagelinks.py works. I think this will be the easiest way to parse your data into format you can use. Then pickle your event data in the page cache directory. Next time you need to read the page data, use the cache. Check how Page use this system to create a pagelinks cache - Page.getPageLinks, Page.parsePageLinks.

-- SeungikLee 2005-10-29 18:26:31

Use page content, not a file.

Why use both data file and a wiki page?

I tried your event test page. It is not clear how you should work with it. I learned by trial and error that each #!eventcal is an event, and I guess you use the date~date as start and end date.

I suggest you write a specification that describe what kind of activities you want to support, and how people should do common tasks. For example, how one should add an event, change event data like start date, end date etc. It is hard to test the implementation when you don't know what the system should do :-)

Looks fine and useful, some wishes

I thought more on using the existing wiki markup for example. The nummeration is done automaticly. 

{ { {
= first event =
 Event description...
 start:: 2005-10-25 14:00
 end:: 2005-10-28 20:00
 foo:: bar
 color:: <#FF0000>
 bgcolor:: <#CCCCCC>

= second event =
 Event description...
 start:: 2005-10-30 14:00
 end:: 2005-11-08 20:00
 foo:: bar

= third event =
 Event description...
 start:: 2005-11-25 14:00
 end:: 2005-11-25 14:00
 foo:: bar

----
CategorySystemCalendar
} } }

While this page is set to the category CategorySystemCalendar it's entries are shown in the SystemCalendar. Similiar to include pages a user could add on an own page private entries secured by acls for only reading from him. Then if he looks at the calendar own entries are shown too but if one else looks his entries are invisible.

If it would be possible to have dependencies the second and following heading levels could be used -- ReimarBauer 2005-11-05 08:44:26

It's an easy format to use IMHO. I'll take it into consideration to the next update. -- SeungikLee 2005-11-29 01:47:58

What if I prefer using RestructuredText to display my Information? Did I get this right, that everything inside { { {#!eventcal ... } } } is parsed by eventcal and then given to the wiki-Parser? Can I tell eventcal to use ReST? (Nesting parsers doesnt seems to work -- which makes sense to me) -- HenningHasemann 2005-11-29 11:08:10

Okay, I think I can live without RST for the few lines / words that define dates, so that isn't too bad, but another thing I would consider useful is some kind of patterns. For example having things happening every Monday or so. Maybe the good old "calendar" program for UNIX/linux would also be a nice example for a syntax where one could easily describe repeating events. From the man page: (\t is the <TAB>-Character, calendar uses this to split dates and information) {{{ Thursday\tEvery Thursday.

}}} -- HenningHasemann

The macro is updated to v0.91. The target of this update is to make it simple to use esp. in event data format reflecting some comments here. Please look through it at http://www.silee.net/CalendarTest and post your valuable comments or suggestions. Thanks. -- SeungikLee 2006-01-13 06:37:01

MoinMoin: MacroMarket/EventCalendar/OlderDiscussion (last edited 2009-07-16 14:50:58 by RuthIvimey)