<?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: The results of the first programming competition for Openmoko phones</title>
	<atom:link href="http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/feed/" rel="self" type="application/rss+xml" />
	<link>http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/</link>
	<description>random words..</description>
	<lastBuildDate>Fri, 03 Sep 2010 09:19:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yogiz</title>
		<link>http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/comment-page-1/#comment-502</link>
		<dc:creator>Yogiz</dc:creator>
		<pubDate>Sat, 11 Apr 2009 12:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://risto.kurppa.fi/blog/?p=1607#comment-502</guid>
		<description>The competition was nice but not quite as well thought out as it could have. If I had donated in confundos for it, I would be rather dissapointed right now, as none of the projects are good enough to include to the Freerunner. I&#039;d suggest giving a longer deadline, two or three months, and hold only one competition at any given time. That way the devs could actually churn out polished code instead of how it went now. I&#039;d make the competition last three months and allow anyone to join in at any time, not just at the beginning. Also there should be a threshold for quality or something. If at the end of the deadline none of the projects are good enough, then just extend the deadline or forfeit the prize. Just my $0.02, worth thinking about though.</description>
		<content:encoded><![CDATA[<p>The competition was nice but not quite as well thought out as it could have. If I had donated in confundos for it, I would be rather dissapointed right now, as none of the projects are good enough to include to the Freerunner. I&#8217;d suggest giving a longer deadline, two or three months, and hold only one competition at any given time. That way the devs could actually churn out polished code instead of how it went now. I&#8217;d make the competition last three months and allow anyone to join in at any time, not just at the beginning. Also there should be a threshold for quality or something. If at the end of the deadline none of the projects are good enough, then just extend the deadline or forfeit the prize. Just my $0.02, worth thinking about though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Treviño</title>
		<link>http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/comment-page-1/#comment-501</link>
		<dc:creator>Treviño</dc:creator>
		<pubDate>Fri, 10 Apr 2009 00:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://risto.kurppa.fi/blog/?p=1607#comment-501</guid>
		<description>Hello, I&#039;m Marco Trevisan, one of the people behind the polls...
So, for clarity I&#039;m posting here (a bit late, sorry), my personal evaluations about the three candidate projects:

&lt;blockquote&gt;
&lt;b&gt;Mokotunes&lt;/b&gt;
----------
This can be considered just a little more than a nice mockup just now
since most part of the core functionalities are not implemented yet. By
the way, looking at its code (that mostly presents some skeleton
functions), I can say that is a very well written/structured C++/EFL
project that uses edje for designing the interface while Gstreamer to
play the media (actually impossible due to the missing interface for
retrieving the data, but the code for playing seems to be all there!).
So, also if what I&#039;ve considered is still something of embryonal, the
core that has already written seems so good, and it could be extended to
get something of functional one day.
&gt;From the GUI point of view, imho, it&#039;s hard to do a consideration, since
actually it only shows a kind of &quot;demo&quot; playlist with some buttons for
controlling the media reproduction. However I don&#039;t know how it&#039;s
planned the management of the podcast feeds and of the downloads.
Finally, from a first test in my Freerunner, the interface seems a
little slow. Also if it includes only few elements in its list, the
scrolling is not so smooth (maybe due to the pixmaps used in the
theme!?) so I don&#039;t expect it to be better in a real scenario.

My vote: 3/10.
In few words: Good start, nice code, but too immature into an unlikely
interface.


&lt;b&gt;Gorshplayer&lt;/b&gt;
-----------
It was the only project sent that was working &quot;by default&quot;, and
basically the author added a new podcast media importer feature to the
existent Neoqplayer/Gorshplayer code.
So, with it is possible to add a podcast url, browse its content,
download it and reproducing it from the playlist (as any other media
that is loaded there). This seems to work quite well also if I was able
to get only ogg files working, however the interface imho isn&#039;t so good
for two reasons: first of all it is not so finger usable (yes, the
buttons are big enough, but there&#039;s no finger scrolling, and
double-clicking is hard! Not to mention that the window is too big to be
used with a shelf, so it&#039;s made for working in fullscreen), then to add
a podcast an user should go into preferences, paste an URL, go in the
podcasts list, load a podcast, double-click an item to download, go back
to the main window where he can select the media to reproduce. All this
is quite annoying.
The player is written in C++/Qt and that is a very good choice in
general, but unfortunately not for the openmoko applications yet. In
fact this toolkit doesn&#039;t support by default some finger-friendly
features that could improve a lot the usability, and from the user point
of view, it is not so easy to be installed in the most part of the
distros available natively for the Openmoko devices (also if it works,
I&#039;ve ran it also in Om2008). Of course this is not a developer fault,
and I guess that this player is a very good choice for distros like
debian (when I mean with it something of &quot;non-telephonic&quot;), but I think
that the toolkit choice is what mostly limited my judgment (that is
mostly focused for getting something of working in a touchscreen daily
device).
I hope, however, that it will improve making the podcast reproduction a
little bit more friendly.

My vote: 5.5/10
In few words: Good player, well written, works, but not focused for the
podcast playing, not so finger usable, not yet ready for any
&quot;telephonic&quot; distro (SHR/OM).



&lt;b&gt;NeoReader&lt;/b&gt;
---------
When I received the code it seemed neither compilable for an openmoko
phone (no problems in my PC, instead), however playing a little with the
Toolchain I got an arm binary. Unfortunately everywhere I&#039;d run this
software, it simply crashed when I tried to fetch the podcast media.
So, if I&#039;d judge its basic functionality, I should say that it simply
doesn&#039;t work. However I liked the idea behind the interface, so I fixed
a little the code to get it working...
Looking at it a little more deeply, I found that it has a kind of C++
core that is used for retrieving the data, parsing the XML, saving the
results in a sqlite database (that stores the xml retrieved and
associates to them the downloaded podcasts), and controlling the media
playing the with mplayer.
All this is quite well done, however around this there&#039;s a C/Elmentary
interface that looks quite cool and that is quite well designed, but
that is imho badly written and that doesn&#039;t uses the E-libraries to
perform some basic tasks (like downloading the media). This causes that
the interface is often blocked while the core is performing some task
(like reading from the database or parsing the xml files). The author
said that he wrote the reader in few days so I can understand why there
are so much workarounds around in the code, but I think that they must
be absolutely fixed (with the bugs that they bring).
By the way the potential of this application is good since the it
already allows to listen multiple podcast sources (that can be added
pasting the feed url), saving the selected media in the phone and
allowing to listen it lately. All this is doable using a very well
finger usable interface (thanks to the tools that Elementary gives).
There are is also a nice interface for mplayer, also if it has some
speed issues when NeoReader is used in a real device.
So finally, I&#039;ve decided to give my vote to this application because
also if it has many bugs, the interface must be improved, and the code
cleaned up, it represents imho the best starting point for having a nice
podcast player for Openmoko.
Some features I&#039;d like to see in this software (after getting a stable
version that should use the e libraries facilities for getting the base
task accomplished, of course :P), are a kind of playlist that should
show all the downloaded media (per podcast and general), the ability to
use an plain file to save the podcast addresses (so it will be easy to
share list of podcasts or simply to import them without using the GUI).

My vote: 7/10
In few words: Good backed, nice elementary GUI but badly integrated with
the core, it&#039;s developed for being just a podcast reader and it seems a
good first step.
&lt;/blockquote&gt;

Bye.</description>
		<content:encoded><![CDATA[<p>Hello, I&#8217;m Marco Trevisan, one of the people behind the polls&#8230;<br />
So, for clarity I&#8217;m posting here (a bit late, sorry), my personal evaluations about the three candidate projects:</p>
<blockquote><p>
<b>Mokotunes</b><br />
&#8212;&#8212;&#8212;-<br />
This can be considered just a little more than a nice mockup just now<br />
since most part of the core functionalities are not implemented yet. By<br />
the way, looking at its code (that mostly presents some skeleton<br />
functions), I can say that is a very well written/structured C++/EFL<br />
project that uses edje for designing the interface while Gstreamer to<br />
play the media (actually impossible due to the missing interface for<br />
retrieving the data, but the code for playing seems to be all there!).<br />
So, also if what I&#8217;ve considered is still something of embryonal, the<br />
core that has already written seems so good, and it could be extended to<br />
get something of functional one day.<br />
&gt;From the GUI point of view, imho, it&#8217;s hard to do a consideration, since<br />
actually it only shows a kind of &#8220;demo&#8221; playlist with some buttons for<br />
controlling the media reproduction. However I don&#8217;t know how it&#8217;s<br />
planned the management of the podcast feeds and of the downloads.<br />
Finally, from a first test in my Freerunner, the interface seems a<br />
little slow. Also if it includes only few elements in its list, the<br />
scrolling is not so smooth (maybe due to the pixmaps used in the<br />
theme!?) so I don&#8217;t expect it to be better in a real scenario.</p>
<p>My vote: 3/10.<br />
In few words: Good start, nice code, but too immature into an unlikely<br />
interface.</p>
<p><b>Gorshplayer</b><br />
&#8212;&#8212;&#8212;&#8211;<br />
It was the only project sent that was working &#8220;by default&#8221;, and<br />
basically the author added a new podcast media importer feature to the<br />
existent Neoqplayer/Gorshplayer code.<br />
So, with it is possible to add a podcast url, browse its content,<br />
download it and reproducing it from the playlist (as any other media<br />
that is loaded there). This seems to work quite well also if I was able<br />
to get only ogg files working, however the interface imho isn&#8217;t so good<br />
for two reasons: first of all it is not so finger usable (yes, the<br />
buttons are big enough, but there&#8217;s no finger scrolling, and<br />
double-clicking is hard! Not to mention that the window is too big to be<br />
used with a shelf, so it&#8217;s made for working in fullscreen), then to add<br />
a podcast an user should go into preferences, paste an URL, go in the<br />
podcasts list, load a podcast, double-click an item to download, go back<br />
to the main window where he can select the media to reproduce. All this<br />
is quite annoying.<br />
The player is written in C++/Qt and that is a very good choice in<br />
general, but unfortunately not for the openmoko applications yet. In<br />
fact this toolkit doesn&#8217;t support by default some finger-friendly<br />
features that could improve a lot the usability, and from the user point<br />
of view, it is not so easy to be installed in the most part of the<br />
distros available natively for the Openmoko devices (also if it works,<br />
I&#8217;ve ran it also in Om2008). Of course this is not a developer fault,<br />
and I guess that this player is a very good choice for distros like<br />
debian (when I mean with it something of &#8220;non-telephonic&#8221;), but I think<br />
that the toolkit choice is what mostly limited my judgment (that is<br />
mostly focused for getting something of working in a touchscreen daily<br />
device).<br />
I hope, however, that it will improve making the podcast reproduction a<br />
little bit more friendly.</p>
<p>My vote: 5.5/10<br />
In few words: Good player, well written, works, but not focused for the<br />
podcast playing, not so finger usable, not yet ready for any<br />
&#8220;telephonic&#8221; distro (SHR/OM).</p>
<p><b>NeoReader</b><br />
&#8212;&#8212;&#8212;<br />
When I received the code it seemed neither compilable for an openmoko<br />
phone (no problems in my PC, instead), however playing a little with the<br />
Toolchain I got an arm binary. Unfortunately everywhere I&#8217;d run this<br />
software, it simply crashed when I tried to fetch the podcast media.<br />
So, if I&#8217;d judge its basic functionality, I should say that it simply<br />
doesn&#8217;t work. However I liked the idea behind the interface, so I fixed<br />
a little the code to get it working&#8230;<br />
Looking at it a little more deeply, I found that it has a kind of C++<br />
core that is used for retrieving the data, parsing the XML, saving the<br />
results in a sqlite database (that stores the xml retrieved and<br />
associates to them the downloaded podcasts), and controlling the media<br />
playing the with mplayer.<br />
All this is quite well done, however around this there&#8217;s a C/Elmentary<br />
interface that looks quite cool and that is quite well designed, but<br />
that is imho badly written and that doesn&#8217;t uses the E-libraries to<br />
perform some basic tasks (like downloading the media). This causes that<br />
the interface is often blocked while the core is performing some task<br />
(like reading from the database or parsing the xml files). The author<br />
said that he wrote the reader in few days so I can understand why there<br />
are so much workarounds around in the code, but I think that they must<br />
be absolutely fixed (with the bugs that they bring).<br />
By the way the potential of this application is good since the it<br />
already allows to listen multiple podcast sources (that can be added<br />
pasting the feed url), saving the selected media in the phone and<br />
allowing to listen it lately. All this is doable using a very well<br />
finger usable interface (thanks to the tools that Elementary gives).<br />
There are is also a nice interface for mplayer, also if it has some<br />
speed issues when NeoReader is used in a real device.<br />
So finally, I&#8217;ve decided to give my vote to this application because<br />
also if it has many bugs, the interface must be improved, and the code<br />
cleaned up, it represents imho the best starting point for having a nice<br />
podcast player for Openmoko.<br />
Some features I&#8217;d like to see in this software (after getting a stable<br />
version that should use the e libraries facilities for getting the base<br />
task accomplished, of course :P), are a kind of playlist that should<br />
show all the downloaded media (per podcast and general), the ability to<br />
use an plain file to save the podcast addresses (so it will be easy to<br />
share list of podcasts or simply to import them without using the GUI).</p>
<p>My vote: 7/10<br />
In few words: Good backed, nice elementary GUI but badly integrated with<br />
the core, it&#8217;s developed for being just a podcast reader and it seems a<br />
good first step.
</p></blockquote>
<p>Bye.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wilder</title>
		<link>http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/comment-page-1/#comment-498</link>
		<dc:creator>Wilder</dc:creator>
		<pubDate>Mon, 06 Apr 2009 13:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://risto.kurppa.fi/blog/?p=1607#comment-498</guid>
		<description>Congratulations!</description>
		<content:encoded><![CDATA[<p>Congratulations!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Risto H. Kurppa</title>
		<link>http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/comment-page-1/#comment-497</link>
		<dc:creator>Risto H. Kurppa</dc:creator>
		<pubDate>Mon, 06 Apr 2009 09:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://risto.kurppa.fi/blog/?p=1607#comment-497</guid>
		<description>@nezza: Congrats again :) I added a link to your site in this post, if you start a trac/project site, please let us know.

We were running it on 2008.12, that&#039;s maybe the reason why the I was broken but we weren&#039;t able to make it run on SHR. Anyway, we&#039;re waiting to hear more from you :)</description>
		<content:encoded><![CDATA[<p>@nezza: Congrats again :) I added a link to your site in this post, if you start a trac/project site, please let us know.</p>
<p>We were running it on 2008.12, that&#8217;s maybe the reason why the I was broken but we weren&#8217;t able to make it run on SHR. Anyway, we&#8217;re waiting to hear more from you :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nezza-_-</title>
		<link>http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/comment-page-1/#comment-496</link>
		<dc:creator>nezza-_-</dc:creator>
		<pubDate>Mon, 06 Apr 2009 00:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://risto.kurppa.fi/blog/?p=1607#comment-496</guid>
		<description>Mh, I&#039;m wondering why you don&#039;t have the timeline in NeoReader (http://0x2a-blog.org/files/06042009/3.png).. I will take a look at the whole thing as soon as I find some time to create the project page etc. 

Thanks!

nezza-_-</description>
		<content:encoded><![CDATA[<p>Mh, I&#8217;m wondering why you don&#8217;t have the timeline in NeoReader (<a href="http://0x2a-blog.org/files/06042009/3.png" rel="nofollow">http://0&#215;2a-blog.org/files/06042009/3.png</a>).. I will take a look at the whole thing as soon as I find some time to create the project page etc. </p>
<p>Thanks!</p>
<p>nezza-_-</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Samblas</title>
		<link>http://risto.kurppa.fi/blog/2009/04/1st-om-programming-competition-result/comment-page-1/#comment-495</link>
		<dc:creator>David Samblas</dc:creator>
		<pubDate>Sun, 05 Apr 2009 21:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://risto.kurppa.fi/blog/?p=1607#comment-495</guid>
		<description>:) well I see I have to ship two leather cases , It would be unfair to have a half a case each winner.XD I try to give tree apps a try and make some report :)
Thanks all organizers, bidders and participants to go an step forward of had cool apps in the Neo.</description>
		<content:encoded><![CDATA[<p>:) well I see I have to ship two leather cases , It would be unfair to have a half a case each winner.XD I try to give tree apps a try and make some report :)<br />
Thanks all organizers, bidders and participants to go an step forward of had cool apps in the Neo.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
