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