Already a member? Log in

Sign up with your...

or

Sign Up with your email address

Add Tags

Duplicate Tags

Rename Tags

Share It With Others!

Save Link

Sign in

Sign Up with your email address

Sign up

By clicking the button, you agree to the Terms & Conditions.

Forgot Password?

Please enter your username below and press the send button.
A password reset link will be sent to you.

If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.

ADVERTISEMENT
ADVERTISEMENT

Links 1 through 10 of 997 Tom Greuter's Bookmarks

These cards summarize the Mobile Web Application Best Practices (MWABP) document. These guidelines aid the development of rich and dynamic mobile Web applications

Share It With Others!

In this guide, we will cover everything you, as a web designer, need to know about the PNG image format.

Share It With Others!

Visie Microsoft op accessibility. Voldoet aan richtlijnen ***

Share It With Others!

svg drawing demo application (paint)

Share It With Others!

RGraph: HTML5 canvas graph library based on the HTML5 canvas tag
Interactive javascript/HTML5 canvas graphs using the HTML5 canvas tag for all platforms

Share It With Others!

Easily create bundles of beautifully matching, free web fonts, with failsafe font stacks to back them up. Including ready-to-go CSS code!

Share It With Others!

Share It With Others!

This document is for web developers who want their pages to work with Google Chrome Frame (aka, GCF). In most cases, making your pages work with GCF is trivial: you just add a single tag to the page. This simple process is described in the next section. The rest of the document is devoted to advanced issues and options.

In short, if your page works in the Google Chrome browser, it'll work in GCF.

Share It With Others!

Share It With Others!

This is a widely known problem that has been talked about to death, yet very popular websites continue to fail at protecting their users. The only effective fix for this problem is full end-to-end encryption, known on the web as HTTPS or SSL. Facebook is constantly rolling out new "privacy" features in an endless attempt to quell the screams of unhappy users, but what's the point when someone can just take over an account entirely? Twitter forced all third party developers to use OAuth then immediately released (and promoted) a new version of their insecure website. When it comes to user privacy, SSL is the elephant in the room.

Share It With Others!

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT