<?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>Nick Vidal</title>
	<atom:link href="http://nick.iss.im/feed/" rel="self" type="application/rss+xml" />
	<link>http://nick.iss.im</link>
	<description>nick . iss . im</description>
	<lastBuildDate>Fri, 26 Feb 2010 22:59:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Media – The Anatomy of an ITOP App</title>
		<link>http://nick.iss.im/2010/02/10/media-%e2%80%93-the-anatomy-of-an-itop-app/</link>
		<comments>http://nick.iss.im/2010/02/10/media-%e2%80%93-the-anatomy-of-an-itop-app/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 20:47:52 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[itop]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=439</guid>
		<description><![CDATA[The media frame is located on the right side of the application window. Media might be an image, an audio, a video, a graph, a flash animation, or a java applet. Conventional Web pages or self-contained Web applications may also be displayed in the media frame. In these cases, they are displayed within an iframe [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://nick.iss.im/wp-content/uploads/2010/02/media.png"><img class="alignright size-full wp-image-440" title="media" src="http://nick.iss.im/wp-content/uploads/2010/02/media.png" alt="media" width="206" height="297" /></a>The media frame is located on the right side of the application window. Media might be an image, an audio, a video, a graph, a flash animation, or a java applet. Conventional Web pages or self-contained Web applications may also be displayed in the media frame. In these cases, they are displayed within an iframe for security reasons.</p>
<p>The media frame features the title bar, the tool bar and the status bar. The title bar contains the name of the media currently being displayed. The tool bar provides buttons to perform actions. The status bar helps the user to be aware of which media is currently being displayed. The buttons provided in the toolbar are also available from a menu on the status bar.</p>
<p>On limited-size screens, the tool bar may be hidden, appearing only when the user hovers over the top part of the screen.</p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/02/10/media-%e2%80%93-the-anatomy-of-an-itop-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Form &#8211; The Anatomy of an ITOP App</title>
		<link>http://nick.iss.im/2010/02/09/form-the-anatomy-of-an-itop-app/</link>
		<comments>http://nick.iss.im/2010/02/09/form-the-anatomy-of-an-itop-app/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 00:56:38 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[itop]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=430</guid>
		<description><![CDATA[The form frame is located in the middle of the application window. Just like the list, the form may be populated from the server-side by calling an appropriate service. To allow secure cross-site access, JSONP is used.
The form frame features the title bar, the tool bar and the status bar. The title bar contains the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://nick.iss.im/wp-content/uploads/2010/02/form.png"><img class="alignright size-full wp-image-431" title="form" src="http://nick.iss.im/wp-content/uploads/2010/02/form.png" alt="form" width="206" height="297" /></a>The form frame is located in the middle of the application window. Just like the list, the form may be populated from the server-side by calling an appropriate service. To allow secure cross-site access, JSONP is used.</p>
<p>The form frame features the title bar, the tool bar and the status bar. The title bar contains the name of the form currently being displayed. The tool bar provides buttons to perform actions. The status bar helps the user to be aware of which part of the form is currently being displayed, since the form might be broken into several parts. The buttons provided in the toolbar are also available from a menu on the status bar.</p>
<p>On limited-size screens, the tool bar may be hidden, appearing only when the user hovers over the top part of the screen.</p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/02/09/form-the-anatomy-of-an-itop-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>List &#8211; The Anatomy of an ITOP App</title>
		<link>http://nick.iss.im/2010/02/08/list-the-anatomy-of-an-itop-app/</link>
		<comments>http://nick.iss.im/2010/02/08/list-the-anatomy-of-an-itop-app/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 01:00:13 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[itop]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=423</guid>
		<description><![CDATA[The list frame is located on the left side of the application window and its main purpose is to help users browse different services. The list may be populated from the server-side by calling an appropriate service. Services may be interlinked with the serviceLink metadata. To allow secure cross-site access, JSONP is used.
Since browsing services [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://nick.iss.im/wp-content/uploads/2010/02/list.png"><img class="size-full wp-image-424 alignright" title="list" src="http://nick.iss.im/wp-content/uploads/2010/02/list.png" alt="list" width="161" height="297" /></a>The list frame is located on the left side of the application window and its main purpose is to help users browse different services. The list may be populated from the server-side by calling an appropriate service. Services may be interlinked with the <a title="serviceLink" href="http://nick.iss.im/2009/03/31/the-servicelink/">serviceLink</a> metadata. To allow secure cross-site access, JSONP is used.</p>
<p>Since browsing services is fundamental, a navigation bar is available on the left corner. The navigation bar allows the user to go back and forth, refresh, check the history, and access shortcuts. On limited-size screens, the navigation bar may be hidden, appearing only when the user hovers over the left part of the screen.</p>
<p>Besides the navigation bar, the list frame also features the title bar, the tool bar and the status bar. The title bar contains the name of the list currently being displayed. The tool bar provides buttons, as well as a search box, which allows users to perform actions or filter the list. The status bar helps the user to be aware of the current services being displayed. To navigate, a user may click on one of the items in the list. A user may also select one or more items to perform an action. The buttons provided in the toolbar are also available from a menu on the status bar.</p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/02/08/list-the-anatomy-of-an-itop-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Frames &#8211; The Anatomy of an ITOP App</title>
		<link>http://nick.iss.im/2010/02/05/frames-the-anatomy-of-an-itop-app/</link>
		<comments>http://nick.iss.im/2010/02/05/frames-the-anatomy-of-an-itop-app/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 14:33:30 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[itop]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=415</guid>
		<description><![CDATA[
Each application window is divided in 3 frames: list, form and media. The framebar may be used to show or hide these frames. The three frames might appear simultaneously, or any combination of two, or just one.
On limited-size screens, only one of the frames may be visible at a time. The framebar may be hidden, [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><a href="http://nick.iss.im/wp-content/uploads/2010/02/frames.png"><img class="aligncenter size-full wp-image-416" title="frames" src="http://nick.iss.im/wp-content/uploads/2010/02/frames.png" alt="frames" width="433" height="234" /></a></p>
<p>Each application window is divided in 3 frames: list, form and media. The framebar may be used to show or hide these frames. The three frames might appear simultaneously, or any combination of two, or just one.</p>
<p>On limited-size screens, only one of the frames may be visible at a time. The framebar may be hidden, appearing only when the user hovers over the right part of the screen.</p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/02/05/frames-the-anatomy-of-an-itop-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tasks &#8211; The Anatomy of an ITOP App</title>
		<link>http://nick.iss.im/2010/02/04/tasks-the-anatomy-of-an-itop-app/</link>
		<comments>http://nick.iss.im/2010/02/04/tasks-the-anatomy-of-an-itop-app/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 15:52:49 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[itop]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=408</guid>
		<description><![CDATA[
On the lower part of the screen, we have the taskbar. The right corner of the taskbar is reserved for status information. The tasks are represented by icons on the left corner of the taskbar. When the user hovers the mouse over one of these icons, four options appear: maximize, minimize, replicate and close.
On limited-size [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><a href="http://nick.iss.im/wp-content/uploads/2010/02/tasks.png"><img class="aligncenter size-full wp-image-409" title="tasks" src="http://nick.iss.im/wp-content/uploads/2010/02/tasks.png" alt="tasks" width="425" height="290" /></a></p>
<p>On the lower part of the screen, we have the taskbar. The right corner of the taskbar is reserved for status information. The tasks are represented by icons on the left corner of the taskbar. When the user hovers the mouse over one of these icons, four options appear: maximize, minimize, replicate and close.</p>
<p>On limited-size screens, such as mobile phones for example, the taskbar may be hidden, appearing only when the user hovers over the lower part of the screen.</p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/02/04/tasks-the-anatomy-of-an-itop-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Overview &#8211; The Anatomy of an ITOP App</title>
		<link>http://nick.iss.im/2010/02/03/overview-the-anatomy-of-an-itop-app/</link>
		<comments>http://nick.iss.im/2010/02/03/overview-the-anatomy-of-an-itop-app/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 02:20:08 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[itop]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=396</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<div id="attachment_397" class="wp-caption aligncenter" style="width: 434px"><a href="http://nick.iss.im/wp-content/uploads/2010/02/itop.png"><img class="size-full wp-image-397           " title="ITOP" src="http://nick.iss.im/wp-content/uploads/2010/02/itop.png" alt="Overview of an iTop Application" width="424" height="234" /></a><p class="wp-caption-text">Overview of an ITOP Application</p></div>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/02/03/overview-the-anatomy-of-an-itop-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Toronto</title>
		<link>http://nick.iss.im/2010/02/02/toronto/</link>
		<comments>http://nick.iss.im/2010/02/02/toronto/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 14:59:10 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[travel]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=386</guid>
		<description><![CDATA[Photos from Toronto:
]]></description>
			<content:encoded><![CDATA[<p>Photos from Toronto:</p>
<p><a href="http://nick.iss.im/wp-content/uploads/2010/02/university.jpg"><img size-thumbnail wp-image-387" title="University of Toronto" src="http://nick.iss.im/wp-content/uploads/2010/02/university-150x150.jpg" alt="University of Toronto" width="150" height="150" /></a><a href="http://nick.iss.im/wp-content/uploads/2010/02/queen.jpg"><img size-thumbnail wp-image-389" title="Queen Park" src="http://nick.iss.im/wp-content/uploads/2010/02/queen-150x150.jpg" alt="Queen Park" width="150" height="150" /></a><a href="http://nick.iss.im/wp-content/uploads/2010/02/museum.jpg"><img size-thumbnail wp-image-388" title="Royal Museum of Ontario" src="http://nick.iss.im/wp-content/uploads/2010/02/museum-150x150.jpg" alt="Royal Museum of Ontario" width="150" height="150" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/02/02/toronto/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linux Favorite Extra Apps</title>
		<link>http://nick.iss.im/2010/01/22/linux-favorite-extra-apps/</link>
		<comments>http://nick.iss.im/2010/01/22/linux-favorite-extra-apps/#comments</comments>
		<pubDate>Fri, 22 Jan 2010 03:40:23 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=371</guid>
		<description><![CDATA[I recently bought a netbook and installed Ubuntu Netbook Remix. This is a list of my favorite applications I added to the default installation:
Graphics:

GIMP: Image editor;
Inkscape: SVG editor;
gThumb: Image resizer;
Xsane: Image scanner.
pdftk: PDF editor.

Internet &#38; Netwok:

Skype: Landline caller;
Samba: File and printer sharer.

Sound &#38; Video:

Audacity: Sound editor;
RecordMyDesktop: Screen recorder;
FFmpeg: Video editor;
WinFF: FFmpeg frontend;
VLC: Video player;
Ubuntu-Restricted-Extras: Proprietary [...]]]></description>
			<content:encoded><![CDATA[<p>I recently bought a netbook and installed <a title="Ubuntu Netbook Remix" href="http://www.canonical.com/projects/ubuntu/unr">Ubuntu Netbook Remix</a>. This is a list of my favorite applications I added to the default installation:</p>
<p>Graphics:</p>
<ul>
<li>GIMP: Image editor;</li>
<li>Inkscape: SVG editor;</li>
<li>gThumb: Image resizer;</li>
<li>Xsane: Image scanner.</li>
<li>pdftk: PDF editor.</li>
</ul>
<p>Internet &amp; Netwok:</p>
<ul>
<li>Skype: Landline caller;</li>
<li>Samba: File and printer sharer.</li>
</ul>
<p>Sound &amp; Video:</p>
<ul>
<li>Audacity: Sound editor;</li>
<li>RecordMyDesktop: Screen recorder;</li>
<li>FFmpeg: Video editor;</li>
<li>WinFF: FFmpeg frontend;</li>
<li>VLC: Video player;</li>
<li>Ubuntu-Restricted-Extras: Proprietary video, sound, flash formats.</li>
</ul>
<p>Web Development:</p>
<ul>
<li>Apache: Web server;</li>
<li>MySQL: Database;</li>
<li>PHP: Script language;</li>
<li>PhpMyAdmin:  Database frontend;</li>
<li>Drupal: CMS;</li>
<li>ExtJS: JavaScript library;</li>
<li>Firebug: Bug tracking for Firefox;</li>
<li>FireFTP: FTP for Firefox;</li>
<li>CVS, SVN, Git: Version-control system.</li>
</ul>
<p>Language Support:</p>
<ul>
<li>Portuguese (language-support-pt);</li>
<li>French (language-support-fr).</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/01/22/linux-favorite-extra-apps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iContent</title>
		<link>http://nick.iss.im/2010/01/20/icontent/</link>
		<comments>http://nick.iss.im/2010/01/20/icontent/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 15:22:14 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[drupal]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=362</guid>
		<description><![CDATA[One of the main features of the upcoming Drupal 7 is the ability to add custom fields to content types in a user-friendly way. For example, one might add a content type called Recipe, where it has the following fields: Title, Ingredients, Instructions and Photo.  On earlier versions of Drupal, such content type had to be hard-coded by a [...]]]></description>
			<content:encoded><![CDATA[<p>One of the main features of the upcoming Drupal 7 is the ability to add custom fields to content types in a user-friendly way. For example, one might add a content type called Recipe, where it has the following fields: Title, Ingredients, Instructions and Photo.  On earlier versions of Drupal, such content type had to be hard-coded by a web programmer. With Drupal 7, a webmaster may create it with a few clicks.</p>
<p>Now imagine a generic content type called iContent that could be transformed into anything instantly by the average user. This content type would include all available types of fields (text, number, date, file, etc) with an unlimited cardinality (i.e. the fields could be repeated if necessary).</p>
<p>So let us suppose a user wants to enter a Recipe. He selects the iContent and starts building the structure on the fly. He adds the Title, then the Ingredients, later the Instructions, and finally a Photo. Now, he might want to enter a Movie. So he adds a Title, then the Director, later the Duration, then the Release Date, the Genre, a Picture, and finally the Plot. He might want to save both the Recipe and Movie structures for later use as templates. But notice that only one content type was necessary to build such different content structures.</p>
<p>This is a simple idea, but a very powerful one. It makes us rethink how we create information today. Email, for example. You only have the option to enter the Title and the Body. No other fields are allowed, with the exception of Attachments, which provide the flexibility we are looking for since it has an unlimited cardinality. Why not extend that same flexibility to the other fields? Blogs are another example. Imagine how much richer would the Web be (semantically) if blogs had this kind of flexibility?</p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/01/20/icontent/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>London, Ontario</title>
		<link>http://nick.iss.im/2010/01/18/london-ontario/</link>
		<comments>http://nick.iss.im/2010/01/18/london-ontario/#comments</comments>
		<pubDate>Mon, 18 Jan 2010 15:44:19 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[family]]></category>
		<category><![CDATA[travel]]></category>

		<guid isPermaLink="false">http://nick.iss.im/?p=345</guid>
		<description><![CDATA[Me and Debbie are currently living in London, ON. This is part of her Ph.D. program. She is continuing her research on Math Education at the University of Western Ontario. We rented a room in a ranch house 400 meters from where she works, so this is nice given all the snow we have outside. Here is a photo [...]]]></description>
			<content:encoded><![CDATA[<p>Me and Debbie are currently living in London, ON. This is part of her Ph.D. program. She is continuing her research on Math Education at the <a title="UWO" href="http://uwo.ca/">University of Western Ontario</a>. We rented a room in a ranch house 400 meters from where she works, so this is nice given all the snow we have outside. Here is a photo of Debbie in the frontyard of our new home and in the backyard with her first snowgirl:</p>
<p style="text-align: center;"><a href="http://nick.iss.im/wp-content/uploads/2010/01/PICT0147.JPG"><img class="aligncenter size-medium wp-image-346" title="Debbie in Canada" src="http://nick.iss.im/wp-content/uploads/2010/01/PICT0147-300x225.jpg" alt="Debbie in Canada" width="300" height="225" /></a></p>
<p><a href="http://nick.iss.im/wp-content/uploads/2010/01/PICT0010.JPG"><img class="aligncenter size-medium wp-image-356" title="SnowGirl" src="http://nick.iss.im/wp-content/uploads/2010/01/PICT0010-300x225.jpg" alt="SnowGirl" width="300" height="225" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://nick.iss.im/2010/01/18/london-ontario/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
