<?xml version="1.0" encoding="iso-8859-15"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Content tagged deforaos</title>
		<link>http://people.defora.org/~khorben/place/category/35/deforaos</link>
		<atom:link href="http://people.defora.org/~khorben/place/category/rss/35/deforaos" rel="self" type="application/rss+xml"/>
		<description></description>
		<language>en</language>
		<item>
			<title>Disassembling Android applications at PSES 2011</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Mon, 20 Jun 2011 15:40:00 +0200</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/137/Disassembling-Android-applications-at-PSES-2011</link>
			<guid>http://people.defora.org/~khorben/place/blog/137/Disassembling-Android-applications-at-PSES-2011</guid>
			<description><![CDATA[I was last Friday in Paris, to contribute to a very nice third instance of the &quot;Pas Sage En Seine&quot; hacking &amp; freedom yearly event [1]. I was supposed to host a workshop about unpacking and disassembly of typical Android applications, but as it turned out, the room was too packed for this format to actually make any sense.<br/>
<br/>
Thankfully I had prepared about fifteen slides to introduce the subject, which I have added to the papers section here [2]. This session was filmed [3], and even though I couldn't complete the last part about direct downloads of applications from the market, I mentioned an additional way to obtain them.<br/>
<br/>
One last note: the session was hosted in French but the slides are in English, as well as xterm in the video :)<br/>
<br/>
[1] <a href="http://www.passageenseine.org/pes-2011/">http://www.passageenseine.org/pes-2011/</a><br/>
[2] <a href="http://people.defora.org/~khorben/papers/pses2011/Android.pdf">http://people.defora.org/~khorben/papers/pses2011/Android.pdf</a><br/>
[3] <a href="http://lacantine.ubicast.eu/videos/pses-disassembling-android-application/">http://lacantine.ubicast.eu/videos/pses-disassembling-android-application/</a><br/>
<br/>
]]></description>
		</item>
		<item>
			<title>What's going on?</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Mon, 30 May 2011 13:59:10 +0200</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/135/What-s-going-on-</link>
			<guid>http://people.defora.org/~khorben/place/blog/135/What-s-going-on-</guid>
			<description><![CDATA[Almost two months without a post?<br/>
<br/>
Well, actually, I meant to post a few notes about how the Gtk+ 2.0 to 3.0 migration went for the DeforaOS project, but ended up forgetting about it. On the other hand, I've been busy debugging and polishing the user interface, and hope to release and package these changes soon.<br/>
<br/>
Speaking of which, I haven't given up on releasing hackable:1 dse2, the smartphone environment based on DeforaOS for the GSM stack and user interface. It's just been a pain to iron out the different issues encountered, with a new one appearing every time I managed to fix something. Regardless, it's looking promising, and I've been able to give and receive phone calls again.<br/>
<br/>
On the security front, the asm project (and its disassembler) is now waiting to be integrated into UWfirmforce, which would also benefit from an updated user interface (and reporting facility even). It'll take a few more coding nights though.<br/>
<br/>
This is also because according to the DeforaOS roadmap, I am focusing on a (re-)implementation of its main functionality: the distributed computing framework. Getting the design right is a challenge in itself already, but I am fairly confident to be able to commit the first working lines of code within a few more weeks.<br/>
<br/>
Looking forward to all of these :)<br/>
<br/>
]]></description>
		</item>
		<item>
			<title>hackable:1 welcomes a new developer: Trim</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Sat, 2 Apr 2011 16:26:00 +0200</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/130/hackable-1-welcomes-a-new-developer--Trim</link>
			<guid>http://people.defora.org/~khorben/place/blog/130/hackable-1-welcomes-a-new-developer--Trim</guid>
			<description><![CDATA[I am glad to announce the arrival of a new developer within the hackable:1 project: Adrien Dorsaz, aka Trim. He has already contributed improvements to the wireless configuration interface (wicd) and calendar application (dates), besides many helpful bug reports!<br/>
<br/>
Welcome Trim, with you the imminent dse2 release has gotten only better. Cheers!<br/>
<br/>
]]></description>
		</item>
		<item>
			<title>hackable:1 builds and provides a package repository for Maemo</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Sun, 20 Mar 2011 22:18:47 +0100</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/123/hackable-1-builds-and-provides-a-package-repository-for-Maemo</link>
			<guid>http://people.defora.org/~khorben/place/blog/123/hackable-1-builds-and-provides-a-package-repository-for-Maemo</guid>
			<description><![CDATA[I had been thinking about testing the DeforaOS graphical applications [1] on my N900 [2] for a while, but remained concentrated on the Openmoko Freerunner [3] and hackable:1 [4] until it was satisfying enough. With the upcoming dse2 [5] release being in a good shape [6], I decided to have a short look anyway.<br/>
<br/>
My first reaction was very much like when I checked Maemo [7] back in 2008:<br/>
<ul>
<li>you need me to install scratchbox, which only supports i386? [8]</li>
<li>the documentation links to external sites (Debian packaging) but doesn't explain how to actually build a package? [9]</li>
<li>you prevent me from navigating the repositories freely? [10]</li>
</ul>
But this time, with the lessons learned while re-implementing strap:1 and cross-compiling Debian packages, I figured I could do it another way: with hackable:1 itself. Here is how.<br/>
<br/>
First, I determined how to populate the cross-compilation environment with the proper binaries. I added trunk/build/strap1/hostname/n900.nokia.maemo, containing:<br/>
<br/>
<pre>ENVIRONMENT=GNOME #it's empty at the momentVERBOSE=1DEBIAN_MIRROR=repository.maemo.orgDEBIAN_REPOSITORIES=sdk/freeDEBIAN_VERSION=maemo5.0DEBIAN_SOURCES=&quot;deb http://$DEBIAN_MIRROR/ $DEBIAN_VERSION $DEBIAN_REPOSITORIES&quot;VENDOR=NokiaMODEL=N900PURPOSE=phone</pre>
This also required handling Nokia-N900-phone as a valid profile, in trunk/build/strap1/profile/Nokia-N900-phone:<br/>
<br/>
<pre>ARCH=&quot;armel&quot;STRIP=&quot;arm-linux-gnueabi-strip&quot;#this device is a phone. &quot;strap1/profiles/include/phone.include&quot;#add bluetooth support. &quot;strap1/profiles/include/bluetooth.include&quot;[...]</pre>
(and so on for the rest of the hardware capabilities)<br/>
<br/>
Once this added, this simple command was enough to populate the environment:<br/>
<pre># ./strap1.sh DESTDIR=/usr/arm-linux-gnueabi HOSTNAME=n900.nokia.maemo install</pre>
There I was. It was even faster than with a regular Debian target, since there are way less packages available to parse. But did I miss installing the development packages? Totally. Yet it doesn't matter:<br/>
<pre># ./strap1.sh DESTDIR=/usr/arm-linux-gnueabi HOSTNAME=n900.nokia.maemo \  PACKAGES=&quot;libssl-dev libgtk2.0-dev&quot; install</pre>
And seconds later, I had these two installed as necessary, along with their dependencies of course. Sweet, but we're not done yet. Let's build actual packages:<br/>
<br/>
<pre>$ cd trunk/packages$ ./packages.sh DEBIAN_ARCH=armel DEBIAN_VERSION=maemo libsystem$ ./packages.sh DEBIAN_ARCH=armel DEBIAN_VERSION=maemo libdesktop$ ./packages.sh DEBIAN_ARCH=armel DEBIAN_VERSION=maemo editor</pre>
Unfortunately, even with the correct binaries and packages definitions installed in the cross-compilation environment, dh_shlibdeps failed to grab the right dependencies. Disabling it during cross-compilation was enough to do the trick (commenting it out in debian/rules from the diff file).<br/>
<br/>
Time to add this new repository into the N900 [11], through &quot;Application manager&quot;-&gt;&quot;Catalogs&quot;-&gt;&quot;New&quot; [12]:<br/>
<pre>Catalog name: hackable:1Web address: <a href="http://build.hackable1.org/debian">http://build.hackable1.org/debian</a>Distribution: wip-maemoComponents: main</pre>
Open a terminal, gain root privileges:<br/>
<pre># apt-get update# apt-get install libsystem0 libdesktop0 editor[...]$ editor</pre>
And it works. I repeat: sweet.<br/>
<br/>
Update:<br/>
<ul>
<li>you can install the following package to fix the missing icons: <a href="http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/f/fixpr12icons/fixpr12icons_1.0+maemo-0_all.deb">http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/f/fixpr12icons/fixpr12icons_1.0+maemo-0_all.deb</a></li>
<li>this page is more exhaustive about the packaging process in Maemo: <a href="http://wiki.maemo.org/Packaging">http://wiki.maemo.org/Packaging</a></li>
</ul>
[1] <a href="http://www.defora.org/os/wiki/3426/Graphical-environment">http://www.defora.org/os/wiki/3426/Graphical-environment</a><br/>
[2] <a href="http://maemo.nokia.com/n900/">http://maemo.nokia.com/n900/</a><br/>
[3] <a href="http://wiki.openmoko.org/wiki/Neo_FreeRunner">http://wiki.openmoko.org/wiki/Neo_FreeRunner</a><br/>
[4] <a href="http://trac.hackable1.org/">http://trac.hackable1.org/</a><br/>
[5] <a href="http://trac.hackable1.org/trac/wiki/AvailableVersions/dse2">http://trac.hackable1.org/trac/wiki/AvailableVersions/dse2</a><br/>
[6] <a href="http://www.defora.org/os/download/download/3512/dse2-Screenshot-2.png">http://www.defora.org/os/download/download/3512/dse2-Screenshot-2.png</a><br/>
[7] <a href="http://www.maemo.org/">http://www.maemo.org/</a><br/>
[8] <a href="http://scratchbox.org/documentation/user/scratchbox-1.0/html/installdoc.html#AEN47">http://scratchbox.org/documentation/user/scratchbox-1.0/html/installdoc.html#AEN47</a><br/>
[9] <a href="http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing">http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing</a><br/>
[10] <a href="http://repository.maemo.org/dists/maemo5.0/">http://repository.maemo.org/dists/maemo5.0/</a><br/>
[11] <a href="http://people.defora.org/~khorben/share/n900/Screenshot-20110321-000354.png">http://people.defora.org/~khorben/share/n900/Screenshot-20110321-000354.png</a><br/>
[12] <a href="http://people.defora.org/~khorben/share/n900/Screenshot-20110321-000410.png">http://people.defora.org/~khorben/share/n900/Screenshot-20110321-000410.png</a><br/>
<br/>
]]></description>
		</item>
		<item>
			<title>New unofficial beta release of hackable:1</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Sun, 13 Mar 2011 21:27:55 +0100</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/122/New-unofficial-beta-release-of-hackable-1</link>
			<guid>http://people.defora.org/~khorben/place/blog/122/New-unofficial-beta-release-of-hackable-1</guid>
			<description><![CDATA[I just announced the availability of the first beta version for dse2, the DeforaOS Smartphone Environment [1] as found in hackable:1 [2]:<br/>
<a href="http://lists.hackable1.org/pipermail/hackable1-dev/2011-March/001686.html">http://lists.hackable1.org/pipermail/hackable1-dev/2011-March/001686.html</a><br/>
<br/>
I don't think I have much to add to this; except on a personal level maybe, which would be appropriate here I guess.<br/>
<br/>
When I was first offered an Openmoko Neo1973 in summer of 2007 [3], I think I was both excited and disappointed about the device. It was a very promising opportunity for Open Source and telephony, at a time where only few devices were known to be usable with alternate and free environments. But I really did not like the look &amp; feel of the device, or the state of the software running on it. Little did I suspect that I would spend so much time and energy with its successor, the Freerunner [4].<br/>
<br/>
This happened first while I was working with Bearstech [5] on the promotion of hackable devices [6]. There, we focused on supporting what seemed to be the most viable solution at the time: the Om2007.2 stack. This part was a very frustrating experience, which I have mentioned already [7].<br/>
<br/>
And now, I begin to feel much better about the whole thing. First, the Openmoko platform is still alive: thanks to Nikolaus Schaller of Golden Delicious [8], and of course thanks to the openness of the platform, a third-party hardware upgrade is available. Then, well, Google happened, Android is everywhere, and many more devices are usable with Open Source software.<br/>
<br/>
But what's more, I am beginning to feel better and better about the DeforaOS project as a whole. This was a painful yet fantastic motivation to bring it where it is today. I had even decided to mostly give it up about a month ago, at least for a while. But the deadline [9] I set for the project on improving the user environment is almost matched now [10]. Better, I have great plans for the following one [11]. I may even go to University again [12]! This is not without reminding me about my own description of myself :) [13]<br/>
<br/>
So yeah, four years later and much to my own surprise, I am getting increasingly comfortable and curious about using the dse2 release as a daily phone. It can only inspire me to push it to the next level :) [14]<br/>
<br/>
To conclude:<br/>
<ul>
<li>special thanks to the Neo1973-gift-maker!</li>
<li>all of this is completely futile, and most of my thoughts are going to people of Japan, Ivory Coast, France and Libya right now.</li>
</ul>
[1] <a href="http://www.defora.org/os/wiki/3438/DeforaOS-Smartphone">http://www.defora.org/os/wiki/3438/DeforaOS-Smartphone</a><br/>
[2] <a href="http://trac.hackable1.org/">http://trac.hackable1.org/</a><br/>
[3] <a href="http://events.ccc.de/camp/2007/Intro/">http://events.ccc.de/camp/2007/Intro/</a><br/>
[4] <a href="http://wiki.openmoko.org/wiki/Neo_FreeRunner">http://wiki.openmoko.org/wiki/Neo_FreeRunner</a><br/>
[5] <a href="http://www.bearstech.com/">http://www.bearstech.com/</a><br/>
[6] <a href="http://hackable-devices.org/">http://hackable-devices.org/</a><br/>
[7] <a href="http://people.defora.org/~khorben/place/blog/88/The-DeforaOS-smartphone-environment">http://people.defora.org/~khorben/place/blog/88/The-DeforaOS-smartphone-environment</a><br/>
[8] <a href="http://www.goldelico.com/">http://www.goldelico.com/</a><br/>
[9] <a href="http://www.defora.org/os/wiki/display/3324/Roadmap">http://www.defora.org/os/wiki/display/3324/Roadmap</a><br/>
[10] <a href="http://www.defora.org/os/wiki/3426/Graphical-environment">http://www.defora.org/os/wiki/3426/Graphical-environment</a><br/>
[11] <a href="http://www.defora.org/os/wiki/3427/Distributed-environment">http://www.defora.org/os/wiki/3427/Distributed-environment</a><br/>
[12] <a href="http://www.net.t-labs.tu-berlin.de/teaching/thesis/#network_virtu">http://www.net.t-labs.tu-berlin.de/teaching/thesis/#network_virtu</a><br/>
[13] <a href="http://people.defora.org/~khorben/place/wiki/12/About">http://people.defora.org/~khorben/place/wiki/12/About</a><br/>
[14] <a href="http://www.defora.org/os/wiki/display/3323/Planned-developments">http://www.defora.org/os/wiki/display/3323/Planned-developments</a><br/>
<br/>
]]></description>
		</item>
		<item>
			<title>Over 10 thousand commits</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Sun, 13 Mar 2011 13:02:26 +0100</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/120/Over-10-thousand-commits</link>
			<guid>http://people.defora.org/~khorben/place/blog/120/Over-10-thousand-commits</guid>
			<description><![CDATA[According to Ohloh [1], I just went over 10,000 commits [2]:<br/>
<ul>
<li>DeforaOS 8173</li>
<li>hackable:1 1350</li>
<li>RunningBear 483</li>
<li>Whitix 13</li>
</ul>
for a total of 10,019.<br/>
<br/>
Now let's see if it was worth the effort...<br/>
<br/>
[1] <a href="http://www.ohloh.net/">http://www.ohloh.net/</a><br/>
[2] <a href="http://www.ohloh.net/accounts/khorben/widgets">http://www.ohloh.net/accounts/khorben/widgets</a><br/>
<br/>
]]></description>
		</item>
		<item>
			<title>Resurrecting RunningBear</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Sun, 27 Feb 2011 02:27:48 +0100</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/118/Resurrecting-RunningBear</link>
			<guid>http://people.defora.org/~khorben/place/blog/118/Resurrecting-RunningBear</guid>
			<description><![CDATA[Today (or tonight) I have finally managed to import most of the fixes pushed into DeforaOS since the last meaningful commits to the RunningBear project (around December 2008 I guess). This was motivated by a few reasons:<br/>
<ul>
<li>a bug report on memchr() in the DeforaOS libc [1]</li>
<li>NetBSD booting on N900 [2]</li>
<li>good progress on DeforaOS [3] [4]</li>
<li>same on hackable:1 [5]</li>
</ul>
Unfortunately, it still isn't good enough to support Xynth's user interface on the system [6]. But it's getting close enough, and I think the missing parts are:<br/>
<ul>
<li>support for setjmp() and longjmp() in the libc;</li>
<li>same for signal(), checking alarm() too;</li>
<li>for NetBSD, importing and adapting Linux' &lt;sys/kd.h&gt; to match the wscons API.</li>
</ul>
These are three hairy issues to tackle, but nothing's too hairy for a RunningBear (hey it's 3 am I'm allowed).<br/>
<br/>
With luck RunningBear could actually begin its career running on both the Openmoko Freerunner and Neo1973, HTC TouchPro and Nokia N900 smartphones, based on either Linux or NetBSD kernels. I'll try to do it with hackable:1 first though :)<br/>
<br/>
Last but not least: RunningBear is on Ohloh now! [7]<br/>
<br/>
The links:<br/>
[1] <a href="http://www.defora.org/os/project/bug_display/3474?bug_id=40">http://www.defora.org/os/project/bug_display/3474?bug_id=40</a><br/>
[2] <a href="http://www.netbsdfr.org/?p=1993">http://www.netbsdfr.org/?p=1993</a><br/>
[3] <a href="http://www.defora.org/os/news/3478/Summary-of-latest-releases">http://www.defora.org/os/news/3478/Summary-of-latest-releases</a><br/>
[4] <a href="http://www.defora.org/os/news/3484/Release-party-for-RunningBear">http://www.defora.org/os/news/3484/Release-party-for-RunningBear</a><br/>
[5] <a href="http://www.hackable1.org/">http://www.hackable1.org/</a><br/>
[6] <a href="http://xynth.sf.net/">http://xynth.sf.net/</a><br/>
[7] <a href="http://www.ohloh.net/p/RunningBear">http://www.ohloh.net/p/RunningBear</a><br/>
<br/>
]]></description>
		</item>
		<item>
			<title>First (unofficial) release of the DeforaOS smartphone environment</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Mon, 20 Sep 2010 16:51:02 +0200</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/96/First-(unofficial)-release-of-the-DeforaOS-smartphone-environment</link>
			<guid>http://people.defora.org/~khorben/place/blog/96/First-(unofficial)-release-of-the-DeforaOS-smartphone-environment</guid>
			<description><![CDATA[I finally have the pleasure to deliver the first version of the DeforaOS Smartphone environment, as featured in the hackable:1 distribution.<br/>
First, the direct links:<br/>
<ul>
<li><a href="http://www.defora.org/download/snapshots/hackable1/Hackable1-Openmoko-Freerunner-user-2010.09a-rootfs.jffs2">http://www.defora.org/download/snapshots/hackable1/Hackable1-Openmoko-Freerunner-user-2010.09a-rootfs.jffs2</a> (flash)</li>
<li><a href="http://www.defora.org/download/snapshots/hackable1/Hackable1-Openmoko-Freerunner-user-2010.09a.tar.gz">http://www.defora.org/download/snapshots/hackable1/Hackable1-Openmoko-Freerunner-user-2010.09a.tar.gz</a> (MicroSD)</li>
</ul>
If you like the artwork better than I do myself, you can also find a splash screen for u-boot there:<br/>
<ul>
<li><a href="http://www.defora.org/download/snapshots/hackable1/Hackable1-Openmoko-Freerunner-user-2010.07a-splash.gz">http://www.defora.org/download/snapshots/hackable1/Hackable1-Openmoko-Freerunner-user-2010.07a-splash.gz</a></li>
</ul>
I have gathered some release notes and documentation within hackable:1's wiki, which you will find there:<br/>
<ul>
<li><a href="http://trac.hackable1.org/trac/wiki/AvailableVersions/dse1">http://trac.hackable1.org/trac/wiki/AvailableVersions/dse1</a></li>
<li><a href="http://trac.hackable1.org/trac/wiki/DeforaOSSmartphone">http://trac.hackable1.org/trac/wiki/DeforaOSSmartphone</a></li>
</ul>
Of course, I gathered some screenshots as well. They can be seen here:<br/>
<ul>
<li><a href="http://www.defora.org/os/project/download/3343/Phone">http://www.defora.org/os/project/download/3343/Phone</a></li>
</ul>
Before I conclude, I am the first one to know that this release is far from perfect. If you feel like you have anything to say about it, you will be more than welcome to let it be known. There are a number of ways to do that:<br/>
<ul>
<li>contacting me personally as described on <a href="http://people.defora.org/~khorben/place/wiki/13/Contact">http://people.defora.org/~khorben/place/wiki/13/Contact</a></li>
<li>using DeforaOS' development mailing-list, as on <a href="http://lists.defora.org/">http://lists.defora.org/</a></li>
<li>filing a bug in DeforaOS: <a href="http://www.defora.org/os/project/bug_new">http://www.defora.org/os/project/bug_new</a> (create your account first at <a href="https://www.defora.org/os/user/register">https://www.defora.org/os/user/register</a>)</li>
</ul>
Now for the final words of this post, I have no reason to hide the fact that hackable:1 itself is probably a dead project already. I seem to be the last developer interested, which I find quite sad since I know no other project providing ready-to-flash Debian images for embedded platforms.<br/>
If you also have a need and desire for such a framework, I encourage you to let it be known. As for myself, I have in mind to improve and maintain such a way to generate ready-to-use images, probably as part of the DeforaOS project as well, unless somebody beats me to it.<br/>
<br/>
Anyway, for more literature on this work, feel free to check earlier blog posts and news announcements on this blog or at <a href="http://www.defora.org/">http://www.defora.org/</a> .<br/>
<br/>
Happy testing!<br/>
<br/>
]]></description>
		</item>
		<item>
			<title>Releasing a new snapshot of the DeforaOS smartphone environment on hackable:1</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Mon, 30 Aug 2010 14:57:56 +0200</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/95/Releasing-a-new-snapshot-of-the-DeforaOS-smartphone-environment-on-hackable-1</link>
			<guid>http://people.defora.org/~khorben/place/blog/95/Releasing-a-new-snapshot-of-the-DeforaOS-smartphone-environment-on-hackable-1</guid>
			<description><![CDATA[I have managed yesterday to release a new snapshot of the DeforaOS smartphone environment, as found packaged on top of the hackable:1 distribution. Unfortunately, there is still one obvious blocker bug before it can be easily tested as a real phone at the moment: as it seems, the modem &quot;forgets&quot; the PIN code a few seconds after accepting it, and is then unable to register correctly.<br/>
Of course, my current plan is to investigate and fix this as soon as possible (with a new snapshot). Yet, among the changes since the last release of the environment, you will already find:<br/>
<ul>
<li>a new finger keyboard, with popup keys (and using Gtk+' theme)</li>
<li>the addition of a phone log;</li>
<li>preferences windows for the phone application;</li>
<li>the return of the background picture, and a preferences window to easily change it;</li>
<li>last but not least, the final version of my initial attempt at SMS encryption.</li>
</ul>
With this, I will continue my work on the user experience:<br/>
<ul>
<li>fix and update the web browser (broken since the switch to Debian testing);</li>
<li>continue improvements to the finger keyboard (bigger keys, multiple layouts)</li>
<li>nicer Gtk+ theme and artwork if I manage (screenshots!)</li>
<li>more actual tests and usability improvements to the phone application;</li>
<li>power management;</li>
<li>GPRS support.</li>
</ul>
I have also begun to implement an application to configure access to wireless networks, with wpa_supplicant's help. It will take another while though.<br/>
<br/>
For more information, as always, check either <a href="http://www.defora.org/,">http://www.defora.org/,</a> the IRC channel of hackable:1 (#hackable1 on Freenode), the respective mailing-lists (devel@lists.defora.org, hackable1-dev@lists.hackable1.org...) or even, feel free to contact me directly of course: <a href="http://people.defora.org/~khorben/place/wiki/13/Contact">http://people.defora.org/~khorben/place/wiki/13/Contact</a><br/>
<br/>
And before I forget, the snapshot itself is announced and available there: <a href="http://www.defora.org/os/news/3394/New-snapshot-of-the-DeforaOS-smartphone">http://www.defora.org/os/news/3394/New-snapshot-of-the-DeforaOS-smartphone</a><br/>
<br/>
]]></description>
		</item>
		<item>
			<title>Improvizing a talk at Debienna</title>
			<author>khorben@defora.org (khorben)</author>
			<pubDate>Thu, 26 Aug 2010 18:54:19 +0200</pubDate>
			<link>http://people.defora.org/~khorben/place/blog/91/Improvizing-a-talk-at-Debienna</link>
			<guid>http://people.defora.org/~khorben/place/blog/91/Improvizing-a-talk-at-Debienna</guid>
			<description><![CDATA[I have been staying a few days in Vienna a couple weeks ago, where I happened to join a Debienna [1] meeting. As things went it felt appropriate to introduce hackable:1 [2] (and my current work on it) to this fine crowd. I have therefore quickly prepared a presentation, of which slides can be found there [3].<br/>
<br/>
It was called &quot;hackable:1 (and then more)&quot;, and I really appreciated this opportunity. See you guys!<br/>
<br/>
[1] <a href="http://www.debienna.at/">http://www.debienna.at/</a><br/>
[2] <a href="http://trac.hackable1.org/">http://trac.hackable1.org/</a><br/>
[3] <a href="http://people.defora.org/~khorben/papers/h1more/h1.html">http://people.defora.org/~khorben/papers/h1more/h1.html</a><br/>
<br/>
]]></description>
		</item>
	</channel>
</rss>

