David Lanzendörfer wrote: >> Yeh I like the plasmoids stuff and that's the kind of thing that I'd >> like to see, and I won't ask how difficult that is. > Cool! Already tried KDE-4.5? > Ist genious. The design enhancements and so on. > I have it also installed on my tablet-netbook. > >> Perhaps there is a >> way to make that stuff easier. I must have a look at Android and how it >> does it with apps. > Hmm. Well. Mokosuit does already some stuff, like Android has done it. > >> I did install mokosuit which did look great but for some reason when I >> ran it I could not get GSM coverage. I went back to SHR-U which is where >> I am at present. > I'm using SHR too. > >> Of the top of my head I wonder how difficult it would be to build a >> Distro which used QT on top of FSO. The obvious reply to that is that >> Enlightenment is lighter then QT. > There was already such a thing: > http://wiki.openmoko.org/wiki/Qalee > But its discontinued. > Perhaps we can rip out the libs and make our own project.
Fragmentation is not an option. We're actually currently maybe too fragmented as it is. The only reason I say that is in reality even if the son of FreeRunner arrived today, (and I'd buy it just to support the idea of it all) I'd still be running the same SW that I'm currently running on the FreeRunner. Three years on and I don't think it's polished. Is it three years? Seems that long anyhow. HW is not the biggest issue. OK it ain't perfect HW but if only HW was the issue a new phone would be a very welcome solution. I've recently gotten some time and sort of attacked the learning curve and tried, with a lot of help from people here and on IRC, to get my head around how the phone gui stuff fits together. I eventually got some sort of understanding of that and was about to start, hopefully, productive work two weeks ago. Then my build system just died. I've been two weeks working on getting a stable build system that I can actually do some work on. Yesterday it was gtk+ recipe which wasn't building. This morning it builds so now I'm hoping to build libphone-ui-shr and then if that works maybe the entire shr-u image. It don't help that the machine I'm on ain't up to it. Ordered a new laptop which I'll hopefully get before the middle of next week. All of the above has nothing at all to do with this thread but I just started ranting. I think the build system is far too flakey and I'm not sure how wise it is to track the org.openembedded.dev branch. I've used gumstix in the past and never had an issue building their oe tree. OK Gumstix probably has a person employed to pull in changes from org.openembedded.dev and make sure that they work before adding them to the gumstix branch. We don't have the luxury of a full time employee. The next time I get a full build working I'm never going to update again! I'll create a new tree and try it out and if it don't work revert to the old stable one. Actually I should revert to the tree from two weeks ago. </rant> Sorry about that, what can I say builds are taking too long, I've too much typing time. > >> Speaking of which my FreeRunner is a >> few years old and I need an upgrade in the open phone area. When is the >> new son of FreeRunner going to arrive? I do hope it's running on a >> Hummingbird processor, or whatever it's called. > The next will be an OMAP35xx. > But we are already organizing OMAP4440. > Lets see how it works. > It will have a keyboard in ANY case. > We are only still debating about the right CAD ^^ > > Well I do a webshop for presale, as soon as we got a working prototype :-) > > best regards > leviathan > > _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
