[ewiki] Re: make PageIndex core feature?
- From: Mario Salzer <mario@xxxxxxxxxxxxx>
- To: ewiki@xxxxxxxxxxxxx
- Date: Tue, 15 Jun 2004 01:18:24 +0200
> > The "PageIndex" plugin however seems useful and general
> > enough to get included into the core script instead. Also it
> > is very little code anyhow, and having it enabled per default
> > wouldn't hurt anybody?!
>
> Lets get it in there! This is past due.
so this is clear.
> > Any other ideas on what to integrate fully into the core script?
> > Following come to mind:
> > - markup/css
>
> Having css markup core would let me have css classes end at the end of
> list elements, please make this core.
Making it core wouldn't automatically give it more power. The current
implementation however is, admitted, more a workaround than a markup
extension. And there is another problem with "@@" in that it is only
supported by ewiki! I have seen at least one other Wiki where "%%"
was used for CSS for example.
Not that I'm going to break backwards-compatibility; but before we tie
this into the basic markup, it should get rock-solid and standardized
at best (I've lately thought of the w3c embracing a WikiMarkupStandard
instead of pushing an ietf-RFC).
Also, the longer I think about it, I'd rather keep it only one of
our "standard features" (instead of "core feature"), because other
people may not need it or be afraid of security problems (emh, even
with CSS this may be an issue, right now IEs "beaviour:url(...)"
shouldn't do any harm with in-tag style= syntax, but it could with
another yet unknown leak).
While I use it and believe it's better then all the backwards color
text wiki markup out there, it may still need more work and not be
enforced too much.
> > - PowerSearch
> Search needs a significant rewrite. I suggest keeping it out for now
> but integrating it in the future.
True, and especially neither "PowerSearch" and "SearchPages" are the
optimal page names for both (we'd keep aliases if we ever changed it).
But we could move some code from PowerSearch into the core function,
and then develop a really powerful PowerSearch extension
("+word -exclude", "AND" and "OR", grouping).
Eventually we even could start a mpi for far more extended search
capabilites (we now have meta data, categories and more, that could
be used to group/sort results).
But that's a different thread...
Other related posts:
