Comments on: CSS Styling for ASP.NET Applications http://www.dennisdeacon.com/web-design/styling-asp-net-apps/ Web Designer, Developer, Marketer, Strategist Tue, 16 Mar 2010 20:18:44 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Lewis Cowles http://www.dennisdeacon.com/web-design/styling-asp-net-apps/comment-page-1/#comment-249 Lewis Cowles Fri, 11 Dec 2009 04:19:14 +0000 http://www.dennisdeacon.com/?p=170#comment-249 I love your encapsulation of the job, it rings very true to me, and also rings a few bells with the css border, a quick tip is that you can use javascript to iterate through the genrated html source code of the asp.net platform and paste into a tabbed textual editor, this will help you to experiment without opening lots of files, reloading and also you can semantically seperate core css needs against extra css for specific website areas To do this all you need to add is a simple before the end of the document body (which should only occur once in a well constructed ASP.net system getElementsByName on common tags p,table etc and setStyle on them as well as setting onclick events which return the line-numer, tag type and info of the tag such as class etc, write the data into the tabbed text editor in a long list for each page and run a comparison (I use textpad) it finds all of the similar elements and groups them together total time less than 20minutes for a 12 screen-type 157-page website (12 independent rendering screens with 157 pages of total content) Hope this helps also once done on one asp.net component you can save the css for that element to streamline further work I love your encapsulation of the job, it rings very true to me, and also rings a few bells with the css border, a quick tip is that you can use javascript to iterate through the genrated html source code of the asp.net platform and paste into a tabbed textual editor, this will help you to experiment without opening lots of files, reloading and also you can semantically seperate core css needs against extra css for specific website areas

To do this all you need to add is a simple before the end of the document body (which should only occur once in a well constructed ASP.net system

getElementsByName on common tags p,table etc and setStyle on them as well as setting onclick events which return the line-numer, tag type and info of the tag such as class etc, write the data into the tabbed text editor in a long list for each page and run a comparison (I use textpad) it finds all of the similar elements and groups them together

total time less than 20minutes for a 12 screen-type 157-page website (12 independent rendering screens with 157 pages of total content)

Hope this helps

also once done on one asp.net component you can save the css for that element to streamline further work

]]>