Needed functionality

[MorMayo]

I just wanted to say that I think this project definately needs to be
readdressed. My current employer uses the original CSSFriendly
assembly. I like the idea of configuring the default CssClasses
rendered. We need a general WizardAdapter too.

[Brian DeMarzo]

Thanks for taking the time to post! Having had the pleasure of working
on doing front-end coding on a WebForms site the past few weeks, I
agree with you. :)

As you can see from the current code, there's a new CheckBoxList and
RadioButtonList adapter. I am now working on a Menu adapter -- I
should have a check-in tonight or tomorrow of the first (limited)
implementation.

Seems many people ask about the Wizard adapter (along with the
GridView adapter, the Menu adapter, the TreeView adapter...). It'd be
interesting to see what people feel is most needed -- not in terms of
what they wish they had, but what is currently most broken in the
CSSFriendly project that should be redone.


- b

[Robin M]

The idea of having a single DLL to include in the project is
excellent.

I think our main goal here should to be able one day to create a
ASP.NET website that is XHTML Strict compliant.

A adapter for each and every asp.net control to generate fully
compliant html code. Is this possible ? Unreal ?

The best practice to get this done ?

How it gonna impact performance ?

I'm already working on some adapters to avoid unnecessary attributes
added automatically by .net like border attribute for asp:image and
stuff like that.

[Brian DeMarzo]

Robin,

Would you be willing to share some of your adapter work with this
project?

(FYI -- I am working on a Wizard adapter, but it's going to take some
time...)