I just overheard this on IRC:
23:31 < osfameron> gah, I forget the @REDIRECT syntax... 23:32 < osfameron> Aha #REDIRECT (not to be confused with @INDEX_LINK) 23:33 <@Dom> yeah, that is confusing.
Maybe we should phase in #INDEX_LINK (or @REDIRECT) in parallel before dropping one of the variant forms. What do people think?
On Tue 22 Jun 2004, Earle Martin openguides@downlode.org wrote:
Maybe we should phase in #INDEX_LINK (or @REDIRECT) in parallel before dropping one of the variant forms. What do people think?
Let's have them both. So #INDEX_LINK and @INDEX_LINK both do the same thing, as do #REDIRECT and @REDIRECT. What can we lose? And each is a single-line change in the code.
Kake
----- Original Message ----- From: "Earle Martin" openguides@downlode.org To: openguides-dev@openguides.org Sent: 22 June 2004 23:44 Subject: [OpenGuides-Dev] Muddled syntax
I just overheard this on IRC:
23:31 < osfameron> gah, I forget the @REDIRECT syntax... 23:32 < osfameron> Aha #REDIRECT (not to be confused with @INDEX_LINK) 23:33 <@Dom> yeah, that is confusing.
Maybe we should phase in #INDEX_LINK (or @REDIRECT) in parallel before dropping one of the variant forms. What do people think?
Bear it in mind that @INDEX_LINK is a construct that will expand to a list of pages in the category/locale at some future date (expand in the sense of expand in-line in the HTML, rather than providing a link that runs a query).
I guess that '@' is a foible of us Perl hackers, that we know means an array. But I think that the future might involve using template language (TT2) in the body of pages instead.
On the other hand, #REDIRECT is syntax stolen^Wborrowed from UseMod.
In my opinion, #REDIRECT is a kludge which we can do better without. Redirection should be handled in page metadata, which allows us to put in place temporary redirects (for showing Christmas trees on the home page for example, without interfering with the contents of the page).
This also allows us to think ahead to future functionality, such as conditional redirects. Doing this in metadata also allows us to use the redirects the other way round, by way of showing all pages that redirect into this page, as template variables when rendering the page.
My $0.02
On Wed, Jun 23, 2004 at 12:49:21AM +0100, IvorW wrote:
Bear it in mind that @INDEX_LINK is a construct that will expand to a list of pages in the category/locale at some future date (expand in the sense of expand in-line in the HTML, rather than providing a link that runs a query).
Wouldn't it then merit a different name, like '@INDEX_LISTING'?
On the other hand, #REDIRECT is syntax stolen^Wborrowed from UseMod.
Personally speaking, I wouldn't mind changing the redirect syntax you could redirect pages by making the first line of the page read simply "redirect: Some Page" (like a pseudo-HTTP header).
Redirection should be handled in page metadata, which allows us to put in place temporary redirects (for showing Christmas trees on the home page for example, without interfering with the contents of the page).
This is an interesting idea; what kind of interface would it require?
Doing this in metadata also allows us to use the redirects the other way round, by way of showing all pages that redirect into this page, as template variables when rendering the page.
I like that. FWIW, I also think having a message at the top saying "(redirected from Some Page)" - where the page name links to the edit form for the redirecting page, like UseModWiki - would be nice to allay potential confusion from people not used to being redirected.
IvorW said:
But I think that the future might involve using template language (TT2) in the body of pages instead.
Yay! In which case the CGI-Wiki formatter plugins would be changed into TT plugins? (Though I guess that some wikis won't want user-visible TT, but they would just pass their raw code to the relevant TT plugin to format it?).
openguides-dev@lists.openguides.org
-
Earle Martin -
IvorW -
Kate L Pugh -
Osfameron