I have created the following.

1. ASPNetSkin Object
2. Sample skin using skin object
3. Source of skin object

I have converted 4 of the ASPNetMenu samples

1-multicolor3d
2-progressiveGray
3-silver3dGradient
4-blackBulleted

This can be edited be changed the SampleSkin property of the skin object
<dnn:ASPNETMENUSKINOBJECT runat="server" id="dnnASPNETMENUSKINOBJECT" SkinSample="3" />

For more inof go here. Register and Log in to download
http://www.corderman.com/Default.aspx?tabid=93

Yes I know Steve beat me to it ...POST( by only a few hours ) but perhaps we can combine our code ? what do you say steve?

Hey Bert,
I have no problem sending you the code. Maybe it's best for everyone if there's only one version out there so people don't get confused. If you want that responsibility that's fine with me. I really created the Skin Object because a client who wanted a skin also wanted to use the ASPNETMenu, and there wasn't a skin object available (at the time) so I put one together.

Let me know if you're willing to be "the guy" and I'll send you the code. Or if you don't want to deal with the support issues, let me know if you'd rather that I support it. Doesn't matter to me, whatever you'd like.

Either way works for me also. Before I do to much work though I am interested in discussing a few things

1. I am intested in hearing more about the Menu Provider that I have heard a few core members talk about.

2. SKinObjects settings.

A skinobject is kindof like a module except it reads its settings form the control definition. This definition is set when uploading the skin. How about a way to modify skinoptions with a GUI?

The question would be how are the settings assoicated with a specific skinobject. I think at first they coudl be defined at the portal level. For example the ASPNetMenu skinobject could get its values from the database based on the portal ID. An override should also be defined in the skin object so it can be configured to pull values form the DB ir use the the settings defined in the control.

Thoughts
Bert

Hi

Yeah good thoughts.

We had made a skinobject that allows to generat dynamic imags based on the active tab.

However lets say you have a portal with a few subportals each using differtn skin but same skin object. If you have white background with red font that would work on skin one but would look weird on sin 2 because that one has a blue background.

The way we fixed it is by giving a skin module its own adminmodule, the administrator will see and edit link in front of the skinobejct abd when clicked will show the admin module. Here you can change the like 50 settings ;)

Each skinobject is referenced by tabid - so giving you the abillity to change the settngs of the skin object per tab id. In our case you can create dynmic header image per tabid, so on etab one blue image with red font, on tab2 blue font on flowe background, on tab3 is font overlayed on background.

Well hats how we did it, Hope to show it soon

Hi Steve and Bert,

I see you guys finished it off and got it out of the gate before me... ! :-)

If you guys are interested getting together on this, I have a developer license for unlimited number of applications, as well as unlimited, royalty-free distribution of the control with solutions built with AspNetMenu.

This way we can package it up as a "complete" module with all the features....

You can get me at: colin_mulcahy@hotmail.com

Oyster

I was wondering if I might have to go out and buy a Developer License just to get this functionality. Since Oyster already has it, it would really be super fantastic if you could collaborate and make this a full package.

It could really move DNN to the next level.

Thanks for all the great work.

I iwll have to get back to you guys with this next week.. no DotNetNuke for me for a weak VEAGS baby !!!

A complete module with the ASPNetMenu would be AWESOME!