<?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>the toe of webdev &#187; Tip Of The Day</title>
	<atom:link href="http://toebot.edublogs.org/category/tip-of-the-day/feed/" rel="self" type="application/rss+xml" />
	<link>http://toebot.edublogs.org</link>
	<description>a disabled developer's point of view</description>
	<lastBuildDate>Sat, 03 Jan 2009 23:21:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The design process MUST start with paper</title>
		<link>http://toebot.edublogs.org/2009/01/03/the-design-process-must-start-with-paper/</link>
		<comments>http://toebot.edublogs.org/2009/01/03/the-design-process-must-start-with-paper/#comments</comments>
		<pubDate>Sat, 03 Jan 2009 23:18:00 +0000</pubDate>
		<dc:creator>toebot</dc:creator>
				<category><![CDATA[Tip Of The Day]]></category>

		<guid isPermaLink="false">http://toebot.edublogs.org/2009/01/03/the-design-process-must-start-with-paper/</guid>
		<description><![CDATA[I don&#8217;t actually mean this in a random &#8220;this is a must follow rule&#8221; kind of way, but in a, &#8220;unless you sit in front of a canvas for a few hours and create something you can sell for thousands of dollars&#8221; you MUST being your design processes on paper.
No, you cannot use your computer [...]]]></description>
			<content:encoded><![CDATA[<p>I don&#8217;t actually mean this in a random &#8220;this is a must follow rule&#8221; kind of way, but in a, &#8220;unless you sit in front of a canvas for a few hours and create something you can sell for thousands of dollars&#8221; you MUST being your design processes on paper.</p>
<p>No, you cannot use your computer to plan out this sketch.&nbsp; Unless of course again the rule stretches to fit you.&nbsp; Can you throw around a few Smart Guides in Photoshop or (guides in) The GIMP and quickly achieve the desired box layout?&nbsp; Can you then immediately throw a few organic compounds into place so your layout starts to flesh out?&nbsp; Can you then immediately match color schemes to the different components of the layouts?</p>
<p>If you can, the rule does not apply.&nbsp; If you cannot, then please, understand one thing&#8230;</p>
<p>The design process MUST start with paper.</p>
<p>Whether designing an application&#8217;s layout or GUI; defining the different components of a Web template; redesigning a company brochure; or creating a flyer for your favorite non-profit or church starting out on paper is a must.</p>
<p>One final tip (as if you could not guess) is if you begin the actual finalization of your layout by taking it from paper to its medium (computer, print, audio, whatever&#8230;) and you encounter problems or additional layout concerns then head immediately back to paper.</p>
<p>Going through this process is as much a learning experience as it is developing a work flow that suits your behaviors.</p>
]]></content:encoded>
			<wfw:commentRss>http://toebot.edublogs.org/2009/01/03/the-design-process-must-start-with-paper/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tip of the Day: Non-User Amenities</title>
		<link>http://toebot.edublogs.org/2008/07/08/tip-of-the-day-non-user-amenities/</link>
		<comments>http://toebot.edublogs.org/2008/07/08/tip-of-the-day-non-user-amenities/#comments</comments>
		<pubDate>Tue, 08 Jul 2008 23:43:51 +0000</pubDate>
		<dc:creator>toebot</dc:creator>
				<category><![CDATA[Tip Of The Day]]></category>

		<guid isPermaLink="false">http://toebot.edublogs.org/?p=22</guid>
		<description><![CDATA[Today&#8217;s post is about non-user, -member, or -registered amenities.  These are those services or features that are offered to end-users who are not yet members of your site.
For example: http://www.pocketpcthoughts.com/
Visit this URL while on a mobile device, or using a mobile browser, or even with spoofed user agent settings and you can see that it [...]]]></description>
			<content:encoded><![CDATA[<p>Today&#8217;s post is about non-user, -member, or -registered amenities.  These are those services or features that are offered to end-users who are not yet members of your site.</p>
<p>For example: http://www.pocketpcthoughts.com/</p>
<p>Visit this URL while on a mobile device, or using a mobile browser, or even with spoofed user agent settings and you can see that it immediately asks you the type of connection you are on and whether or not you would like the full user experience or a limited one (for those with obvious broadband deficiencies).</p>
<p><a href="http://toebot.edublogs.org/files/2008/07/20080708_193148.jpg"><img class="aligncenter size-full wp-image-23" src="http://toebot.edublogs.org/files/2008/07/20080708_193148.jpg" alt="Pocket PC Thoughts Screen Shot" width="240" height="320" /></a></p>
<p>Now, let&#8217;s be honest.  No one needs to provide everyone anything.  That is, if I have a commercial site or a site that generates revenue in any fashion &#8212; it is simply NOT my responsibility to provide for users that have not enlisted my services.</p>
<p>So for them to be aware of this situation and then develop their site accordingly is a very unique, far too uncommon practice.  I would not be surprised if they had an R&amp;D person or two.</p>
<p>Think about these things when you develop your applications or sites.  After all, giving a bear a taste of honey is not a way to scare him off.</p>
]]></content:encoded>
			<wfw:commentRss>http://toebot.edublogs.org/2008/07/08/tip-of-the-day-non-user-amenities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Do you understand what understanding means?</title>
		<link>http://toebot.edublogs.org/2008/06/10/do-you-understand-what-understanding-means/</link>
		<comments>http://toebot.edublogs.org/2008/06/10/do-you-understand-what-understanding-means/#comments</comments>
		<pubDate>Tue, 10 Jun 2008 08:37:57 +0000</pubDate>
		<dc:creator>toebot</dc:creator>
				<category><![CDATA[Rambling]]></category>
		<category><![CDATA[Tip Of The Day]]></category>

		<guid isPermaLink="false">http://toebot.edublogs.org/2008/06/10/do-you-understand-what-understanding-means/</guid>
		<description><![CDATA[Take heed my small sampling of readers — when you read a tutorial for whatever purpose — make sure you completely understand it.
Often I read a tutorial on JavaScript or some advanced Photoshop tutorial and I am left thinking, &#8220;What the hell did I just read?&#8221;
I know it can be difficult because you may think, [...]]]></description>
			<content:encoded><![CDATA[<p>Take heed my small sampling of readers — when you read a tutorial for whatever purpose — make sure you <strong>completely</strong> understand it.</p>
<p>Often I read a tutorial on JavaScript or some advanced Photoshop tutorial and I am left thinking, &#8220;What the hell did I just read?&#8221;</p>
<p>I know it can be difficult because you may think, &#8220;Who do I ask when I do not understand?&#8221;  The answer is not at all clear, but you can help yourself in a number of ways.</p>
<ul>
<li>IRC &#8211; Yep, Internet Relay Chat.&nbsp; You can search for channels (chat rooms) that contain listings such as &#8220;programming,&#8221; &#8220;javascript,&#8221; or even &#8220;love&#8221; &#8212; and find someone, somewhere who is willing to deal with your issues.</p>
<p>Just make sure you obey the laws of netiquette and you should be fine.&nbsp; In addition, make sure to obey the laws of the given medium.&nbsp; If IRC, then how to behave on IRC.&nbsp; If newsgroups, then how to behave on newsgroups, et cetera.</li>
<li>School</li>
<li>Internet</li>
<li>Socially accepted mediums &#8211; Twitter, Facebook, Slashdot, Digg, hell, even MySpace.</li>
</ul>
<p>Woah, woah&#8230; the Internet?&nbsp; Twitter?</p>
<p>What the hell am I talking about you say?</p>
<p>The thing is, that beyond the scope of the millions and millions of blog users out there &mdash; you have the &#8220;socially accepted mediums.&#8221;</p>
<p>These are the sites, chat rooms, blogs, forums, et cetera where like-minded people share and trade ideas, wisdom, and other semi-useful information.</p>
<p>Twitter for example exclaims, &#8220;What are you doing?&#8221;&nbsp; Well, I am currently writing this post.&nbsp; However, it means what are you doing (for the day)!?&nbsp; Are you studying?&nbsp; Skiing?&nbsp; Flirting?</p>
<p>Does it not make sense to ask others who are doing the same thing as you for their opinion?</p>
<p>Seriously.&nbsp; Whether it is a StumbleUpon&#8217;d site or someone who happens to share a few of the same interests as you, it is always wise to let others know that you value their opinion and have a desire to digest the information that only they (or someone just like them) can provide.</p>
<p>Did the Internet response floor you?&nbsp; Why!?</p>
<p>How many times a day do you Google information?&nbsp; How many times a day do you fire up a browser just to look up a reference at Mozilla or Microsoft?&nbsp; How many times a day do you review DevGuru&#8217;s CSS reference?&nbsp; How often do you visit Programmer&#8217;s Heaven?</p>
<p>Um&#8230; hello!?&nbsp; That is the Internet!&nbsp; Every time you seek information that is not included in a software program&#8217;s help resource or visit a &#8220;reference&#8221; site, you are referring to the Internet.</p>
<p>Trust in it, just do not be led astray by it.&nbsp; Much like Wikipedia.&nbsp; I do not give two cents for what others think &mdash; Wikipedia is an excellent resource!&nbsp; However, you need to be smart enough to discern the multitudes of shite from the grade &#8220;A&#8221; fertilizer.</p>
]]></content:encoded>
			<wfw:commentRss>http://toebot.edublogs.org/2008/06/10/do-you-understand-what-understanding-means/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tip of the Day: Learn an API documentation syntax.</title>
		<link>http://toebot.edublogs.org/2008/06/02/tip-of-the-day-learn-an-api-documentation-syntax/</link>
		<comments>http://toebot.edublogs.org/2008/06/02/tip-of-the-day-learn-an-api-documentation-syntax/#comments</comments>
		<pubDate>Tue, 03 Jun 2008 03:34:41 +0000</pubDate>
		<dc:creator>toebot</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Tip Of The Day]]></category>

		<guid isPermaLink="false">http://toebot.edublogs.org/2008/06/02/tip-of-the-day-learn-an-api-documentation-syntax/</guid>
		<description><![CDATA[If you write programs or &#8220;code applications,&#8221; then you should seriously check into the standard commenting and API documentation syntax available to that language.
This has 2 primary benefits, possible others:

You learn to properly comment your code.
Your code explains itself to other programmers.

And anything that increases your efficiency and aptitude in  something you enjoy either [...]]]></description>
			<content:encoded><![CDATA[<p>If you write programs or &#8220;code applications,&#8221; then you should seriously check into the standard commenting and API documentation syntax available to that language.</p>
<p>This has 2 primary benefits, possible others:</p>
<ol>
<li>You learn to properly comment your code.</li>
<li>Your code explains itself to other programmers.</li>
</ol>
<p>And anything that increases your efficiency and aptitude in  something you enjoy either as a hobbyist or as a professional can only result in positive learning — the best kind.</p>
<p><a href="http://en.wikipedia.org/wiki/Comparison_of_documentation_generators">Wikipedia&#8217;s comparison of documentation generators can be found here.</a>  This lists the majority of those I could possibly think to show you, so make sure to research the language you code with.</p>
<p>These tools generate API documentation based on your properly formatted comments.</p>
<p>The ones I keep in mind are:</p>
<ul>
<li><a href="http://jsdoc.sourceforge.net/">JSDoc</a> for JavaScript</li>
<li><a href="http://apydia.ematia.de/">Apydia</a> for Python</li>
<li><a href="http://www.gtk.org/gtk-doc/">GTK-Doc</a> for C</li>
<li><a href="http://www.phpdoc.org/">phpDocumentor</a> for PHP</li>
<li>See &#8220;best for last&#8221; at the bottom of the page for PHP, C#, and Python.</li>
</ul>
<p>Otherwise, I have not used any others, but I have heard that:</p>
<ul>
<li>Doc-O-Matic</li>
<li>ROBODoc</li>
<li>TwinText</li>
<li>Universal Report</li>
</ul>
<p>Are the most robust.&nbsp; And the <a href="http://en.wikipedia.org/wiki/Comparison_of_documentation_generators">article I provided earlier</a> illustrates that same assumption.</p>
<p>I believe I saved the best for last, and that is <a href="http://www.doxygen.org/">Doxygen</a>.&nbsp; As far as I know, Doxygen can automatically generate well-formatted API documentation for several languages and is by far the most robust*.&nbsp; If it currently had deep support for JavaScript and/or ASM (assembler or assembly) I would tentatively call it the ultimate and only tool necessary.</p>
<p>* Please let me know if there is a more robust or preferred tool — either by industry or by popularity.</p>
]]></content:encoded>
			<wfw:commentRss>http://toebot.edublogs.org/2008/06/02/tip-of-the-day-learn-an-api-documentation-syntax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
