Use a mvw (model/view/whatever) pattern
- model: "pure" javascript library modelling abstract concepts. This part usually contains objects & methods names related to the application domain (car business -> car objects / insurance contracts) and the data access logic.
- view: a custom language describing how your UI look like. Preferably, the language should be close to HTML.
- something to make both part communicate without having one depend too much on the other. A change in the model data must result in a change in the corresponding elements of the view (model -> view). A mouse click mouse result in a method call somewhere in the model (view -> model).
With those concepts, you can choose different stacks
- You can use a big framework such as angular. The views are html dom template. The model is divided between controllers & services.
- you can use backbone (~model) + jquery (~view)
- you can use react.js
... the list goes on. The number of tools available is actually pretty scary. Check http://todomvc.com/ for a nice list of examples.
Example solution with angular
In angular, the connection between the model & the view is performed with a viewmodel & dual way data binding. A view model is a javascript object. Both the view & the model can read & write to this object, and react to changes.
in your view, you write the HTML:
<TABLE class="list_grey" style="float: left; margin-left: 20px;" ng-hide="hideAll">
<TR ng-repeat="row in rows">
<td ng-repeat="val in row" ng-class="{selected : val.sel}"> {{ val.label }} </td>
</TR>
</TABLE>
in your controller, you only deal with javascript values:
$scope.rows = [
[{label : "foo"}, {label : "bar"}],
[{label : "foo2"}, {label : "bar2", sel : true}]
]
$scope.hideAll = false;
ng-repeat
allows you to display a list of items. ng-class
& ng-hide
are used to control the class & visibility of the elements.
Closing words
Using other frameworks, the resulting organization may vary, but the essential separation still exists. In react.js, the data binding is unidirectional, which implies different construct. The mvw framework usually deals with the communication between the components, so you don't have to use jquery at all.
This is a good thing if your project isn't trivial. Managing a complex app with only jquery can lead to a mess of callback interactions which may become hard to maintain.
Using a full mvw framework such as angular or ember requires some learning. Some other libraries have a smaller scope such as react.js & knockout.js.
Of course you don't have to start learning one of these tools right now. The important thing is to achieve the separation between the view & the model. You can use jquery to write functions which will edit the dom according to observation made on a pure javascript library.
You can also use jquery to write the (view -> model) callbacks. (model -> view) can be written using publisher/observer. This part should be as small as possible, and be the only thing connecting the model and the views.
Best Answer
Yes. Definitely valid advice. CSS classes, for the most part, should not be tied directly to what they look like. Tie them, instead, to what they mean.
If you're using
.blue
to provide emphasis, and your site design changes so that you no longer want your emphasis to be blue, then you have a disconnect between the display of the element, and the class name.If, instead, you used
.emphasize
, you could change the color in the CSS, and the HTML attribute would still be meaningful. You get the change without having to touch the HTML (or, in this case, you could style theem
tag, and get even better semantics in the HTML).In addition, it makes your CSS more readable. When you're changing
.blue
, it's not obvious what elements on your page you're changing. But if you're changing.emphasize
or.pull-quote
, you can immediately tell.There are instances when non-semantic class names are unavoidable, but this is mostly when creating generic layout. Things like
column
orcolumn-left
orhalf
orthird
are necessary in grid-based layouts.So, my opinion is that layout doesn't need to be semantic, and usually won't be. But content should definitely be semantic. Ask yourself what your content is, and make the class name represent that, so it can be used in a meaningful way.