<?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>frogr on mariospr.org</title><link>https://mariospr.org/category/frogr/</link><description>Recent content in frogr on mariospr.org</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 25 Nov 2018 00:02:19 +0000</lastBuildDate><atom:link href="https://mariospr.org/category/frogr/index.xml" rel="self" type="application/rss+xml"/><item><title>Frogr 1.5 released</title><link>https://mariospr.org/2018/11/25/frogr-1-5-released/</link><pubDate>Sun, 25 Nov 2018 00:02:19 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=2635</guid><description>&lt;p&gt;It&amp;rsquo;s &lt;a href="https://mariospr.org/2017/12/28/frogr-1-4-released/"&gt;almost one year later&lt;/a&gt; and, despite the &lt;a href="https://blog.flickr.net/en/2018/04/20/together-smugmug-flickr-faq/?utm_campaign=flickr-launch&amp;amp;utm_source=SmugMug&amp;amp;utm_medium=referral&amp;amp;utm_content=ms-footer-txt"&gt;acquisition by SmugMug a few months ago&lt;/a&gt; and the predictions from some people that it would mean me stopping from using Flickr &amp;amp; maintaining Frogr, here comes the &lt;a href="https://mail.gnome.org/archives/gnome-announce-list/2018-November/msg00024.html"&gt;new release of frogr 1.5&lt;/a&gt;.&lt;a href="https://mariospr.org/wp-content/uploads/2018/11/frogr-empty-burger-menu.png"&gt;&lt;img class="size-medium wp-image-2639 alignright" src="https://mariospr.org/wp-content/uploads/2018/11/frogr-empty-burger-menu-300x188.png" alt="Frogr 1.5 screenshot" width="300" height="188" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Not many changes this time, but some of them hopefully still useful for some people, such as the empty initial state that is now shown when you don&amp;rsquo;t have any pictures, as requested a while ago already by Nick Richards (thanks Nick!), or the removal of the applications menu from the shell&amp;rsquo;s top panel (now integrated in the hamburger menu), in line with the &lt;a href="https://gitlab.gnome.org/GNOME/Initiatives/wikis/App-Menu-Retirement"&gt;&amp;ldquo;App Menu Retirement&amp;rdquo; initiative&lt;/a&gt;.&lt;/p&gt;</description><content:encoded><![CDATA[<p>It&rsquo;s <a href="/2017/12/28/frogr-1-4-released/">almost one year later</a> and, despite the <a href="https://blog.flickr.net/en/2018/04/20/together-smugmug-flickr-faq/?utm_campaign=flickr-launch&amp;utm_source=SmugMug&amp;utm_medium=referral&amp;utm_content=ms-footer-txt">acquisition by SmugMug a few months ago</a> and the predictions from some people that it would mean me stopping from using Flickr &amp; maintaining Frogr, here comes the <a href="https://mail.gnome.org/archives/gnome-announce-list/2018-November/msg00024.html">new release of frogr 1.5</a>.<a href="/wp-content/uploads/2018/11/frogr-empty-burger-menu.png"><img class="size-medium wp-image-2639 alignright" src="/wp-content/uploads/2018/11/frogr-empty-burger-menu-300x188.png" alt="Frogr 1.5 screenshot" width="300" height="188" /></a></p>
<p>Not many changes this time, but some of them hopefully still useful for some people, such as the empty initial state that is now shown when you don&rsquo;t have any pictures, as requested a while ago already by Nick Richards (thanks Nick!), or the removal of the applications menu from the shell&rsquo;s top panel (now integrated in the hamburger menu), in line with the <a href="https://gitlab.gnome.org/GNOME/Initiatives/wikis/App-Menu-Retirement">&ldquo;App Menu Retirement&rdquo; initiative</a>.</p>
<p>Then there were some fixes here and there as usual, and quite so many updates to the translations this time, including a brand new translation to Icelandic! (thanks Sveinn).</p>
<p>So this is it this time, I&rsquo;m afraid. Sorry there&rsquo;s not much to report and sorry as well for the long time that took me to do this release, but this past year has been pretty busy between hectic work at <a href="https://endlessm.com">Endless</a> the first time of the year, a whole international relocation with my family to <a href="/2018/08/03/on-moving/">move back to Spain during the summer</a> and me getting <a href="https://www.igalia.com/nc/igalia-247/news/item/igalias-chromium-team-continues-to-grow/">back to work at Igalia as part of the Chromium team</a>, where I&rsquo;m currently pretty busy working on the <a href="https://www.chromium.org/servicification">Chromium Servicification project</a> (which is material for a completely different blog post of course).</p>
<p>Anyway, last but not least, feel free to grab frogr from the usual places as <a href="https://wiki.gnome.org/Apps/Frogr#Get_Frogr">outlined in its main website</a>, among which I&rsquo;d recommend the <a href="https://flatpak.org/">Flatpak</a> method, either via <a href="https://wiki.gnome.org/Apps/Software">GNOME Software</a>  or from the command line by just doing this:</p>
<pre>flatpak install --from \
    https://flathub.org/repo/appstream/org.gnome.frogr.flatpakref</pre>
<p>For more information just check the <a href="https://wiki.gnome.org/Apps/Frogr">main website</a>, which I also updated to this latest release, and don&rsquo;t hesitate to reach out if you have any questions or comments.</p>
<p>Hope you enjoy it. Thanks!</p>
]]></content:encoded></item><item><title>Frogr 1.4 released</title><link>https://mariospr.org/2017/12/28/frogr-1-4-released/</link><pubDate>Thu, 28 Dec 2017 02:45:24 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=2476</guid><description>&lt;p&gt;Another year goes by and, again, I &lt;em&gt;feel the call&lt;/em&gt; to make one more release just before 2017 over, so here we are: &lt;a href="https://mail.gnome.org/archives/gnome-announce-list/2017-December/msg00009.html"&gt;frogr 1.4 is out!&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://mariospr.org/wp-content/uploads/2017/12/20171228-frogr-screenshot.png"&gt;&lt;img class="aligncenter size-large wp-image-2501" src="https://mariospr.org/wp-content/uploads/2017/12/20171228-frogr-screenshot-600x375.png" alt="Screenshot of frogr 1.4" width="600" height="375" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Yes, I know what you&amp;rsquo;re thinking: &lt;em&gt;&amp;ldquo;Who uses Flickr in 2017 anyway?&amp;quot;&lt;/em&gt;. Well, as shocking as this might seem to you, it is apparently not just me who is using this small app, but also another &lt;b id="yui_3_11_0_1_1514425191744_315"&gt;8,935 users&lt;/b&gt; out there issuing an average of 0.22 Queries Per Second every day (&lt;strong&gt;19008 queries a day&lt;/strong&gt;) for the past year, according to the stats provided by Flickr for the API key.&lt;/p&gt;</description><content:encoded><![CDATA[<p>Another year goes by and, again, I <em>feel the call</em> to make one more release just before 2017 over, so here we are: <a href="https://mail.gnome.org/archives/gnome-announce-list/2017-December/msg00009.html">frogr 1.4 is out!</a></p>
<p><a href="/wp-content/uploads/2017/12/20171228-frogr-screenshot.png"><img class="aligncenter size-large wp-image-2501" src="/wp-content/uploads/2017/12/20171228-frogr-screenshot-600x375.png" alt="Screenshot of frogr 1.4" width="600" height="375" /></a></p>
<p>Yes, I know what you&rsquo;re thinking: <em>&ldquo;Who uses Flickr in 2017 anyway?&quot;</em>. Well, as shocking as this might seem to you, it is apparently not just me who is using this small app, but also another <b id="yui_3_11_0_1_1514425191744_315">8,935 users</b> out there issuing an average of 0.22 Queries Per Second every day (<strong>19008 queries a day</strong>) for the past year, according to the stats provided by Flickr for the API key.</p>
<p>Granted, it may be not a huge number compared to what other online services might be experiencing these days, but for me this is enough motivation to keep the little green frog working and running, thus worth updating it one more time. Also, I&rsquo;d argue that these numbers for a niche app like this one (aimed at users of the Linux desktop that still use Flickr to upload pictures in 2017) do not even look too bad, although without more specific data backing this comment this is, of course, just my personal and highly-biased opinion.</p>
<p>So, what&rsquo;s new? Some small changes and fixes, along with other less visible modifications, but still relevant and necessary IMHO:</p>
<ul>
 	<li>Fixed integration with GNOME Software (fixed a bug regarding <em style="font-size: 1rem;">appstream</em><span style="font-size: 1rem;"> data).</span></li>
 	<li>Fixed errors loading images from certain cameras &amp; phones, such as the OnePlus 5.</li>
 	<li>Cleaned the code by finally migrating to using <em>g_auto</em>, <em>g_autoptr</em> and <em>g_autofree</em>.</li>
 	<li>Migrated to the meson build system, and removed all the autotools files.</li>
 	<li>Big update to translations, now with more than 22 languages 90% - 100% translated.</li>
</ul>
Also, this is the first release that happens after having a fully operational centralized place for <a href="https://flatpak.org/">Flatpak</a> applications (aka <a href="https://flathub.org/">Flathub</a>), so I've <a href="https://github.com/flathub/org.gnome.frogr/commit/cc48dcb30ec472c5182ea9083fa242f178348c02">updated the manifest</a> and I'm happy to say that frogr 1.4 is already available for <em>i386</em>, <em>arm</em>, <em>aarch64</em> and <em>x86_64</em>. You can install it either from <a href="https://wiki.gnome.org/Apps/Software">GNOME Software</a> (details on how to do it at <em><a href="https://flathub.org">https://flathub.org</a></em>), or from the command line by just doing this:
<pre>flatpak install --from https://flathub.org/repo/appstream/org.gnome.frogr.flatpakref</pre>
Also worth mentioning that, starting with Frogr 1.4, I will no longer be updating my <a href="https://launchpad.net/~mariospr/+archive/ubuntu/frogr">PPA at Launchpad</a>. I did that in the past to make it possible for Ubuntu users to have access to the latest release ASAP, but now we have Flatpak that's a much better way to install and run the latest stable release in any supported distro (not just Ubuntu). Thus, I'm dropping the extra work required to deal with the PPA and flat-out recommending users to use Flatpak or wait until their distro of choice packages the latest release.
<p>And I think this is everything. As usual, feel free to check the <a style="font-size: 1rem;" href="https://wiki.gnome.org/Apps/Frogr">main website</a><span style="font-size: 1rem;"> for extra information on </span><a style="font-size: 1rem;" href="https://wiki.gnome.org/Apps/Frogr#Get_Frogr">how to get frogr</a><span style="font-size: 1rem;"> and/or </span><a style="font-size: 1rem;" href="https://wiki.gnome.org/Apps/Frogr#Get_Involved">how to contribute to it</a><span style="font-size: 1rem;">. Feedback and/or help is more than welcome.</span></p>
<p>Happy new year everyone!</p>
]]></content:encoded></item><item><title>Frogr 1.3 released</title><link>https://mariospr.org/2017/05/20/frogr-1-3-released/</link><pubDate>Sat, 20 May 2017 23:58:25 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=2374</guid><description>&lt;p&gt;Quick post to let you know that I just &lt;a href="https://mail.gnome.org/archives/frogr-list/2017-May/msg00000.html"&gt;released frogr 1.3&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is mostly a small update to incorporate a bunch of updates in translations, a few changes aimed at improving the &lt;a href="http://flatpak.org/"&gt;flatpak&lt;/a&gt; version of it (the desktop icon has been broken for a while until a few weeks ago) and to remove some deprecated calls in recent versions of GTK+.&lt;/p&gt;
&lt;p&gt;Ah! I&amp;rsquo;ve also officially dropped support for OS X via &lt;a href="https://wiki.gnome.org/Projects/GTK%2B/OSX/Building"&gt;gtk-osx&lt;/a&gt;, as I was systematically failing to update and use (I only use frogr from GNOME these days) since &lt;a href="https://mariospr.org/2012/12/29/frogr-0-8-released/"&gt;a loooong time ago&lt;/a&gt;,  and so it did not make sense for me to keep pretending that the mac version is something that is usable and maintained anymore.&lt;/p&gt;</description><content:encoded><![CDATA[<p>Quick post to let you know that I just <a href="https://mail.gnome.org/archives/frogr-list/2017-May/msg00000.html">released frogr 1.3</a>.</p>
<p>This is mostly a small update to incorporate a bunch of updates in translations, a few changes aimed at improving the <a href="http://flatpak.org/">flatpak</a> version of it (the desktop icon has been broken for a while until a few weeks ago) and to remove some deprecated calls in recent versions of GTK+.</p>
<p>Ah! I&rsquo;ve also officially dropped support for OS X via <a href="https://wiki.gnome.org/Projects/GTK%2B/OSX/Building">gtk-osx</a>, as I was systematically failing to update and use (I only use frogr from GNOME these days) since <a href="/2012/12/29/frogr-0-8-released/">a loooong time ago</a>,  and so it did not make sense for me to keep pretending that the mac version is something that is usable and maintained anymore.</p>
<p>As usual, you can go to the <a href="https://wiki.gnome.org/Apps/Frogr">main website</a> for extra information on <a href="https://wiki.gnome.org/Apps/Frogr#Get_Frogr">how to get frogr</a> and/or <a href="https://wiki.gnome.org/Apps/Frogr#Get_Involved">how to contribute to it</a>. Any feedback or help is more than welcome!</p>
<p> </p>
]]></content:encoded></item><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.9 released</title><link>https://mariospr.org/2014/01/17/frogr-0-9-released/</link><pubDate>Fri, 17 Jan 2014 15:29:50 +0000</pubDate><guid isPermaLink="false">https://mariospr.org/?p=1702</guid><description>&lt;p&gt;So, after a bit more than one year without releasing any version of &lt;a title="Frogr web site" href="https://wiki.gnome.org/Apps/Frogr"&gt;frogr&lt;/a&gt;, I finally managed to get some &amp;ldquo;spare&amp;rdquo; time to put all the pieces together and ship the ninth version of it, which I believe/hope is going to be a quite solid one.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://mariospr.org/2014/01/17/frogr-0-9-released/20140117-frogr-screenshot/" rel="attachment wp-att-1705"&gt;&lt;img class="aligncenter size-large wp-image-1705" alt="Frogr 0.9" src="https://mariospr.org/wp-content/uploads/2014/01/20140117-frogr-screenshot-600x375.png" width="584" height="365" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In all honesty, though, this version does not come with many new features as the previous ones, yet some changes and fixes that I believe were quite necessary, and therefore should help improving the user experience in some subtle ways.&lt;/p&gt;</description><content:encoded><![CDATA[<p>So, after a bit more than one year without releasing any version of <a title="Frogr web site" href="https://wiki.gnome.org/Apps/Frogr">frogr</a>, I finally managed to get some &ldquo;spare&rdquo; time to put all the pieces together and ship the ninth version of it, which I believe/hope is going to be a quite solid one.</p>
<p><a href="/2014/01/17/frogr-0-9-released/20140117-frogr-screenshot/" rel="attachment wp-att-1705"><img class="aligncenter size-large wp-image-1705" alt="Frogr 0.9" src="/wp-content/uploads/2014/01/20140117-frogr-screenshot-600x375.png" width="584" height="365" /></a></p>
<p>In all honesty, though, this version does not come with many new features as the previous ones, yet some changes and fixes that I believe were quite necessary, and therefore should help improving the user experience in some subtle ways.</p>
<p>For instance, the layout of the dialog to edit the details of a picture has changed (as per <a title="Ana Rey on Twitter" href="https://twitter.com/anaRB">Ana Rey</a>&rsquo;s comments during <a title="GUADEC" href="http://www.guadec.org">GUADEC</a>) to enable a more efficient usage of vertical space, so much needed these days in small widescreen laptops. Of course, design-wise still sucks, but I believe it&rsquo;s much more convenient now from a pragmatical point of view.</p>
<p>Also, frogr is now a little bit more &ldquo;modern&rdquo; in things such as that it now supports GStreamer 1.0 (0.10 still supported), a lot of deprecated code (e.g. Stock items, GtkActions) has been replaced internally and it now integrates better with <a title="GNOME" href="http://www.gnome.org">GNOME</a> Shell&rsquo;s search box. Ah! and it also now provides an <a href="http://people.freedesktop.org/~hughsient/appdata/">AppData</a> file to integrate with <a title="GNOME Software Center" href="http://blogs.gnome.org/hughsie/2013/08/29/gnome-software-center-and-you/">GNOME Software Center</a>, which is a nice touch too.</p>
<p>Another interesting thing is that I finally fixed the problem that we have with multiple selections in the main view, which was neither intuitive nor very useful, as Ctrl and Shift modifiers did not work as expected. So, from now on, it is finally possible to work with disjoint multiple selections of pictures, a feature I was missing so much.</p>
<p>Last, I fixed two important problems in the code that caused frogr consume two much memory, specially after uploading pictures. It was a quite severe problem since frogr was not properly freeing the memory used by pictures even after those were uploaded and removed from the UI, causing important issues in cases where people tried to upload a lot of pictures at once. It&rsquo;s hopefully fixed now.</p>
<p>And that&rsquo;s all I think. As usual, you can check <a title="Frogr's website" href="https://live.gnome.org/Frogr">the website of the project</a> to know <a title="Get frogr" href="https://live.gnome.org/Frogr#Get_Frogr">how to install frogr on your system</a> if you don&rsquo;t want to wait for your favourite distribution to ship it, or if you just want to check more information about the project or to contribute to it.</p>
<img class="alignright size-full wp-image-1709" alt="FOSDEM 2014" src="/wp-content/uploads/2014/01/fosdem-logo.png" width="165" height="33" />
<p>Ah! By the way&hellip; I&rsquo;m going to <a title="FOSDEM" href="http://www.fosdem.org">FOSDEM</a> again this year, but this time <a href="http://en.wikipedia.org/wiki/Eurostar">by train</a>. Can&rsquo;t wait to be there! :)</p>
]]></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></channel></rss>