[on list reply]
# behind a selector apply the rule to the elements that have an id equal to the selector name
 
glad that you find it cool ;))
 
Gauthier
----- Original Message -----
Sent: Thursday, May 30, 2002 7:31 AM
Subject: RE: Witango-Talk: Something usefull/helpfull for Witango developers

[Off List]
Very Cool... ;-)
 
As I am learning also, Why did you put a "#" in front of a couple of the Style Sheet definitions?
 
Ben "the newbie in CSS" Johansen
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [Gauthier]
Sent: Wednesday, May 29, 2002 9:36 PM
To: Multiple recipients of list witango-talk
Subject: Witango-Talk: Something usefull/helpfull for Witango developers

Hi, here is a snippet that I've just done for the community use, it will help you when debugging your application files.
 
Please feedback any suggestion or even if you just find it usefull.
If anyone add some extensions It will be glad that it remain available for the communauty
 
I plan to have a better rendering of arrays etc...
 
I know that there is many @rows loop that can be optimised with use of variables assigments
but I've just done this because I'm completly excited with the DOM features and I know it will help me in any Witango development, and I'm not a mad developer that can implement everything in the first batch ;)
 
Gauthier
 
ps:
WARNING:
-it work only on standard compliant browser, that's not an issue as soon as it's fired only on the developper computer and he can easily install a compliant browser ;)
-you should change the local$scopeArray values to add array that matter for you
 
here is the first bugs that I've reported to myself:
-if you change the current tab, the ex-selected var will remain 'selected' in the tab content
-if you have variable with same name in multiple scopes, they all are showed when you click one, but it's finally a kind of feature so I keep it for the moment

Reply via email to