Great news!<br>I'll wait next release, then I want to help in building extra ipk packages...<br>d<br><br><div class="gmail_quote">On Mon, Nov 2, 2009 at 10:59 AM, Sander van Grieken <span dir="ltr"><<a href="mailto:sander@3v8.net">sander@3v8.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for the update!<br>
<br>
Ever since I saw that the SHR feeds didn't get updated for a while I compiled SHR myself<br>
from the shr/import branch, so I already knew that there was a lot of activity going on<br>
under the radar.<br>
<br>
For me the usage of opimd for contacts is the nicest new feature. It has a VCF backend, so<br>
I could just scp my Kaddressbook contacts over to the FR and have all my contacts<br>
available. nice!<br>
<br>
Graphic speed felt a little slower though, and the interfacing with FSO was broken in some<br>
places, like the power management. Also the power button didn't bring up the popup menu.<br>
But these are all findings of a few weeks back, so most will probably be long fixed<br>
already.<br>
<br>
Thanks again, looking forward to the next stable unstable release of SHR!<br>
<br>
grtz,<br>
<font color="#888888">Sander<br>
</font><div><div></div><div class="h5"><br>
<br>
On Sunday 01 November 2009 17:04:30 Thomas Zimmermann wrote:<br>
> For the SHR users that aren't reading the SHR mailing lists i'm forwarding<br>
> this message from spaetz:<br>
><br>
><br>
><br>
> Betreff: [Shr-User] What's going on in SHR land<br>
> Datum: Sonntag 01 November 2009<br>
> Von: Sebastian Spaeth <<a href="mailto:Sebastian@sspaeth.de">Sebastian@sspaeth.de</a>><br>
> An: <a href="mailto:shr-devel@lists.shr-project.org">shr-devel@lists.shr-project.org</a>, <a href="mailto:shr-user@lists.shr-project.org">shr-user@lists.shr-project.org</a><br>
><br>
> Hi all, for those of you few that do not live 24/7 in IRC land, here is<br>
> a not-so-brief update on what is happening in SHR land. No, we are not<br>
> all dead :).<br>
><br>
> There are a couple of major transitions that have slowed down new images<br>
> or indeed any updates in the SHR feed. Let me try to sum up a few and I<br>
> am sure others will chime in and list whatever I have forgotten:<br>
><br>
> - Transition from the obsolete kdrive-glamo driver to a proper xorg<br>
> server infrastructure. This took some time, but it appears that it is<br>
> working fine now. Don't expect any (initial) performance boosts, but<br>
> being on a regular xorg server and having a driver that is actually<br>
> being developed and maintained is a good thing for the future (thanks to<br>
> Weiss and others for some really hard work here).<br>
><br>
> - More fso...d goodness. Rather than having Mickey Lauer's python<br>
> prototyped phone backend, we are starting to his re-written bits and<br>
> pieces (coded in vala, which should give us a nice performance boost<br>
> over python). For the beginning we have the resource handling<br>
> (fsoresourced) on board and look forward to the next bits and pieces. I<br>
> know very little about the state of things here, so others might have<br>
> more information.<br>
><br>
> -New phone apps: As if that were not enough changes, the core team<br>
> (mrmoku, tasn, dos1, and others?) has started to redevelop the frontend<br>
> applications for SHR. the old ophonekitd was initially developed by a<br>
> guy called quickev who has been missing in action since quite some<br>
> months now. Don't ask ME why, but apparently the now design allows for<br>
> better/quicker/whatnot development. I'll let one of them speak out for<br>
> themselves about the motivations. Besides lots of work,this gives us<br>
> also a chance to redesign the screens and make the UI better. So goodbuy<br>
> ophonekitd and libphone-efl, welcome phoneui, and libphoneui-shr.<br>
><br>
> -Bernd Prünzler(spelling?) is kind enough to help out with some theme<br>
> development (BTW, you did know there is a theme contest going on, do<br>
> you? So, go and design and submit something already!). The default theme<br>
> has been designed for powerful desktops, and is using more transparency<br>
> and other fancy stuff than the slow graphics can do. He is developing a<br>
> theme that should be much faster on the Freerunner (but don't expect<br>
> miracles, the hardware will still be barely able to drive a full<br>
> VGA-resolution screen). So expect a big fight between dos1 (niebee<br>
> theme) and bernd (gry theme) for the fastest performance (while<br>
> retaining good looks).<br>
><br>
> Last but not least: what we had done the last few months, is basically<br>
> taking a fork of OpenEmbedded and developing from that. While this gave<br>
> us the stability to code apps without having others break our stuff (we<br>
> are quite capabable of doing that ourselves it seems :-) ), this led to<br>
> a quickly diverging SHR and OE tree. It was decided that we really<br>
> should include our stuff into OpenEmbedded proper, rather than just<br>
> doing our stuff in parallel. So we had first put all the stuff into an<br>
> "SHR/import" git tree which is in the openembedded code repository.<br>
> Next, mrmoku created the "shr/merge" tree which is kept in sync with the<br>
> OpenEmbedded tree and we ported all our enhancements there. The plan is<br>
> to take our bits and pieces from here and merge them into OE over time.<br>
> This is where we currently stand, we want to keep using the shr/merge<br>
> tree which gives us a current OE tree, but of courseby using more<br>
> updated components, lots of stuff was broken. The guys have fought<br>
> really hard in the last days (and weeks) to overcome compilation errors,<br>
> nonbooting phones, and crashing components. It seems we are now really<br>
> close. The new images compile fine (yay!), the phone actually boots, and<br>
> many of the crashes have been eliminated. AFAIK, we are currently still<br>
> stuck with a segfaulting dbus. As soon as these issues are ironed out,<br>
> mrmoku will continue to put updated SHR-unstable images and packages<br>
> out. This could take 1,2, or 4 days. I don't know how long and it<br>
> depends on how good things will turn out. But there will be a new image<br>
> soon. Expect some teething troubles with the new images at first (I am<br>
> not sure an opkg upgrade will work), but this is all fancy new stuff<br>
> that we are very happy about.<br>
><br>
> spaetz<br>
><br>
> _______________________________________________<br>
> Openmoko community mailing list<br>
> <a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
> <a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
><br>
<br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br>