Hello all,
the company I'm working at is evaluating some technologies for multi-platform development for smart phones, tablets etc. So far, we've eliminated most of the choices, with only LambdaNative, PhoneGap/Cordova and Kivy remaining. No actual experiments have been done so far, no actual phones bought, only theoretical thinking-about-what-the-net-says. I'm the team's biggest Scheme proponent and know both JavaScript and Python, while all the other devs would have to learn another language, no matter which solution we choose. So here's the big question:
Can I use LambdaNative to deploy to Windows Phone 8, or are there any plans to support it in the not-so-far future?
Best regards,
Leif Bruder
Afficher les réponses par date
Hi Leif,
It's great to hear that you are giving Gambit and LambdaNative consideration for development within your company. LambdaNative does not currently support Windows Phone 8 though. I'm confident that Gambit Scheme itself will build for it, and there is some interest in making LambdaNative run on it as well. Personally I'd like to see LambdaNative support all the major mobile operating systems. With the arrival of the NDK in WP8 it should be possible to make that happen. We would just need to write a DirectX rendering backend, and figure out how to drive the windows build from our command line model. At this point however, there are no definite plans for making that happen.
Chris
________________________________________ From: gambit-list-bounces@iro.umontreal.ca [gambit-list-bounces@iro.umontreal.ca] On Behalf Of Leif Bruder [lbruder@leif-bruder.net] Sent: Tuesday, September 17, 2013 8:25 AM To: Gambit-List Subject: [gambit-list] Gambit-C and LambdaNative on Windows Phone?
Hello all,
the company I'm working at is evaluating some technologies for multi-platform development for smart phones, tablets etc. So far, we've eliminated most of the choices, with only LambdaNative, PhoneGap/Cordova and Kivy remaining. No actual experiments have been done so far, no actual phones bought, only theoretical thinking-about-what-the-net-says. I'm the team's biggest Scheme proponent and know both JavaScript and Python, while all the other devs would have to learn another language, no matter which solution we choose. So here's the big question:
Can I use LambdaNative to deploy to Windows Phone 8, or are there any plans to support it in the not-so-far future?
Best regards,
Leif Bruder _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
On 2013-09-17, at 11:25 AM, Leif Bruder lbruder@leif-bruder.net wrote:
Hello all,
the company I'm working at is evaluating some technologies for multi-platform development for smart phones, tablets etc. So far, we've eliminated most of the choices, with only LambdaNative, PhoneGap/Cordova and Kivy remaining. No actual experiments have been done so far, no actual phones bought, only theoretical thinking-about-what-the-net-says. I'm the team's biggest Scheme proponent and know both JavaScript and Python, while all the other devs would have to learn another language, no matter which solution we choose.
Portability is certainly one of the main features of Gambit (and LambdaNative). Gambit Scheme can be used as an abstration of the underlying platform. Here are a few things you should also take into account:
1) With Gambit's Scheme infix extension ("six"), you can develop using a syntax that is very close to C, and you can mix this with code written in the standard prefix syntax. This is helpful to bring to Scheme people who are uncomfortable with S-expressions. Here's a quick example:
(define-macro (six.x^y x y) `(expt ,x ,y))
\ for (int i=0; i<10; i++) { println("i=",i," 2^i=",2^i); }
2) Gambit-C generates portable C, C++ and Objective-C code, so it is easy to move from one platform to another. In addition, there are backends being developped that generate JavaScript, ruby, python and php. This means that the Scheme code developped with Gambit can be integrated to other environments. These backends are not feature complete, but that will improve with time.
Marc