entrepreneurship, design, development, django, jquery. A designer and developer in Eugene Oregon. Love my family, my work and the outdoors.
In our never-ending quest to provide fonts for all platforms and devices, we’ve rolled out support for Typekit fonts on the iPhone. This means you can now use @font-face across all supporting desktop browsers, as well as the iPad, iPhone, and iPod Touch.
Looking forward to using this!
Great overview of OOCSS. I've been working towards for some time now. I break my objects out by discipline. Layout, Typography, Forms, etc.
You can see a sample of what I use here: http://github.com/davemerwin/starterkit
Comments [3]
I'm finally getting back into the swing of things after a great trip to Portland for DjangoCon 2009. Needless to say I learned a TON.
The thing that I have been continuously impressed with about the Django community is a stringently agnostic approach to development. Django does not and will not commit to a specific JavaScript framework, database, or gizmo. Being agnostic provides a framework that allows me to do what I want, how I want. However, there is one exception. (X)HTML output. XHTML should not be the default output. And not for any ideological reasons relating to doctype, javascipt preference, or mime type rendering. But simply because it is not an agnostic decision. It's not loosely coupled, its magical, its not consistent, and it's doesn't encourage best practices. As a "front end guy" I do not want to be told that I can ONLY use XHTML if I want my documents to validate. To me, that would be like me telling a developer you HAVE to use MySQL. It just doesn't seem like a choice that the developer gets to make for me. This is NOT a discussion about HTML vs XHTML as a proper doctype. I could care less that you want to use XHTML and I want HTML. I'm going to assume that we are all going to make educated decisions about what we are doing. So please, save the doctype debate for a different day. Simon Willison has created a great Django app called django-html. The heart of it allows me the ability to swap doctypes at will and create instances of widgets as I need them to be with additional class name options. And that is really useful. In Django, a great solution for front end developers would be to create widget templates. These templates could be overwritten by the designer or front end guy for any purpose. For instance, why not do this based on the widget classes:templates/widgets/checkbox.htmlComments [3]
Comments [0]