Craig Weber crgwbr

OOCSS vs OOSass

note that this requires Sass 3.2 alpha or higher

OOCSS is awesome because it helps us organize our style sheets in clean and simple ways but it can be far too rigid for the new responsive web. How can we use preprocessors to preserve both flexibility and cleanliness of code? Can these objects be abstracted to our preprocessors?

Lets first take a look at three column widths in OOCSS to see how they compare.

CSS

	WITH tab AS (
	SELECT
	a.attrelid::regclass::text AS t,
	a.attname AS c,
	pg_get_serial_sequence(a.attrelid::regclass::text, a.attname) AS s,
	nextval(pg_get_serial_sequence(a.attrelid::regclass::text, a.attname)) AS v
	FROM pg_attribute a
	JOIN pg_class c ON c.oid = a.attrelid
	WHERE
	a.attrelid::regclass::text LIKE '%'

	from django.template.loader_tags import ExtendsNode

	def get_extends_parent(self, context):
	"""
	Patched onto Django's ``ExtendsNode.get_parent`` which is
	responsible for loading the template to extend from with
	the ``extends`` template tag.

	This patch allows the template foo/bar.html to extend
	foo/bar.html, given that there is another version of it that