Showing posts with label web design. Show all posts
Showing posts with label web design. Show all posts

Thursday, May 14, 2009

REST, Restful

How I explained REST to my wife...

We need to be able to talk to all machines about all the stuff that's on all the other machines. So we need some way of having one machine tell another machine about a resource that might be on yet another machine.

Wife: Sounds like GET is a pretty important verb.

Ryan: It is. Especially when you're using a web browser because browsers pretty much just get stuff. They don't do a lot of other types of interaction with resources. This is a problem because it has led many people to assume that HTTP is just for getting. But HTTP is actually a general purpose protocol for applying verbs to nouns.



Ryan: Because web pages are designed to be understood by people. A machine doesn't care about layout and styling. Machines basically just need the data. Ideally, every URL would have a human readable and a machine readable representation. When a machine GETs the resource, it will ask for the machine readable one. When a browser GETs a resource for a human, it will ask for the human readable one.


Tim Berners-Lee on the next Web

Friday, February 08, 2008

Open Visuals

Open Font Library
http://openfontlibrary.org

Open Clip Art Library
http://openclipart.org/

Icon Library from Tango Desktop Project
http://tango.freedesktop.org/Tango_Desktop_Project

Tango is used in Jaws is a Framework and Content Management System for building dynamic web sites: http://www.jaws-project.com

Source: http://osuosl.org/hosting/clients

A very good list of Open Source sofware

Thursday, November 22, 2007

Webdesign - forms

Niceforms

http://www.badboy.ro/articles/2007-01-30/niceforms/

http://blog.makemepulse.com/2007/07/04/niceforms-optimisation-and-new-features/

Tuesday, November 13, 2007

Google Web Toolkit a Year Later: Was it the correct level of abstraction?

A little over a year ago, Ajaxian published an editorial entitled Google Web Toolkit: The correct level of abstraction? In it, Dion raised some important questions about GWT:

  • Isn't debugging generated Javascript going to be messy?
  • Wouldn't the large size of the generated Javascript make it's use infeasible?
  • Where is all of the cool stuff, like effects libraries, etc.?
  • Is generating "assembler" in Javascript really the right level of abstraction?

Now that a year has passed and people have had a chance to experiment and develop with GWT, I thought it would be a good idea to revisit these questions. I interviewed GWT practitioners Dr. Adam Tacy and Robert Hanson, who -- aside from working on commercial projects featuring GWT -- have just finish their first book on the subject, GWT in Action: Easy Ajax with the Google Web Toolkit. They were kind enough to answer a few of my questions.

Sunday, September 16, 2007