6

The two don't have to fight necessarily but generally I'm in agreement that the "OOP CSS" people generally don't have a clue about good programming or good CSS. Some do, but a lot don't. First of all when people talk about OOP-style CSS, what they're really talking about is a componentization scheme. Not OOP. That they're willing to call it OOP is an ...


3

Do use the visual designer to layout your GUI. Doing anything else is masochism. Don’t put all of your code in the Form’s code behind. Do use the Model-View-Presenter pattern. The form raises an event, which the presenter listens for, and reacts to by modifying the view and performing other business logic.


2

I personally can get on board with a nice balance of the two where in you have oocss for helpers and you have semantic css for components... and the decision to create a component would come in when you find yourself applying the same oocss elements repeatedly. I don't get why people are so all or nothing, there needs to be a balance, one nice thing about a ...


1

Thanks for your comments - I've been able to clarify my thoughts on this. The distinction between the two seems to be on workflow. The former (object oriented css) is more of a traditional print based approach where colours and styles are chosen first for a branding goal, and then the website is assembled from that later. The latter (semantic css) approach ...


Only top voted, non community-wiki answers of a minimum length are eligible