Comments for The Bright Lines

Comment on Cool cross-browser styling with CSS and IE’s filter by Ali

Ali — Fri, 12 Feb 2010 15:00:45 +0000

IMPORTANT::
To solve the problem of fuzzy text in IE when using a filter, wrap the content of filtered element and set it’s position style to relative.
EXAMPLE:

CONTENT

Comment on PixEm: Pixel to Em Converter by Coder Man

Coder Man — Fri, 05 Feb 2010 20:18:59 +0000

Hi admin, nice tool!
Why you don’t make a open source?

Thanks

Comment on PixEm: Pixel to Em Converter by Jai

Jai — Sat, 30 Jan 2010 17:14:15 +0000

You might find this useful as well. http://pixel2em.kleptomac.com
This provides an online pixels to em converter and you can also do a complete CSS file conversion.

Comment on Webfont pitfalls by Wouter Bos

Wouter Bos — Thu, 21 Jan 2010 22:31:06 +0000

Thanks for clearing that up!

Comment on Webfont pitfalls by Ono

Ono — Thu, 21 Jan 2010 18:50:55 +0000

Hey Wouter. You’re not entirely correct about hinting. Hints don’t really color pixels or create smooth lines. They are an extra set of instructions for each character to align it’s outline with a raster (i.e. pixels). Hints actually adjust it’s shape by shifting certain points in order to improve contrast and legibility.

It works with both aliasing and anti-aliasing. Or more accurate: it’s intended to counter undesired (anti-)aliasing effects. And it can really affect the appearance of a font on small font sizes.

Also, be carefull with auto-hinting. In some cases the result can be worse than no hinting at all.

Good article though

Comment on CSS debugging by Sareesh

Sareesh — Thu, 21 Jan 2010 04:16:17 +0000

Thank you for your detailed report

Comment on Implementing font-face cross domain by Webfont pitfalls | The Bright Lines

Webfont pitfalls | The Bright Lines — Tue, 19 Jan 2010 22:30:42 +0000

[...] Implementing font-face cross domain [...]

Comment on Cool cross-browser styling with CSS and IE’s filter by Chrissteven81

Chrissteven81 — Thu, 14 Jan 2010 17:08:41 +0000

senshikaze- You are bending over backwards for other browsers IE has very nice ways of doing it far more clean. more like we are bending over backwards for other browsers lol.

Comment on Why do it yourself? Somebody else already did it for you! by Wouter Bos

Wouter Bos — Wed, 16 Dec 2009 20:05:48 +0000

Hi Sinbad. Thank you for your comment.

Most cons in your list do not have to be that bad:

- Performance: most cms’s are heavy because they have lots of features or are scalable. Buying extra RAM is a cheap price compared to the labor of hand-weriting your own code
- Design: some CMS’s indeed can be very limiting. But not all are. And sometimes you just have to learn a CMS to know what’s possible.
- Poorly written modules and plugins: You always have to watch out for something like that. It’s not always easy, but at Wordpress they seem to do just fine.
- Scalability: I work with Sitecore, which is very scalable and flexible. But indeed, some CMS’s aren’t that scalable, so you have to build something that’s suitable for the CMS.

I agree that external CMS’s have their limits, but I’m still convinced that hand-crafted code is expensive. Use what’s out there instead.

Comment on Why do it yourself? Somebody else already did it for you! by Sinbad

Sinbad — Wed, 16 Dec 2009 14:38:16 +0000

Here are a couple of reasons why I dropped CMS and went back to custom code:

Performance – in most cases (Drupal, Joomla, SilverStripe, etc) cms are slow, resource hogs. Go to the Drupal forums and there are many threads on poor performance, and the answer given is nearly always get more memory, put on APC cache, etc, no one addresses why a page needs 1000+ DB queries to run or why drupal requires 10 times the memory of a custom built cms.

Design – Most (there are notable exceptions, MOdX for instnce) cms are a nightmare for designers to design for, which increases development time.

Poorly written modules / plugins – So great you get this pre-written functionality with modules / plugins, problem is half of them are so poorly written (in the case of open source) that they slow or unsecure, so you then have to check then for yourself.

Difficult to customize / maintain – even the most extensible / flexible of these CMS are a nightmare if you wish to do anything too far outside of their range so you end up with a patchwork of messy code that is difficult to maintain and as for the pain of major upgrades, forget it.