As a developer, you must have faced a classical issue, the UI guy says “dude, the control that you have used got converted into table (<tr><td>) structure and it has screwed up my entire styling/CSS, I have to do a rework”. And the timeline has to be extended. This is a classic problem when we work in group, startup or as a freelancer. In big companies, there a specialist to create ASP.NET UI, but at smaller scale becomes very crucial.
My suggestion to developers and designers is that they should not hate .NET in terms of UI. You are already provided with lots of settings with each control. Some examples are as below:
1. Radio button list and checkbox list
- repeat layout: table, flow, unordered list, unordered list
repeatDirection: horizontal or verticalrepeatcolumns: enter the number 
2. Tables/Grids
For giving a try to listview, trust me, you can say your designer that created any UI, anyway and I will repeat the template/row/structure using listview. Just read well about listview and you will fall in love with it.
3. Buttons
A common practice by designers is that they will create buttons using href tag and give them hover effects, and developer will make everything go waste by replacing them by normal asp:button tag just because they are in the habit of using it and working on click events. End result, UI gets bad. Ask the UI guy to use anything for button but as developer keep your eyes open to use the following buttons:
Button: Renders as input:button- Link Button: Renders as “
a” tag - Image Button: Renders with background image and “
a” tag
And the list goes on for all the controls, study them well and make peace within the team.
The post Classic problem between developers and UI designers appeared first on Clear your dot net issues.
