Re: built-in scripting languages.
I would like to propose a number of bindings a preferred scripting language should have - Bluetooth bindings - Webservice bindings, 'lightweight' request/response access to networked services - Persistence bindings, optimized access to large datasets (sqlite?) On Tuesday 03 April 2007 21:54:26 Bryan Larsen wrote: > A scripting language should be chosen as the default. Yes, it'll be a > hard choice, but there's also no 'wrong choice' (except for "none"). > I've put a lot of work into > http://wiki.openmoko.org/wiki/Wishlist:BuiltInScriptingLanguage. Please > comment here or on the discussion page. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[News]List of iphone competitors / neo appears twice :p
http://www.mobilewhack.com/top-ten-list-of-iphone-competitors/ Funny, the neo appears twice in this comparative ? In fact it's a mix of the greenphone (i guess it was the one they wanted to describe...) with the neo's features (even imaginary ones: "multi-touch gesture recognition"). http://www.engadget.com/2006/11/07/fics-linux-based-fic-gta001-gsm-smartphone-encourages-hacking/ Maybe, at the time of writing, the neo was only at planning stage? Cheers Florent ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Choice of scripting langage: towards Web2.0?
What would be the best platform for using web 2.0 APIs? There are interesting web 2.0 services, almost all offering free-to-use APIs (http://www.programmableweb.com/), such as the recent netvibes crossplatform widget API http://dev.netvibes.com/ or Imity, who recently released an open source phone client. Imity uses your mobile phone (bluetooth) to sense people around you, people that are members of the same social networks as you. http://www.imity.com/pocket-radar http://code.google.com/p/imity-client/ What's interesting about it is that it's not restricted to one social network, but to other ones too (ex: flickr). And it works offline too . "Imity will support integration with partners through dynamic objects. Imity objects will allow social networks of any kind to use Imity as a platform for physical real-life support of their web application." I'd be happy to do the same with last.fm neighbours in real life... Or any friend-based network: "oh you know my friend *** ?" We should take a second look at the python twisted networking framework: the twistedmatrix projects allow easy use of ssh, sftp, http client/server, smtp, imap, pop, dns, nntp, IM client/servers (OSCAR (AIM and ICQ), IRC, MSN, TOC (AIM), jabber). http://twistedmatrix.com/trac/wiki/TwistedProjects Maybe this could help in the scripting language decision. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Choice of scripting langage: towards Web2.0?
For a dynamic scripting language that would be best served to consume web resources and already tie into a big development community there are two primary choices: Python and Ruby. Python has had incredible support and impact on Nokia mobiles with Py60 (see Nokia's Py60 extensions to device access: http://wiki.opensource.nokia.com/projects/PyS60_extensions), and Maemo (N800) Python/Hildon bindings for building 'native' applications. Ruby has a growing community, but hasn't yet gotten good support on mobile devices. There are some potential projects for building Ruby bindings on Maemo that will be very useful. So could look at it either that Ruby doesn't have a big mobile community contingent so why bother, or that the community really *wants* a Ruby mobile so would jump on the chance. Both languages have excellent networking libraries/frameworks, so this really isn't a concern. Really, both languages could be supported in tandem and in fact build on one another's work/efforts. And you wouldn't really be dividing effort since the two communities are both strong in their own right, and so would support their framework. Andrew On 4/4/07, Florent THIERY <[EMAIL PROTECTED]> wrote: What would be the best platform for using web 2.0 APIs? There are interesting web 2.0 services, almost all offering free-to-use APIs (http://www.programmableweb.com/), such as the recent netvibes crossplatform widget API http://dev.netvibes.com/ or Imity, who recently released an open source phone client. Imity uses your mobile phone (bluetooth) to sense people around you, people that are members of the same social networks as you. http://www.imity.com/pocket-radar http://code.google.com/p/imity-client/ What's interesting about it is that it's not restricted to one social network, but to other ones too (ex: flickr). And it works offline too . "Imity will support integration with partners through dynamic objects. Imity objects will allow social networks of any kind to use Imity as a platform for physical real-life support of their web application." I'd be happy to do the same with last.fm neighbours in real life... Or any friend-based network: "oh you know my friend *** ?" We should take a second look at the python twisted networking framework: the twistedmatrix projects allow easy use of ssh, sftp, http client/server, smtp, imap, pop, dns, nntp, IM client/servers (OSCAR (AIM and ICQ), IRC, MSN, TOC (AIM), jabber). http://twistedmatrix.com/trac/wiki/TwistedProjects Maybe this could help in the scripting language decision. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Andrew Turner [EMAIL PROTECTED]42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Choice of scripting langage: towards Web2.0?
Andrew Turner wrote: For a dynamic scripting language that would be best served to consume web resources and already tie into a big development community there are two primary choices: Python and Ruby. Python has had incredible support and impact on Nokia mobiles with Py60 (see Nokia's Py60 extensions to device access: http://wiki.opensource.nokia.com/projects/PyS60_extensions), and Maemo (N800) Python/Hildon bindings for building 'native' applications. Ruby has a growing community, but hasn't yet gotten good support on mobile devices. There are some potential projects for building Ruby bindings on Maemo that will be very useful. So could look at it either that Ruby doesn't have a big mobile community contingent so why bother, or that the community really *wants* a Ruby mobile so would jump on the chance. Both languages have excellent networking libraries/frameworks, so this really isn't a concern. Really, both languages could be supported in tandem and in fact build on one another's work/efforts. And you wouldn't really be dividing effort since the two communities are both strong in their own right, and so would support their framework. Andrew Out of those two, I vote Python. The only reasons are that I "feel" as though Python has better supporting libraries (and community) and I also prefer its syntax. That said, I still think we should consider perl. People say that it is losing support, but I "feel" as though that is propaganda from the other languages. I don't think it is even a close comparison when you look at the number of supporting libraries compared to just about any other language. However, I do feel perl is at a crossroads. It isn't the "cool" language anymore (python and ruby currently take that crown). So you have a lot of older gurus that could do just about anything with it, but who may not be willing to learn a new language. Then you have new developers that are just learning the "in" languages (ie python and ruby). So you kinda have a clash of cultures. Me, I'm still pretty young but learned perl straight out of college and I love it as it is just so powerful and there are libraries to do just about anything you can imagine. All that to say, lets at least consider putting perl back into the conversation. I'm not going to be disappointed or upset with just about any decision, but I wanted to throw this out before it was too late. I'm not too old to learn a new language ;) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re:[News]List of iphone competitors / neo appears twice :p
Their description of the Samsung F700 as their first touchpad phone is interesting. I've got an i300 on my belt... They also need a native English speaker to do a spelling-and-grammar check on their site. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Google maps & caching
Hi All, I've read through several threads on this list, and others, which discuss the use of Google Maps for mobiles. It has been mentioned several times that Google doesn't allow map tiles to be cached. I've read through the Google Maps API "Terms of Use" and I can't seem to find any mention of caching being prohibited. Could someone please point me to the relevant section please? I find it a little odd that Google doesn't allow caching of map tiles as they are quite large and I can imagine Google's server & bandwidth costs are huge if every tile is fetched directly without going through a caching http proxy. My train of thought is going along the lines of running squid or similar on the actual phone... Cheers, Tom ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Google maps & caching
When I use filez to look at the stuff stored on my PalmOS Treo 650 there is a fairly obvious google maps cache file. So I'm pretty sure they do cache tiles for performance, the point is that we cannot decode or use that tile cache for any other purpose. Adrian On 4/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi All, I've read through several threads on this list, and others, which discuss the use of Google Maps for mobiles. It has been mentioned several times that Google doesn't allow map tiles to be cached. I've read through the Google Maps API "Terms of Use" and I can't seem to find any mention of caching being prohibited. Could someone please point me to the relevant section please? I find it a little odd that Google doesn't allow caching of map tiles as they are quite large and I can imagine Google's server & bandwidth costs are huge if every tile is fetched directly without going through a caching http proxy. My train of thought is going along the lines of running squid or similar on the actual phone... Cheers, Tom ___ 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: Choice of scripting langage: towards Web2.0?
On 4/4/07, Jonathon Suggs <[EMAIL PROTECTED]> wrote: That said, I still think we should consider perl. ... So you have a lot of older gurus that could do just about anything with it, but who may not be willing to learn a new language. Hmm. well yes, Provided I can make it do perl for me I am selfish enough not to worry if it isn't built-in - however I couldn't help noticing the other day http://wiki.openmoko.org/wiki/Wishlist:BuiltInScriptingLanguage which is worth a look, and especially mentions Ruby and Python and two others for being small. The language Lua looked particularly interesting for its (to me) modern approach of being self-extensible. And Brazil is a big place. We need to think worldwide here. I googled for Lua language tutorial features and got a huge pile of fascinating reading. I must try this. cheers, clare ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community