 and the GTK application development on OpenMoco. And well, so I have to switch here to my first slide. So what am I going to talk about? I'm going to give you a quick overview about the platform, the software platform and the hardware platform of OpenMoco. It's quite often a bit difficult to get the information because currently it is still spread out across emailing, across the wiki and across different websites. This is currently in the state of change. OpenMoco has hired a couple of people who are going to maintain full-time the wiki and the technical documentation. They have hired a community manager whose name is Michael Schiello, who is there to make the communication between the community and the developers. So I'm myself an independent developer. And oops, I'm just playing here. Sorry for that. That's the wrong direction. I'm always playing with things that I have my fingers. Obviously a bad habit, I think. So the platform, so I'm myself an independent developer and the reason or the idea of talking here is simply to explain how easy it actually is to make development for a mobile phone, for an embedded device. Because I felt for me like I have been doing some GTK development before and I felt that the hurdle to actually get into development for OpenMoco seemed to be really high until we have figured out how it actually works. And once you know how it works, it is really easy. So giving you the overview of the hardware platform, what's currently happening, what's happening in future, then talking a bit about the software platform and then what you need actually for the development environment, how you're going to set that up. And I again pressed, no, I pressed on the wrong button here, development environment and then actually my favorite, how you get started in 15 minutes from sitting down on your computer having the first application running on the device. I'm going to talk a bit about the GPS application that I have been developing, which is called Tango GPS. Okay, so getting the right button here this time. So the hardware platform, and that always needs some explanation, so finally they figured out how they're going to call it. The first edition of the phone is called the Neo 1973. It's this one here and this is now out of stock. And the next edition is going to be called the Neo Free Render and is hopefully coming into sale in about April, about April is the idea. And what is the platform? And the really important thing is actually, don't look at it like a phone, look at it as a complete mobile computer, a Linux computer in this tiny form factor. I don't think like about how I have to develop for a phone. We have now a little computer in this size with everything with a screen on it, which is actually as performed as a computer probably six, seven years ago. So you have 120 megabytes of RAM inside of it. You have a screen here on this phone of 48640. You have, and that's why I say you have additionally have a GSM modem, so it makes it a phone tool. You have a GPS and on the next version of the phone of the free runner, you will have a Wi-Fi inside, so you can connect wherever you have wireless network. And last, not least, a very cool thing of the phone is you do have USB networking, a USB connector, and you have Bose, you have device mode and host mode. And that actually means that you can connect a printer to the phone. You can actually connect everything that is USB onto this phone. This is just cool. It's not a computer. It's not a phone, it's a computer. And yeah, so get some more ideas about far beyond of being on a phone because you have USB. Next phone actually, the free runner will have host mode which is powered. The current phone here does not have electricity, so you need to have a powered USB hub for actually doing something of it. Okay, I'll go one. Okay, the software platform here. And this is really the stripped down version because if you go on the website, you have these great little charts with all the components. But actually, the phone, the most important software components that you need to know about is the X. You have X running on it. Currently you have GTK running and you're using Open Embedded. Anybody here who has been using Open Embedded before? Some people, some few ones. Open Embedded, a word about Open Embedded. Open Embedded actually is some kind of Gen2. You have all heard, I guess, a lot, the Gen2 Linux distribution. And what Open Embedded is doing for you, you have the recipes and the recipes actually just grab the software from wherever it is, take it into your cross-compiling environment and just compiles everything for you and packages it. So the whole pain that you had like five, six, seven years ago developing for Open Embedded always having the development environment setting up the cross-compile tool chain. All that is gone now. All this hassle, all these headaches is being taken over by Open Embedded and you have nothing anymore to do with that. So I want to, one more time, I want to say that what definitely is, it's always difficult with Open Mocha to figure out what they really are going to do. It's a bit difficult to get all the information. What Open Mocha says they really want to do is they want to stick with X. They are going currently to port even Qtopia to X. You have even other platforms that I've seen outside. I think NewStep is developing for you too. So it will definitely be X applications. Everything that's currently running on the X you actually can easily port over to Open Mocha. GTK is something that will stay definitely in the open mobile world too because the Limo Foundation with all the big players intent to support GTK and what Open Embedded is a whole system by itself and for sure is going to stay for long. Okay, yeah. Here are two more words about Open Embedded. So it is Open Embedded is a built environment including cross-compiler. And the great thing is, again, that you have something that is called the mocha mail file which is doing an automatic setup. So what you do is you just get the mocha mail file from the web. You just make Open, make make file and then it just starts to get everything from the web fully automatic. It just sets up all your cross-compiling environment and it takes a bit more than 50 minutes that I have to admit actually it takes about eight, nine hours so you have to do something in between. But once that's set up, you have your complete cross-compile environment just sitting there ready for you to use. Okay, next. Yeah, how to get started in 15 minutes once you have done the eight hours. Okay, so here I have that written. So what you do, you get the mocha mail file, make stack up, get more than one cup of coffee because it now takes eight hours or maybe even 10, 12 hours, but it works absolutely well. It is perfectly well maintained and then what you do afterwards you make Open mocha development image which just gets the whole image compiled for you ready for flashing onto the device. And you have nothing to do, it's absolutely no brainer. That's the interesting, the important thing here to say. That's it. That's it. Just three steps and you can go. Okay, what have I been using here for the software I've been using Unyuta, Esma, IDE, and Glade because it just makes it so easy and the auto tools. And actually whatever kind of IDE you want to use, Unyuta simply produces for you the source code and you just can go later on. You build your distribution. So Unyuta makes for you the tab all and then you have in the next step the BitBake recipe and that goes again for Open Embedded. You have a recipe like this and in the recipe you just put into the location of your tab all and it just takes the tab all, automatically compiles it and produces a package out of it. That's it. So once again, in order to develop for this device what you have to do is you set up the Open Embedded build environment by the three steps that I just told you. You just get the local make file, make setup, make development image and in the next step you develop your application exactly like on the desktop. It's an application that runs on the desktop. You set up this BitBake file, actually this is just all that you need here and in the next step you do just execute the command BitBake here for me that is Tango GPS and then you have a ready-made package already. So like when you have your normal distribution for SUSE you would have the RPM or for Red Hat if you have the RPM for Dibby and you have the depths. So you come to this point and you have it ready-made there just for installing it on your phone. Okay, so few words about Tango GPS. It's actually just a mapping application which is designed for the Neo and it uses GConf, Dibo, SlipCurl and GDK PigsBuff so just to give you an idea of what I'm using in it and I'm developing on the desktop and just making the cross-compiler later on. So without anything I just develop on Unutor, make my distribution, have my tab all and open embedded just all does the rest for you. So nothing big. This is just a picture here of it and what I'm usually using here the upper part is just a normal menu. I have normal GDK buttons here that is just GDK buttons. I have a GDK slider, I have labels here and the bigger part is just a big GDK PigsBuff and what I'm using here for Tango GPS I'm using the maps from the OpenStreetMac project. I don't know if you've heard about that. OpenStreetMac is user-developed, user-made card data on OpenStreetMac. So actually we have no problems here with any copyright restrictions taking Google Maps or something like that because we can just use them for free and you see they have in many places already a perfect state. Okay, so future development what am I going to for sure and the next things that are going to come is a friend finder and that is so interesting again why not just having a phone here but it is a Linux computer plus a GPS and the idea is simply that you can go and you can find where your friends you can set up actually who can see you or who cannot see you so you have the choice for doing that then next thing that always goes together with any kind of GPS implications the point of interest so that you can put in your own point of interest you can share them with other people back and forth there's lots of development going on inside of OpenMorgo 2 and the real idea here is to use the Java protocol which actually supports XMPP2 so the XMPP protocol of Java supports GPS location data this way around so that you have both the possibility of doing communication, instant messaging and you can exchange your position with a well-known protocol which is supported by Google and others track management and for sure the last thing the interesting thing is OSM integration OpenStreetMap integration so for those that are actively tracking streets they have the chance of using Tango GPS for making streets for OpenStreetMap projects okay why to develop for OpenMorgo my last minute here it's fun I tell you I've seen that I did my test out before like with people putting it into the hands and everybody loves to walk around and see the red dot walking over the little map and see how many meters you have been walking it's really I just can tell you get one of the phones and enjoy it most open platform for now Google Android somebody where is the code hmm not open not open okay many things to be done for OpenMorgo you can easily get into it because there are many many little things where you just have immediate success like even just things like a lamp clock or lots of configuration things are still missing then why GTK it's still a good option for the future there are some most likely OpenMorgo is going to use the EFL to the Enlightenment Foundation libraries but with GTK you still have a good track into the future and for example Nokia is using some kind of GTK2 on their Mimo platform and last but not least I simply believe it's a great opportunity for us developing for an open form because we are now in the right position to make a difference for the future thanks a lot for listening applause