{"id":578,"date":"2006-02-16T19:08:13","date_gmt":"2006-02-16T19:08:13","guid":{"rendered":"\/ifbookblog\/?p=578"},"modified":"2006-02-16T19:08:13","modified_gmt":"2006-02-16T19:08:13","slug":"yahoo_ui_design_library","status":"publish","type":"post","link":"https:\/\/futureofthebook.org\/blog\/2006\/02\/16\/yahoo_ui_design_library\/","title":{"rendered":"yahoo! ui design library"},"content":{"rendered":"<p><img decoding=\"async\" src=\"http:\/\/yhoo.client.shareholder.com\/press\/images\/yahoobang.gif\" alt=\"yahoo! logo\" title=\"Yahoo!\" style=\"margin-right: 15px; float: left;\">There are several reasons that Yahoo! released some of their <a href=http:\/\/developer.yahoo.net\/yui\/ target=\"_blank\">core UI code<\/a> for free. A callous read of this would suggest that they did it to steal back some goodwill from Google (still riding the successful Goolge API release from 2002). A more charitable soul could suggest that Yahoo! is interested in making the web a better place, not just in their market-share. Two things suggest this&mdash;the code is available under an open <a href=http:\/\/developer.yahoo.net\/yui\/license.txt target=\"_blank\">BSD license<\/a>, and their release of <a href=\" http:\/\/developer.yahoo.net\/ypatterns\/index.php\" target=\"_blank\">design patterns<\/a>. The code is for playing with; the design patterns for learning from.<br \/>\nThe code is squarely aimed at folks like me who would struggle mightily to put together a default library to handle complex interactions in Javascript using AJAX (all the rage now) while dealing with the intricacies of modern and legacy browsers. Sure, I could pull together the code from different sources, test it, tweak it, break it, tweak it some more, etc. Unsurprisingly, I&#8217;ve never gotten around to it. The Yahoo! code release will literally save me at least a hundred hours. Now I can get right down to designing the interaction, rather than dealing with technology.<br \/>\nThe design patterns library is a collection of best practice instructions for dealing with common web UI problems, providing both a solution and a rationale, with a detailed explanation of the interaction\/interface feedback. This is something that is more familiar to me, but still stands as a valuable resource. It is a well-documented alternate viewpoint and reminder from a site that serves more users in one day than I&#8217;m likely to serve in a year.<br \/>\nOf course Yahoo! is hoping to reclaim some mind-space from Google with developer community goodwill. But since the code is general release, and not brandable in any particular way (it&#8217;s all under-the-hood kind of stuff), it&#8217;s a little difficult to see the release as a directly marketable item. It really just seems like a gift to the network, and hopefully one that will bear lovely fruit. It&#8217;s always heartening to see large corporations opening their products to the public as a way to grease the wheels of innovation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There are several reasons that Yahoo! released some of their core UI code for free. A callous read of this would suggest that they did it to steal back some goodwill from Google (still riding the successful Goolge API release from 2002). A more charitable soul could suggest that Yahoo! is interested in making the [&hellip;]<\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[225,467,469,743,879,887,932,1060,1068,1591,1942,2051,2052],"tags":[3099],"class_list":["post-578","post","type-post","status-publish","format-standard","hentry","category-bsd","category-design","category-design_pattern","category-gift_economy","category-innovation","category-interaction","category-javascript","category-libraries-search-and-the-web","category-license","category-remix","category-user_interface","category-y","category-yahoo","tag-yahoo-y-design-user_interface-javascript-design_pattern-innovation-gift_economy-bsd-license-interaction"],"_links":{"self":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/578","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/comments?post=578"}],"version-history":[{"count":0,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/578\/revisions"}],"wp:attachment":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/media?parent=578"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/categories?post=578"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/tags?post=578"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}