Re: Features Listing

"Tomislav Grabic" <[email protected]> wrote in message
news:[email protected]
> Jason Judge wrote:
> > "Tomislav Grabic" <[email protected]> wrote in message
> > news:[email protected]
> >> mikespub wrote:
> >>> In article <bk7106$35j$1-111RdWWlOxkOkXtL6OYfHgC/[email protected]>, "Tomislav Grabic"
> >>> <[email protected]> wrote:
> [...]
> >> I didn´t know this... so, to have an example, [article:it came from
> >> the desert:aid:89] would lead to
> >> http://www.iroke.de/index.php/blogs/89 in my case? What happens if I
> >> move the article to another category, does the ID change?
> >
> > It doesn't do exactly that yet - but you are on the right lines. If
> > you let me know what you _would_ like it to do, and what the matching
> > string should look like, then I can set up some examples in the
> > default install to do exactly that.
>
> Why is it neccessary to have the title in the [link], shouldn´t it be
> prevented that two objects in the system don´t use the same ID? If it´s
> unique, you wouldn´t need the article title to identify the object in
> question. :-) Having the ID shown in the admin overview for articles would
> be nice btw.
>
> There are two kinds of links I can think of right now with slight optional
> possebilities. Internal and external, so i.e.

There is an example of an external autolink in autolinks now. The RE will
match any external URL (i.e. a URL for a site other than the current site).

> [aid:89] creates <a href="http://www.iroke.de/index.php/blogs/89">it came
> from the desert</a>
>
> [title:my alternative title blabla:aid:89] creates <a
> href="http://www.iroke.de/index.php/blogs/89">my alternative title</a>
>
> [aid:89:e] creates <a href="http://www.iroke.de/index.php/blogs/89">it
came
> from the desert</a> in a new window (e for external, whatever :-) )
>
> [xaraya.de] creates <a href=http://www.xaraya.de>Xaraya title</a> in the
> same window
>
> [xaraya.de:e] creates <a href=http://www.xaraya.de>Xaraya title</a> in a
new
> window

All these are possible now.

> I didn´t include the target=blank stuff as it isn´t xhtml compliant and
the
> Javascript I use doesn´t work with browsers with JS turned off...

The variable '$target' will be passed to the rendering template to use as it
pleases. The target could be empty, _blank, or even some window name of
choice. Whether the template uses that value, and how it uses it, is up to
the theme writer. At the moment the default template creates a target="name"
attribute in the 'external' example, but if we ever have a system-wide
standard for creating separate windows, then that could be built into the
template too.

> ...and when I think about it, I´m not sure whether a WSYIWYG wouldn´t be a
> better way to do it instead of using autolinks?

As always, it depends on what you are trying to achieve...

-- JJ