<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    >

<channel>
    <title>Webmonkey &#187; Programming</title>
    <atom:link href="http://www.webmonkey.com/tag/programming/feed/" rel="self" type="application/rss+xml" />
    <link>http://www.webmonkey.com</link>
    <description>The Web Developer&#039;s Resource</description>
    <lastBuildDate>Fri, 05 Apr 2013 20:20:46 +0000</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>http://wordpress.org/?v=3.4.2</generator>
    
    <item>
        <title>Write Better CSS With &#8216;Idiomatic CSS&#8217;</title>
        <link>http://www.webmonkey.com/2012/06/write-better-css-with-idiomatic-css/</link>
        <comments>http://www.webmonkey.com/2012/06/write-better-css-with-idiomatic-css/#comments</comments>
        <pubDate>Mon, 11 Jun 2012 15:49:20 +0000</pubDate>

                <dc:creator>Scott Gilbertson</dc:creator>

        <guid isPermaLink="false">http://www.webmonkey.com/?p=57298</guid>
        		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Programming]]></category>
            <enclosure url="http://www.webmonkey.com/wp-content/uploads/2012/06/CSS_sheep-157x100.jpg" type="image/jpeg" length="48000" />
                    <description><![CDATA[<div class="rss_thumbnail"><img src="http://www.webmonkey.com/wp-content/uploads/2012/06/CSS_sheep.jpg" alt="Write Better CSS With &#8216;Idiomatic CSS&#8217;" /></div>Large projects with many programmers contributing can result in tangled code, but style guides like Idiomatic CSS offer a way out of the confusion.]]></description>

            <content:encoded><![CDATA[<p><!-- wpautop enabled -->
<p><div id="attachment_57299" class="wp-caption alignleft" style="width: 167px"><a href="http://www.webmonkey.com/wp-content/uploads/2012/06/CSS_sheep.jpg"><img src="http://www.webmonkey.com/wp-content/uploads/2012/06/CSS_sheep.jpg" alt="" title="CSS_sheep" width="157" height="192" class="size-full wp-image-57299" /></a><p class="wp-caption-text">Wooly, the CSS Sheep <em>Image: <a href='http://www.w3.org/Style/Woolly/woolly-icon.svg'>W3C</a></em></p></div>If you&#8217;ve ever worked on a large programming project you know all about the joy of trying to read other people&#8217;s code. And of course that&#8217;s how everyone else feels about reading your code. That&#8217;s why formal programming style guides exist &#8212; to help bridge the gap between individual styles. </p>
<p>There is no right or wrong style of writing code, but there are styles that are easier to read and share with other people. Search the web and you&#8217;ll find  formal guides to writing readable JavaScript, Python, Ruby and countless other popular languages, but one language that doesn&#8217;t get as much attention is CSS. </p>
<p>Developer Nicolas Gallagher wants to change that. To do so Gallagher has put together <a href="https://github.com/necolas/idiomatic-css">Idiomatic CSS</a>, a style guide for how to format, organize and craft quality CSS that anyone can work with. Here are the general principles of the project:</p>
<blockquote>
<blockquote>
<p>&#8220;Part of being a good steward to a successful project is realizing that writing code for yourself is a Bad Idea™. If thousands of people are using your code, then write your code for maximum clarity, not your personal preference of how to get clever within the spec.&#8221; &mdash; Idan Gazit</p>
</blockquote>
<ul>
<li>All code in any code-base should look like a single person typed it, no matter how many people contributed.</li>
<li>Strictly enforce the agreed upon style.</li>
<li>If in doubt use existing, common patterns.</li>
</ul>
</blockquote>
<p>Idiomatic CSS follows in the footsteps of Rick Waldron&#8217;s <a href="https://github.com/rwldrn/idiomatic.js">Idiomatic JS</a>, which does the same thing for JavaScript. </p>
<p>If you&#8217;ve made the leap to a CSS preprocessor like <a href="http://sass-lang.com/">SASS</a> or <a href="http://lesscss.org/">LESS</a>, fear not, Idiomatic CSS has you covered as well. Preprocessor syntax varies and Idiomatic CSS offers examples in SCSS, but the more general rule, &#8220;your conventions should be extended to accommodate the particularities of any preprocessor in use,&#8221; apply to others as well.</p>
<p>Wrangling CSS on large projects can be a pain, but if you take the time to create a set of conventions and ensure that everyone sticks to them it becomes a much more manageable task. If you&#8217;ve got experience and insight to share, head on over to the <a href="https://github.com/necolas/idiomatic-css">Idiomatic CSS GitHub page</a> and contribute your knowledge.</p>
<div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2012/06/write-better-css-with-idiomatic-css/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    
    <item>
        <title>Google Kicks Off Summer of Code 2012</title>
        <link>http://www.webmonkey.com/2012/05/google-kicks-off-summer-of-code-2012/</link>
        <comments>http://www.webmonkey.com/2012/05/google-kicks-off-summer-of-code-2012/#comments</comments>
        <pubDate>Tue, 22 May 2012 14:54:38 +0000</pubDate>

                <dc:creator>Scott Gilbertson</dc:creator>

        <guid isPermaLink="false">http://www.webmonkey.com/?p=56746</guid>
        		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Google]]></category>
            <enclosure url="http://www.webmonkey.com/wp-content/uploads/2012/05/summerofcode-200x100.jpg" type="image/jpeg" length="48000" />
                    <description><![CDATA[<div class="rss_thumbnail"><img src="http://www.webmonkey.com/wp-content/uploads/2012/05/summerofcode.jpg" alt="Google Kicks Off Summer of Code 2012" /></div>Google's annual Summer of Code project, an effort to get college students writing open source software during their summer vacations, is underway.]]></description>

            <content:encoded><![CDATA[<p><!-- wpautop enabled -->
<p><div id="attachment_56748" class="wp-caption alignleft" style="width: 330px"><a href="http://www.webmonkey.com/wp-content/uploads/2012/05/summerofcode.jpg"><img src="http://www.webmonkey.com/wp-content/uploads/2012/05/summerofcode.jpg" alt="" title="summerofcode" width="320" height="214" class="size-full wp-image-56748" /></a><p class="wp-caption-text">Students: Step into your summer office. <em>Image: <a href='http://www.flickr.com/photos/-arpi/4323800353/'>Lost In The RP</a>/Flickr</em></p></div>Students, start your coding engines. Google&#8217;s annual <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012">Summer of Code</a> program, which helps college students write open source software during their summer vacations, starts today. </p>
<p>Past participants have helped improve everything from popular web frameworks to browser add-ons and even operating systems. Summer of Code is also not a half bad way to get yourself on Google&#8217;s radar &#8212; the company looks at the results of the program to help it &#8220;identify potential recruits.&#8221;</p>
<p>Summer of Code has served as a launchpad for quite a few new open source software projects as well as helping to jumpstart work on existing favorites. This year&#8217;s roster includes some 1,208 students who will spend the next 12 weeks writing code for 180 different open source organizations.</p>
<p>With 208 proposed projects, there&#8217;s a pretty good chance that some Summer of Code improvements will be rolled into your favorite open source projects later this year. Among the things we&#8217;ll be keeping an eye on are <a href="http://www.metalinker.org/">Metalink&#8217;s</a> various efforts to <a href="http://www.google-melange.com/gsoc/org/google/gsoc2012/metalink">improve the download capabilities in Firefox and Chrome</a>. Eventually Metalink wants to bring error recovery/repair for large downloads to everything from Chrome to wget.</p>
<p>Other promising projects include several efforts to help <a href="http://www.google-melange.com/gsoc/org/google/gsoc2012/osm">improve OpenStreetMap</a>, the so-called &#8220;Wikipedia of maps,&#8221; as well as <a href="http://www.google-melange.com/gsoc/org/google/gsoc2012/codeforamerica">Code for America&#8217;s various projects</a>, some <a href="http://www.google-melange.com/gsoc/org/google/gsoc2012/git">new features for Git</a> and an ambitious plan to <a href="http://www.google-melange.com/gsoc/project/google/gsoc2012/lothiraldan/18002">bring Pylint into the modern world of Python 3</a>.</p>
<p>For more info on this year&#8217;s Summer of Code, head over to Google&#8217;s <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012">Summer of Code website</a>, which has details on all the various projects and participants. You can also get updates from the <a href="https://plus.google.com/b/102168248469649733567/">Summer of Code page at Google+</a>.</p>
<div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2012/05/google-kicks-off-summer-of-code-2012/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    
    <item>
        <title>Development Tips to Improve Your Code Quality</title>
        <link>http://www.webmonkey.com/2010/10/development-tips-to-improve-your-code-quality/</link>
        <comments>http://www.webmonkey.com/2010/10/development-tips-to-improve-your-code-quality/#comments</comments>
        <pubDate>Wed, 20 Oct 2010 20:42:30 +0000</pubDate>

                <dc:creator>Scott Gilbertson</dc:creator>

        <guid isPermaLink="false">http://www.webmonkey.com/?p=49001</guid>
        		<category><![CDATA[Programming]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[tips]]></category>
            <enclosure url="http://www.webmonkey.com/wp-content/uploads/2010/10/qualityyoucantaste.jpg" type="image/jpeg" length="48000" />
                    <description><![CDATA[<div class="rss_thumbnail"><img src="http://www.webmonkey.com/wp-content/uploads/2010/10/qualityyoucantaste.jpg" alt="Development Tips to Improve Your Code Quality" /></div>Any good programmer can tell you writing code is an art form, and as with most art forms, the key to success is good habits and lots of practice. The Ruby Learning blog recently posted an interesting list of ways to improve your code quality and, perhaps more importantly, develop habits that will lead to [...]]]></description>

            <content:encoded><![CDATA[<p><!-- wpautop enabled -->
<p><img src="http://www.webmonkey.com/wp-content/uploads/2010/10/qualityyoucantaste.jpg" alt="quality you can taste" title="quality you can taste" /></p>
<p>Any good programmer can tell you writing code is an art form, and as with most art forms, the key to success is good habits and lots of practice.</p>
<p>The Ruby Learning blog recently posted an interesting list of ways to <a href="http://rubylearning.com/blog/2010/10/18/do-you-enjoy-your-code-quality/">improve your code quality</a> and, perhaps more importantly, develop habits that will lead to better code creation. Developer James Schorr&#8217;s tips range from the obvious, like using a good version control system, to the more subtle: &#8220;realize that just because we &#8220;can&#8221; doesn&#8217;t mean that we &#8220;should&#8221;&#8230; anything&#8217;s possible, but not everything&#8217;s advisable.&#8221;</p>
<p>The article is broken into the three major parts of any programming workflow: pre-development, development and post-development. There are a number of great suggestions in each, but our favorite parts are the fourth category: Enjoying Your Development. Almost any project is fun and enjoyable in the beginning, but then there seems to come that point at which the fun evaporates and we get bogged down in the grunt work of writing code. Schorr has few tips to help break you out of those boring stretches:</p>
<blockquote><p>Give yourself time to think and rest. There are some days where I just can&#8217;t write code well; other days where it&#8217;s just flowing. This is due to how your brain functions. You need sleep and a change of pace and scenery now and then.</p>
<p>Walk away for a while. It&#8217;s easy to get &#8220;tunnel vision&#8221; and think that you&#8217;re close to solving a problem and to think that more effort will solve it&#8230; You would be surprised at the ideas or solutions that will spring into your mind as you are thinking about or doing other things.</p>
</blockquote>
<p>Head over to the <a href="http://rubylearning.com/blog/2010/10/18/do-you-enjoy-your-code-quality/">Ruby Learning blog</a> to read some of the other helpful tips and tricks for producing quality code.</p>
<p><em>Photo: Christian Hellman/<a href="http://www.flickr.com/photos/codepo8/4998539771/">Flickr</a>/CC</em></p>
<p><strong>See Also:</strong><br/></p>
<ul>
<li><a href="http://www.webmonkey.com/2008/07/commenting_your_code_-_what_s_too_much__too_little_/">Commenting Your Code — What&#8217;s Too Much, Too Little?</a></li>
<li><a href="http://www.webmonkey.com/2007/11/become_a_better_programmer_with_refactormycode/">Become A Better Programmer With RefactorMyCode</a></li>
<li><a href="http://www.webmonkey.com/2010/09/how-to-speed-up-your-site-with-yslow-and-page-speed/">How to Speed Up Your Site With YSlow and Page Speed</a></li>
</ul>
<div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/10/development-tips-to-improve-your-code-quality/feed/</wfw:commentRss>
        <slash:comments>3</slash:comments>

        
    </item>
    
    <item>
        <title>XSS Vulnerabilities, Raw SQL Top List of Common Programming Errors</title>
        <link>http://www.webmonkey.com/2010/03/xss-vulnerabilities-raw-sql-top-list-of-common-programming-errors/</link>
        <comments>http://www.webmonkey.com/2010/03/xss-vulnerabilities-raw-sql-top-list-of-common-programming-errors/#comments</comments>
        <pubDate>Wed, 24 Mar 2010 18:24:21 +0000</pubDate>

                <dc:creator>Scott Gilbertson</dc:creator>

        <guid isPermaLink="false">http://www.webmonkey.com/?p=46976</guid>
        		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Databases]]></category>
		<category><![CDATA[Web Apps]]></category>
		<category><![CDATA[xss]]></category>
            <enclosure url="http://www.webmonkey.com/wp-content/uploads/2010/03/bobbytables.jpg" type="image/jpeg" length="48000" />
                    <description><![CDATA[<div class="rss_thumbnail"><img src="http://www.webmonkey.com/wp-content/uploads/2010/03/bobbytables.jpg" alt="XSS Vulnerabilities, Raw SQL Top List of Common Programming Errors" /></div>No programmer is perfect, but some mistakes are more dangerous than others. While some mistakes might just slow down your site, others can open up vulnerabilities that expose your code, your database and even your users to all manner of attack. To help you identify the more serious errors common in programs of all types, [...]]]></description>

            <content:encoded><![CDATA[<p><!-- wpautop enabled -->
<p><a href="http://xkcd.com/327/"><img src="http://www.webmonkey.com/wp-content/uploads/2010/03/bobbytables-300x176.jpg" alt="bobbytables" title="bobbytables" width="300" height="176" class="alignleft size-medium wp-image-46975" /></a>No programmer is perfect, but some mistakes are more dangerous than others. While some mistakes might just slow down your site, others can open up vulnerabilities that expose your code, your database and even your users to all manner of attack.</p>
<p>To help you identify the more serious errors common in programs of all types, a group of top software security experts in the US and Europe have released their <a href="http://cwe.mitre.org/top25/">Top 25 Most Dangerous Programming Errors</a>.</p>
<p>Unsurprisingly, cross-site scripting vulnerabilities and improperly handled SQL top the list of common and dangerous mistakes. Remember kids, sanitize your database inputs; you just never know when someone is going to name their child: &#8220;Robert&#8217;) DROP TABLE Students;&#8221;</p>
<p>While not all the errors in the list are common in web programming, some of the more serious things are concerns for web developers &#8212; cross-site request forgeries, missing encryption of sensitive data and unrestricted file uploads are all common web programming issues.</p>
<p>Also interesting is the <a href="http://cwe.mitre.org/top25/profiles.html#ProfileLang">weaknesses by language</a> section, which breaks down common mistakes in PHP, Java, Perl and C/C++. No doubt web developers would like to have seen Python and Ruby in that list, but it should at least be useful for PHP and Perl programmers.</p>
<p><strong>See Also:</strong><br/></p>
<ul>
<li><a href="http://www.webmonkey.com/2009/04/oauth_security_exploit_tests_limits_of_open_web_standards/">OAuth Security Exploit Tests Limits of Open Web Standards</a></li>
<li><a href="http://www.webmonkey.com/2010/01/creating_a_better_privacy_policy/">Warning: This Site May Be Sharing Your Data</a></li>
<li><a href="http://www.webmonkey.com/2007/09/google_wants_global_privacy_rules/">Google Wants Global Privacy Rules</a></li>
</ul>
<div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/03/xss-vulnerabilities-raw-sql-top-list-of-common-programming-errors/feed/</wfw:commentRss>
        <slash:comments>3</slash:comments>

        
    </item>
    
    <item>
        <title>Hexadecimal</title>
        <link>http://www.webmonkey.com/2010/02/hexadecimal/</link>
        <comments>http://www.webmonkey.com/2010/02/hexadecimal/#comments</comments>
        <pubDate>Mon, 15 Feb 2010 20:45:47 +0000</pubDate>

                <dc:creator>Webmonkey Staff</dc:creator>

        <guid isPermaLink="false">http://stag.wired.com/primate/?p=250</guid>
        		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[color]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[wiki]]></category>
        <description><![CDATA[The hexadecimal (base 16) number system used for Web-page design consists of 16 unique symbols:0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, and F. For example, the decimal number 15 is equal to the hexadecimal number F. In HTML, an RGB color can be designated by RRGGBB with [...]]]></description>

            <content:encoded><![CDATA[<!-- wpautop disabled --><p>The hexadecimal (base 16) number system used for Web-page design consists of 16 unique symbols:0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, and F.

</p>

For example, the decimal number 15 is equal to the hexadecimal number F. In HTML, an <a href="/2010/02/RGB" title="Reference:RGB"> RGB</a> color can be designated by <pre class="brush: js">RRGGBB</pre> with the first two numerals representing the amount of red, the second two the amount of green, and the last two the amount of blue. If you wanted your background to be red, you could write the code for a body background color as <pre class="brush: js">&lt;body bgcolor="#FF0000"&gt;</pre> Black is the absence of all color and white is the presence of all color, so in hexadecimal, black is at the bottom of the system (no red, green, or blue:<pre class="brush: js">#000000</pre> and white is at the top (the maximum amount of red, green, and blue:<pre class="brush: js">#FFFFFF</pre><div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/02/hexadecimal/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    
    <item>
        <title>API</title>
        <link>http://www.webmonkey.com/2010/02/api/</link>
        <comments>http://www.webmonkey.com/2010/02/api/#comments</comments>
        <pubDate>Mon, 15 Feb 2010 20:45:47 +0000</pubDate>

                <dc:creator>Webmonkey Staff</dc:creator>

        <guid isPermaLink="false">http://stag.wired.com/primate/?p=35</guid>
        		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[wiki]]></category>
        <description><![CDATA[The application program interface (API) is a set of building blocks for programmers. APIs are made up of routines, protocols, and tools. Most operating environments provide an API so that programmers can write applications consistent with that environment. For example, developing software using the Windows API ensures that your user interface will be consistent with [...]]]></description>

            <content:encoded><![CDATA[<!-- wpautop disabled --><p>The application program interface (API) is a set of building blocks for programmers.

</p><p>APIs are made up of <a href="/2010/02/Routines" title="Reference:Routines">routines</a>, <a href="/2010/02/Protocols" class="new" title="Reference:Protocols">protocols</a>, and tools. Most operating environments provide an API so that programmers can write applications consistent with that environment. For example, developing software using the Windows API ensures that your user interface will be consistent with other Windows applications, making it easier for users to learn your new programs.

</p>

<a name="Use_on_the_Web"></a><h2> <span class="mw-headline">Use on the Web</span></h2>

<p>Web APIs provide simple ways to interact with websites. Using an API, you can extract public data from sites like del.icio.us, Flickr and Digg to create mashups, reuse data or just about anything else you can imagine.



</p><p>APIs are also useful for extracting your own private data from a web service so that you can back it up elsewhere or display it on another site.

</p><p>When talking about APIs you&#8217;ll here the following terms quite a bit.

</p>

<a name="Common_Web_API_Related_Terms"></a><h3> <span class="mw-headline">Common Web API Related Terms</span></h3>

<ul><li> <b>Web service/API</b> &#8212; These terms are largely interchangeable and simple refer to the ways you can interact with the data on your favorite websites.

</li></ul>

<ul><li> <b>Method</b> &#8212; A method is just one aspect of an API; you might also see methods refered to a functions. For instance, if you&#8217;re interacting with Flickr, you might want to get your public photos. To do so you would use the get_user_photos method.

</li></ul>

<ul><li> <b>Response</b> &#8212; The information returned by the API method that you&#8217;ve called.



</li></ul>

<ul><li> <b>REST</b> &#8212; Short for Representational State Transfer. REST treats data as a web document that lives at a specific URL. REST APIs use standard HTTP requests such as GET, PUT, HEAD, DELETE and POST to interact with data.

</li></ul>

<ul><li> <b>XML-RPC</b> &#8212; This older API scheme formats method calls and responses as XML documents which are sent over HTTP.

</li></ul>

<ul><li> <b>SOAP</b> &#8212; Simple Object Access Protocol. A W3C standard for passing messages across the network. SOAP is the successor to XML-RPC. It&#8217;s complexity has led many to disparage SOAP and with more APIs leaning toward REST, SOAP&#8217;s future is uncertain.

</li></ul>

<ul><li> <b>Ajax</b> &#8212; Asynchronous JavaScript and XML. Technically it has nothing to do with APIs, however many sites using APIs send their queries out using Ajax which is partially responsible for the popularity of JSON.



</li></ul>

<ul><li> <b>JSON</b> &#8212; JavaScript Object Notation. JSON&#8217;s main advantage is that it is easy to convert from JSON to nearly any other programming language. JSON uses key-value pairs and arrays, something common to PHP, Python, Perl, Ruby and most other languages. The portability of JSON has made it an increasingly popular choice for sites developing APIs.

</li></ul>

<p><br />

</p>

<a name="Popular_Web_APIs"></a><h2> <span class="mw-headline">Popular Web APIs</span></h2>

<ul><li> <a href="http://www.google.com/apis/maps/" class="external text" title="http://www.google.com/apis/maps/" rel="nofollow">Google Maps</a>

</li><li> <a href="http://developer.yahoo.com/maps/" class="external text" title="http://developer.yahoo.com/maps/" rel="nofollow">Yahoo Maps</a>



</li><li> <a href="http://www.flickr.com/services/api/" class="external text" title="http://www.flickr.com/services/api/" rel="nofollow">Flickr</a>

</li><li> <a href="http://code.google.com/apis/youtube/overview.html" class="external text" title="http://code.google.com/apis/youtube/overview.html" rel="nofollow">YouTube</a>

</li><li> <a href="http://del.icio.us/help/api/" class="external text" title="http://del.icio.us/help/api/" rel="nofollow">del.icio.us</a>

</li><li> <a href="http://wiki.ma.gnolia.com/Ma.gnolia_API" class="external text" title="http://wiki.ma.gnolia.com/Ma.gnolia_API" rel="nofollow">Ma.gnolia</a>

</li><li> <a href="http://twitter.com/help/api" class="external text" title="http://twitter.com/help/api" rel="nofollow">Twitter</a>

</li><li> <a href="http://www.yelp.com/developers/documentation/search_api" class="external text" title="http://www.yelp.com/developers/documentation/search_api" rel="nofollow">Yelp</a>



</li><li> <a href="http://openid.net/" class="external text" title="http://openid.net/" rel="nofollow">OpenID</a>

</li><li> <a href="http://www.amazonws.com/" class="external text" title="http://www.amazonws.com/" rel="nofollow">Amazon S3</a>

</li><li> <a href="http://atomenabled.org/" class="external text" title="http://atomenabled.org/" rel="nofollow">AtomAPI</a>

</li><li> <a href="http://meta.wikimedia.org/wiki/API" class="external text" title="http://meta.wikimedia.org/wiki/API" rel="nofollow">MediaWiki API</a>

</li><li> <a href="http://api.vzaar.com/" class="external text" title="http://api.vzaar.com/" rel="nofollow">vzaar API</a><div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/02/api/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    
    <item>
        <title>Operator</title>
        <link>http://www.webmonkey.com/2010/02/operator/</link>
        <comments>http://www.webmonkey.com/2010/02/operator/#comments</comments>
        <pubDate>Mon, 15 Feb 2010 20:45:47 +0000</pubDate>

                <dc:creator>Webmonkey Staff</dc:creator>

        <guid isPermaLink="false">http://stag.wired.com/primate/?p=258</guid>
        		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[wiki]]></category>
        <description><![CDATA[An expression tells JavaScript what to do with the data it gets, and within each expression are operators and operands. Operands are the data or data types the expression gets, and operators are the shorthand characters that tell the expression what to do with the operand. JavaScript has arithmetic (+,-,*,/), assignment (=), bitwise (&#38;, &#124;), [...]]]></description>

            <content:encoded><![CDATA[<!-- wpautop disabled --><p><br />

An <a href="/2010/02/Expression" title="Reference:Expression">expression</a> tells JavaScript what to do with the data it gets, and within each expression are operators and operands. Operands are the data or data types the expression gets, and operators are the shorthand characters that tell the expression what to do with the operand. JavaScript has arithmetic <tt>(+,-,*,/)</tt>, assignment <tt>(=)</tt>, bitwise <tt>(&amp;, |)</tt>, comparison <tt>(&gt;, &lt;,)</tt>, logical <tt>(&amp;, ||,&nbsp;!)</tt>, special <tt>(., [])</tt>, and string <tt>(+)</tt> operators. Operators are a feature of many programming and <a href="/2010/02/Scripting_Language" title="Reference:Scripting Language">scripting languages</a>. At first there were a relatively limited menu of operators to use in JavaScript, but version 1.2 allowed for the support of regular expressions and a group of operators large enough to compare to other scripting languages.



</p><div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/02/operator/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    
    <item>
        <title>Event</title>
        <link>http://www.webmonkey.com/2010/02/event/</link>
        <comments>http://www.webmonkey.com/2010/02/event/#comments</comments>
        <pubDate>Mon, 15 Feb 2010 20:45:47 +0000</pubDate>

                <dc:creator>Webmonkey Staff</dc:creator>

        <guid isPermaLink="false">http://stag.wired.com/primate/?p=120</guid>
        		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[UI/UX]]></category>
		<category><![CDATA[wiki]]></category>
        <description><![CDATA[Events are user interactions with their computer, such as a mouse click or key press. In the good ol&#8217; days, computers handled user interactions as input of batched data. The user fed a hunk of data in, the computer did something to that data, then produced the results. With the advent of interactive devices like [...]]]></description>

            <content:encoded><![CDATA[<!-- wpautop disabled --><p>Events are user interactions with their computer, such as a mouse click or key press.

</p><p>In the good ol&#8217; days, computers handled user interactions as input of batched data. The user fed a hunk of data in, the computer did something to that data, then produced the results. With the advent of interactive devices like the GUI interface, computers could display answers to computations onscreen. The input for these interactions are events caused by the user, which could be keystrokes, button clicks, or the position of the mouse pointer.

(see <a href="/special?title=Event_Handler&amp;action=edit" class="new" title="Event Handler">Event Handler</a>).

</p><div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/02/event/feed/</wfw:commentRss>
        <slash:comments>1</slash:comments>

        
    </item>
    
    <item>
        <title>Perl</title>
        <link>http://www.webmonkey.com/2010/02/perl/</link>
        <comments>http://www.webmonkey.com/2010/02/perl/#comments</comments>
        <pubDate>Mon, 15 Feb 2010 20:45:47 +0000</pubDate>

                <dc:creator>Webmonkey Staff</dc:creator>

        <guid isPermaLink="false">http://stag.wired.com/primate/?p=272</guid>
        		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[wiki]]></category>
        <description><![CDATA[Practical extraction and reporting language, or Perl, is a scripting language first created by Larry Wall to be used as duct tape for programming with the Unix operating system. Due to its immense power for handling piles of text and, consequently, as a common gateway interface (CGI) scripting language, Perl became very popular among server-side [...]]]></description>

            <content:encoded><![CDATA[<!-- wpautop disabled --><p><br />

Practical extraction and reporting language, or Perl, is a scripting language first created by Larry Wall to be used as duct tape for programming with the Unix operating system. Due to its immense power for handling piles of text and, consequently, as a common gateway interface (CGI) scripting language, Perl became very popular among server-side scripters. Perl has a large community of contributing programmers and, what&#8217;s more, costs nothing and is free to redistribute. These circumstances have helped Perl evolve from a scripting language used to generate server stats into a language many use for database administration. All along Perl has maintained its zaniness. Most Perl documentation reads as though written by early vaudeville comedians.

</p><div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/02/perl/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    
    <item>
        <title>Expression</title>
        <link>http://www.webmonkey.com/2010/02/expression/</link>
        <comments>http://www.webmonkey.com/2010/02/expression/#comments</comments>
        <pubDate>Mon, 15 Feb 2010 20:45:47 +0000</pubDate>

                <dc:creator>Webmonkey Staff</dc:creator>

        <guid isPermaLink="false">http://stag.wired.com/primate/?p=125</guid>
        		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[wiki]]></category>
        <description><![CDATA[In JavaScript, expressions are phrases that the interpreter can evaluate. For example, x + 10 and x &#60; 10 are expressions since they can be evaluated, while x = 10 is simply a statement. In linguistical terms, JavaScript is made up of sentences, phrases, and words. The sentences are JavaScript statements, in which an entire [...]]]></description>

            <content:encoded><![CDATA[<!-- wpautop disabled --><p>In JavaScript, expressions are phrases that the interpreter can evaluate. For example, <pre class="brush: js">x + 10</pre> and <pre class="brush: js">x &lt; 10</pre> are expressions since they can be evaluated, while <pre class="brush: js">x = 10</pre> is simply a <a href="/2010/02/Statement" title="Reference:Statement">statement</a>.



<p>In linguistical terms, JavaScript is made up of sentences, phrases, and words. The sentences are JavaScript statements, in which an entire action is expressed. The phrases are JavaScript expressions, in which the elements of the action can be created and put together to make a statement. The words are JavaScript <a href="/2010/02/Operator" title="Reference:Operator">operators</a>, which are used to act upon the data passed to them.

</p><div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/02/expression/feed/</wfw:commentRss>
        <slash:comments>1</slash:comments>

        
    </item>
    </channel>
</rss>