Mon Jan 14 11:37:11 CET 2013
This is amazing - works like a charm - fantastic.
Quick comment -
It would be very nice to make the client and server in fac_example.zip
run "out of the box"
client.erl is a *must read* file. server.erl does not export main/0 and
should be changed to
spawn the server - otherwise you don't get control in the shell ...
- The download is rather large - I'm sure this could be made a *lot
- Need Erlang APIs to the camera, GPS, .... etc.
- The client.erl example shows I can make an application *without* eclipse
it would be very nice top abstract the details of the layout() function
so as not to see the XML :-)
On Sun, Jan 13, 2013 at 9:06 PM, Erik Reitsma <> wrote:
> Hi all,
> I have put my port of Erlang to Android on Google Code:
> To install it on your Android device, you should allow applications from
> unknown sources, because the app is not delivered through Google Play
> (yet). The Android device does *not* have to be rooted.
> It depends on Scripting Layer for Android (SL4A). So in order to use it,
> you should first install SL4A r6 from here:
> http://code.google.com/p/android-scripting/downloads/detail?name=sl4a_r6.apkThen install the APK for Erlang, this one:
> This app is just the installer. Run it to actually install Erlang/OTP. I
> have included as much of OTP as might be remotely useful, so the download
> is 36.5 MB. Of course you want to use the megaco and orber applications on
> your phone!
> You can use the SL4A API through the module android that I have added. I
> have added a very simple example, to show you how you can make a small gui
> and respond to events. Study the SL4A API to do other Android things.
> You can run some Erlang code by putting your source in the SL4A scripts
> directory on the Android device, which is /sdcard/sl4a/scripts/. The .erl
> file should contain and export a function main/0, which will be called when
> the script is run. The .erl file will be compiled to a .beam file
> automatically, only if the .beam file does not exist. A minor inconvenience
> now is, that if the .erl file is modified, it will not be recompiled unless
> the .beam file is removed. The scripts directory will be in the code path,
> so if you put other .beam files there, they will be found, and .erl files
> there will be compiled too, if necessary.
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions