<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ubuntu on mariospr.org</title><link>https://mariospr.org/category/ubuntu/</link><description>Recent content in Ubuntu on mariospr.org</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 05 Oct 2016 13:46:49 +0000</lastBuildDate><atom:link href="https://mariospr.org/category/ubuntu/index.xml" rel="self" type="application/rss+xml"/><item><title>Frogr 1.2 released</title><link>https://mariospr.org/2016/10/05/frogr-1-2-released/</link><pubDate>Wed, 05 Oct 2016 13:46:49 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=2237</guid><description>&lt;p&gt;Of course, just a few hours after &lt;a href="https://mariospr.org/2016/10/05/frogr-1-1-released/"&gt;releasing frogr 1.1&lt;/a&gt;, I&amp;rsquo;ve noticed that there was actually no good reason to depend on &lt;em&gt;gettext&lt;/em&gt; 0.19.8 for the purposes of removing the &lt;em&gt;intltool&lt;/em&gt; dependency only, since 0.19.7 would be enough.&lt;/p&gt;
&lt;p&gt;So, as raising that requirement up to 0.19.8 was causing trouble to package frogr for some distros still in 0.19.7 (e.g. &lt;a href="http://packages.ubuntu.com/xenial/gettext"&gt;Ubuntu 16.04 LTS&lt;/a&gt;), I&amp;rsquo;ve decided to do a quick new release and frogr &lt;a href="https://mail.gnome.org/archives/frogr-list/2016-October/msg00001.html"&gt;1.2 is now out with that only change&lt;/a&gt;.&lt;/p&gt;</description><content:encoded><![CDATA[<p>Of course, just a few hours after <a href="/2016/10/05/frogr-1-1-released/">releasing frogr 1.1</a>, I&rsquo;ve noticed that there was actually no good reason to depend on <em>gettext</em> 0.19.8 for the purposes of removing the <em>intltool</em> dependency only, since 0.19.7 would be enough.</p>
<p>So, as raising that requirement up to 0.19.8 was causing trouble to package frogr for some distros still in 0.19.7 (e.g. <a href="http://packages.ubuntu.com/xenial/gettext">Ubuntu 16.04 LTS</a>), I&rsquo;ve decided to do a quick new release and frogr <a href="https://mail.gnome.org/archives/frogr-list/2016-October/msg00001.html">1.2 is now out with that only change</a>.</p>
<p>One direct consequence is that you can now install the <a href="https://launchpad.net/%7Emariospr/+archive/ubuntu/frogr/+packages">packages for Ubuntu from my PPA</a> if you have Ubuntu Xenial 16.04 LTS or newer, instead of having to wait for Ubuntu Yakkety Yak (yet to be released). Other than that 1.2 is <strong>exactly</strong> the same than 1.1, so you probably don&rsquo;t want to package it for your distro if you already did it for 1.1 without trouble. Sorry for the noise.</p>
<p> </p>
]]></content:encoded></item><item><title>Frogr 1.1 released</title><link>https://mariospr.org/2016/10/05/frogr-1-1-released/</link><pubDate>Wed, 05 Oct 2016 01:24:36 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=2225</guid><description>&lt;p&gt;After almost one year, I&amp;rsquo;ve finally &lt;a href="https://mail.gnome.org/archives/frogr-list/2016-October/msg00000.html"&gt;released another small iteration of frogr&lt;/a&gt; with a few updates and improvements.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://mariospr.org/wp-content/uploads/2016/10/20161005-frogr-screenshot.png"&gt;&lt;img class="aligncenter size-large wp-image-2226" src="https://mariospr.org/wp-content/uploads/2016/10/20161005-frogr-screenshot-600x338.png" alt="Screenshot of frogr 1.1" width="474" height="267" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Not many things, to be honest, bust just a few as I said:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Added support for &lt;a href="http://flatpak.org/"&gt;flatpak&lt;/a&gt;&lt;/strong&gt;: it's now possible to authenticate frogr from inside the sandbox, as well as open pictures/videos in the appropriate viewer, thanks to the &lt;em&gt;OpenURI&lt;/em&gt; &lt;a href="https://github.com/flatpak/flatpak/wiki/Portals"&gt;portal&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Updated translations&lt;/strong&gt;: as it was noted in the past when I released 1.0, several translations were left out incomplete back then. Hopefully the new version will be &lt;a href="https://l10n.gnome.org/module/frogr/"&gt;much better&lt;/a&gt; in that regard.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dropped&lt;/strong&gt; the build dependency on &lt;strong&gt;&lt;em&gt;intltool&lt;/em&gt;&lt;/strong&gt; (requires &lt;em&gt;gettext&lt;/em&gt; &amp;gt;= 0.19.8).&lt;/li&gt;
&lt;li&gt;A few &lt;strong&gt;bugfixes&lt;/strong&gt; too and other maintenance tasks, as usual.&lt;/li&gt;
&lt;/ul&gt;
Besides, another significant difference compared to previous releases is related to the way I'm &lt;strong&gt;distributing&lt;/strong&gt; it: in the past, if you used &lt;a href="http://www.ubuntu.com/"&gt;Ubuntu&lt;/a&gt;, you could configure &lt;a href="https://launchpad.net/~mariospr/+archive/ubuntu/frogr/+packages"&gt;my PPA&lt;/a&gt; and install it from there even in fairly old versions of the distro. However, this time that's only possible if you have Ubuntu 16.10 &lt;em&gt;"Yakkety Yak"&lt;/em&gt;, as that's the one that ships g&lt;em&gt;ettext&lt;/em&gt; &amp;gt;= 0.19.8, which is required now that I removed all trace of intltool (more info in &lt;a href="https://blogs.gnome.org/mclasen/2016/07/21/using-modern-gettext/"&gt;this post&lt;/a&gt;).
&lt;p&gt;However, this is also the first time I&amp;rsquo;m using &lt;a href="http://flatpak.org/"&gt;flatpak&lt;/a&gt; to distribute frogr so, regardless of which distribution you have, you can now install and run it as long as you have the &lt;a class="http" href="http://flatpak.org/runtimes.html"&gt;org.gnome.Platform/x86_64/3.22 stable runtime &lt;/a&gt;installed locally. Not too bad! :-). See more &lt;a href="https://wiki.gnome.org/Apps/Frogr#Flatpak"&gt;detailed instructions in its web site&lt;/a&gt;.&lt;/p&gt;</description><content:encoded><![CDATA[<p>After almost one year, I&rsquo;ve finally <a href="https://mail.gnome.org/archives/frogr-list/2016-October/msg00000.html">released another small iteration of frogr</a> with a few updates and improvements.</p>
<p><a href="/wp-content/uploads/2016/10/20161005-frogr-screenshot.png"><img class="aligncenter size-large wp-image-2226" src="/wp-content/uploads/2016/10/20161005-frogr-screenshot-600x338.png" alt="Screenshot of frogr 1.1" width="474" height="267" /></a></p>
<p>Not many things, to be honest, bust just a few as I said:</p>
<ul>
 	<li><strong>Added support for <a href="http://flatpak.org/">flatpak</a></strong>: it's now possible to authenticate frogr from inside the sandbox, as well as open pictures/videos in the appropriate viewer, thanks to the <em>OpenURI</em> <a href="https://github.com/flatpak/flatpak/wiki/Portals">portal</a>.</li>
 	<li><strong>Updated translations</strong>: as it was noted in the past when I released 1.0, several translations were left out incomplete back then. Hopefully the new version will be <a href="https://l10n.gnome.org/module/frogr/">much better</a> in that regard.</li>
 	<li><strong>Dropped</strong> the build dependency on <strong><em>intltool</em></strong> (requires <em>gettext</em> &gt;= 0.19.8).</li>
 	<li>A few <strong>bugfixes</strong> too and other maintenance tasks, as usual.</li>
</ul>
Besides, another significant difference compared to previous releases is related to the way I'm <strong>distributing</strong> it: in the past, if you used <a href="http://www.ubuntu.com/">Ubuntu</a>, you could configure <a href="https://launchpad.net/~mariospr/+archive/ubuntu/frogr/+packages">my PPA</a> and install it from there even in fairly old versions of the distro. However, this time that's only possible if you have Ubuntu 16.10 <em>"Yakkety Yak"</em>, as that's the one that ships g<em>ettext</em> &gt;= 0.19.8, which is required now that I removed all trace of intltool (more info in <a href="https://blogs.gnome.org/mclasen/2016/07/21/using-modern-gettext/">this post</a>).
<p>However, this is also the first time I&rsquo;m using <a href="http://flatpak.org/">flatpak</a> to distribute frogr so, regardless of which distribution you have, you can now install and run it as long as you have the <a class="http" href="http://flatpak.org/runtimes.html">org.gnome.Platform/x86_64/3.22 stable runtime </a>installed locally. Not too bad! :-). See more <a href="https://wiki.gnome.org/Apps/Frogr#Flatpak">detailed instructions in its web site</a>.</p>
<p>That said, it&rsquo;s <em>interesting</em> that you also have the <a href="https://github.com/flatpak/xdg-desktop-portal">portal frontend service</a> and a <a href="http://flatpak.org/runtimes.html">backend implementation</a>, so that you can authorize your flickr account using the browser outside the sandbox, via the <em>OpenURI</em> <a href="https://github.com/flatpak/flatpak/wiki/Portals">portal</a>. If you don&rsquo;t have that at hand, you can still used the sandboxed version of frogr, but you&rsquo;d need to copy your configuration files from a non-sandboxed frogr (under <em><del>/.config/frogr</em>) first, right into <em></del>/.var/app/org.gnome.Frogr/config</em>, and then it should be usable again (opening files in external viewers would not work yet, though!).</p>
<p>So this is all, hope it works well and it&rsquo;s helpful to you. I&rsquo;ve just finished uploading a few hundreds of pictures a couple of days ago and it seemed to work fine, but you never know&hellip; <em>devil is in the detail</em>!</p>
<p> </p>
]]></content:encoded></item><item><title>Frogr 1.0 released</title><link>https://mariospr.org/2015/12/30/frogr-1-0-released/</link><pubDate>Wed, 30 Dec 2015 06:04:21 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=2112</guid><description>&lt;p&gt;I&amp;rsquo;ve just &lt;a href="https://mail.gnome.org/archives/frogr-list/2015-December/msg00000.html"&gt;released frogr 1.0&lt;/a&gt;. I can&amp;rsquo;t believe it took me 6 years to move from the 0.x series to the 1.0 release, but here it is finally. For good or bad.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://mariospr.org/wp-content/uploads/2015/12/20151230-frogr-screenshot.png"&gt;&lt;img class="aligncenter size-large wp-image-2113" src="https://mariospr.org/wp-content/uploads/2015/12/20151230-frogr-screenshot-600x338.png" alt="Screenshot of frogr 1.0" width="584" height="329" /&gt;&lt;/a&gt;This release is again a small increment on top of the previous one that fixes a few bugs, should make the UI look a bit more consistent and &amp;ldquo;modern&amp;rdquo;, and includes some cleanups at the code level that I&amp;rsquo;ve been wanting to do for some time, like using &lt;a href="https://developer.gnome.org/gobject/unstable/gobject-Type-Information.html#G-DECLARE-FINAL-TYPE:CAPS"&gt;G_DECLARE_FINAL_TYPE&lt;/a&gt;, which helped me get rid of ~1.7K LoC.&lt;/p&gt;</description><content:encoded><![CDATA[<p>I&rsquo;ve just <a href="https://mail.gnome.org/archives/frogr-list/2015-December/msg00000.html">released frogr 1.0</a>. I can&rsquo;t believe it took me 6 years to move from the 0.x series to the 1.0 release, but here it is finally. For good or bad.</p>
<p><a href="/wp-content/uploads/2015/12/20151230-frogr-screenshot.png"><img class="aligncenter size-large wp-image-2113" src="/wp-content/uploads/2015/12/20151230-frogr-screenshot-600x338.png" alt="Screenshot of frogr 1.0" width="584" height="329" /></a>This release is again a small increment on top of the previous one that fixes a few bugs, should make the UI look a bit more consistent and &ldquo;modern&rdquo;, and includes some cleanups at the code level that I&rsquo;ve been wanting to do for some time, like using <a href="https://developer.gnome.org/gobject/unstable/gobject-Type-Information.html#G-DECLARE-FINAL-TYPE:CAPS">G_DECLARE_FINAL_TYPE</a>, which helped me get rid of ~1.7K LoC.</p>
<p>Last, I&rsquo;ve created a few <a href="https://launchpad.net/~mariospr/+archive/ubuntu/frogr/+packages">packages for Ubuntu in my PPA</a> that you can use now already if you&rsquo;re in Vivid or later while it does not get packaged by the distro itself, although I&rsquo;d expect it to be eventually <a href="https://wiki.gnome.org/Apps/Frogr#Binary_packages">available via the usual means in different distros</a>, hopefully soon. For extra information, just take a look to <a href="https://wiki.gnome.org/Apps/Frogr#Binary_packages">frogr&rsquo;s website at live.gnome.org</a>.</p>
<p>Now remember to take lots of pictures so that you can upload them with <a href="https://wiki.gnome.org/Apps/Frogr">frogr</a> :)</p>
<p>Happy new year!</p>
]]></content:encoded></item><item><title>Frogr 0.11 released</title><link>https://mariospr.org/2015/01/08/frogr-0-11-released/</link><pubDate>Thu, 08 Jan 2015 04:09:49 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=1782</guid><description>&lt;p style="text-align: center;"&gt;&lt;a href="https://mariospr.org/wp-content/uploads/2015/01/20150107-frogr-screenshot.png"&gt;&lt;img class="size-full wp-image-1784 aligncenter" alt="Screenshot of Frogr 0.11" src="https://mariospr.org/wp-content/uploads/2015/01/20150107-frogr-screenshot-thumb.png" width="520" height="325" /&gt;&lt;/a&gt;&lt;/p&gt;
So, after neglecting my responsibilities with this project for way too long, I finally &lt;a title="Announcement email" href="https://mail.gnome.org/archives/frogr-list/2015-January/msg00000.html"&gt;released frogr 0.11 now&lt;/a&gt;, making the most that I'm now enjoying some kind of "parenting vacation" for a few days.
&lt;p&gt;Still, do not expect this new release to be fully loaded of new features and vast improvements, as it&amp;rsquo;s more like another incremental update that adds a couple of nice new things and fixes a bunch of problems I was really unhappy about (e.g. general slowness, crashes).&lt;/p&gt;</description><content:encoded><![CDATA[<p style="text-align: center;"><a href="/wp-content/uploads/2015/01/20150107-frogr-screenshot.png"><img class="size-full wp-image-1784 aligncenter" alt="Screenshot of Frogr 0.11" src="/wp-content/uploads/2015/01/20150107-frogr-screenshot-thumb.png" width="520" height="325" /></a></p>
So, after neglecting my responsibilities with this project for way too long, I finally <a title="Announcement email" href="https://mail.gnome.org/archives/frogr-list/2015-January/msg00000.html">released frogr 0.11 now</a>, making the most that I'm now enjoying some kind of "parenting vacation" for a few days.
<p>Still, do not expect this new release to be fully loaded of new features and vast improvements, as it&rsquo;s more like another incremental update that adds a couple of nice new things and fixes a bunch of problems I was really unhappy about (e.g. general slowness, crashes).</p>
<p>Wrapping it up, the main changes included with this release are:</p>
<ul>
	<li>Moved to the new GTK+'s header bar plus the typical <em>menu button</em> when GTK+ &gt;= 3.12 (GTK+ 3.4 is still supported). I personally like this change a lot, as it makes frogr much more compact and sleek IMHO, and much better integrated with newer releases of <a title="The GNOME project" href="http://www.gnome.org">GNOME</a>.</li>
	<li>Added a new option to automatically replace the "date posted" field in flickr with the "date taken" value from the EXIF metadata when uploading pictures. Useful to keep your photo stream sorted regardless of when you uploaded which pictures. Thanks a lot to <a title="Luc Pionchon's blog" href="http://oluc.blogspot.co.uk/">Luc Pionchon</a> for <a title="Bug 734193 - on upload, set 'upload date' to 'taken date' " href="https://bugzilla.gnome.org/show_bug.cgi?id=734193">requesting this feature</a>. I never thought of it before, now I use it all the time!</li>
	<li>Sped up the load of pictures into the main window, as it was a very slow process when importing tags from the XMP keywords was enabled. I measured a 3x improvement, but <em>YMMV</em>.</li>
	<li>Fixed random crashes due to the missing initialization of the gcrypt library introduced with the recent changes to use SSL API end points. Thanks a lot <a title="Andres's blog" href="http://blog.andresgomez.org/">Andrés</a> for your help with this!</li>
	<li>Fixed issues related to the OS X port, which prevented frogr 0.9 from having video support and caused many problems with the 0.10 release. Now it should be fine, <a title="OS X port of frogr" href="http://ftp.acc.umu.se/pub/gnome/binaries/mac/frogr">grab the bundle from here</a>.</li>
	<li>Other things: removed calls to deprecated APIs, updated translations, fixed a few minor bugs and a bit of a clean-up here and there, which is usually good.</li>
</ul>
As usual, feel free to check <a title="Frogr's website" href="https://wiki.gnome.org/Apps/Frogr">the website of the project</a> in case you want to know more about <a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr">frogr</a>, <a title="Get frogr" href="https://wiki.gnome.org/Apps/Frogr#Get_Frogr">how to get it</a> or how to contribute to it. I'm having a hard time lately to find time to devote to this pet project, so any help anyone can provide will be more than welcome :-) <a href="http://www.fosdem.org"><img class="size-full wp-image-1802 alignright" alt="fosdem-15-logo" src="/wp-content/uploads/2015/01/fosdem-15-logo.png" width="163" height="29" /></a>
<p>By the way, I&rsquo;m going to <a href="http://www.fosdem.org">FOSDEM</a> this year again, so feel free to say &ldquo;hi&rdquo; if you want to chat and/or share a beer (or more!).</p>
]]></content:encoded></item><item><title>Frogr 0.10 released</title><link>https://mariospr.org/2014/06/17/frogr-0-10-released/</link><pubDate>Tue, 17 Jun 2014 03:44:27 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=1722</guid><description>&lt;p&gt;&lt;a href="https://mariospr.org/2014/06/17/frogr-0-10-released/frogr/" rel="attachment wp-att-1723"&gt;&lt;img class="alignright size-full wp-image-1723" alt="frogr" src="https://mariospr.org/wp-content/uploads/2014/06/frogr.png" width="128" height="128" /&gt;&lt;/a&gt;Quick post to let the world know that I&amp;rsquo;ve &lt;a title="Announcement email" href="https://mail.gnome.org/archives/frogr-list/2014-June/msg00000.html"&gt;just released a new version of frogr right now&lt;/a&gt;, in order to address a few issues present in the previous version. Mainly:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Deprecation of non-SSL end points for the &lt;a title="Flickr API" href="https://www.flickr.com/services/developer/api/"&gt;Flickr API&lt;/a&gt; (see these &lt;a title="New SSL Endpoints for the Flickr API" href="http://code.flickr.net/2014/02/24/new-ssl-endpoints-for-the-flickr-api/"&gt;two&lt;/a&gt; &lt;a title="Flickr API Going SSL-Only on June 27th, 2014" href="http://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-27th-2014/"&gt;posts&lt;/a&gt; for more info). From now on, &lt;a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr"&gt;frogr&lt;/a&gt; will use SSL-only API calls.&lt;/li&gt;
&lt;li&gt;Address issues with &lt;a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr"&gt;frogr&lt;/a&gt;'s &lt;a title="AppData specification" href="http://people.freedesktop.org/~hughsient/appdata/"&gt;AppData&lt;/a&gt; file. Apparently, the AppData file was neither valid (according to &lt;a title="AppData validation tools" href="https://github.com/hughsie/appdata-tools"&gt;&lt;em&gt;appdata-validate&lt;/em&gt;&lt;/a&gt;) nor being installed properly, preventing &lt;a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr"&gt;frogr&lt;/a&gt; from showing up nicely in the &lt;a title="GNOME Software" href="https://wiki.gnome.org/Apps/Software"&gt;GNOME Software app&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Allow disabling video uploads at configuration time (enabled by default), instead of making the decision depending on the detected platform. This will hopefully make life easier for packagers of other platforms (e.g. &lt;a title="MacPorts" href="http://www.macports.org/"&gt;MacPorts&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;Removed &lt;a title="libsoup" href="https://wiki.gnome.org/action/show/Projects/libsoup"&gt;libsoup-gnome&lt;/a&gt; code once and for all (API deprecated a while ago).&lt;/li&gt;
&lt;li&gt;Other things: updated translations and fixed a few minor bugs.&lt;/li&gt;
&lt;/ul&gt;
As usual, feel free to check &lt;a title="Frogr's website" href="https://wiki.gnome.org/Apps/Frogr"&gt;the website of the project&lt;/a&gt; in case you want to know more about &lt;a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr"&gt;frogr&lt;/a&gt;, &lt;a title="Get frogr" href="https://wiki.gnome.org/Apps/Frogr#Get_Frogr"&gt;how to get it&lt;/a&gt; or how to contribute to it.</description><content:encoded><![CDATA[<p><a href="/2014/06/17/frogr-0-10-released/frogr/" rel="attachment wp-att-1723"><img class="alignright size-full wp-image-1723" alt="frogr" src="/wp-content/uploads/2014/06/frogr.png" width="128" height="128" /></a>Quick post to let the world know that I&rsquo;ve <a title="Announcement email" href="https://mail.gnome.org/archives/frogr-list/2014-June/msg00000.html">just released a new version of frogr right now</a>, in order to address a few issues present in the previous version. Mainly:</p>
<ul>
	<li>Deprecation of non-SSL end points for the <a title="Flickr API" href="https://www.flickr.com/services/developer/api/">Flickr API</a> (see these <a title="New SSL Endpoints for the Flickr API" href="http://code.flickr.net/2014/02/24/new-ssl-endpoints-for-the-flickr-api/">two</a> <a title="Flickr API Going SSL-Only on June 27th, 2014" href="http://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-27th-2014/">posts</a> for more info). From now on, <a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr">frogr</a> will use SSL-only API calls.</li>
	<li>Address issues with <a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr">frogr</a>'s <a title="AppData specification" href="http://people.freedesktop.org/~hughsient/appdata/">AppData</a> file. Apparently, the AppData file was neither valid (according to <a title="AppData validation tools" href="https://github.com/hughsie/appdata-tools"><em>appdata-validate</em></a>) nor being installed properly, preventing <a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr">frogr</a> from showing up nicely in the <a title="GNOME Software" href="https://wiki.gnome.org/Apps/Software">GNOME Software app</a>.</li>
	<li>Allow disabling video uploads at configuration time (enabled by default), instead of making the decision depending on the detected platform. This will hopefully make life easier for packagers of other platforms (e.g. <a title="MacPorts" href="http://www.macports.org/">MacPorts</a>).</li>
	<li>Removed <a title="libsoup" href="https://wiki.gnome.org/action/show/Projects/libsoup">libsoup-gnome</a> code once and for all (API deprecated a while ago).</li>
	<li>Other things: updated translations and fixed a few minor bugs.</li>
</ul>
As usual, feel free to check <a title="Frogr's website" href="https://wiki.gnome.org/Apps/Frogr">the website of the project</a> in case you want to know more about <a title="Frogr" href="https://wiki.gnome.org/Apps/Frogr">frogr</a>, <a title="Get frogr" href="https://wiki.gnome.org/Apps/Frogr#Get_Frogr">how to get it</a> or how to contribute to it.
]]></content:encoded></item><item><title>Frogr 0.8 released</title><link>https://mariospr.org/2012/12/29/frogr-0-8-released/</link><pubDate>Sat, 29 Dec 2012 20:15:49 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=1239</guid><description>&lt;p&gt;During the last weeks, I decided to make the most of some spare time I had while still in &amp;ldquo;nowhere land&amp;rdquo; (see &lt;a title="Moving On" href="https://mariospr.org/2012/11/19/moving-on/"&gt;my previous post&lt;/a&gt;) and so I&amp;rsquo;ve been working in &lt;a title="frogr website" href="https://live.gnome.org/Frogr"&gt;frogr&lt;/a&gt; to see if I could release the 0.8 version before the end of the year. In my mind it looked like kind of a nice and humble Christmas present to the world and, at the same time, a interesting way to spent this time I had between my depart from &lt;a title="Igalia" href="http://www.igalia.com"&gt;my previous job&lt;/a&gt; and the start of the new one.&lt;/p&gt;</description><content:encoded><![CDATA[<p>During the last weeks, I decided to make the most of some spare time I had while still in &ldquo;nowhere land&rdquo; (see <a title="Moving On" href="/2012/11/19/moving-on/">my previous post</a>) and so I&rsquo;ve been working in <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> to see if I could release the 0.8 version before the end of the year. In my mind it looked like kind of a nice and humble Christmas present to the world and, at the same time, a interesting way to spent this time I had between my depart from <a title="Igalia" href="http://www.igalia.com">my previous job</a> and the start of the new one.</p>
<p>And it turns out that, at the end, I didn&rsquo;t manage to have as much spare time as I initially expected to have (I was pretty busy most of the time, actually), mainly due to many unrelated things I needed also to take care of, but in the end I still managed to steal some minutes here and there and I&rsquo;m now proudly announcing that <a title="Announcement mail for frogr 0.8" href="https://mail.gnome.org/archives/frogr-list/2012-December/msg00002.html">the new release is finally out</a>.</p>
<p>But before going on, see the mandatory screenshot, as taken in my <a title="Fedora project" href="http://fedoraproject.org/">Fedora</a> 18 machine:
<a href="/2012/12/29/frogr-0-8-released/20121226-frogr-screenshot-2/" rel="attachment wp-att-1257"><img class="aligncenter size-large wp-image-1257" title="Frogr 0.8" src="/wp-content/uploads/2012/12/20121226-frogr-screenshot1-600x375.png" alt="" width="584" height="365" /></a></p>
<p>As you can already spot in the screenshot, some changes are already quite visible, but some others are not, so let&rsquo;s now comment on the most important ones, one by one&hellip;</p>
<h3>Ported to GtkApplication and GMenu</h3>
<a href="/2012/12/29/frogr-0-8-released/20121226-frogr-menus/" rel="attachment wp-att-1261"><img class="aligncenter size-large wp-image-1261" title="Frogr 0.8: Ported to GMenu" src="/wp-content/uploads/2012/12/20121226-frogr-menus-600x145.png" alt="" width="584" height="141" /></a>
<p>It&rsquo;s no secret that one of my favourite changes in this release is the integration with <a title="GNOME 3" href="http://www.gnome.org/gnome-3/">GNOME 3</a>&rsquo;s &ldquo;global menu&rdquo; (aka the <em>application menu</em>), which makes <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> more beatifully integrated with the desktop than ever. However that came with a price: I needed to port <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> to <a title="GtkApplication" href="http://developer.gnome.org/gtk3/3.4/GtkApplication.html">GtkApplication</a> first and then implement both the application menu and the menu bar using <a title="GMenu" href="http://developer.gnome.org/gio/2.32/GMenu.html">GMenu</a>, which also made me raise the required version for <a title="GTK+" href="http://www.gtk.org">GTK+</a> up to 3.4.</p>
<p>Sure I could have kept adding more <em>ifdefs</em> to the code to keep supporting previous <a title="GTK+" href="http://www.gtk.org">GTK+</a> versions, but I also saw this as a good opportunity to clean up the code and get rid of so many conditional compilation units that were increasingly harder to maintain, and so I did it. As a plus, the <a title="OS X" href="http://en.wikipedia.org/wiki/OS_X">OS X</a> specific code has been reduced enormously as well, since <a title="GTK+" href="http://www.gtk.org">GTK+</a> 3.4 integrates very well with <a title="OS X" href="http://en.wikipedia.org/wiki/OS_X">OS X</a> without having to do anything special, as I needed to do when I used <a title="GTK+" href="http://www.gtk.org">GTK+</a> 2.24 for that port.</p>
<h3>Loading and saving 'projects'</h3>
<a href="/2012/12/29/frogr-0-8-released/20121226-frogr-projects/" rel="attachment wp-att-1262"><img class="aligncenter size-large wp-image-1262" title="Frogr 0.8: Support for projects" src="/wp-content/uploads/2012/12/20121226-frogr-projects-600x145.png" alt="" width="584" height="141" /></a>
<p>This has been one of the features that several people have suggested in the past in different occasions, and so one of those I hope people will enjoy the most with this new release: the possibility to save the current session into a &ldquo;project file&rdquo;, so you can resume your work later.</p>
<p>How it works it&rsquo;s actually pretty simple: when you save a session to a project, <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> will just serialize your current pictures, sets, groups and local tags to a json file (using <a title="json-glib" href="https://live.gnome.org/JsonGlib/"><em>json-glib</em></a>) that you can use to restore the state later. It could be more sophisticated, but I think that it works reasonably well in the tests I did considering what it was designed for. In any case, please feel free to report bugs or feature requests to improve or fix things if needed.</p>
<h3>Support for video uploads</h3>
<a href="/2012/12/29/frogr-0-8-released/20121226-frogr-videos/" rel="attachment wp-att-1263"><img class="aligncenter size-large wp-image-1263" title="Frogr 0.8: support for video uploads" src="/wp-content/uploads/2012/12/20121226-frogr-videos-600x145.png" alt="" width="584" height="141" /></a>
<p>Believe it or not, <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> has been <em>almost</em> ready to upload videos since some time ago, since for <a title="Flickr" href="http://www.flickr.com">Flickr</a> a video is just a &ldquo;moving picture&rdquo;, and it&rsquo;s <a title="Videos in the flickr API" href="http://code.flickr.net/2008/05/01/videos-in-the-flickr-api/">treated in exactly the same way than pictures</a> when it comes to the <a title="Flickr's upload API" href="http://www.flickr.com/services/api/upload.api.html">upload API</a>.</p>
<p>The only thing that was missing to remove that <em>almost</em> from here was to generate thumbnails for videos so they could get loaded into the UI. Not rocket science, sure, but something which needed doing and which was not a priority at all until now. And to be honest, it is not a priority yet anyway, but I felt like doing it this time once and for all, so from now on you can upload videos too.</p>
<h3>Other features &amp; bug fixes</h3>
Besides those three and perhaps more noticeable features, <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> 0.8 comes with several other new things, bug fixes, small changes and refinement that I hope will make this release more stable, useful and fun to use than ever.
<p><a href="/2012/12/29/frogr-0-8-released/20121226-frogr-maximized/" rel="attachment wp-att-1264"><img class="aligncenter size-large wp-image-1264" title="Frogr 0.8: hide title bar when maximized" src="/wp-content/uploads/2012/12/20121226-frogr-maximized-600x145.png" alt="" width="584" height="141" /></a></p>
<p>Some examples of those other new things are, as taken from <a title="Frogr's NEWS file" href="http://git.gnome.org/browse/frogr/plain/NEWS">the NEWS file</a>:</p>
<ul>
	<li>Handle and report errors in a better way (no more mysterious failures).</li>
	<li>Perform after-upload operations (add to sets/groups, set license...) in parallel.</li>
	<li>Avoid fetching sets/groups/tags when still not connected yet to <a title="Flickr" href="http://www.flickr.com">Flickr</a>.</li>
	<li>Hide title bar when main window is maximized (see screenshot above).</li>
	<li>Renamed the 'Actions' menu to 'Edit' and brought the 'File' menu back.</li>
	<li>Allow sorting elements in the icon view by size.</li>
</ul>
Last, I'm also quite happy to tell that the <a title="OS X" href="http://en.wikipedia.org/wiki/OS_X">OS X</a> port of <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> has been finally migrated to <a title="GTK+" href="http://www.gtk.org">GTK+</a> 3 in this release (at last!), <strong>and</strong> that the whole process of building it for that platform is now easier than ever, thanks to a specific <a title="Jhbuild" href="https://live.gnome.org/Jhbuild">Jhbuild</a> <a title="Frogr's moduleset for OS X" href="http://git.gnome.org/browse/frogr/plain/osx/jhbuild/frogr.modules">moduleset I created for that purpose</a>, following <a title="GEdit's moduleset for OS X" href="http://git.gnome.org/browse/gedit/plain/osx/jhbuild/gedit.modules">the lead of GEdit</a> (thanks <a title="Nacho's blog" href="http://blogs.gnome.org/nacho/">Nacho</a> for the suggestion).
<p>Check out the <a title="README file to build frogr for OS X" href="http://git.gnome.org/browse/frogr/plain/osx/README">README</a> file in the <a title="osx/ directory" href="http://git.gnome.org/browse/frogr/tree/osx">osx/ directory</a> if you feel curious about the process or if you want to build it yourself. It shouldn&rsquo;t take more than 2-3 commands in the terminal to get something like this running in your <a title="OS X" href="http://en.wikipedia.org/wiki/OS_X">OS X</a> machine:</p>
<p><a href="/2012/12/29/frogr-0-8-released/20121226-frogr-screenshot-osx/" rel="attachment wp-att-1255"><img class="aligncenter size-large wp-image-1255" title="Frogr 0.8 for Mac OS X" src="/wp-content/uploads/2012/12/20121226-frogr-screenshot-osx-600x375.png" alt="" width="584" height="365" /></a></p>
<p>Also, another advantage of having that moduleset created, is that now it&rsquo;s trivial to properly document (by means of <a title="generate-SOURCES script" href="http://git.gnome.org/browse/frogr/plain/osx/generate-SOURCES">a shell script</a>) the bundle file used to distribute <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> in <a title="OS X" href="http://en.wikipedia.org/wiki/OS_X">OS X</a>, instead of just providing an &ldquo;opaque&rdquo; pre-compiled bundle, as I used to do in an &ldquo;unofficial way&rdquo; with previous versions. Feel free to <strong>grab the bundle</strong> I&rsquo;ve just created for this release <a title="Frogr 0.8 for Mac OS X" href="http://ftp.gnome.org/pub/gnome/binaries/mac/frogr/0.8/">from the GNOME FTP server</a>.</p>
<p>So that&rsquo;s it. I hope you enjoy using <a title="frogr website" href="https://live.gnome.org/Frogr">frogr</a> 0.8 as much as I did writing it, and if you eventually find it useful too, then even better! As usual, check <a title="Frogr's website" href="https://live.gnome.org/Frogr">the website of the project</a> for additional information or just to know <a title="Get frogr" href="https://live.gnome.org/Frogr#Get_Frogr">how to install frogr on your system</a>.</p>
]]></content:encoded></item><item><title>Frogr 0.7 released</title><link>https://mariospr.org/2012/05/23/frogr-0-7-released/</link><pubDate>Wed, 23 May 2012 19:08:34 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=742</guid><description>&lt;p&gt;As you might already know &lt;a title="Flickr now Supports OAuth 1.0a" href="http://code.flickr.com/blog/2011/06/21/flickr-now-supports-oauth-1-0a/"&gt;Flickr has added support for OAuth a while ago&lt;/a&gt;, which is meant to be the obvious replacement to the &lt;a title="The old Flickr auth API" href="http://www.flickr.com/services/api/misc.userauth.html"&gt;old Flickr auth API&lt;/a&gt; that has been available since a long long time ago, which has been used by many applications our there, like &lt;a title="Frogr" href="https://live.gnome.org/Frogr"&gt;frogr&lt;/a&gt;. But the important point here for apps using the old auth method is that &lt;a title="Farewell FlickrAuth" href="http://code.flickr.com/blog/2012/01/13/farewell-flickrauth"&gt;it won&amp;rsquo;t be longer available after July 31st&lt;/a&gt;, which means they should get updated if they want to keep working as so far.&lt;/p&gt;</description><content:encoded><![CDATA[<p>As you might already know <a title="Flickr now Supports OAuth 1.0a" href="http://code.flickr.com/blog/2011/06/21/flickr-now-supports-oauth-1-0a/">Flickr has added support for OAuth a while ago</a>, which is meant to be the obvious replacement to the <a title="The old Flickr auth API" href="http://www.flickr.com/services/api/misc.userauth.html">old Flickr auth API</a> that has been available since a long long time ago, which has been used by many applications our there, like <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a>. But the important point here for apps using the old auth method is that <a title="Farewell FlickrAuth" href="http://code.flickr.com/blog/2012/01/13/farewell-flickrauth">it won&rsquo;t be longer available after July 31st</a>, which means they should get updated if they want to keep working as so far.</p>
<p><a href="/wp-content/uploads/2012/05/20120523-frogr-screenshot.png"><img class="aligncenter" src="/wp-content/uploads/2012/05/20120523-frogr-screenshot-thumb.png" alt="Frogr 0.7" width="520" height="325" /></a></p>
<p>So, this is the <strong>main point of this release</strong>: to update the internal implementation of the <a title="Flickr REST API" href="http://www.flickr.com/services/api/">Flickr REST API</a> in <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a> (which, ideally, will be released independently as a library at some point) to use <a title="OAuth documentation" href="http://oauth.net/">OAuth</a> instead of the old authentication API.</p>
<p>Additionally, in order to make things easier for users of older versions, the application will take care of exchanging the authentication token from the old system to the new ones used by the <a title="OAuth documentation" href="http://oauth.net/">OAuth</a> API. If you want to know more details about this, check <a title="flickr.auth.oauth.getAccessToken" href="http://www.flickr.com/services/api/flickr.auth.oauth.getAccessToken.html">the related API</a>. For the rest of you, you shouldn&rsquo;t notice anything the first time you run this new release.</p>
<p>Still, some other things were included in this new release that are worth mentioning:</p>
<ul>
	<li>Ability to import tags already present in pictures  (e.g. as set by f-spot or shotwell).</li>
	<li>Allow users deciding, right from <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a> and on a picture-by-picture basis, whether to set the geolocation information for pictures when uploading them to <a title="Flickr" href="http://www.flickr.com">Flickr</a>.</li>
	<li>New tags are added to the auto-completion without having to upload anything first.</li>
	<li>Allow using a dark version of your theme if available (e.g. Adwaita).</li>
	<li>Some redesign of the menu bar, thinking of a future migration to <a title="GMenu API documentation" href="http://developer.gnome.org/gio/stable/GMenu.html">GMenu</a>.</li>
	<li>Added menu accelerators for the most common operations.</li>
	<li>As usual, bugfixes, cleanups... that kind of stuff.</li>
</ul>
Also, you can check the <a title="Frogr 0.7 announcement mail" href="https://mail.gnome.org/archives/gnome-announce-list/2012-May/msg00023.html">announcement mail</a> or the <a title="Frogr's NEWS file" href="http://git.gnome.org/browse/frogr/tree/NEWS">NEWS file</a> if you want for more detail about this new release, as well as <a title="Frogr's website" href="https://live.gnome.org/Frogr">the website of the project</a> for additional information, such as knowing about <a title="Get involved in frogr" href="https://live.gnome.org/Frogr#Get_Involved">ways of collaborating</a> or <a title="Get frogr" href="https://live.gnome.org/Frogr#Get_Frogr">how to get frogr installed on your system</a>.
<p>I think that&rsquo;s it. Enjoy!</p>
]]></content:encoded></item><item><title>Frogr 0.6.1 (bugfixing) release</title><link>https://mariospr.org/2011/08/19/frogr-0-6-1-bugfixing-release/</link><pubDate>Fri, 19 Aug 2011 19:18:10 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=552</guid><description>&lt;p&gt;Shit happens in many ways, and sometimes that means you release an application with some bugs you just can&amp;rsquo;t stand and need to roll out a bugfixing release as soon as possible. Does this sound familiar to you? :)&lt;/p&gt;
&lt;p&gt;So that&amp;rsquo;s why this new release of frogr, just &lt;a href="https://mariospr.org/2011/08/13/frogr-0-6-released/"&gt;one week after the 0.6 version had been published&lt;/a&gt;, has arrived, taking care exclusively of fixing the following problems, as stated in the &lt;a title="Frogr's NEWS file" href="http://git.gnome.org/browse/frogr/tree/NEWS"&gt;NEWS file&lt;/a&gt;:&lt;/p&gt;</description><content:encoded><![CDATA[<p>Shit happens in many ways, and sometimes that means you release an application with some bugs you just can&rsquo;t stand and need to roll out a bugfixing release as soon as possible. Does this sound familiar to you? :)</p>
<p>So that&rsquo;s why this new release of frogr, just <a href="/2011/08/13/frogr-0-6-released/">one week after the 0.6 version had been published</a>, has arrived, taking care exclusively of fixing the following problems, as stated in the <a title="Frogr's NEWS file" href="http://git.gnome.org/browse/frogr/tree/NEWS">NEWS file</a>:</p>
<ul>
	<li>﻿Fix memory leaks, the most important one happening in the editing details dialog.</li>
	<li>Problems using combo boxes with versions of GTK prior to 2.24.</li>
	<li>Fixed problems authorizing frogr on the MacOSX version.</li>
</ul>
From those above, patches for some them were already included in the debian packages from <a href="http://launchpad.net/~mariospr/+archive/frogr">frogr's Ubuntu PPA</a> and in the package for the Mac, but the most important ones -the leaks- were not, so that's why I decided to roll this new version out.
<p>So that&rsquo;s all, if you were already an user of frogr, <a title="Get frogr" href="https://live.gnome.org/Frogr#Get_Frogr">go and grab it through the usual ways</a>.</p>
]]></content:encoded></item><item><title>Frogr 0.6 released</title><link>https://mariospr.org/2011/08/13/frogr-0-6-released/</link><pubDate>Sat, 13 Aug 2011 11:02:06 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=532</guid><description>&lt;div&gt;
&lt;p&gt;After some changes here and there &lt;a title="Frogr" href="https://live.gnome.org/Frogr"&gt;frogr&lt;/a&gt; 0.6 is finally &lt;a href="http://mail.gnome.org/archives/frogr-list/2011-August/msg00001.html"&gt;out&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://mariospr.org/wp-content/uploads/2011/08/20110813-frogr-0.6-screenshot.png"&gt;&lt;img src="https://mariospr.org/wp-content/uploads/2011/08/20110813-frogr-0.6-screenshot-thumb.png" alt="Frogr 0.6 running in GNOME 3" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Besides the usual bugfixing work, the main new features on this release are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Integration with the GNOME general proxy settings (optional).&lt;/li&gt;
&lt;li&gt;Open pictures in the default image viewer  from the details dialog and the main view.&lt;/li&gt;
&lt;li&gt;Allow users to specify the license to be set for the pictures.&lt;/li&gt;
&lt;li&gt;A new &lt;em&gt;User Manual, &lt;/em&gt;under "Help &amp;gt; Contents".&lt;/li&gt;
&lt;li&gt;Some UI improvements.&lt;/li&gt;
&lt;/ul&gt;
As usual, you can get &lt;a title="Frogr" href="https://live.gnome.org/Frogr"&gt;frogr&lt;/a&gt; through different ways: you can grab the source code &lt;a title="Frogr's git repository" href="http://git.gnome.org/browse/frogr"&gt;from its git repository&lt;/a&gt; or via the &lt;a title="frogr-0.6.tar.xz" href="http://download.gnome.org/sources/frogr/0.6/frogr-0.6.tar.xz"&gt;xz&lt;/a&gt; and &lt;a title="frogr-0.6.tar.bz2" href="http://download.gnome.org/sources/frogr/0.6/frogr-0.6.tar.bz2"&gt;bzip2&lt;/a&gt; tarballs, specific packages &lt;a title="Frogr packages for Fedora" href="http://people.gnome.org/~mario/files/frogr/fedora" target="_blank"&gt;for Fedora&lt;/a&gt; or &lt;a title="Frogr PPA at launchpad" href="http://launchpad.net/~mariospr/+archive/frogr"&gt;for Ubuntu&lt;/a&gt; (ranging from Karmic to Oneiric) and even a &lt;a title="MacOSX packages of frogr (Intel)" href="ftp://ftp.gnome.org/pub/GNOME/binaries/mac/frogr/frogr-0.6.macosx.intel.dmg"&gt;version for MacOSX&lt;/a&gt;, if you dare to use it.
&lt;p&gt;By the way, at the moment &lt;a title="Frogr" href="https://live.gnome.org/Frogr"&gt;frogr&lt;/a&gt; is already being packaged in some distros (see &lt;a title="Get Frogr" href="https://live.gnome.org/Frogr#Get_Frogr"&gt;this&lt;/a&gt;) and others might follow, so perhaps it could be that you already were able to install it by just using your favorite package manager with the standard repos. Otherwise, it might be just a matter of time, I guess&amp;hellip;&lt;/p&gt;</description><content:encoded><![CDATA[<div>
<p>After some changes here and there <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a> 0.6 is finally <a href="http://mail.gnome.org/archives/frogr-list/2011-August/msg00001.html">out</a>.</p>
<p><a href="/wp-content/uploads/2011/08/20110813-frogr-0.6-screenshot.png"><img src="/wp-content/uploads/2011/08/20110813-frogr-0.6-screenshot-thumb.png" alt="Frogr 0.6 running in GNOME 3" /></a></p>
<p>Besides the usual bugfixing work, the main new features on this release are:</p>
<ul>
	<li>Integration with the GNOME general proxy settings (optional).</li>
	<li>Open pictures in the default image viewer  from the details dialog and the main view.</li>
	<li>Allow users to specify the license to be set for the pictures.</li>
	<li>A new <em>User Manual, </em>under "Help &gt; Contents".</li>
	<li>Some UI improvements.</li>
</ul>
As usual, you can get <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a> through different ways: you can grab the source code <a title="Frogr's git repository" href="http://git.gnome.org/browse/frogr">from its git repository</a> or via the <a title="frogr-0.6.tar.xz" href="http://download.gnome.org/sources/frogr/0.6/frogr-0.6.tar.xz">xz</a> and <a title="frogr-0.6.tar.bz2" href="http://download.gnome.org/sources/frogr/0.6/frogr-0.6.tar.bz2">bzip2</a> tarballs, specific packages <a title="Frogr packages for Fedora" href="http://people.gnome.org/~mario/files/frogr/fedora" target="_blank">for Fedora</a> or <a title="Frogr PPA at launchpad" href="http://launchpad.net/~mariospr/+archive/frogr">for Ubuntu</a> (ranging from Karmic to Oneiric) and even a <a title="MacOSX packages of frogr (Intel)" href="ftp://ftp.gnome.org/pub/GNOME/binaries/mac/frogr/frogr-0.6.macosx.intel.dmg">version for MacOSX</a>, if you dare to use it.
<p>By the way, at the moment <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a> is already being packaged in some distros (see <a title="Get Frogr" href="https://live.gnome.org/Frogr#Get_Frogr">this</a>) and others might follow, so perhaps it could be that you already were able to install it by just using your favorite package manager with the standard repos. Otherwise, it might be just a matter of time, I guess&hellip;</p>
<p>For more information about the project and also <a title="Get Involved" href="https://live.gnome.org/Frogr#Get_Involved">how to contribute</a>, check out <a title="Frogr's web site" href="http://live.gnome.org/Frogr">its web site</a>.</p>
<p>Last, but not least, I&rsquo;d like to make an special mention here to the awesome <a title="Quinn Dombrowski's website" href="http://www.quinndombrowski.com/">Quinn Dombrowski</a>, who very well could be the &ldquo;most passionate frogr user I&rsquo;ve ever known&rdquo; and who was kind enough to design, <strong>handcraft </strong>and send -from Chicago to Spain- a stuffed frogr mascot plus a beautiful vest for my son (which design comes also with <a title="Medieval Children's art" href="http://www.goldschp.net/archive/childart.html">its own incredible story</a>), as a sign of gratitude for writing this tiny app. I&rsquo;m still shocked about it, see what I&rsquo;m talking about:</p>
<p><a title="Frogr mascot by quinn.anya, on Flickr" href="http://www.flickr.com/photos/quinnanya/5718731924/"><img class="alignnone" src="https://farm4.static.flickr.com/3215/5718731924_fa2c8542f5_m.jpg" alt="Frogr mascot" width="240" height="160" /></a> <a title="Onfim vest by quinn.anya, on Flickr" href="http://www.flickr.com/photos/quinnanya/5718169711/"><img class="alignnone" src="https://farm3.static.flickr.com/2343/5718169711_2812e0dc43_m.jpg" alt="Onfim vest" width="240" height="160" /></a></p>
<p>If you want to see more pictures you can check <a title="Frogr handcrafted stuff, by Quinn Dombrowski" href="http://www.flickr.com/photos/mariosp/sets/72157627293035281/">my set in flickr</a>, although I warn you these two ones taken by the artist are way better than mine :-)</p>
<p>Seriously Quinn&hellip; and yet once again: Thank you!</p>
</div>
]]></content:encoded></item><item><title>Frogr 0.5 released</title><link>https://mariospr.org/2011/05/27/frogr-0-5-released/</link><pubDate>Fri, 27 May 2011 12:24:17 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=510</guid><description>&lt;p&gt;Now announcing that the new release of &lt;a title="Frogr" href="https://live.gnome.org/Frogr"&gt;frogr&lt;/a&gt; is finally out.&lt;/p&gt;
&lt;p&gt;This time, I&amp;rsquo;m afraid you won&amp;rsquo;t find huge changes in the application, but a bunch of small improvements instead, in the way of subtle -yet handy- new features, bug fixes and new and uptaded translations mainly. Still, I can mention some of the new small features that I specially like, since I use it a lot:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Uploading pictures stored in remote machines via well-known protocols like smb, ssh, ftp... well anything supported by &lt;a title="GVFS" href="http://developer.gnome.org/gio/stable/GVfs.html"&gt;GVFS&lt;/a&gt;, basically.&lt;/li&gt;
&lt;li&gt;Sort pictures in the interface by title and date taken (and keep the pictures sorted as you add more pictures!).&lt;/li&gt;
&lt;li&gt;Allow disabling tags autocompletion (seems to slow frogr down when you have thousands of tags).&lt;/li&gt;
&lt;li&gt;Tooltips with basic info about the pictures in the icon view (title, size, date taken).&lt;/li&gt;
&lt;li&gt;Show the total amount of data to be uploaded in the status bar.&lt;/li&gt;
&lt;li&gt;Allow filling the details for pictures right from the photoset details, when creating a new one.&lt;/li&gt;
&lt;li&gt;Correct picture orientation in the icon view, if needed (rotation).&lt;/li&gt;
&lt;li&gt;Support both for Gtk+2 and Gtk+3 (now this is the default toolkit for building).&lt;/li&gt;
&lt;li&gt;Support for generating &lt;a title="MacOSX" href="http://en.wikipedia.org/wiki/Macosx"&gt;MacOSX&lt;/a&gt; packages, thanks to &lt;a title="GTK-OSX" href="http://gtk-osx.sourceforge.net"&gt;the GTK-OSX project&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;As usual, several other bug fixes, improvements and nitpicky stuff.&lt;/li&gt;
&lt;/ul&gt;
As usual, you can get it through different ways:
&lt;ul&gt;
&lt;li&gt;Source code: clone from &lt;a title="Frogr's git repository" href="http://git.gnome.org/browse/frogr"&gt;the git repository at gnome.org&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Tarballs: both in &lt;a title="frogr-0.5.tar.xz" href="http://download.gnome.org/sources/frogr/0.5/frogr-0.5.tar.xz"&gt;xz&lt;/a&gt; and &lt;a title="frogr-0.5.tar.bz2" href="http://download.gnome.org/sources/frogr/0.5/frogr-0.5.tar.bz2"&gt;bzip2&lt;/a&gt; formats.&lt;/li&gt;
&lt;li&gt;Pre-compiled packages for &lt;a title="The Fedora Project" href="http://www.fedoraproject.org"&gt;Fedora&lt;/a&gt;: at &lt;a title="Frogr packages for Fedora" href="http://people.gnome.org/~mario/files/frogr/fedora" target="_blank"&gt;my personal public folder in gnome.org&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;For the specific case of &lt;a title="Ubuntu Linux" href="http://www.ubuntu.com"&gt;Ubuntu&lt;/a&gt; you can use &lt;a title="Frogr PPA at launchpad" href="http://launchpad.net/~mariospr/+archive/frogr"&gt;this PPA at LaunchPad&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a title="MacOSX" href="http://en.wikipedia.org/wiki/Macosx"&gt;MacOSX&lt;/a&gt; packages (Intel) in the &lt;a title="MacOSX package of frogr (Intel)" href="//ftp.gnome.org/pub/GNOME/binaries/mac/frogr/frogr-0.5.macosx.intel.dmg"&gt;GNOME FTP server&lt;/a&gt; (experimental, yet ready for everyday use)&lt;/li&gt;
&lt;/ul&gt;
&lt;em&gt;&lt;strong&gt;[Update 31/05/2011]: &lt;/strong&gt;If you have &lt;strong&gt;already installed frogr 0.5&lt;/strong&gt; for Ubuntu from my PPA or from the pre-compiled packages, &lt;strong&gt;please do upgrade&lt;/strong&gt; to the latest version of the Ubuntu packages &lt;strong&gt;a&lt;/strong&gt;&lt;strong&gt;s soon as possible&lt;/strong&gt;, as available &lt;a title="Frogr packages at Frogr's PPA" href="https://launchpad.net/~mariospr/+archive/frogr/+packages"&gt;in my PPA&lt;/a&gt;. If you already have the PPA configured in your system, you can upgrade just frogr by simply doing this:&lt;/em&gt;
&lt;blockquote&gt;&lt;em&gt;sudo apt-get update &amp;amp;&amp;amp; sudo install frogr&lt;/em&gt;&lt;/blockquote&gt;
&lt;em&gt;There was a problem with the generation of the previous version of the packages for Ubuntu (files being installed under /tmp/frogr, instead of /usr/share) and all of them are broken and need to be updated. &lt;em&gt;Sorry for the hassle.&lt;/em&gt;&lt;/em&gt;
&lt;p&gt;If you want to contribute, remember you can do it by proposing ideas, &lt;a title="Frogr module at l10n.gnome.org" href="http://l10n.gnome.org/module/frogr/"&gt;translating&lt;/a&gt;, &lt;a title="Frogr's git repository" href="http://git.gnome.org/browse/frogr"&gt;coding&lt;/a&gt;, &lt;a title="Frogr's mailing list" href="http://mail.gnome.org/mailman/listinfo/frogr-list"&gt;discussing&lt;/a&gt; or &lt;a title="File new bugs for Frogr" href="https://bugzilla.gnome.org/enter_bug.cgi?product=frogr"&gt;filing&lt;/a&gt; and/or &lt;a title="Frogr's list of bugs" href="https://bugzilla.gnome.org/browse.cgi?product=frogr"&gt;fixing&lt;/a&gt; bugs.&lt;/p&gt;</description><content:encoded><![CDATA[<p>Now announcing that the new release of <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a> is finally out.</p>
<p>This time, I&rsquo;m afraid you won&rsquo;t find huge changes in the application, but a bunch of small improvements instead, in the way of subtle -yet handy- new features, bug fixes and new and uptaded translations mainly. Still, I can mention some of the new small features that I specially like, since I use it a lot:</p>
<ul>
	<li>Uploading pictures stored in remote machines via well-known protocols like smb, ssh, ftp... well anything supported by <a title="GVFS" href="http://developer.gnome.org/gio/stable/GVfs.html">GVFS</a>, basically.</li>
	<li>Sort pictures in the interface by title and date taken (and keep the pictures sorted as you add more pictures!).</li>
	<li>Allow disabling tags autocompletion (seems to slow frogr down when you have thousands of tags).</li>
	<li>Tooltips with basic info about the pictures in the icon view (title, size, date taken).</li>
	<li>Show the total amount of data to be uploaded in the status bar.</li>
	<li>Allow filling the details for pictures right from the photoset details, when creating a new one.</li>
	<li>Correct picture orientation in the icon view, if needed (rotation).</li>
	<li>Support both for Gtk+2 and Gtk+3 (now this is the default toolkit for building).</li>
	<li>Support for generating <a title="MacOSX" href="http://en.wikipedia.org/wiki/Macosx">MacOSX</a> packages, thanks to <a title="GTK-OSX" href="http://gtk-osx.sourceforge.net">the GTK-OSX project</a>.</li>
	<li>As usual, several other bug fixes, improvements and nitpicky stuff.</li>
</ul>
As usual, you can get it through different ways:
<ul>
	<li>Source code: clone from <a title="Frogr's git repository" href="http://git.gnome.org/browse/frogr">the git repository at gnome.org</a>.</li>
	<li>Tarballs: both in <a title="frogr-0.5.tar.xz" href="http://download.gnome.org/sources/frogr/0.5/frogr-0.5.tar.xz">xz</a> and <a title="frogr-0.5.tar.bz2" href="http://download.gnome.org/sources/frogr/0.5/frogr-0.5.tar.bz2">bzip2</a> formats.</li>
	<li>Pre-compiled packages for <a title="The Fedora Project" href="http://www.fedoraproject.org">Fedora</a>: at <a title="Frogr packages for Fedora" href="http://people.gnome.org/~mario/files/frogr/fedora" target="_blank">my personal public folder in gnome.org</a>.</li>
	<li>For the specific case of <a title="Ubuntu Linux" href="http://www.ubuntu.com">Ubuntu</a> you can use <a title="Frogr PPA at launchpad" href="http://launchpad.net/~mariospr/+archive/frogr">this PPA at LaunchPad</a>.</li>
	<li><a title="MacOSX" href="http://en.wikipedia.org/wiki/Macosx">MacOSX</a> packages (Intel) in the <a title="MacOSX package of frogr (Intel)" href="//ftp.gnome.org/pub/GNOME/binaries/mac/frogr/frogr-0.5.macosx.intel.dmg">GNOME FTP server</a> (experimental, yet ready for everyday use)</li>
</ul>
<em><strong>[Update 31/05/2011]: </strong>If you have <strong>already installed frogr 0.5</strong> for Ubuntu from my PPA or from the pre-compiled packages, <strong>please do upgrade</strong> to the latest version of the Ubuntu packages <strong>a</strong><strong>s soon as possible</strong>, as available <a title="Frogr packages at Frogr's PPA" href="https://launchpad.net/~mariospr/+archive/frogr/+packages">in my PPA</a>. If you already have the PPA configured in your system, you can upgrade just frogr by simply doing this:</em>
<blockquote><em>sudo apt-get update &amp;&amp; sudo install frogr</em></blockquote>
<em>There was a problem with the generation of the previous version of the packages for Ubuntu (files being installed under /tmp/frogr, instead of /usr/share) and all of them are broken and need to be updated. <em>Sorry for the hassle.</em></em>
<p>If you want to contribute, remember you can do it by proposing ideas, <a title="Frogr module at l10n.gnome.org" href="http://l10n.gnome.org/module/frogr/">translating</a>, <a title="Frogr's git repository" href="http://git.gnome.org/browse/frogr">coding</a>, <a title="Frogr's mailing list" href="http://mail.gnome.org/mailman/listinfo/frogr-list">discussing</a> or <a title="File new bugs for Frogr" href="https://bugzilla.gnome.org/enter_bug.cgi?product=frogr">filing</a> and/or <a title="Frogr's list of bugs" href="https://bugzilla.gnome.org/browse.cgi?product=frogr">fixing</a> bugs.</p>
<p>Also if you want to see <a title="Frogr" href="https://live.gnome.org/Frogr">frogr</a> packaged for your favourite distro and can help with that (maybe you&rsquo;re a packager or know better than me the required steps for that), that would be awesome. At the moment only <a title="Debian" href="http://www.debian.org">Debian</a> has packaged it so far that I know of (thanks <a title="Berto's blog" href="https://blogs.igalia.com/berto">Berto</a>!), but I would love to see it also in other distros (specially in <a title="The Fedora Project" href="http://www.fedoraproject.org">Fedora</a>, which is what I currently use) so more people can use it without having to use either <a title="My PPA at launchpad" href="http://launchpad.net/~mariospr/+archive/frogr">the Frogr PPA</a> or <a title="Frogr website: downloads" href="http://people.gnome.org/~mario/files/frogr" target="_blank">the homegrown packages I usually prepare with each release</a>.</p>
<p>For more information, just check out <a title="Frogr's web site" href="http://live.gnome.org/Frogr">its web site</a>. Here you have a screenshot of how <a title="Frogr" href="https://live.gnome.org/Frogr">frogr 0.5</a> looks in the awesome <a title="GNOME 3: Made of Easy" href="http://gnome3.org/">GNOME 3</a> in my <a title="The Fedora Project" href="http://www.fedoraproject.org">Fedora</a> box:</p>
<p><a href="/wp-content/uploads/2011/05/20110527-frogr-0.5-screenshot.png"><img class="aligncenter" src="/wp-content/uploads/2011/05/20110527-frogr-0.5-screenshot-thumb.png" alt="Frogr 0.5 running in GNOME 3" width="520" height="325" /></a></p>
]]></content:encoded></item></channel></rss>