Re: Features Listing
"Jason Judge" <[email protected]> Tue, 16 Sep 2003 16:25:15 +0100
| Newsgroups | gmane.comp.cms.xaraya.documentation |
|---|---|
| Organization | Xaraya News Server |
| Message-ID | <[email protected]> |
"mikespub" <[email protected]> wrote in message news:[email protected] > In article <bk7106$35j$1-111RdWWlOxkOkXtL6OYfHgC/[email protected]>, "Tomislav Grabic" <[email protected]> wrote: > >> Could someone update/check this: > >> http://www.wikipedia.org/wiki/Xaraya > >> > >> and post to Xaraya? Or if that's the current info, please confirm, so > >> I can add it to br.x.com? > > > >there“s something much more interesting... the way WIKI creates links within > >the system is easy, fast and would be a great feature for Xaraya. perhaps as > >an addon for autolinks, or unique IDs for articles, then linking to those > >would be totally easy... > >ciao > > > >tomi > > With autolinks, you can already link to articles (or other stuff) based on > some predefined codes. [article:title:aid:123] would show the title of > article 123 with a link to it, for instance. It's a really appalling matching key though ([article:title:aid:N]) - I had better change it before people start thinking it is more than just an example ;-) Suggestions welcomed. As an example though, it shows how an API can be called for each matchimg string, so a WIKI link could use the name of a document in your text - [wiki-page:mypagename] for example - but replace it with a link to the page ID and full title <a href="...pid=123">My Page Title</a>, for example. > For more details, see Jason :-) Ta. Real-life examples are very useful. I'm also thinking about opening up an API for setting up links, so that a link type, link, dd object, properties and DD instance can be created all in one go, from a single array or XML file of the same structure (any good XML<->array conversion functions out there?). In the same way that DD supports many other modules, Autolinks could service other modules that have the need to provide dynamic linking to content. You know a bit about hooks: is is possible to provide different types of hooks from a module to different modules? For example, could Autolinks provide a transform hook to all modules, but a create/update GUI hook to a selected few modules? Or is it an all-hooks-or-nothing system, with the hook module deciding when it should and should not supply hook details? I'm probably asking the wrong questions there - as I am not very familiar with the GUI side of hooks. Just something I am beginning to mull over as I see transform hooks with preg-replaces pop up all over BK... -- JJ