| Previous · Next | |
| User | Message |
|
rogier
|
Date: 11/11/2009 10:13 am · Subject: Classname for subscribe/unsubscribe · Rating: 0
Does this make any sense? From the collaboration template: <tmpl_if user.isSubscribed> This allows a designer to style the unsubscribe link different from the subscribe link. But it's still possible to make them identical. Alternatively we could use:
There's probably more instances of this type of "dynamic" links, so I thought it would be useful to come up with a standard. Any ideas? Can anyone think of another examples of this type of link?
Rogier | United Knowledge |
| Back to Top |
Rate [ | ]
|
|
serif
|
Date: 11/18/2009 1:39 pm · Subject: Re: Classname for subscribe/unsubscribe · Rating: 0
Although the logic behind your suggestion is clever, "subscribe un" kind of reminds me of pig latin. ;) I'd tend to identify other areas with links like this (if they exist) and then have a general class with the classes "subscribe" and "unsubscribe". If there aren't any other links like this, your suggestion is fine. I believe Tabb compiled a list of controls for each asset, so I'll take a look at that when I get a moment.
Tessa Harmon |
| Back to Top |
Rate [ | ]
|