It would be an understatement to say that the iPhone changed the way we looked at and used phones – after all, full touchscreen smartphones never really caught on with the masses until Apple introduced their game changer 5 years ago. Well, some are still resistant to the idea, and decided to stick to a QWERTY keyboard on their handsets instead, although such phone models are slowly but surely getting fewer in number. Tactus Display might want to change things by introducing a touchscreen display that actually morphs from a numeric dialpad into a QWERTY keyboard, ensuring that fans of either side of the divide are able to get their input format of choice – you can either go touch, or physical. It would be interesting to see just when Tactus Display will introduce this technology into modern day smartphones, giving the choice back to consumers instead of dictating trends for them. According to Tactus Display, their technology will see action in real world products from next year onwards, so we intend to keep a keen eye peeled out for this when it happens.
Tactus Display brings physical buttons to touchscreen devices
Zocial Button Set: 72 CSS3 Buttons
The idea behind this project was to produce a consistent set of buttons that could be used for the range of social actions frequently taken in Web applications. These actions are often important goals for users, such as connecting third-party accounts or sharing content to third-party platforms, so their appearance has to be attractive and clear.
The standard buttons provided by third parties (such as Facebook, Twitter and SoundCloud) vary in size, style and interactivity. A consistent button set could reduce a lot of that visual noise and inconsistency. Furthermore, having it in CSS format means that changing the text for certain actions would be a breeze for developers, and it also allows administrators of non-English websites to translate labels into their native languages.
The button set was designed from the beginning to require no extra markup, and the elements used are entirely the choice of the (semantically considerate) designer. All buttons are fully scalable and customizable, and they degrade gracefully on older browsers, although the aesthetics in IE 6 and 7 are admittedly inferior to image-based alternatives.
No raster images or sprites were used. Instead, vector icons were inserted using a custom font file, an @font-face rule and pseudo elements. For more information, John Hicks has an informative write-up on this technique.
This button set is free to use and extend, personally or commercially. No attribution is required.
100%-vector CSS3 buttons@font-face icons and custom font files72 services supportedButton and icon versions supportedEm sizing for full scalabilityGeneric primary and secondary action buttons for consistencyGraceful degradation on older browsersScreenshots of each set are below. Or view a live demo.
The button set was designed with simplicity and semantics in mind. No unnecessary or extra markup is required, and button types are called through class names. Call the zocial.css file on your page (make sure the font files and the zocial.css file are in the same directory). Buttons can be displayed with the following markup:
The parent element is agnostic, so you may use ,
Zocial Button Set: 72 CSS3 Buttons
The idea behind this project was to produce a consistent set of buttons that could be used for the range of social actions frequently taken in Web applications. These actions are often important goals for users, such as connecting third-party accounts or sharing content to third-party platforms, so their appearance has to be attractive and clear.
The standard buttons provided by third parties (such as Facebook, Twitter and SoundCloud) vary in size, style and interactivity. A consistent button set could reduce a lot of that visual noise and inconsistency. Furthermore, having it in CSS format means that changing the text for certain actions would be a breeze for developers, and it also allows administrators of non-English websites to translate labels into their native languages.
The button set was designed from the beginning to require no extra markup, and the elements used are entirely the choice of the (semantically considerate) designer. All buttons are fully scalable and customizable, and they degrade gracefully on older browsers, although the aesthetics in IE 6 and 7 are admittedly inferior to image-based alternatives.
No raster images or sprites were used. Instead, vector icons were inserted using a custom font file, an @font-face rule and pseudo elements. For more information, John Hicks has an informative write-up on this technique.
This button set is free to use and extend, personally or commercially. No attribution is required.
100%-vector CSS3 buttons@font-face icons and custom font files72 services supportedButton and icon versions supportedEm sizing for full scalabilityGeneric primary and secondary action buttons for consistencyGraceful degradation on older browsersScreenshots of each set are below. Or view a live demo.
The button set was designed with simplicity and semantics in mind. No unnecessary or extra markup is required, and button types are called through class names. Call the zocial.css file on your page (make sure the font files and the zocial.css file are in the same directory). Buttons can be displayed with the following markup:
The parent element is agnostic, so you may use ,
Sponsors
