A question about the stylesheets. There appear to be two sets: one that provides default functionality, the other providing "theme-related" styling. Am I right in thinking that the intended implementation is that pages using (say) the adapted Menu control should link to the former styles as well as the "theme" styles? When I remove the link to the basic styles in the source code project, I don't notice any difference in appearance or behaviour... have I missed or misunderstood something?

dotcomsoftware:

The same goes for other properties such as StaticDisplayLevels.

By the way, the reason I mentioned this property is so that the menu can be used with the SiteMapDataSource. Sitemaps only allow one root element, conventionally the site home page. Displaying just a single menu item for the home page is usually not enough; normally you want to display the second tier of links as well. To achieve this with the Menu control, you set the StaticDisplayLevels property to 2, thereby "flattening" the first two tiers of the hierarchy into one. If you try this with the adapted control, it doesn't work.

dotcomsoftware:

When I remove the link to the basic styles in the source code project, I don't notice any difference in appearance or behaviour... have I missed or misunderstood something?

OK, I see it now, you're using embedded stylesheets, so the link from the page to the .css is not necessary. I suggest removing those explicit links in the pages and highlighting somewhere that you are using embedded css definitions so as to avoid confusion.

dotcomsoftware:

The same goes for other properties such as StaticDisplayLevels.

By the way, the reason I mentioned this property is so that the menu can be used with the SiteMapDataSource. Sitemaps only allow one root element, conventionally the site home page. Displaying just a single menu item for the home page is usually not enough; normally you want to display the second tier of links as well. To achieve this with the Menu control, you set the StaticDisplayLevels property to 2, thereby "flattening" the first two tiers of the hierarchy into one. If you try this with the adapted control, it doesn't work.

The goal is to implement all properties so they have the same behavior as they do today. The only thing the adapters should do is change HTML markup -- not behavior. So, yes, a proper implementation would include support for StaticDisplayLevels.

For those following along, I just made some notable updates to the AspNetControlAdapters project (see http://code.google.com/p/aspnetcontroladapters).

Of note...

• Baseline support for all common WebControl style properties (BackColor, ForeColor, Style, etc.) is built in, and it will be easily integrated into future controls.
• The CheckBoxList has additional support, and has been thoroughly tested with postbacks.
• Documentation is updated, as always, with each change: http://code.google.com/p/aspnetcontroladapters/wiki/CheckBoxList?ts=1224689420&updated=CheckBoxList 

I'm interested!

I need to render a Wizard in a standards compliant way. I embarked on writing my own page from scratch to reflect the functionality of the wizard, but have run into problems.

I found Tokely's WizardAdapter at http://andrewtokeley.net/archive/2008/05/16/css-adapter-for-asp.wizard-control.aspx and so installed the CSSFriendlyAdapters. The problem I have is that I can't specify my own layout. Some of the divs are in the wrong place for my liking. I guess I'd have to write my own adapter to output the divs as I wanted them. However I daren't jump into that just yet - I'm only a junior developer with 2 years experience, and I have deadlines looming!

I have done a little work on a new Wizard Adapter in the AspNetControlAdapters project: http://code.google.com/p/aspnetcontroladapters

It is very much incomplete, but if someone can provide some real-world examples of current usage, it would be easier for me to finish coding it. (I don't do much WebForms development now, so real-world samples are lacking.)

If you want to contribute to the effort, post on the Google group at http://groups.google.com/group/aspnetcontroladapters -- provide as much as you can in terms of an example of your CURRENT Wizard code (aspx and codebehind), the CURRENT generated output, and the DESIRED output.