On Tue, 2004-16-11 at 16:56 -0800, Brion Vibber wrote:
Spiffy. There are some obvious problems of course,
namely the loss of
all the user options and message notifications...
Well, so, here's my theory: if we get an email-notification (or even
IM/Jabber notification... mmmm!) built-in, it will make new-message
notifications much less crucial.
Also, I think that it's possible to do some CSS, cookies and
Javascript-based client-side skinning that would obviate the need for
most of the user preferences we have now. I'm thinking something along
these lines...
http://www.alistapart.com/articles/alternate/
...but I think that's where we're going to have to go with Wikitravel.
We just can't afford the cycles to figure out who likes ? and who likes
red paint for broken links.
Your client-side cache problem on edit should be
solved by sending
appropriate cache-control headers to force the client to re-check on
every hit. I'm not sure offhand how to get Apache to do that, but I
suspect it's doable.
I'm thinking about trying to tag a random URL parameter at the end,
like:
http://example.com/wiki/Some_title_here?random=04567AC1
...but there might be an easier way to do that.
The problem is hard to reproduce, though.
The template invalidation list query is really ugly;
we really should
remember to stuff things in a template link table for 1.4; it shouldn't
be that hard.
Yeah, it's a bummer. A mitigating factor for Wikitravel is that we don't
use a lot of templates yet.
Another thing I'd really love is to concentrate on for 1.4 is building
extension modules rather than a monolithic application. I'd really like
to enable some kind of hooks-processing to make building behaviour
extensions easier.
~ESP
--
Evan Prodromou <evan(a)wikitravel.org>