|
|
|
|
| Author |
Messages |
|
Lance Long
Registered Users
Nuke Wiz
Posts:131
 |
|
Lance Long
Registered Users
Nuke Wiz
Posts:131
|
| 1/17/2008 12:55 PM |
|
| No??? Nobody wants to put Child Links in the skin instead of as a module? |
|
|
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:12450
|
| 1/17/2008 2:01 PM |
|
| The difficulty with the skin object is that you can't set the properties dynamically, e.g. you would need to define them when designing your skin using skin.xml, are you familiar with this method? Its the way you set properties on current skin objects? |
|
Scott McCulloch
Site Administrator |
|
|
Lance Long
Registered Users
Nuke Wiz
Posts:131
|
| 1/17/2008 2:20 PM |
|
I generally skip the XML+ HTML method and go straight to the .ascx. but, yes I'm aware of the implications. It would make the skin object a "professional" option. I use skin objects with over 30 attributes so complexity doesn't scare me.
What I like most about the child link module is the template control. ( Better if it were in a folder like property agent but the current method is livable.) The template means I have full control over my mark up. If I want to use DLs, I can. If I want to make a JS menu system I (could). Most other menu modules are strict about how the menu is marked up and follow one school of thought on CSS mark up etc. That mean I need a number of them to meet design needs. If Child Links had exposed templates, sub levels and skin object support, it would be the only menu I would need. |
|
|
|
|
|
| You are not authorized to post a reply. |
|
|
|
ActiveForums 3.7
|
|
|