Create a Google group and then use its embed feature to integrate it with your main website http://support.google.com/groups/bin/answer.py?hl=en&answer=1191206
I believe the FreeRunner has proved its point. It is totally unfair to compare it alongside other commercial phones. It is of no use to end users. It is of exceptional use to developers though.
I have a Freerunner and to me it's a generic 400MHz 128MB embedded device. I develop mobile software. I can install any distribution on this device so that I can get the set of libraries that are needed for my development - sometimes EFL (enlightenment), other times Qt, or pygame. I have also installed Android. So it's very versatile development platform.
Also it's two bootloaders make it almost impossible to brick. You can't break it as far as software goes. As a developer I don't care for support for software. What I like is, I can develop for 3-4 different smartphone platforms, with this single device.
Openmoko's goal was ambitious and also very experimental. It's hardly a surprise that they failed in one of the products (considering the big economy itself failing, it's no big deal). Openmoko was a good experiment in right direction and Freerunner will give a good data point in future business models based on open source.
does the same thing. If app wants to make sure user doesn't miss it: give expire time as 0. If app wants to convey critical message there is urgency option (-u). I am sure some graphics work can make the notifications prettier (like growl on macosx); but the mechanism is already there. And the decision of whether to demand action from user, is left to apps.
I had attempted an implementation of similar concept limited to Java applications and based on top of JXTA P2P protocol as my MS project.
http://www-users.cs.umn.edu/~salvi/downloads/jyro_aos_project.doc
All the possible applications mentioned in this article are nice and are known for a long time. What matters is execution. Good luck to the project!
I don't see why the same thing cannot be achieved with technologies already available today. VMware workstation, Linux KVM, allow you to run multiple operating systems on the same machine. With thin client technologies (e.g. Wyse) you can actually use a single machine to run many OSes simultaneously and users can have their own thin computers that will access those OS instances remotely. If the different OS need is not very necessary, then VNC is the simplest solution that one can use for this kind of split access.
Slashdot Mirror
Create a Google group and then use its embed feature to integrate it with your main website
http://support.google.com/groups/bin/answer.py?hl=en&answer=1191206
In case your IP is blocked by ACM as mine.
http://webcache.googleusercontent.com/search?q=cache:5hQeyIzYvqEJ:queue.acm.org/detail.cfm%3Fid%3D1883592+ed+catmull+acm&cd=1&hl=en&ct=clnk&gl=in
I believe the FreeRunner has proved its point. It is totally unfair to compare it alongside other commercial phones. It is of no use to end users. It is of exceptional use to developers though.
I have a Freerunner and to me it's a generic 400MHz 128MB embedded device. I develop mobile software. I can install any distribution on this device so that I can get the set of libraries that are needed for my development - sometimes EFL (enlightenment), other times Qt, or pygame. I have also installed Android. So it's very versatile development platform.
Also it's two bootloaders make it almost impossible to brick. You can't break it as far as software goes. As a developer I don't care for support for software. What I like is, I can develop for 3-4 different smartphone platforms, with this single device.
Openmoko's goal was ambitious and also very experimental. It's hardly a surprise that they failed in one of the products (considering the big economy itself failing, it's no big deal). Openmoko was a good experiment in right direction and Freerunner will give a good data point in future business models based on open source.
I don't understand how is it different from what exists already. The mechanism is already there:
[CLI] notify-send "Hi there!" -t expire-time-in-mseconds [/CLI]
does the same thing. If app wants to make sure user doesn't miss it: give expire time as 0. If app wants to convey critical message there is urgency option (-u).
I am sure some graphics work can make the notifications prettier (like growl on macosx); but the mechanism is already there. And the decision of whether to demand action from user, is left to apps.
I had attempted an implementation of similar concept limited to Java applications and based on top of JXTA P2P protocol as my MS project. http://www-users.cs.umn.edu/~salvi/downloads/jyro_aos_project.doc All the possible applications mentioned in this article are nice and are known for a long time. What matters is execution. Good luck to the project!
I liked the interview of its CEO at Web 2.0 summit. http://radar.oreilly.com/2008/11/a-conversation-with-shai-agass.html
Interesting results, and great if you're planning a server, but what about desktop use?
Totally agree!
I don't see why the same thing cannot be achieved with technologies already available today. VMware workstation, Linux KVM, allow you to run multiple operating systems on the same machine. With thin client technologies (e.g. Wyse) you can actually use a single machine to run many OSes simultaneously and users can have their own thin computers that will access those OS instances remotely. If the different OS need is not very necessary, then VNC is the simplest solution that one can use for this kind of split access.