Re: Advanced dev kit
On 9/11/07, poncenby <[EMAIL PROTECTED]> wrote: > I've ordered the Neo Advanced GTA-01, which has not been delivered yet, > and was wondering whether the development hardware/software which comes > in this kit will be compatible/usable for development on the GTA-02 phone? The JTAG connector will fit both the -01 and -02 phones, so the extra bits in the advanced kit are compatible and usable for development. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Convince me NOT to cancel my order.
On 8/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I am not interested to disect the argument around axis of symmetry to help > you prove your childish argument. > If you are one of the disgruntled whiners about the Neo, then unsubscribe. It appear the tongue-in-cheek humour was lost on you. Sorry to upset :-) Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Convince me NOT to cancel my order.
On 8/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Read the post before you jump to conclusions. > The suggestion was to make at least the bottom square. I did: On 8/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I prefer the aesthetic look of the Neo and there is nothing more > comfortable to handle than a symmetric design. > > Point in case, a classical rounded edge shaped bar of soap is the > easiest to handleSquare soap never worked for me. The structure and order of your statements give the impression that your 'point in case' refers to your preference of symmetric designs. That example compares two symmetric shapes as if one were not. The square-bottomed Neo suggestion is still symmetric about two of the three axes as well :-P Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Convince me NOT to cancel my order.
On 8/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > I prefer the aesthetic look of the Neo and there is nothing more > comfortable to handle than a symmetric design. > > Point in case, a classical rounded edge shaped bar of soap is the > easiest to handleSquare soap never worked for me. If I have my definitions right, squares are also symmetrical :-P Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Screenshots? (was: Balancing simplicity with complexity)
On 8/21/07, Erland Lewin <[EMAIL PROTECTED]> wrote: > Sean Moss-Pultz wrote: > > We went back to the drawing board with OpenedHand -- lead by their vast > > experience with GTK+, Matchbox, and mobile user interfaces -- and > > redesigned an incredibly promising new interface. > > > Sounds great! > > Are there screenshots available anywhere? Yes, on the wiki. http://wiki.openmoko.org/wiki/Dialer/2007.2 for example... Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Linux embedded dev board
Just read about this development board on Make: http://www.uniconsys.com/devkit-ucn2410-c.html It has more than a handful of similarities with the Neo (ARM9, touchscreen, USB, JTAG, but no GSM or GPS), and may help scratch some itches for new ideas and toys that have been floating on the list for the last half year. I have no idea what they mean when they mention an included 'license agreement', but I suppose there are some unsavory limitations. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: sudden death of device
On 8/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > hi community, Please try the device owners list :-) http://lists.openmoko.org/mailman/listinfo/device-owners Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Google Phone is coming...
On 8/4/07, Jeremy G <[EMAIL PROTECTED]> wrote: > On 8/4/07, Harrison Metzger <[EMAIL PROTECTED]> wrote: > > Why doesn't Google join Openmoko/Neo? > > Google has too many closed-source applications to fit with the > completely open nature of OpenMoko, and likely, they intend to use > their phone as an avenue to promote their applications, closed and > open alike. Well, yes and no. Why couldn't they order units and flash whatever they want on them? That's what the Neo //is// about. Sure, it wouldn't be very considerate to close everything afterward, but it's certainly feasible, if only FIC could make as many phones as Google would order. Along those lines, if any other company was watching this developer release (and the many stumbles), they'd know to stay away from FIC until they had their supply chains and order process more robust and sustainable. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OK, the forum is coming..
On 7/22/07, Mickael Faivre-Macon <[EMAIL PROTECTED]> wrote: What about creating a google group ? You can still receive each mail individually if you want, or watch it as a forum. Everybody is happy. And have the threaded view for those that want it. You can view flat as well threaded: http://groups.google.com/group/google-code-hosting/browse_frm/thread/844ef0e6ed264357/# flat: http://groups.google.com/group/google-code-hosting/browse_thread/thread/844ef0e6ed264357?tvc=2 Same discussion :-) Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OK, the forum is coming..
On 7/22/07, Joe Friedrichsen <[EMAIL PROTECTED]> wrote: In regards to my suggestions, both LQ and Google groups keep discussions flat like a phpBB board. You can of course quote people to explicitly bring context to your reply. Actually, Google Groups //does// support properly threaded reading on the web. Take a look at this thread: http://groups.google.com/group/google-code-hosting/browse_frm/thread/844ef0e6ed264357/# for an example. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OK, the forum is coming..
On 7/22/07, Henryk Plötz <[EMAIL PROTECTED]> wrote: Based on http://aktuell.de.selfhtml.org/artikel/gedanken/foren-boards/ (sorry, it's in German, but there are clarifying pictures) I'd make a distinction between a forum, which is inherently threaded (not in the phpBB-sense), and a board, which is flat (like phpBB). That's a great clarification. I stand corrected: phpBB "forums" aren't threaded in the same sense as a discussion forum. In regards to my suggestions, both LQ and Google groups keep discussions flat like a phpBB board. You can of course quote people to explicitly bring context to your reply. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OK, the forum is coming..
On 7/22/07, Sebastian Krause <[EMAIL PROTECTED]> wrote: As far as I could see it in all phpBB forums until now, the messages are sorted by the date and time are posted, but by whom they're answering to. I think you meant to say: "As far as I could see it in all phpBB forums until now, the messages are [not] sorted by the date and time [they] are posted, but by whom they're answering to." phpBB forums are sorted by all three characteristics: date, time, poster. As I'm sure you know, any single phpBB forum may be divided into sub-forums or categories. Each category has threads in it, with the newest threads at the top (sorting by 'time and date'). A thread is a group of posts, the first post being the thread's seed and the others being replies to that post (sorting by 'whom they're answering to'). When reading a thread, the posts are also displayed with the seed at the top and the replies below, in chronological order (a second sorting by 'time and date'). While not a phpBB forum, LinuxQuestions.org is a great example of how all three characteristics are used to group and display the discussions. phpBB isn't that different from LQ's default, which lets you tweak a lot of display preferences (maybe you like oldest on bottom? no problem). To add more suggestions to the pile, maybe a new sub-forum in "Linux - Distributions" area of LQ would helpful. At least for OpenMoko. . . I don't know where/if the Neo and later devices would fit. Also, another way to have a usable 'forum' (both from mail and web) is a Google Group. Google groups offer RSS feeds as well, file and page hosting, and moderation. Do I need to mention that search is also a feature ;-P Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Marketing... aGPS uses
On 7/21/07, Krzysztof Kajkowski <[EMAIL PROTECTED]> wrote: 2007/7/21, Adam Krikstone <[EMAIL PROTECTED]>: > AGPS is where focus needs to be. This natural (and free) comparative > advantage needs to be developed to attract new developers and customers. > > 5. Auto sync location dependent - arrive at home wifi/bt turn on and > attempt to sync, sync when movement is sensed in the morning > Hi! That's a wonderful list you made! I have one doubt though - how well would that AGPS chip work, especially in buildings. I have Garmin GPS which does not get signal reception if anything is between it and GPS satellite so it does not work in my appartment or shows locations with massive error. Does anyone tested AGPS yet? You can see it working inside a building (FIC headquarters) on YouTube: http://youtube.com/watch?v=5D6i6vLlhGA Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Marketing... aGPS uses
On 7/20/07, Adam Krikstone <[EMAIL PROTECTED]> wrote: AGPS is where focus needs to be. This natural (and free) comparative advantage needs to be developed to attract new developers and customers. Holy schnikees! What a list o_0 Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Sorting out development interests
On 7/18/07, Daniel Robinson <[EMAIL PROTECTED]> wrote: I think the thing that is missing is for people to find collaborators to work on these projects. Is this the right forum? There is http://projects.openmoko.org/ and folks can discuss development ideas on a project-specific list, but I don't think the core team has even thought about administering it lately considering that the most recent project was created three months ago. I also remember reading a while back that new projects would propose/announce themselves on this list as part of the application process. So maybe by starting a thread for the project you want, you can get some attention for your GForge application. We just can't cut the core team any slack :-) First, we want phones, now we want projects, next we'll want a cookie! Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Shipping update
On 7/17/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: Sorry for our sub-optimal handling of the logistics for phase 1. We promise to get this fix in the _very_ near future. Heh, you can tell how often FOSS folk sell things, and how experienced FIC is at direct-to-user sales. This first round felt like amateur hour :-D Now I can put money aside for SH2. Glad to see things getting in order! Keep up the diligence :-) Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Support for Left handers
On 7/14/07, Jeff Andros <[EMAIL PROTECTED]> wrote: we need a way to select which on-screen item to scroll if there's more than one (for simplicity's sake this should be a rare occurance... but web sites love scrollable elements). Yes, good point; and there is one method already. Have you ever edited a long passage in a text box on some web site? A Wiki page, or blog entry, or holiday email come to mind. And when editing, did the mouse have a scroll wheel? How did scrolling change depending on the location of the mouse pointer? (man, what a bunch of rhetorical questions, sorry) We can adapt that behavior to the Neo. Finger moving in the text box? Then scroll that. Finger moving in the document? Then scroll that. For later devices it will be important to have scroll bars as they may not have touch screens. But use the hardware while we've got it! Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Support for Left handers
On 7/14/07, Ortwin Regel <[EMAIL PROTECTED]> wrote: Shouldn't the spinner thing replace scrollbars, though? What else would it be for? Here here! I very much like the idea of not having scrollbars. If anything, maybe a narrow indicator that shows relative position in the document. We have a *touch screen* folks! Why use a widget that was made to replace tactile interaction when the whole screen can be a widget? Seems like a little overly zealous retrofitting. . . This carburettor will fit on the electric car, dag nab it! ;-) Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buying FIC stock long
On 7/12/07, Alexander E Genaud <[EMAIL PROTECTED]> wrote: PS - Clarification: Is FIC a publicly traded company and if so, what is the ticker code (or a division closest to OpenMoko) and upon what exchange is it traded? Looks like the TSEC/TAIEX: http://203.74.228.63/t40/e_C_public.jsp?strMode=1 or if the IP address is too scary: http://www.tse.com.tw/en/products/stock_code.php and click on 'Public Companies'. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: What apps will be included with GTA02 phone?
On 7/12/07, Jonas Berlin <[EMAIL PROTECTED]> wrote: I'm a bit concerned that the community will have these GTA01 phones when writing software, yet GTA02 has new features that the community can only simulate. For me this sounds like the GTA02 will have cool hardware, but the greater part of the community will only begin to write cool software for it after it gets released. While SH1 owners cannot directly write for the new hardware in GTA02 (WiFi / accelerometers), they will be writing and expanding a lot of the other core applications (contacts, dialer, calendar, timer, etc.). But I share your concern that well-tested and intuitive software will be the most important thing to a new end-user (even though they may not think, "I want well-tested and intuitive apps."). It will be difficult for the community to write for the new hardware without access to it. Maybe the wizards in the core team will make the first whiz-bang apps for the new hardware. My hope is that the slower processor in SH1 will encourage (or force ;-) the community to write efficient and simple code and not encourage them to just let it slide until the newer/faster processor is available. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Get them while they're still hot!
On 7/8/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: Neos are waiting in customs just outside our factory in SuZhou. Early this week, they will start their journey to FIC America in Fremont, California. We're sending them by air so they should arrive really fast. (We'll update you as soon as we know more tracking information.) So the FCC likes the Neo? FIC++ Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko ads now on youtube
On 7/4/07, Luit van Drongelen <[EMAIL PROTECTED]> wrote: Well, OpenMoko isn't really 'here' yet, is it? It's public, true, but it's not final. Far from it, IMHO. Then OpenMoko will never be here and final in the sense that the Linux kernel will never be here and final. ;-D Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko ads now on youtube
The funny thing is that OpenMoko is here //now//. It's the phone that's coming soon :-) Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New wishlist item: Side-mounted touch strip sensor
On 6/19/07, Jordan Anderson <[EMAIL PROTECTED]> wrote: I have a touch strip on my HTC Excalibur, and one of the first things I did was shut it off -- simply handling the phone was causing the volume to go up and down, or my browser to go back. Obviously a personal thing, but with a physical button it's easier to remember that it's there. True enough. My phone is a V401D by Mitsubishi, and its shape and design didn't really lend to unintentional scrolling. The touch strip is on the side in a place that is easy to reach with a thumb, but not in the place where you would naturally hold the phone. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New wishlist item: Side-mounted touch strip sensor
On 6/19/07, Ortwin Regel <[EMAIL PROTECTED]> wrote: I could also see some applications for a Blackberry style wheel, for example volume control and scrolling. I don't think using a futuristic sensor would be a good idea because we already have an analog device without feedback which is the touchscreen. Futuristic for some countries :-) My Japanese mobile has a touch strip, and I bought it in Q2 2004. It made scrolling through texts and sites very easy and the friction provided by the slightly rubbery strip made for some great feedback (touching a touch screen is different than sliding on a touch strip, despite the misleading names). Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Air War - WallSteet Journal June 14, 2007
On 6/14/07, Mark McClellan <[EMAIL PROTECTED]> wrote: Today's WSJ has an article on the frontpage about US wireless carriers and device makers being in conflict over the features that consumers are actually offered. I look forward to OpenMoko changing the wireless landscape forever FIC still needs the FCC's blessing :-) But once the Neo gets the stamp of approval, its flexibility will be very stunning. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openness (was RE: Concern for usability and ergonomics)
Michele Manzato wrote: Don't get me wrong, I can guess (some of) the reasons behind the plain words. But then I wonder whether there is really any transparency in the development of Neo/OpenMoko? I can sympathize with you to an extent. I fully support the concept and goal of OpenMoko. If I didn't, then I would have to say that I like one distro but not another. On the other hand, I also feel a bit frustrated at the more-than-intermittent silence and side-stepping updates that do get to the list. However, I don't think the problem lies with FIC, or at least entirely with FIC. My frustration comes from my expectations not being met, so then I start to look at my expectations. Are they reasonable? Are they justified? The folks at FIC haven't outlined how much information they will share, nor how often they will share it. And so when hearing 'OpenMoko is a libre OS for a phone, and the Neo will be the first to run it,' I projected my ideas of a FLOSS project onto FIC. That is not necessarily the case, though. Given that launching new hardware is incredibly difficult, and predicting its development time line is even more difficult, I was surprised to read concrete dates at all. I'm more familiar with after-the-fact milestone-based updates: * "We've just finished the latest revision and we're waiting for a few new prototype units." * "The new units are here, but they're buggy. We're chasing the bugs down." * "The bugs have been dealt with, we're ordering some new units." and so on. Perhaps this is a learning experience for everyone. FIC can ease some of the tension in the community by outlining what they intend to be 'open' in their processes. What they will share, how much, and how often. They can also relieve some of the pressure on themselves by not forecasting specifics. And the community can give FIC the benefit of the doubt. The software is real, it is open, and it is available now. Real working units exist and are being used. The community can also allow FIC to change its behavior. I suspect that FIC was excited at the beginning and shared information prematurely and that we took that as par for the course. So now that they have learned a bit about launching a new product and interacting with 'the bazaar', I imagine that that FIC will adapt as they see fit. Please allow them to grow :-) It wouldn't help them in any way to alienate the developer community, but I don't think they are actively trying to do that. Their recent inaction could speak to growing complacency on their part, but I don't suspect that either. I only see misleading expectations, partly from FIC's opening strategy and the assumed definition of 'open' in regards to product development. See you on the pre-order list, Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMoko != Neo1973 (Was: Openness (was RE: Concern for usability and ergonomics))
On 6/12/07, Rod Whitby <[EMAIL PROTECTED]> wrote: OpenMoko (the registered organisation, separate from FIC the company who is creating the first piece of hardware designed for the OpenMoko software) never promised open hardware. They promised open software (the OpenMoko software, which is being developed *completely* in the open), and they gave some dates that they *expected* (not promised) FIC (the hardware company) to be ready to sell some hardware (the Neo1973) that the OpenMoko software runs on. Yes, most of the hardware designs and schematics aren't distributed, but there are shadows of scraps here and there thanks to Werner ( http://svn.openmoko.org/developers/werner/usb-pullup/new.spice ). The Neo appears to be a well-assembled collection of chips and parts not designed or fabbed by FIC. They took some Legos and made a remarkable product. It's like a capstone design project on steriods. Given that this phone is meant to be opened and tinkered with, I imagine that schematics could be drafted without too much strain. The phone could then be //conceivably// reproduced. However, I don't know at this point how valuable open hardware would to an individual be since silicon and copper aren't that easily modified or produced at home. Quality surface-mount soldering and RF noise are just a few of the smaller hurldes to jump over. Software has the advantage for now :-) Those simple text files are just too easy to change! Until we get our own fab-labs, Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unbundling of phone services
On 6/12/07, Robin Paulson <[EMAIL PROTECTED]> wrote: so my question is: is there a similar movement anywhere for the equivalent of LLU for mobile phone networks? i.e. allowing other operators to use networks of vodafone/state-owned telco/sprint/whoever at reasonable price? most countries don't have monopolies providing mobile services (even nz has 2 providers), but they still act as though they are monoplies, providing (in my experience) vastly overpriced, very limited services If I understood you correctly, there is something like this in the US. These mobile carriers are called MVNOs (Mobile virtual network operators -- http://en.wikipedia.org/wiki/MVNO ). There are a number of options for service from MVNOs, but it's nearly all prepaid. The MVNOs in the US were reviewed by C-Net, and you can read about it here: http://reviews.cnet.com/4520-3504_7-6260217-5.html?tag=arw . It definitely feels like you're making a deal with devil when you sign up for any kind of mobile service anywhere. I just bought a T-Mobile prepaid phone, but I haven't used a US carrier yet so I'm not sure what to expect. My best experience so far was with Vodafone in Japan, but when I was in Australia, Optus wasn't too bad. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GUI and Energy
Hypermiling with the Neo? Nice :-) On 6/8/07, Gilles Casse <[EMAIL PROTECTED]> wrote: * Energy-Efficient Graphical User Interface Design http://www.ruf.rice.edu/~mobile/publications/eegui_accepted.pdf From the abstract -- "We demonstrate that energy-efficient GUI (E2GUI) design techniques can improve the average system energy of three benchmarks (text-viewer, personnel viewer, and calculator) by 26.9%, 45.2% and 16.4%, respectively. Average performance is simultaneously improved by 23.7%, 34.6% and 19.3%, respectively." Some general points -- * "proper selection of content placement can improve GUI interaction speed" * "GUIs with better color schemes and contrast ratios are easier to read" * "a GUI should present as few choices as possible" * "a GUI should utilize as much screen area as possible for widgets to be hit. Widgets that are supposed to be hit sequentially should be placed near each other." The examples that the authors give and test have a few new ideas and the rest feel like common sense. One new idea for reading text was neglecting scroll bars and instead using invisible half-screen buttons for page up and page down. The top half of the screen was a page up button, and the bottom half was a page down button. The power-saving color schemes were awful. It looks like the iPhone doesn't care to sip from its battery. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SVHMPC] concept phone with only a touchscreen for UI
On 6/5/07, Bradley Hook <[EMAIL PROTECTED]> wrote: Steven Milburn wrote: > Personally, I'd like to see a touchscreen with some type of ability to > raise > dimples at any point under software control. Kind of like a braille reader > on acid. If only such a thing existed. (does it?) One word: expensive. Refreshable Braille displays do exist, and even the cheapest functional ones make the current cost of the Neo look like pocket change. Incorporating this sort of technology into the Neo would not only be expensive, but the mechanics of these things require a lot of maintenance, not a fun thing to have in a phone. While refreshable Braille on a touch screen would be the final goal for accessibility, I think the OP was talking about mimicking buttons, which I imagine wouldn't need to be nearly as precise. One 'bump' per finger-space requires a much smaller resolution than six bumps per finger-space (as is used in Braille). Mechanical movement is still the challenge, but reducing the actuators by a factor of 6 is a big help. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FCC Approval
It would be great to know if any of the P0 folks are US-based as well. The majority sound European, save Rod :-) Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ubuntu Mobile and Embedded
On 5/8/07, Vincent <[EMAIL PROTECTED]> wrote: On 08/05/07, Marcin Juszkiewicz <[EMAIL PROTECTED]> wrote: > > But GMAE project (which you talk about) was created by companies which > already work in embedded world - for example OpenedHand (which work on > most of OpenMoko framework). Isn't that even better? Ubuntu mostly works closely with Gnome, so if GMAE was created by companies which already work in the embedded world then Ubuntu can profit from that experience. In reading this thread, the tone appears to be the opposite: people are hoping that OM et al can benefit from Ubuntu's efforts, not the othe way around. Certainly collaboration and help will be going in both directions, so I'll be happy either way it goes since it will be both. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Some light ahead...
I'm certainly grateful for all of the lost sleep and long flights. Thanks for your diligence! I'm eagerly awaiting the pre-order stage and news about the phase 1.5 discount ;-) sigh... you give a meter, we take a mile. Joe ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community