View source for Stable Hybrid Release
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Stable Hybrid Release.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Stable Hybrid Release.
SHR is one of the many distributions that currently work on the Openmoko phones. You can compare a distribution with an Operating System on normal computers. It gives the phone all the software needed for operating. For more information about the different flavors, see distributions. Template:SHR
The Stable Hybrid Release (SHR) is intended to be a combination of the FSO, some of the Openmoko2007.2 GTK software, and the ASU that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.
Follow the project here: SHR Project Homepage
At first, SHR was introduced in order to use the Openmoko2007.2 GTK software with the new FSO. Things have changed.
FSO is the initiative by Mickey Lauer and crew to create a good D-Bus infrastructure which runs on the neos, among other devices.
FSO is by far the most stable & usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)
FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.
Other people are supposed to put a front end on FSO. So that's what we're doing.
So SHR is FSO, with us doing the necessary work to get some basic applications runing on a stable platform.
See the Developer Info on the upper right side of the SHR project page.
The list of tasks is available at the SHR Milestone page. Some information is missing this is why the table below is still valid.
Task | Status | Owner | Helping out | Last update | Comment |
Run the build host | Have server CPU time and disk space | paulproteus | 2008-07-03 | ||
Test & label good SHR releases | Awaiting builds | Nobody |
Completed tasks:
Task | Resolution | When resolved |
Set up launcher (home) page and document how to add new apps to it | The launcher will be the apps tab of openmoko-today2 | 2008-07-08 |
Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR | Done! SHR Project HomePage | 2008-07-08 |
fork media player for SHR | Done! | 2008-08-07 |
Statuses:
We're currently hosted by Ainulindale on svn://daria.forty-two.fr/shr . In order to contribute, you have to ask Ainulindale to get your public key on the server.
There is no need to download the code independently as it is automatically obtained when setting the development environment described in SHR Development.
Current applications (openmoko-dialer3 and openmoko-panel-gsm) use frameworkd. So in order to be able to build and test these applications, you have to build frameworkd and gsm0710muxd.
In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.
SHR uses FSO to interface to the hardware, so see the FSO architecture documentation, too. For how the openmoko*3 applications that SHR forked off 2007.2 access FSO, see http://www.calaquendi.org/om/lf.png.
From FSO:
Additionally:
This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.
From 2007-07-07
12:36 < wurp2> Everything *new* goes on OM projects site 12:36 < Ainulindale> I totally agree 12:36 < wurp2> Updates to 2007.2 apps go back into the home svn 12:36 < Ainulindale> paulproteus: no, you're an external cabal all by yourself :-) 12:36 < cb22> anyone planning on drawing up a roadmap? 12:36 < paulproteus> cb22, We can do that in Trac in fact. 12:36 < wurp2> And changes to the underlying release go as patches into our OE branch, yes? 12:36 < paulproteus> (or on the wiki page) 12:36 < paulproteus> wurp2, Right 12:36 < paulproteus> mwester, Sanity-check my terminology where I mess things up! 12:37 < Ainulindale> hmmm fuzzy for me but what should go in OM and what should go in OE ? 12:37 <@mwester> Sure 12:37 <@mwester> What do you mean by OM? 12:37 < paulproteus> Ainulindale, New software we write goes in the projects.openmoko.org. 12:37 <@mwester> right. 12:37 < Ainulindale> Ok so the wrapper for example 12:37 < wurp2> Anything stand-alone goes in OM (projects.openmoko.org) 12:37 < wurp2> yeah 12:37 <@mwester> So we will use projects.openmoko.org for as much as we can, and OE to build the distro. 12:37 < Ainulindale> Sounds right to me 12:37 < wurp2> Great! 12:38 <@mwester> We *will not* use the OM git repo, as that is owned and controlled by Openmoko the company...