DayCalendar macro will show events on a single day with similar features as MonthCalendar (including colouring for group calendaring).

Currently it stores dates as BasePage/2002-02-11/2100 meaning that BasePage entity has a date at day 2002-02-11 at 21:00 and lasting for 30 minutes (because half an hour is the current resolution of the DayCalendar and intervals are not handled yet).

Open questions:

Will upload the macro as soon as this is a bit more clear to me and the implementation then gets more usable...


It probably would make more sense to store the appointments in a database, and then display them via the macro itself, so that you only have one page with the macro call, which then allows one to extend and explore the database.

Database can mean anything from flat files, XML, CSV, dbhash, SQL.

I'm still looking for the WikiWay of doing that sort of thing. SQL surely is not. -- ThomasWaldmann 2002-07-27 12:27:08


The problem with the sub page solution is, you get lots of tiny subpages that mess up AbandonedPages. This is a little bit annoying in the MonthCalendar (which I really like a lot though!).

Just to give you a different idea, how about a table with all the events, like:

date

start-time

end-or-length

optional WikiName

optional summary

2002-07-26

1200

+200

WhoJoinsLunch

go for lunch

... and you get an editable table of contents for free. I propose a macro syntax like [DayCalendar(WikiName1,WikiName2,...,year,month,day,year-offset,month-offset,day-of-set)] so you can split the table on more than one page.

A variation on this: in the above example, look for events in WhoJoinsLunch/year-month-day, but in the without the date column. Oh, forgive me, I'm carried away now. Take what you like.

twiki has a calendar plugin that reads its events from a topic page, but it has a different concept, it can display only a fixed month. Here's a link: http://twiki.org/cgi-bin/view/Plugins/CalendarPlugin - I would change the date format to use year-month-day.

-- MichaelRadziej

Michael, your suggestion would lead to quite some processing (and coding) needs:

Thinks that cannot be done (or at least would be somewhat complicated):

Further, this stuff should somewhat integrate with MonthCalendar and with Wiki without much hassle.

-- ThomasWaldmann 2002-07-27 16:54:30


I really like the idea of mananging DayCalendar and MonthCalendar concepts via MoinMoin. I have tried several "calendaring" apps. and utilities, being the most interesting AFAIK, eGroupware Calendar. Calendar without the chance of informing others via mail, it is NOT useful inside wiki concepts. Actually, one of the many things Moin is great at, is notifying subscribers.

So if Moin is a collaborative platform, Calendar should also be consequent to that "principle". However, using "external" tools/apps. such as SQL stuff, I personally wouldn't agree (I know very little about DB's but I know they gotta be kept somehow, while Moin doesn't) because then we'll start losing some of the control.

Besides, if Moin incorporates SQL stuff, then myabe next step is to build a Moin macro or parallel system in which we can send/receive mails and have them wikied (impact in a wiki way) into our Moin pages sites. That would be very cool, so we can relate and keep logs of mails regarding a specific subject discussed by wiki pages, but again, if it means external use of languages and apps. then why not simply use eGroupware or something like it.

-- MauricioHernandez 2004-11-19 14:05:53

Why not simply use MonthCalendar to create days pages, and use standard markup on the page:

08:00
Go to work
09:00 - 12:00
Try to do some work
12:30 - 13:00

lunch with JoeDoe

and so on.

Month calender may read those pages and show you all or some items in its floating boxes. For example, the macro can read today page, and show you all the events left. Before 08:00 it will show all or first items, on 12:00 it will show you only the lunch item.


MoinMoin: DayCalendar (last edited 2007-10-29 19:21:58 by localhost)