<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for EddieOffermann dot com</title>
	<link>http://eddieoffermann.com/blog</link>
	<description>The reel, resume and contact resource for Eddie Offermann, Visual Effects Scripter, CG VFX and Integration Artist</description>
	<pubDate>Tue, 06 Jan 2009 12:12:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>Comment on XML, Python and the Visual Effects Pipeline by Cameron O'Rourke</title>
		<link>http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-73</link>
		<dc:creator>Cameron O'Rourke</dc:creator>
		<pubDate>Mon, 15 Dec 2008 01:36:52 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-73</guid>
		<description>Yeah, I guess that makes sense. As long as a human is involved in kicking off the process that says "this asset is ready", it would be very natural to update the project tracker.  

We are in the beginning stages, but we have an industrial-strength workflow system running under the covers along with email notifications. We could totally mark one task as 'complete', mark the next task as 'in-progress', start putting the assets into position, and put a notification up on the next artists' dashboard.

Something that I just realized is that these steps could be driven by workflow, or by the Python script. Hmmm. I had been assuming that we needed a user-configurable workflow system all this time. 

Do you already have a project tracker, or are you building one? I would be very interested to know what you would like to see in such a tool.</description>
		<content:encoded><![CDATA[<p>Yeah, I guess that makes sense. As long as a human is involved in kicking off the process that says &#8220;this asset is ready&#8221;, it would be very natural to update the project tracker.  </p>
<p>We are in the beginning stages, but we have an industrial-strength workflow system running under the covers along with email notifications. We could totally mark one task as &#8216;complete&#8217;, mark the next task as &#8216;in-progress&#8217;, start putting the assets into position, and put a notification up on the next artists&#8217; dashboard.</p>
<p>Something that I just realized is that these steps could be driven by workflow, or by the Python script. Hmmm. I had been assuming that we needed a user-configurable workflow system all this time. </p>
<p>Do you already have a project tracker, or are you building one? I would be very interested to know what you would like to see in such a tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XML, Python and the Visual Effects Pipeline by Eddie</title>
		<link>http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-72</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Sun, 14 Dec 2008 07:58:05 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-72</guid>
		<description>I see absolutely no reason to not introduce this sort of interaction.  I think it's a natural!

One of the features I'm planning to implement relatively soon is the ability for artists to register their interest in data for a particular shot.  For instance, if a lighter is waiting on a camera to be published, the lighter would be able to access an interface (web or inside of Maya) and indicate that they would like to receive notification when a camera or revised animation is available.  When an animator or tracker releases the needed asset, the lighter receives an instant message or an email to indicate that their asset is ready.  These notifications could even be set up by production coordinators or producers to help speed things along.  If there's anything I personally hate, it's having to call/IM/email someone just to say "Hey, that animation data is ready!"

Since my pipeline tools are extending to encompass model and texture publishing and eventually even lighting and rendering setups (they already include limited functionality for compositors - and that'll grow soon as well), it's possible for the system to report when an artist has picked up a shot to work on, when they complete it and when it has moved on (or is ready to move on) to the next stage.

Reporting this data to a project tracking system is handy.</description>
		<content:encoded><![CDATA[<p>I see absolutely no reason to not introduce this sort of interaction.  I think it&#8217;s a natural!</p>
<p>One of the features I&#8217;m planning to implement relatively soon is the ability for artists to register their interest in data for a particular shot.  For instance, if a lighter is waiting on a camera to be published, the lighter would be able to access an interface (web or inside of Maya) and indicate that they would like to receive notification when a camera or revised animation is available.  When an animator or tracker releases the needed asset, the lighter receives an instant message or an email to indicate that their asset is ready.  These notifications could even be set up by production coordinators or producers to help speed things along.  If there&#8217;s anything I personally hate, it&#8217;s having to call/IM/email someone just to say &#8220;Hey, that animation data is ready!&#8221;</p>
<p>Since my pipeline tools are extending to encompass model and texture publishing and eventually even lighting and rendering setups (they already include limited functionality for compositors - and that&#8217;ll grow soon as well), it&#8217;s possible for the system to report when an artist has picked up a shot to work on, when they complete it and when it has moved on (or is ready to move on) to the next stage.</p>
<p>Reporting this data to a project tracking system is handy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XML, Python and the Visual Effects Pipeline by Cameron O'Rourke</title>
		<link>http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-71</link>
		<dc:creator>Cameron O'Rourke</dc:creator>
		<pubDate>Sun, 14 Dec 2008 06:24:55 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-71</guid>
		<description>Hi Eddie. I've been working hard on an online collaboration and project tracking tool for VFX (think mashup between Basecamp and VFX Showrunner.) Someone suggested that I should offer Python bindings into the system for ease of integration with pipelines. 

Do you think this would be useful? Or are pipeline automation and project tracking operating at totally different levels of granularity to be integrated? I'm having trouble coming up with a scenario where this would be useful. 

Since you are knee-deep in this aspect of the industry which I am not, any insights would be very helpful. 

Cheers, 
Cameron</description>
		<content:encoded><![CDATA[<p>Hi Eddie. I&#8217;ve been working hard on an online collaboration and project tracking tool for VFX (think mashup between Basecamp and VFX Showrunner.) Someone suggested that I should offer Python bindings into the system for ease of integration with pipelines. </p>
<p>Do you think this would be useful? Or are pipeline automation and project tracking operating at totally different levels of granularity to be integrated? I&#8217;m having trouble coming up with a scenario where this would be useful. </p>
<p>Since you are knee-deep in this aspect of the industry which I am not, any insights would be very helpful. </p>
<p>Cheers,<br />
Cameron</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reel by Josh Johnson</title>
		<link>http://eddieoffermann.com/blog/reel/#comment-34</link>
		<dc:creator>Josh Johnson</dc:creator>
		<pubDate>Tue, 26 Aug 2008 08:38:21 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/reel/#comment-34</guid>
		<description>Fantastic work! I sent you a message on youtube.  You are a true inspiration.

Josh</description>
		<content:encoded><![CDATA[<p>Fantastic work! I sent you a message on youtube.  You are a true inspiration.</p>
<p>Josh</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Video game convergence by Video game convergence &#124; SL Blogs</title>
		<link>http://eddieoffermann.com/blog/2008/07/12/video-game-convergence/#comment-29</link>
		<dc:creator>Video game convergence &#124; SL Blogs</dc:creator>
		<pubDate>Sat, 12 Jul 2008 18:08:09 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/07/12/video-game-convergence/#comment-29</guid>
		<description>[...] View original here: Video game convergence [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] View original here: Video game convergence [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-platform Mobile Deployment by Austin</title>
		<link>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-24</link>
		<dc:creator>Austin</dc:creator>
		<pubDate>Thu, 19 Jun 2008 20:15:24 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-24</guid>
		<description>I agree with most of what you said!


But doesn't mobilesafari have hooks into the API to allow you to use corelocation and things like that? I bet if this is truly signaling a change, things of that nature will start to be built into other phones. I know you can't count on that right now (and it would be silly to develop for something that may happen in the future as I'm sure you're well aware of) but I think it could actually be game changing.


And again, I'm surprised you're not already on twitter, haha.</description>
		<content:encoded><![CDATA[<p>I agree with most of what you said!</p>
<p>But doesn&#8217;t mobilesafari have hooks into the API to allow you to use corelocation and things like that? I bet if this is truly signaling a change, things of that nature will start to be built into other phones. I know you can&#8217;t count on that right now (and it would be silly to develop for something that may happen in the future as I&#8217;m sure you&#8217;re well aware of) but I think it could actually be game changing.</p>
<p>And again, I&#8217;m surprised you&#8217;re not already on twitter, haha.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-platform Mobile Deployment by Eddie</title>
		<link>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-23</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Thu, 19 Jun 2008 02:23:35 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-23</guid>
		<description>Well the project is definitely a download-to-phone sort of thing - and because of what it does, there's no reason to have it on a non-smartphone.  Browser-based just isn't going to work for this unless phone browsers become much more sophisticated (and are able to tie into aspects of the phone's hardware that no browser really *ought* to be able to access for security reasons)

I think the winds are changing there: the iPhone introduced "smartphone" devices to a much broader market and I think we'll see that the internet as we know it ceases to be the sit-and-type and read and watch YouTube thing that it is today.  The internet is a way of communicating information, and information has always been a lot more than newspapers, textbooks and television.

As phones come to know where they are and are able to tie into a variety of realtime data sources, a lot can happen that the vast majority of people aren't even beginning to see yet. The mobile web won't greatly resemble the desktop one: and browsers won't be the best interface for it until they make some changes.

In the meantime, it's gotta be applications.</description>
		<content:encoded><![CDATA[<p>Well the project is definitely a download-to-phone sort of thing - and because of what it does, there&#8217;s no reason to have it on a non-smartphone.  Browser-based just isn&#8217;t going to work for this unless phone browsers become much more sophisticated (and are able to tie into aspects of the phone&#8217;s hardware that no browser really *ought* to be able to access for security reasons)</p>
<p>I think the winds are changing there: the iPhone introduced &#8220;smartphone&#8221; devices to a much broader market and I think we&#8217;ll see that the internet as we know it ceases to be the sit-and-type and read and watch YouTube thing that it is today.  The internet is a way of communicating information, and information has always been a lot more than newspapers, textbooks and television.</p>
<p>As phones come to know where they are and are able to tie into a variety of realtime data sources, a lot can happen that the vast majority of people aren&#8217;t even beginning to see yet. The mobile web won&#8217;t greatly resemble the desktop one: and browsers won&#8217;t be the best interface for it until they make some changes.</p>
<p>In the meantime, it&#8217;s gotta be applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-platform Mobile Deployment by Austin</title>
		<link>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-22</link>
		<dc:creator>Austin</dc:creator>
		<pubDate>Thu, 19 Jun 2008 00:41:17 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-22</guid>
		<description>The problem I see with developing for the much larger crowd using Java is A) you have to use java, and B) the majority of the larger crowd don't download apps for their phone.

It's one of the same reasons why cell phone games haven't taken off in America like they have in other countries where people are used to downloading things on their phone, and using their phone for everything. Not to mention their lower end phones are generally much nicer than our lower-end phones.

Even when I had a nice Sony Ericsson, the only thing I ever downloaded on it was GMail, and I barely even used it.

I can see it more taking off in the smartphone market, but like with most products, developing native is always better. Java is such a turd I hate it I hate it I hate it.</description>
		<content:encoded><![CDATA[<p>The problem I see with developing for the much larger crowd using Java is A) you have to use java, and B) the majority of the larger crowd don&#8217;t download apps for their phone.</p>
<p>It&#8217;s one of the same reasons why cell phone games haven&#8217;t taken off in America like they have in other countries where people are used to downloading things on their phone, and using their phone for everything. Not to mention their lower end phones are generally much nicer than our lower-end phones.</p>
<p>Even when I had a nice Sony Ericsson, the only thing I ever downloaded on it was GMail, and I barely even used it.</p>
<p>I can see it more taking off in the smartphone market, but like with most products, developing native is always better. Java is such a turd I hate it I hate it I hate it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-platform Mobile Deployment by Carrie</title>
		<link>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-20</link>
		<dc:creator>Carrie</dc:creator>
		<pubDate>Mon, 16 Jun 2008 23:08:22 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-20</guid>
		<description>DAMN IT!

http://en.wikipedia.org/wiki/Stan_Winston</description>
		<content:encoded><![CDATA[<p>DAMN IT!</p>
<p><a href="http://en.wikipedia.org/wiki/Stan_Winston" rel="nofollow">http://en.wikipedia.org/wiki/Stan_Winston</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-platform Mobile Deployment by Eddie</title>
		<link>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-19</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Mon, 16 Jun 2008 18:36:56 +0000</pubDate>
		<guid>http://eddieoffermann.com/blog/2008/06/15/crossplatform-mobile-deployment/#comment-19</guid>
		<description>I know their development cycle is somewhat slow - and "coming soon" is always a little bit of a warning sign for me.  I can put "Coming soon: Time machines!" on my webpage, but delivering is a whole different story.

I haven't looked into any other cross-platform development systems yet, mainly because I haven't seen anything else that seems as promising.  If it's a case of having to separately develop for a variety of different phones, then I'll just have to wait and do Java midlets for everything until I can devote time and/or budget to doing native applications.

Have you seen anything else that looks good?  For obvious reasons, I'm really intending to avoid spending a lot of time cross-developing right now: I'll do iPhone and *something* else - hopefully that something is more than one platform.</description>
		<content:encoded><![CDATA[<p>I know their development cycle is somewhat slow - and &#8220;coming soon&#8221; is always a little bit of a warning sign for me.  I can put &#8220;Coming soon: Time machines!&#8221; on my webpage, but delivering is a whole different story.</p>
<p>I haven&#8217;t looked into any other cross-platform development systems yet, mainly because I haven&#8217;t seen anything else that seems as promising.  If it&#8217;s a case of having to separately develop for a variety of different phones, then I&#8217;ll just have to wait and do Java midlets for everything until I can devote time and/or budget to doing native applications.</p>
<p>Have you seen anything else that looks good?  For obvious reasons, I&#8217;m really intending to avoid spending a lot of time cross-developing right now: I&#8217;ll do iPhone and *something* else - hopefully that something is more than one platform.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
