<?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: Google Android update: videos, development group, blogs</title>
	<atom:link href="http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/feed/" rel="self" type="application/rss+xml" />
	<link>http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/</link>
	<description>Augusto's corner of art, code and fun</description>
	<lastBuildDate>Tue, 23 Feb 2010 08:25:54 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Augusto</title>
		<link>http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/comment-page-1/#comment-1507</link>
		<dc:creator>Augusto</dc:creator>
		<pubDate>Thu, 15 Nov 2007 22:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/#comment-1507</guid>
		<description>Saptarshi;

&quot;The reason they dont have the SE graphics because they wanted Android to be working on low-end handsets. &quot;

What is so heavy weight about Graphics2D, they have the same functionality enabled (but different API) for their graphics. They also have OpenGL support, which is way more complicated than what Graphics2D provides.

&quot;JavaFX (mobile or otherwise) is not open-source and Google’s Android is open-source. &quot;

JavaFX is supposed to become open source, just like Android. Right now we don&#039;t have the source to the Android SDK either!</description>
		<content:encoded><![CDATA[<p>Saptarshi;</p>
<p>&#8220;The reason they dont have the SE graphics because they wanted Android to be working on low-end handsets. &#8221;</p>
<p>What is so heavy weight about Graphics2D, they have the same functionality enabled (but different API) for their graphics. They also have OpenGL support, which is way more complicated than what Graphics2D provides.</p>
<p>&#8220;JavaFX (mobile or otherwise) is not open-source and Google’s Android is open-source. &#8221;</p>
<p>JavaFX is supposed to become open source, just like Android. Right now we don&#8217;t have the source to the Android SDK either!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saptarshi</title>
		<link>http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/comment-page-1/#comment-1468</link>
		<dc:creator>Saptarshi</dc:creator>
		<pubDate>Thu, 15 Nov 2007 04:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/#comment-1468</guid>
		<description>The reason they dont have the SE graphics because they wanted Android to be working on low-end handsets. Swing is pretty heavy and would have been problematic for low-end handsets.

JavaFX (mobile or otherwise) is not open-source and Google&#039;s Android is open-source. Although some handset manufacturers could add whatever they want to in Android because of the flexible Apache license!</description>
		<content:encoded><![CDATA[<p>The reason they dont have the SE graphics because they wanted Android to be working on low-end handsets. Swing is pretty heavy and would have been problematic for low-end handsets.</p>
<p>JavaFX (mobile or otherwise) is not open-source and Google&#8217;s Android is open-source. Although some handset manufacturers could add whatever they want to in Android because of the flexible Apache license!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paulo</title>
		<link>http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/comment-page-1/#comment-1407</link>
		<dc:creator>paulo</dc:creator>
		<pubDate>Tue, 13 Nov 2007 21:40:56 +0000</pubDate>
		<guid isPermaLink="false">http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/#comment-1407</guid>
		<description>And some utility classes for dealing with those anoying try catch stupidities. For example (my poison) :
/**
     * Close closeables. Use this in a finally clause.
     */
    public static void close(Closeable... closeables) {
        for (Closeable c : closeables) {
            if (c != null) {
                try {
                    c.close();
                } catch (Exception ex) {
                    ex.printStackTrace();
                }
            }
        }
    }

and

    /**
     * If possible reads an object, if not tries to instanciate the  
     * object with the given Callable. This allows lazy instantiation.
     * If an exception occurs in the lazy instantiantion it returns null.
     * Remember that if using Externalizable transient fields/static scopes 
     * fields ARE initalized. The use of the default constructor assures that. 
     * The order of inicialization is:
     * Externalizable : default constructor, readExternal
     * Serializable : first non-serializable super class default constructor, 
     * readObject
     * So with externalizable you need to be carefull not to use automatically 
     * assigned fields of the class in the constructor, that will be read back, 
     * and in serializable, replace the constructor.
     */
    public static  T readObject(String objectLocation, Callable t) {
        ObjectInputStream s = null;
        try {
            s = new ObjectInputStream(new BufferedInputStream(new FileInputStream(objectLocation)));
            return (T) s.readObject();
        } catch (Exception ex) {
            try {
                return (T) t.call();
            } catch (Exception e) {
                e.printStackTrace();
            }
        } finally {
            close(s);
        }
        return null;
    }

If you&#039;d need to reuse the stream you could pass the stream instead and remove the finally to outside and close there.</description>
		<content:encoded><![CDATA[<p>And some utility classes for dealing with those anoying try catch stupidities. For example (my poison) :<br />
/**<br />
     * Close closeables. Use this in a finally clause.<br />
     */<br />
    public static void close(Closeable&#8230; closeables) {<br />
        for (Closeable c : closeables) {<br />
            if (c != null) {<br />
                try {<br />
                    c.close();<br />
                } catch (Exception ex) {<br />
                    ex.printStackTrace();<br />
                }<br />
            }<br />
        }<br />
    }</p>
<p>and</p>
<p>    /**<br />
     * If possible reads an object, if not tries to instanciate the<br />
     * object with the given Callable. This allows lazy instantiation.<br />
     * If an exception occurs in the lazy instantiantion it returns null.<br />
     * Remember that if using Externalizable transient fields/static scopes<br />
     * fields ARE initalized. The use of the default constructor assures that.<br />
     * The order of inicialization is:<br />
     * Externalizable : default constructor, readExternal<br />
     * Serializable : first non-serializable super class default constructor,<br />
     * readObject<br />
     * So with externalizable you need to be carefull not to use automatically<br />
     * assigned fields of the class in the constructor, that will be read back,<br />
     * and in serializable, replace the constructor.<br />
     */<br />
    public static  T readObject(String objectLocation, Callable t) {<br />
        ObjectInputStream s = null;<br />
        try {<br />
            s = new ObjectInputStream(new BufferedInputStream(new FileInputStream(objectLocation)));<br />
            return (T) s.readObject();<br />
        } catch (Exception ex) {<br />
            try {<br />
                return (T) t.call();<br />
            } catch (Exception e) {<br />
                e.printStackTrace();<br />
            }<br />
        } finally {<br />
            close(s);<br />
        }<br />
        return null;<br />
    }</p>
<p>If you&#8217;d need to reuse the stream you could pass the stream instead and remove the finally to outside and close there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paulo</title>
		<link>http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/comment-page-1/#comment-1406</link>
		<dc:creator>paulo</dc:creator>
		<pubDate>Tue, 13 Nov 2007 21:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/#comment-1406</guid>
		<description>I&#039;m actually glad that swing is not included. Swing component model is great, but it needs an update, such as a real view - model separation and features like css, animation. You know what would be great? If they had included the fuse project in there. Currently its only for swing or swt but as Romain Guy works for google i&#039;m sure that sweet dependency injection framework could be included.</description>
		<content:encoded><![CDATA[<p>I&#8217;m actually glad that swing is not included. Swing component model is great, but it needs an update, such as a real view &#8211; model separation and features like css, animation. You know what would be great? If they had included the fuse project in there. Currently its only for swing or swt but as Romain Guy works for google i&#8217;m sure that sweet dependency injection framework could be included.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Android update: videos, development group, blogs</title>
		<link>http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/comment-page-1/#comment-1385</link>
		<dc:creator>Google Android update: videos, development group, blogs</dc:creator>
		<pubDate>Tue, 13 Nov 2007 13:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/#comment-1385</guid>
		<description>[...] mailroomuk@zdnet.com (Peter Judge) wrote an interesting post today onHere&#8217;s a quick excerptBut it’s interesting to see in the Google Group there’sa lot of “why can’tI develop in X technology with Android, type of threads. Obviously, not everybody is happy with the choice of Java as the development language for this platform. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="mailto:mailroomuk@zdnet.com">mailroomuk@zdnet.com</a> (Peter Judge) wrote an interesting post today onHere&#8217;s a quick excerptBut it’s interesting to see in the Google Group there’sa lot of “why can’tI develop in X technology with Android, type of threads. Obviously, not everybody is happy with the choice of Java as the development language for this platform. &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Android update: videos, development group, blogs &#8212; Google Android</title>
		<link>http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/comment-page-1/#comment-1362</link>
		<dc:creator>Google Android update: videos, development group, blogs &#8212; Google Android</dc:creator>
		<pubDate>Tue, 13 Nov 2007 01:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://sellmic.com/blog/2007/11/12/google-android-update-videos-development-group-blogs/#comment-1362</guid>
		<description>[...] Read the rest of this great post here [...]</description>
		<content:encoded><![CDATA[<p>[...] Read the rest of this great post here [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
