1 |
On Sun, 2005-11-27 at 10:20 -0500, Curtis Napier wrote: |
2 |
> I thought of that too. The problem is that I would have to add a new |
3 |
> function to the href's parser and I'm not sure I want to add anymore |
4 |
> complexity than we have too. Not to mention the href parser won't work |
5 |
> on hard coded links in the menus and jumppads, only on dynamically |
6 |
> created ones from xml files. This means if you turn off the ads then |
7 |
> click a link in the menu the ads come back but if you click a link |
8 |
> within the content area the ads will stay off. This is inconsistant |
9 |
> behaviour and not really something I would want to do. Changing the href |
10 |
> parser to work on the menu links wouldn't be an easy task. I would have |
11 |
> to think about how to do that and experiment a little. |
12 |
|
13 |
It may now be a moot point, but I don't think you understand what I |
14 |
meant, it is extremely simple to do and works exactly like full=1 or |
15 |
style=printable, etc., I still don't know what you mean by "href parser" |
16 |
or adding a new function to it, and yes if you click a link you change |
17 |
the current page and the ads come back...the same thing will happen with |
18 |
javascript unless you use cookies and technically you could use cookies |
19 |
this way as well, but cookies aren't something I think we would ever |
20 |
want to use anyways, so doing it in XSL would still give you the same |
21 |
effect as javascript, without javascript. |
22 |
|
23 |
-- |
24 |
Blackace |
25 |
Gentoo Linux |
26 |
Infrastructure Developer |