Wikevent talk:Todo

From Wikevent

Jump to: navigation, search

Data

OK, so I've added an extension from Christof Damian to draw calendars on events pages. Each date on each calendar links out to one or more events pages. There are a couple of potential problems with this approach:

  • I'm not sure I like having a page per-event, but I can live with it.
  • I haven't decided how to do cross-referencing
  • We will still have to allow for calendars to be uploaded in iCalendar format somehow.

Anyhow, it's something, so that folks at least can enter event data if they want to. If we run into a problem of needing to migrate data later, well then that's a pretty good problem to have. -- Mark 11:27, 5 November 2006 (EST)

I see a lot of potential problems for the page per-event approach. Mainly, that there will be thousands upon thousands of pages that will be hard to keep track of. One of the other issues is that I think it would be a turn off for contributors. If a contributor wants to share information they have to enter the info into multiple pages rather than just being able to enter the info one one or two pages. -- Sapphire 01:32, 6 November 2006 (EST)
It could be that we can have our cake and eat it too, at least as far as this goes. It seems to me that there are several points in favor of each event gets it's own page, and some more points in favor of doing them as batches. Really I think the best thing would have to be to do both. Besides we still have to do cross-referencing. All of this should be possible with an
incompleteeventwarning at
tag extension.  I'm starting on it tonight on the train (first I had to copy the setup from the server). --  09:59, 6 November 2006 (EST)
Would that work similar to <see>, <do>, <eat>, etc. tags that Evan created for Wikitravel and I've been converting listings to? -- 10:51, 6 November 2006 (EST)
It would be very similar in some respects, I think. For data-entry purposes I think they would be pretty much exactly the same. There are quite a few other good examples on the MediaWiki extensions page. If there's anything else in there that looks useful please do feel free to point it out. -- 10:58, 6 November 2006 (EST)

Recurring events

Bear with me as I try to explain what I would like to see in the language of "Giberi", a sophisticated form of "Giberish". Is there anyway we can create a page for recurring events like "United States of America 07 04", which will automatically fill in the calendar date of July 4th every year without the need to create an independence day page each year? -- 13:50, 12 November 2006 (EST)

Event

Moved from by .

I'm not sure this is necessary, since this should be filled in automagically by the event extension. If that's not happening please raise it as a bug. -- 10:11, 14 December 2006 (EST)

So simply use ? I was going to use that, but then thought I'd better play it safe. -- 10:13, 14 December 2006 (EST)
Even that shouldn't be necessary. Just click on a calendar date, and this stuff will already be there on the event page. It's automagical (actually it uses a preEdit hook). -- 10:25, 14 December 2006 (EST)
I hadn't noticed that until just a few moments ago, so I've already deleted this template and removed it from the MediaWiki template. Is now obsolete?
Yep.
As you can see I've been working on a lot of stuff that doesn't show up in recent changes. Next up is some graphic design. Then I'm going to do automatic cross-referencing of events from artist pages to venue pages. Then it's AJAX time. -- 11:17, 14 December 2006 (EST)
What exactly is AJAX? I know you can use it to do some in-browser image editing, but aside from that I'm not sure what it's purpose is. Thanks in advance. -- ~~~~
AJAX is a (somewhat silly IMHO) acronym for asyncronous Javascript and XML. The idea basically is that you can use Javascript to make http requests on an already loaded page, thus allowing users to do stuff which requires some server-side process without reloading. What I intend to do with it is to make it much simpler and hopefully faster to fill in the event tag, and in place on a venue or artist page (I've started leaning toward "artist" over performer). -- ~~~~
    Personal tools