wesruv likes stuff - regurgitations & reblogs

*openly weeps.

Might as well ask me to end world hunger. The code was terminally ill.

Not only all of this fun stuff (read more to see all of it), text-shadow is great (I’m sure designers are more excited than devs), and rounded corners. Although rounded corners have browser specific implementations at the moment (the styles are prefixed with -moz- or -webkit-) they’re fun to mess around with. Take a look at my Tumblr template on for my blog to see how I have tried it out

Fun trick I’ve been doing lately, since CSS3 is seeing implementation in all non-ie browsers, you can use it to create IE specific (general styles) then create a style for every other browser by using a pseudo selector.

For Example:

#prevLink:hover {
	background: url(images/lightbox_previous-ie6.png) left 20% no-repeat;
}

#prevLink[href]:hover {
	background: url(images/lightbox_previous.png) left 20% no-repeat;
}

mattonrails:

A lot of exciting changes have come in CSS3, but like me, there is most likely plenty of detail you haven’t heard about. I want to show you some of the advanced selectors you can write with CSS3. Of course, browser support for these selectors can vary. But they will work in your modern, standards-compliant browser that you’re using, right? ;)

Read More

Please, all forces that be, let this put a bullet in the bastard…

Here’s an e-mail I got from google:

Dear Google Apps admin,​

In order to continue to improve our products and deliver more sophisticated features and performance, we are harnessing some of the latest improvements in web browser technology. This includes faster JavaScript processing and new standards like HTML5. As a result, over the course of 2010, we will be phasing out support for Microsoft Internet Explorer 6.0 as well as other older browsers that are not supported by their own manufacturers.

We plan to begin phasing out support of these older browsers on the Google Docs suite and the Google Sites editor on March 1, 2010. After that point, certain functionality within these applications may have higher latency and may not work correctly in these older browsers. Later in 2010, we will start to phase out support for these browsers for Google Mail and Google Calendar.

Google Apps will continue to support Internet Explorer 7.0 and above, Firefox 3.0 and above, Google Chrome 4.0 and above, and Safari 3.0 and above.

Starting this week, users on these older browsers will see a message in Google Docs and the Google Sites editor explaining this change and asking them to upgrade their browser. We will also alert you again closer to March 1 to remind you of this change.

In 2009, the Google Apps team delivered more than 100 improvements to enhance your product experience. We are aiming to beat that in 2010 and continue to deliver the best and most innovative collaboration products for businesses.

Thank you for your continued support!

Sincerely,

The Google Apps team

Email preferences: You have received this mandatory email service announcement to update you about important changes to your Google Apps product or account.

Google Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043

musicismyeverest:

In coming up with a presentation for work on characteristics of quality, I’ve done a lot of expanding my brain.  Lots of defining, clarifying, quantifying, and a fair amount of reading.  This morning I took another looks at Apple’s ADC guide for Human Interface Guidelines—particularly the part on Characteristics of Great Software.  I’m pretty sure they’d updated it since the last time I’d been there, as I noticed a link on that page to another page called “Know Your Audience”.  I followed. First nugget: “It is useful to create scenarios that describe a typical day of a person who uses the type of software product you are designing.” Second nugget: “Develop your product with people and their capabilities—not computers and their capabilities—in mind.” Third nugget: “It is not your needs or your usage patterns that you are designing for, but those of your (potential) customers.” Read it. Enough said.

nejimakidori89:

1. Simple and natural dialogue 
- simple means no irrelevant or rarely used information 
- natural means an order that matches the task

2. Speak the user’s language
- use concepts from the user’s world 
- don’t use system-specific engineering terms

3. Minimize user memory load
- don’t make the user remember things from one action to the next 
- leave information on the screen until it is no longer needed

4. Be consistent
- action sequences learned in one part of the system should apply in other parts

5. Provide feedback
- let users know what effect their actions have on the system

6. Provide clearly marked exits
- if users get into part of the system that doesn’t interest them, they should be able to get out quickly without damaging anything.

7. Provide shortcuts
- help experienced users avoid lengthy dialogues and informational messages they don’t need

8. Good error messages
- let the user know what the problem is and how to correct it

9. Prevent errors
- whenever you discover an error message, ask if that error could have been prevented.