Last post Mar 07, 2007 03:30 PM by Falcon
Mar 07, 2007 12:09 PM|MrPea|LINK
I've been using the CSS Adapters for a little while and it seems that they aren't built as solidly and as fully as the original asp.net sort of control - like the Gridview for example. There are areas where if you put a property on a control, it doesn't
seem to make any difference...also on the gridview it doesn't appear to remember it's selected index between postbacks whereas the original asp.net version does remember
- so my question is really...the CSS adapters make the controls alot nicer, they build them in a much friendlier way...but are do they by consiquence make it harder to code, are we having to find alot more dirty hacks to solve problems which were already
solved before the CSS adapters came in?
I'm not knocking them at all, I think they're brilliant, I just wondered what experiences people have had
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Mar 07, 2007 01:45 PM|bdemarzo|LINK
I agree with your basic assessment. They are good, but quirky. Perhaps the recent change coming to their future (outlined
here) will help solve these.
I use them in every ASP.Net project I have that requires the 2.0 membership API. Things are a bit "unpredictable" at times. I'm not incredibly familiar with the inner workings of the adapters, but there does seem to be a lot of complexity to them. That's
more due to the complexity of the underlying control than the adapter itself.
Mar 07, 2007 03:30 PM|Falcon|LINK
There are areas where if you put a property on a control, it doesn't seem to make any difference...
Keep in mind that some of those properties not working are by design. The adapters assume you will be controlling presentation through CSS and not by inline styles and properties on the controls.
If, however, there are properties that are not presentational and are not working, you should post about those properties here. With Microsoft opening up community involvement on the adapters, it would probably help to get a list of all of the unsupported
properties that need to be implemented.