<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Object-Oriented Wireframes</title>
	<atom:link href="http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/</link>
	<description>Because every IA has something funky up their sleeve</description>
	<lastBuildDate>Wed, 28 Jul 2010 06:45:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Drew</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-2810</link>
		<dc:creator>Drew</dc:creator>
		<pubDate>Mon, 27 Jul 2009 05:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-2810</guid>
		<description>I&#039;ve been doing this technique for awhile now... using the &quot;background page&quot; property you can create all sort of objects and then `layer` them, which really speeds up the cycle.  The other part that is nice, is that visio will output to html for you (DO NOT USE THIS CODE FOR ANYTHING OTHER THAN DISPLAYING THE WIREFRAME).  For instance, I had to show a business a &#039;clickable&#039; wireframe so that their partners could &#039;grasp&#039; the concept.  After putting it all together in visio, adding the hyperlinks (to the other pages in the wireframe) is seemingly acted like a web site, which they then were able to sell the design to the business. </description>
		<content:encoded><![CDATA[<p>I&#039;ve been doing this technique for awhile now&#8230; using the &quot;background page&quot; property you can create all sort of objects and then `layer` them, which really speeds up the cycle.  The other part that is nice, is that visio will output to html for you (DO NOT USE THIS CODE FOR ANYTHING OTHER THAN DISPLAYING THE WIREFRAME).  For instance, I had to show a business a &#039;clickable&#039; wireframe so that their partners could &#039;grasp&#039; the concept.  After putting it all together in visio, adding the hyperlinks (to the other pages in the wireframe) is seemingly acted like a web site, which they then were able to sell the design to the business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Component Based Wireframes &#8250; Wireframes Magazine</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-1307</link>
		<dc:creator>Component Based Wireframes &#8250; Wireframes Magazine</dc:creator>
		<pubDate>Mon, 11 May 2009 16:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-1307</guid>
		<description>[...] Object-Oriented Wireframes [...]</description>
		<content:encoded><![CDATA[<p>[...] Object-Oriented Wireframes [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Iozzo</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-1025</link>
		<dc:creator>Nick Iozzo</dc:creator>
		<pubDate>Sat, 02 May 2009 03:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-1025</guid>
		<description>Ideally, the modules map back to the components the developer wishes to develop. I have worked in some situations where I worked with the developers in order to create a name space for the modules. That way, when I reused a module within my design, they would be able to all reuse that same module in the new location. You can so the same if the content is coming from a CMS system. The name space this technique creates allows you to develop some meaningful references in which to refer to the data. </description>
		<content:encoded><![CDATA[<p>Ideally, the modules map back to the components the developer wishes to develop. I have worked in some situations where I worked with the developers in order to create a name space for the modules. That way, when I reused a module within my design, they would be able to all reuse that same module in the new location. You can so the same if the content is coming from a CMS system. The name space this technique creates allows you to develop some meaningful references in which to refer to the data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: occipocci</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-1021</link>
		<dc:creator>occipocci</dc:creator>
		<pubDate>Sat, 02 May 2009 02:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-1021</guid>
		<description>Do you have any detail as to how programmers use these wireframes whilst they are coding? I have always been confused as to whether this documentation is for their benefit or the designers, and how much of it the coders actually use. </description>
		<content:encoded><![CDATA[<p>Do you have any detail as to how programmers use these wireframes whilst they are coding? I have always been confused as to whether this documentation is for their benefit or the designers, and how much of it the coders actually use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason furnell</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-926</link>
		<dc:creator>jason furnell</dc:creator>
		<pubDate>Wed, 29 Apr 2009 02:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-926</guid>
		<description>i use a similar approach for defining the scope of stories when using agile, its good for building up the components on the page as the build progresses </description>
		<content:encoded><![CDATA[<p>i use a similar approach for defining the scope of stories when using agile, its good for building up the components on the page as the build progresses</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Iozzo</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-919</link>
		<dc:creator>Nick Iozzo</dc:creator>
		<pubDate>Tue, 28 Apr 2009 16:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-919</guid>
		<description>Its all Visio. I dug into the shapesheets of Visio to make some custom shapes with some custom actions on contextual menus. It also help to change the default fonts </description>
		<content:encoded><![CDATA[<p>Its all Visio. I dug into the shapesheets of Visio to make some custom shapes with some custom actions on contextual menus. It also help to change the default fonts</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vance</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-918</link>
		<dc:creator>Vance</dc:creator>
		<pubDate>Tue, 28 Apr 2009 14:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-918</guid>
		<description>Out of curiosity, what tool do you use to produce the beautiful wireframes used in your posts?  Is it just something like Fireworks with your own custom template/styling, or is there a wireframe tool you&#039;re using? 
 
Thanks. </description>
		<content:encoded><![CDATA[<p>Out of curiosity, what tool do you use to produce the beautiful wireframes used in your posts?  Is it just something like Fireworks with your own custom template/styling, or is there a wireframe tool you&#039;re using? </p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik</title>
		<link>http://wireframes.linowski.ca/2009/04/object-oriented-wireframes/comment-page-1/#comment-916</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Tue, 28 Apr 2009 12:50:27 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=827#comment-916</guid>
		<description>Nice idea... just started doing similar myself for showing logged in / logged out states on content blocks. 
 
Nik </description>
		<content:encoded><![CDATA[<p>Nice idea&#8230; just started doing similar myself for showing logged in / logged out states on content blocks. </p>
<p>Nik</p>
]]></content:encoded>
	</item>
</channel>
</rss>
