login
Search
I for one definitely prefer GTK: as a toolkit I know and like it (in fairness I haven't developed for qt -- I have GTK and especially GTKmm), but in general I find I prefer the "look" of GTK-based apps better). I also felt the direction the phone was moving up until the ASU was looking very good and promising to me. It was much more along the lines of a handheld computer with phone featuers, which is what I want (the automatic sync with evolution was also very nice). I just noticed the other day that the scaredycat images are still based on the GTK stack -- I hope to be trying that out in the next couple of days. _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
I must have missed something... Can you post some links to explain what are the future plans for the Software Stack? Will GTK not be present any more? _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
IIRC GTK is still present and always will be. But there are no more plans to varous a complete software set based on it. Apparently, this is more or less considered a feature from the OM team that no GUI is prefered over the other. Which is why I wondered what happended to the previous plans to provide a complete "mobility software set". But perhaps the aim of OpenMoko has _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
I wondered the exact same thing. From the front page of the wiki: "Openmoko™ born as an Open Source project under GPL and LGPL license and dedicated to delivering an open software stack on mobile platforms, shipped its first product, the Neo 1973, on July 9 2007; and then, turned the project into a start-up company with one aim: create great mobile products using the Openmoko stack: Open. Mobile. Free." So the plan from the early days was to release an Open Source software stack, but this stack had to be radically altered at the 11th hour to get the hardware out of the door? Erm... _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Yes, with FSO we move to a UI toolkit agnostic standpoint. Where Guiologists are free. http://wiki.openmoko.org/wiki/OpenmokoFramework -----Original Message----- From: community-bounces@lists.openmoko.org [mailto:community-bounces@lists.openmoko.org] On Behalf Of cedric cellier Sent: Friday, June 27, 2008 8:53 AM To: List for Openmoko community discussion Subject: Re: Community Initiative GTK IIRC GTK is still present and always will be. But there are no more plans to varous a complete software set based on it. Apparently, this is more or less considered a feature from the OM team that no GUI is prefered over the other. Which is why I wondered what happended to the previous plans to provide a complete "mobility software set". But perhaps the aim of OpenMoko has always _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Basically Openmoko has stopped the development of the GTK stack in order to start a new stack called ASU. There are some 10.000 developers for GTK who can start any time making software for the Neo while there are very few developers for ASU, maybe 50. ASU is only used on the Neo whereas your GTK apps will run on the desktop or on the new MID devices like the ASUS eeePC right out of the box. Naturally for an open source developer it is a difference if the software will run on some hundred Neos or on some million PCs and MIDs. The GTK stack simply needs maintainance and bugfixing to remain a perfect platform for future developments. A really nice thing about the current GTK stack is the abilily to work in portrait and landscape mode just the same. It is just a lot of fun to automatically turn your screen while turning the phone in your hands. _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Am I right in understanding that the earlier software stack wrote GTK to the framebuffer, whereas the ASU required the incorporation of an X11 server to the image? Stroller. _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
I'm confused what this ASU stack is that you are talking about? When I look at the architecture picture on the framework page http://wiki.openmoko.org/wiki/OpenmokoFramework I don't see ASU. I see Gtk+ and Qtopia and Enlightenment (and X11). So this ASU stack is only used on the Neo and nowhere else? If ASU is Qtopia or EFL, then I'm not so sure that's true... Regards, -mike _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
A Qtpia build based on X11. (Qtopia is usually framebuffer) Fancy enlightenment launcher and applications menu. Qtopia base apps. And some individual new apps only seen on this platform. i think based It's both. -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community