Search Results

Search found 3 results on 1 pages for 'sexyprout'.

Page 1/1 | 1 

• Weird font hinting in Firefox 4

  - by sexyprout

  Hi everyone. I know this a recurrent topic but I just can't find a decent solution--although I found one for Chrome. Just take look at the following screenshots: Chrome 9 Firefox 4 See the slight difference? I can't identify the exact difference but I can tell fonts in Chrome look smoother. Here are my system preferences (prefer to show a screenshot as I don't know the exact translations in English): Anyone got a solution? Thanks. Update: from my point of view, it doesn't seem to actually be a hinting problem. I'd say Firefox uses subpixel rendering instead of grayscale rendering. (yet I can't find the setting in fontconfig) But this is a subjective opinion, can you confirm?

  Read the article

• -webkit-transition-property for translation

  - by sexyprout

  Hai. What is the transition property for translations in CSS3? I'm currently using all but I got a bug in iOS so I want to test another property. -webkit-transform: translate(-320px, 0);   -webkit-transition: ??? .5 ease-in-out; See the bug with an iOS device here (swipe horizontally), there's a kind of flash. Update: to anyone interested, I found a way to fix it thanks to Duopixel: E { -webkit-transition: all .5s ease-in-out; -webkit-transform: translate3d(0, 0, 0); // perform an "invisible" translation } // Then you can translate with translate3d(), no bug! document.querySelector('E').webkitTransform = 'translate3d(-320px, 0, 0)'

  Read the article

• Who needs singletons?

  - by sexyprout

  Imagine you access your MySQL database via PDO. You got some functions, and in these functions, you need to access the database. The first thing I thought of is global, like: $db = new PDO('mysql:host=127.0.0.1;dbname=toto', 'root', 'pwd'); function some_function() { global $db; $db->query('...'); } But it's considered as a bad practice. So, after a little search, I ended up with the Singleton pattern, which "applies to situations in which there needs to be a single instance of a class." According to the example of the manual, we should do this: class Database { private static $instance, $db; private function __construct(){} static function singleton() { if(!isset(self::$instance)) self::$instance = new __CLASS__; return self:$instance; } function get() { if(!isset(self::$db)) self::$db = new PDO('mysql:host=127.0.0.1;dbname=toto', 'user', 'pwd') return self::$db; } } function some_function() { $db = Database::singleton(); $db->get()->query('...'); } some_function(); But I just can't understand why you need that big class when you can do it merely with: class Database { private static $db; private function __construct(){} static function get() { if(!isset(self::$rand)) self::$db = new PDO('mysql:host=127.0.0.1;dbname=toto', 'user', 'pwd'); return self::$db; } } function some_function() { Database::get()->query('...'); } some_function(); This last one works perfectly and I don't need to worry about $db anymore. But maybe I'm forgetting something. So, who's wrong, who's right?

  Read the article

1