Re: New Oceans
First of all congratulations to the FIC team. Can someone enlighten us about which configuration (base/advanced) should one order? What is the use of the debug board? What cannot I do without it? Shall I be able to use it with GTA02 and later versions? Thanks, Emre On 6/28/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: Starting July 9th, we will launch openmoko.com and start taking orders. We're going to have two configurations: Neo Base -- everything the mobile application developer needs to enjoy the benefits of the first freed phone, the Neo 1973: * Neo 1973 (GTA01B_v4) * Battery * Stylus * Headset * AC Charger * Phone Pouch * Lanyard * SanDisk 512MB MicroSD Card (2x) * Micro USB Connectivity Cable Neo Advanced -- everything the mobile device hacker wants to get down and dirty with the first freed phone, the Neo 1973: * Neo 1973 (GTA01B_v4) * Battery (2x) * Stylus * Headset * AC Charger * Phone Pouch * Lanyard * SanDisk 512MB MicroSD Card (2x) * Mini USB Connectivity Cable (2x) * USB Host Mode Cable * Debug Flex Cable * Debug Board v2 (JTAG and serial console) * Ruggedized Toolbox with shoulder strap * Guitar Pick (for opening case) * Torx T6 screwdriver The delays have been expensive for us and annoying for you. We've decided that instead of setting up a complicated return or tracking system to remember who gets a discount for GTA02, we going to give you _all_ a discount on GTA01. We're going to sell the Neo Base for $300. The Neo Advanced will be $450. GTA02 (AKA: The Mass Market Neo 1973) is on schedule to go on sale in October. It will have the following new hardware components: * 802.11 b/g WiFi * Samsung 2442 SoC * SMedia 3362 Graphics Accelerator * 2 3D Accelerometers * 256MB Flash We will sell this device through multiple channels. Direct from openmoko.com, the price will be $450 for the Neo Base and $600 for Neo Advanced. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New Oceans
Fantastic news, Thank you sean for the long announcement, I tell ya for all the wait, it was worth it. Now am gonna take a large printout of the announcement and paste it outside my room to inspire my parents to increase my allowance. :P Onto World domination! Regards Sudharshan S ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Clarification Rant
Ryan Prior writes: > If FIC/OpenMoko could run some sort of deal where I could buy the > GTA01 for $300 and send it back in for a $150 or $200 upgrade when the > GTA02 comes out, I would buy into that. I wouldn't be making decisions at that point -- it'd be an absolute no-brainer. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New Oceans
Outstanding news. Thanks again to you and the rest of the team for your vision, judgement, and determination. Full speed ahead into the new waters! :-) Mark C. On Thu, Jun 28, 2007 at 09:20:13AM +0800, Sean Moss-Pultz wrote: > Dear Community, > > Andre Gide once said, "Man cannot discover new oceans unless he has the > courage to lose sight of the shore." Sexism aside, I can't think of a > better way to describe our adventures this past year. > > Around the end of March, we were three months behind schedule. Critical > hardware bugs were being discovered almost weekly. I had just returned > from an exhausting trip around the world. Harald landed in Taiwan the > following week. One look at his face and I knew he was in basically the > same depleted state I was in. But, we were both dedicated to keep > pushing forward. We've come to realize, largely because of your support, > that failure is not an option for this project. > > For the people pushing this project, an open phone is not really even a > product. It's the very embodiment of our vision of technology. We > absolutely, passionately, believe that something as fundamental to our > lives as the mobile phone must be open. > > OpenMoko has become far bigger than just a small group of people trying > to build an open mobile platform. I can tell you for sure, things will > never be the same again inside FIC. To their credit, whole departments > and divisions have been reorganized to maximize the opportunity for > OpenMoko. This is the reason for my absence from this list for so long. > > The people inside FIC are amazingly open-minded. Our CEO and Chairman > are the two greatest supporters inside this company. Earlier this month > they did something courageous and support of the communities commitment. > The entire mobile communications division was restructured to build > devices for OpenMoko. And OpenMoko -- the project will officially become > OpenMoko -- the company. This is how much they believe in us. This is > how much faith they have that we will be successful. > > What does all this mean to us as a company and community? > > In one word: focus. > > We now have full control over the future of OpenMoko and the resources > needed to give it every possible chance of succeeding. Behind us (well > actually still in the same building :-) sits an supportive 800 pound > gorilla in the OEM/ODM world, eagerly waiting to work with us to make > our dreams a reality. > > OpenMoko -- together with all of you in the community -- will design, > from the ground up, open devices and write the free software platform > that powers them. FIC will build the hardware and help us set phones > free around the world. This is about the most perfect relationship we > can think of. Sure there will be rough times ahead. If it were easy, you > know who would have done this long before. Making new things is never > easy. But we're in this together. This project has changed me, changed > you, and changed FIC. Hopefully, one day, this project will change the > world. > > Now that OpenMoko is officially a company inside the FIC Group, > blueprints of our office modifications cover the desk and walls where > I'm sitting. Writing this letter to you all is finally giving me time to > reflect on this thrilling roller coaster ride. Sorry for putting so many > bits into your inbox. But I just can't help it. It's been months that we > could hardly step back and see things from a big picture. Now, I really > don't think I've been this excited since the day I got my first set of > Lincoln Logs. For those of us that love to build new things, Taiwan, > especially now at FIC and OpenMoko, is a great place to be. > > So here's the point of this email, finally after more than one year, > we're entering into a new ocean. > > In our factory in China, 400 Neos are waiting for you all. Another 600 > will be ready before next week. More are queued up waiting for us to say > go. > > We've had a particularly challenging time trying to setup the online > infrastructure and figure out how to ship these phones. Sometime later > today or early tomorrow we're going to make another announcement asking > for some advice. > > (Here come the details.) > > Starting July 9th, we will launch openmoko.com and start taking orders. > We're going to have two configurations: > > Neo Base -- everything the mobile application developer needs to enjoy > the benefits of the first freed phone, the Neo 1973: > > * Neo 1973 (GTA01B_v4) > * Battery > * Stylus > * Headset > * AC Charger > * Phone Pouch > * Lanyard > * SanDisk 512MB MicroSD Card (2x) > * Micro USB Connectivity Cable > > Neo Advanced -- everything the mobile device hacker wants to get down > and dirty with the first freed phone, the Neo 1973: > > * Neo 1973 (GTA01B_v4) > * Battery (2x) > * Stylus > * Headset > * AC Charger > * Phone Pouch > * Lanyard > * SanDisk 512MB MicroSD Card (2x) > * Mini USB Connectivity
Re: Preorder
Vruyr F. Gyolchanyan wrote: I'm ready to by one too. But what about delivery to Moscow (actually to Russia in general), I ordered Qutopia GreenPhone, and the delivery was canceled and sent back to US as it received to UK. The delivery company was FedEx, and they said that "Mobile phones are prohibited commodity for Russia to import". Also I had problems when I was expecting to receive a cell phone from Canada. Lucky me that the phone was certified for Russia. Hope to figure out how to get openmoko to Moscow when it will be available. Best regards, Vruyr F. Gyolchanyan. P.S. Sorry for my English. P.P.S. I'm also in Moscow. the usual solution to these issues is to go visit somewhere for a while, and take the device back with you. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Stylus, the iPhone, and multi touch screens
I personally don't like the idea of using a stylus, or rather, needing one, but I've read that there will be certain tasks/apps that will have a UI designed for a stylus. I saw a video of the iPhone in operation and all tasks were easily performed with the fingers. Does the multi-touch screen make this easier somehow? Also what exactly is multi-touch and is it near the top of the hardware addition list? -Cailan ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Clarification Rant
If FIC/OpenMoko could run some sort of deal where I could buy the GTA01 for $300 and send it back in for a $150 or $200 upgrade when the GTA02 comes out, I would buy into that. agreed, but really, what would they do with it? I could see /maybe/ a slight discount... but 150+ is a lot as I am not a developer, I think I am best off waiting until the October release. Wifi is too useful to pass up! ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Clarification Rant
On 6/6/07, Gabriel Ambuehl <[EMAIL PROTECTED]> wrote: On Wednesday 06 June 2007 01:12:18 Ryan Prior wrote: > I'm in the same situation. I need a phone, no question. The Neo 1973 is the > phone I want, no question. The question is this: will the Neo1973 with WiFi > be available by the time I cannot live without a phone for any longer? How about getting the cheapest phone you can find? Around here there are 15EUR phones without contract (but sim locked to one carrier)... That's my plan for now - I need a reliable phone to use alongside my GTA01 (if I buy one - it's hard to justify buying a GTA01 when the GTA02 will have WiFi, something I will use a lot.) If FIC/OpenMoko could run some sort of deal where I could buy the GTA01 for $300 and send it back in for a $150 or $200 upgrade when the GTA02 comes out, I would buy into that. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Clarification Rant
On Wednesday 06 June 2007 01:12:18 Ryan Prior wrote: > I'm in the same situation. I need a phone, no question. The Neo 1973 is the > phone I want, no question. The question is this: will the Neo1973 with WiFi > be available by the time I cannot live without a phone for any longer? How about getting the cheapest phone you can find? Around here there are 15EUR phones without contract (but sim locked to one carrier)... pgper5OJTwjNv.pgp Description: PGP signature ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
the keyboard on the competition
someone on this list had a similar idea for enlarging number keys i think, they would appear or resize depending on context iirc? http://www.apple.com/iphone/usingiphone/keyboard_large.html ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re:New Oceans
Thanks for the information! Decisions, decisions... ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
New Oceans
Dear Community, Andre Gide once said, "Man cannot discover new oceans unless he has the courage to lose sight of the shore." Sexism aside, I can't think of a better way to describe our adventures this past year. Around the end of March, we were three months behind schedule. Critical hardware bugs were being discovered almost weekly. I had just returned from an exhausting trip around the world. Harald landed in Taiwan the following week. One look at his face and I knew he was in basically the same depleted state I was in. But, we were both dedicated to keep pushing forward. We've come to realize, largely because of your support, that failure is not an option for this project. For the people pushing this project, an open phone is not really even a product. It's the very embodiment of our vision of technology. We absolutely, passionately, believe that something as fundamental to our lives as the mobile phone must be open. OpenMoko has become far bigger than just a small group of people trying to build an open mobile platform. I can tell you for sure, things will never be the same again inside FIC. To their credit, whole departments and divisions have been reorganized to maximize the opportunity for OpenMoko. This is the reason for my absence from this list for so long. The people inside FIC are amazingly open-minded. Our CEO and Chairman are the two greatest supporters inside this company. Earlier this month they did something courageous and support of the communities commitment. The entire mobile communications division was restructured to build devices for OpenMoko. And OpenMoko -- the project will officially become OpenMoko -- the company. This is how much they believe in us. This is how much faith they have that we will be successful. What does all this mean to us as a company and community? In one word: focus. We now have full control over the future of OpenMoko and the resources needed to give it every possible chance of succeeding. Behind us (well actually still in the same building :-) sits an supportive 800 pound gorilla in the OEM/ODM world, eagerly waiting to work with us to make our dreams a reality. OpenMoko -- together with all of you in the community -- will design, from the ground up, open devices and write the free software platform that powers them. FIC will build the hardware and help us set phones free around the world. This is about the most perfect relationship we can think of. Sure there will be rough times ahead. If it were easy, you know who would have done this long before. Making new things is never easy. But we're in this together. This project has changed me, changed you, and changed FIC. Hopefully, one day, this project will change the world. Now that OpenMoko is officially a company inside the FIC Group, blueprints of our office modifications cover the desk and walls where I'm sitting. Writing this letter to you all is finally giving me time to reflect on this thrilling roller coaster ride. Sorry for putting so many bits into your inbox. But I just can't help it. It's been months that we could hardly step back and see things from a big picture. Now, I really don't think I've been this excited since the day I got my first set of Lincoln Logs. For those of us that love to build new things, Taiwan, especially now at FIC and OpenMoko, is a great place to be. So here's the point of this email, finally after more than one year, we're entering into a new ocean. In our factory in China, 400 Neos are waiting for you all. Another 600 will be ready before next week. More are queued up waiting for us to say go. We've had a particularly challenging time trying to setup the online infrastructure and figure out how to ship these phones. Sometime later today or early tomorrow we're going to make another announcement asking for some advice. (Here come the details.) Starting July 9th, we will launch openmoko.com and start taking orders. We're going to have two configurations: Neo Base -- everything the mobile application developer needs to enjoy the benefits of the first freed phone, the Neo 1973: * Neo 1973 (GTA01B_v4) * Battery * Stylus * Headset * AC Charger * Phone Pouch * Lanyard * SanDisk 512MB MicroSD Card (2x) * Micro USB Connectivity Cable Neo Advanced -- everything the mobile device hacker wants to get down and dirty with the first freed phone, the Neo 1973: * Neo 1973 (GTA01B_v4) * Battery (2x) * Stylus * Headset * AC Charger * Phone Pouch * Lanyard * SanDisk 512MB MicroSD Card (2x) * Mini USB Connectivity Cable (2x) * USB Host Mode Cable * Debug Flex Cable * Debug Board v2 (JTAG and serial console) * Ruggedized Toolbox with shoulder strap * Guitar Pick (for opening case) * Torx T6 screwdriver The delays have been expensive for us and annoying for you. We've decided that instead of setting up a complicated return or tracking system to remember who gets a discount for GTA02, we going to give you _all_ a discount on GTA01. We're go
New Oceans
Dear Community, Andre Gide once said, "Man cannot discover new oceans unless he has the courage to lose sight of the shore." Sexism aside, I can't think of a better way to describe our adventures this past year. Around the end of March, we were three months behind schedule. Critical hardware bugs were being discovered almost weekly. I had just returned from an exhausting trip around the world. Harald landed in Taiwan the following week. One look at his face and I knew he was in basically the same depleted state I was in. But, we were both dedicated to keep pushing forward. We've come to realize, largely because of your support, that failure is not an option for this project. For the people pushing this project, an open phone is not really even a product. It's the very embodiment of our vision of technology. We absolutely, passionately, believe that something as fundamental to our lives as the mobile phone must be open. OpenMoko has become far bigger than just a small group of people trying to build an open mobile platform. I can tell you for sure, things will never be the same again inside FIC. To their credit, whole departments and divisions have been reorganized to maximize the opportunity for OpenMoko. This is the reason for my absence from this list for so long. The people inside FIC are amazingly open-minded. Our CEO and Chairman are the two greatest supporters inside this company. Earlier this month they did something courageous and support of the communities commitment. The entire mobile communications division was restructured to build devices for OpenMoko. And OpenMoko -- the project will officially become OpenMoko -- the company. This is how much they believe in us. This is how much faith they have that we will be successful. What does all this mean to us as a company and community? In one word: focus. We now have full control over the future of OpenMoko and the resources needed to give it every possible chance of succeeding. Behind us (well actually still in the same building :-) sits an supportive 800 pound gorilla in the OEM/ODM world, eagerly waiting to work with us to make our dreams a reality. OpenMoko -- together with all of you in the community -- will design, from the ground up, open devices and write the free software platform that powers them. FIC will build the hardware and help us set phones free around the world. This is about the most perfect relationship we can think of. Sure there will be rough times ahead. If it were easy, you know who would have done this long before. Making new things is never easy. But we're in this together. This project has changed me, changed you, and changed FIC. Hopefully, one day, this project will change the world. Now that OpenMoko is officially a company inside the FIC Group, blueprints of our office modifications cover the desk and walls where I'm sitting. Writing this letter to you all is finally giving me time to reflect on this thrilling roller coaster ride. Sorry for putting so many bits into your inbox. But I just can't help it. It's been months that we could hardly step back and see things from a big picture. Now, I really don't think I've been this excited since the day I got my first set of Lincoln Logs. For those of us that love to build new things, Taiwan, especially now at FIC and OpenMoko, is a great place to be. So here's the point of this email, finally after more than one year, we're entering into a new ocean. In our factory in China, 400 Neos are waiting for you all. Another 600 will be ready before next week. More are queued up waiting for us to say go. We've had a particularly challenging time trying to setup the online infrastructure and figure out how to ship these phones. Sometime later today or early tomorrow we're going to make another announcement asking for some advice. (Here come the details.) Starting July 9th, we will launch openmoko.com and start taking orders. We're going to have two configurations: Neo Base -- everything the mobile application developer needs to enjoy the benefits of the first freed phone, the Neo 1973: * Neo 1973 (GTA01B_v4) * Battery * Stylus * Headset * AC Charger * Phone Pouch * Lanyard * SanDisk 512MB MicroSD Card (2x) * Micro USB Connectivity Cable Neo Advanced -- everything the mobile device hacker wants to get down and dirty with the first freed phone, the Neo 1973: * Neo 1973 (GTA01B_v4) * Battery (2x) * Stylus * Headset * AC Charger * Phone Pouch * Lanyard * SanDisk 512MB MicroSD Card (2x) * Mini USB Connectivity Cable (2x) * USB Host Mode Cable * Debug Flex Cable * Debug Board v2 (JTAG and serial console) * Ruggedized Toolbox with shoulder strap * Guitar Pick (for opening case) * Torx T6 screwdriver The delays have been expensive for us and annoying for you. We've decided that instead of setting up a complicated return or tracking system to remember who gets a discount for GTA02, we going to give you _all_ a discount on GTA01. We're go
Re: Hi There
On 6/26/07, Rui Moreira <[EMAIL PROTECTED]> wrote: Hi : My name is Rui Moreira and i am a very enthusiastic linux user, i am starting to play around with openmoko using qemu. I am running it on a Fedora 7 box, and the system is very slow... any pointers ? These are suggestions for QEMU use in general, so if you are already familiar with QEMU and are wondering specifically about making OpenMoko more sprightly, you'll have to be more specific (and perhaps ask on the devel list, where the deep magic happens). QEMU is CPU-bound and a memory hog, so make sure you are giving it as much memory as you can. OpenMoko shouldn't need a ton of memory, but I don't think it would hurt to give it more than it needs - say, a gigabyte. If you need to put more memory into your computer, this would be a good time. If you are using a processor with hyperthreading, ensure that the QEMU process is running on real cores and not a virtual core. QEMU necessarily has some overhead because of the way that it is designed, but there is a kernel module called kqemu that overcomes the overhead, making the VM run at nearly the speed it would on bare metal. Best of luck wrangling QEMU into shape! ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: New CPU
For a viable commercial product I would expect the CPU to be first of all the cheapest one that meets the minimal horsepower requirements, and obviously other considerations, such as power consumption. Would you prefer to run Microsoft office for 30s or have your battery last for a week? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Varga-Háli Dániel Sent: Tuesday, May 29, 2007 1:13 PM To: community@lists.openmoko.org Subject: New CPU Hi! I don't know if there were any discussion about this. Today I was looking at the processor and I saw (sadly) that it's got only 200-266MHz. Do you think it is going to enough? I get the info from: http://wiki.openmoko.org/wiki/Neo1973_Hardware#Processor I am guessing that the core team is planning to put a faster CPU in. Do you think, that this CPU would be better? http://www.samsung.com/products/semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2443/S3C2443.htm What CPU are they planning to use? Dan ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
OpenMokoCamp anyone (after next wave of Neo 1973's arrive)?
I also like the idea of a camp. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: rough seas
Hi, You should all be commended for your professionalism in taking the time to ensure you can commit to public announcements. Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Moss-Pultz Sent: Wednesday, June 27, 2007 4:45 AM To: Tomasz Zielinski Cc: community@lists.openmoko.org Subject: Re: rough seas On Wed, 2007-06-27 at 09:15 +0200, Tomasz Zielinski wrote: > 2007/6/20, Sean Moss-Pultz <[EMAIL PROTECTED]>: > > > In less than a week, we will update you about what's going on at > FIC/ > > OpenMoko, the status of GTA01/02, and our plans for selling these > neos. > > One week has passed silently... Almost done with the announcement...I've still got a day left (Taiwan time) ;-) The delay is not writing the announcement, but finalizing things internally so we can publicly commit. -Sean ___ 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
Re: An introduction
It looks like Gmail swallowed my last response so let me try again... On 6/27/07, Hans De Croix <[EMAIL PROTECTED]> wrote: Hello, Under what license exactly is silverlight/moonlight? "Microsoft's DLR is a layer on top of their Common Language Runtime (CLR), which provides support for dynamically typed languages such as Python, Ruby and JavaScript. The great news is that the DLR is released under Microsoft's Permissive License—their way of saying open source. Microsoft's .NET/DLR implementations of Python and Ruby, named IronPython and IronRuby respectively, are both covered by the same Permissive License as DLR." "Novell will be requiring copyright assignments or contributions to be made under the MIT X11 license to Moonlight to ensure that we can ship this plugin with proprietary drivers if necessary (and also to relicense Moonlight for embedded system users)." I imagine the OpenMoko embedded system is a special case. On 6/27/07, Florent THIERY <[EMAIL PROTECTED]> wrote: I'd be surprised if no hardware acceleration was needed... It is not needed though it is used if available. They got help from their Xgl+Compiz+Glitz guy David Reveman. Here is Miguel de Icaza describing the development decisions some more... "The other consideration to move away from C# to C at the time had to do with the early conversations with David Reveman who wanted to hardware accelerate this. The idea was to turn the Silverlight high-level operations into a scene description that we could transfer from the client applications directly onto the compositing manager (On modern X installations this is what actually puts the bits on the screen and what has enabled all those spicy effects like the rotating cube). The idea here is that the Silverlight client could detect if it was running under a compositing manager that offered rendering on the server and it would off-load all the rendering to the layer that can talk directly to the OpenGL hardware. " Regards, Vlad FYI I am just a lowly Mono consumer (if you are generous you could say QA) I am neither associated with Mono or Novell directly so it is always better to check with the actual source. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: An introduction
Plus, since moonlight is technically language agnostic, those who want to write in c# could, those who like c or c++ could.. With IronPython or IronRuby or even Javascript there are a number of options for scripting and having user interfaces that work seamlessly together.. Regardless of the technology used to build the application code underneath. From my understanding.. We could even mix with different UI elements interacting with different types of applications ... By that I mean portions of the same UI could be sending events to scripts or C# or c/c++ code. Is that right? And XAML can be created dynamically giving the ability to not just theme/skin but completely alter the UI at runtime. By that I mean you don't have to have a static interface with a skin file and theme but the interface could be radically changed as new code is added and new xaml nodes are created.. Does that make any sense? --Tim On Wed, 27 Jun 2007 5:49, Vladimir Giszpenc wrote: On 6/27/07, Tim Newsom wrote: This could provide the xaml parser for use in an interface design some of us have spoken about. Separating the interface from the actual code that processes the events... Or that's how I understand it. Its a truely awesome development. Yes it certainly could and would provide a XAML parser. Read this http://jacksonito.blogspot.com/2007/06/mono-developers-guide-to-writing-xaml.html for some more details. They are planning for tools written in MoonLight so that you could develop on Linux or even a Mac (though I sense no love lost on Apple products on this list :). On 6/27/07, Hans De Croix wrote: Under what license exactly is silverlight/moonlight? The Mono part of Moonlight uses the DLR. So... "Microsoft's DLR is a layer on top of their Common Language Runtime (CLR), which provides support for dynamically typed languages such as Python, Ruby and JavaScript. The great news is that the DLR is released under Microsoft's Permissive License—their way of saying open source. Microsoft's .NET/DLR implementations of Python and Ruby, named IronPython and IronRuby respectively, are both covered by the same Permissive License as DLR." Mono as a whole has this answer to the license question: " What license or licenses are you using for the Mono Project? We use three open source licenses: * The C# Compiler and tools are released under the terms of the GNU General Public License (http://www.opensource.org/licenses/gpl-license.html) (GPL). * The runtime libraries are under the GNU Library GPL 2.0 (http://www.gnu.org/copyleft/library.html#TOC1) (LGPL 2.0). * The class libraries are released under the terms of the MIT X11 (http://www.opensource.org/licenses/mit-license.html) license. Both the Mono runtime and the Mono C# Compiler are also available under a proprietary license for those who can not use the LGPL and the GPL in their code. For licensing details, contact [EMAIL PROTECTED]" Specifically Moonlight... "Novell will be requiring copyright assignments or contributions to be made under the MIT X11 license to Moonlight to ensure that we can ship this plugin with proprietary drivers if necessary (and also to relicense Moonlight for embedded system users)." I imagine the OpenMoko embedded system is a special case since it is open but the license is definitely open source. On 6/27/07, Florent THIERY wrote: I'd be surprised if no hardware acceleration was needed... It is not needed though it is used if available. They got help from their Xgl+Compiz+Glitz guy David Reveman. Here is Miguel de Icaza describing the development decisions some more... "The other consideration to move away from C# to C at the time had to do with the early conversations with David Reveman who wanted to hardware accelerate this. The idea was to turn the Silverlight high-level operations into a scene description that we could transfer from the client applications directly onto the compositing manager (On modern X installations this is what actually puts the bits on the screen and what has enabled all those spicy effects like the rotating cube). The idea here is that the Silverlight client could detect if it was running under a compositing manager that offered rendering on the server and it would off-load all the rendering to the layer that can talk directly to the OpenGL hardware. " Vlad ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: An introduction
On 6/27/07, Tim Newsom wrote: This could provide the xaml parser for use in an interface design some of us have spoken about. Separating the interface from the actual code that processes the events... Or that's how I understand it. Its a truely awesome development. Yes it certainly could and would provide a XAML parser. Read this http://jacksonito.blogspot.com/2007/06/mono-developers-guide-to-writing-xaml.html for some more details. They are planning for tools written in MoonLight so that you could develop on Linux or even a Mac (though I sense no love lost on Apple products on this list :). On 6/27/07, Hans De Croix wrote: Under what license exactly is silverlight/moonlight? The Mono part of Moonlight uses the DLR. So... "Microsoft's DLR is a layer on top of their Common Language Runtime (CLR), which provides support for dynamically typed languages such as Python, Ruby and JavaScript. The great news is that the DLR is released under Microsoft's Permissive License—their way of saying open source. Microsoft's .NET/DLR implementations of Python and Ruby, named IronPython and IronRuby respectively, are both covered by the same Permissive License as DLR." Mono as a whole has this answer to the license question: " What license or licenses are you using for the Mono Project? We use three open source licenses: * The C# Compiler and tools are released under the terms of the GNU General Public License (http://www.opensource.org/licenses/gpl-license.html) (GPL). * The runtime libraries are under the GNU Library GPL 2.0 (http://www.gnu.org/copyleft/library.html#TOC1) (LGPL 2.0). * The class libraries are released under the terms of the MIT X11 (http://www.opensource.org/licenses/mit-license.html) license. Both the Mono runtime and the Mono C# Compiler are also available under a proprietary license for those who can not use the LGPL and the GPL in their code. For licensing details, contact [EMAIL PROTECTED]" Specifically Moonlight... "Novell will be requiring copyright assignments or contributions to be made under the MIT X11 license to Moonlight to ensure that we can ship this plugin with proprietary drivers if necessary (and also to relicense Moonlight for embedded system users)." I imagine the OpenMoko embedded system is a special case since it is open but the license is definitely open source. On 6/27/07, Florent THIERY wrote: I'd be surprised if no hardware acceleration was needed... It is not needed though it is used if available. They got help from their Xgl+Compiz+Glitz guy David Reveman. Here is Miguel de Icaza describing the development decisions some more... "The other consideration to move away from C# to C at the time had to do with the early conversations with David Reveman who wanted to hardware accelerate this. The idea was to turn the Silverlight high-level operations into a scene description that we could transfer from the client applications directly onto the compositing manager (On modern X installations this is what actually puts the bits on the screen and what has enabled all those spicy effects like the rotating cube). The idea here is that the Silverlight client could detect if it was running under a compositing manager that offered rendering on the server and it would off-load all the rendering to the layer that can talk directly to the OpenGL hardware. " Vlad ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: rough seas
Looking forward to hearing from you. ;) 2007/6/27, Sean Moss-Pultz <[EMAIL PROTECTED]>: On Wed, 2007-06-27 at 09:15 +0200, Tomasz Zielinski wrote: > 2007/6/20, Sean Moss-Pultz <[EMAIL PROTECTED]>: > > > In less than a week, we will update you about what's going on at > FIC/ > > OpenMoko, the status of GTA01/02, and our plans for selling these > neos. > > One week has passed silently... Almost done with the announcement...I've still got a day left (Taiwan time) ;-) The delay is not writing the announcement, but finalizing things internally so we can publicly commit. -Sean ___ 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
Re: rough seas
On Wed, 2007-06-27 at 09:15 +0200, Tomasz Zielinski wrote: > 2007/6/20, Sean Moss-Pultz <[EMAIL PROTECTED]>: > > > In less than a week, we will update you about what's going on at > FIC/ > > OpenMoko, the status of GTA01/02, and our plans for selling these > neos. > > One week has passed silently... Almost done with the announcement...I've still got a day left (Taiwan time) ;-) The delay is not writing the announcement, but finalizing things internally so we can publicly commit. -Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: An introduction
Hello, Under what license exactly is silverlight/moonlight? Cheers, Hans Op woensdag 27 juni 2007 04:27, schreef Vladimir Giszpenc: > Hello OpenMoko community, > > OpenMoko is very exciting. I and many Mono developers like myself > would like to get involved. The Mono team has developed Moonlight -- > a port of Microsoft's SilverLight to Linux. Here are some of the > things it can do http://www.youtube.com/watch?v=qRSO7p0HAIw > > It is Open Source, small, fast and works well with others. The Mono > team has made it easy for .Net developers to access this technology > but it is not limited to them. You don't need Mono to use MoonLight. > > The Mono team would help you create hype give you access to millions > of C#, VisualBasic, JavaScript, IronPython and Ruby developers because > it not only has ported the .Net CLR but they made Microsoft's DLR work > on Linux as well. The DLR is licensed with a BSD type license. > > How do we get involved? > > Thanks, > > Vlad > > ___ > 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
Re: rough seas
> 2007/6/20, Sean Moss-Pultz <[EMAIL PROTECTED]>: > >> In less than a week, we will update you about what's going on at FIC/ >> OpenMoko, the status of GTA01/02, and our plans for selling these neos. > > One week has passed silently... Well, technically you posted your message 9 hours too early ;) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: rough seas
2007/6/20, Sean Moss-Pultz <[EMAIL PROTECTED]>: In less than a week, we will update you about what's going on at FIC/ OpenMoko, the status of GTA01/02, and our plans for selling these neos. One week has passed silently... -- Tomek Z. [EMAIL PROTECTED] ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Hi There
Hi : My name is Rui Moreira and i am a very enthusiastic linux user, i am starting to play around with openmoko using qemu. I am running it on a Fedora 7 box, and the system is very slow... any pointers ? Thanks ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
