-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathQuestion_2.pg
55 lines (38 loc) · 15.3 KB
/
Question_2.pg
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
flags: 0 1 0 1 0 0
blocks: <p>Just wondering, I was following the steps you outlined in your Perl Client on Android page and tried running the android_launcher.pl script but the editor window opens up the script with no launch. I'm pressing the "right turn" arrow to Run the script. Is that correct ? Also, it looks like the sl4a folder was installed on my sdcard. Is that where it's supposed to go ? Also, when I press the terminal button on the menu, all I get is a black screen and I can't type anything. My phone is rooted and I've been looking to use Perl on my phone, luv your work.</p><p>Keep it up, YOU GUYS ROCK !!</p><p>-- colstelhml 2015-10-11 15:05 UTC</p><h2 class="commentsHeading">Comments:</h2><div class="userComment"><p>Hi! Sorry for the late answer.</p><p>Indeed, it seems like <a class="url http outside" href="https://groups.google.com/forum/#!topic/android-scripting/rXDVgLdyTBw">SL4A is not working on android 5+</a>. In fact, SL4A is abandoned for almost 4 years, just look at the <a class="url http outside" href="https://github.com/damonkohler/sl4a/graphs/contributors">activity graph on GitHub</a>. <a class="url http outside" href="https://github.com/damonkohler/sl4a/network">There are some forks</a> but none of them is active enough.</p><p>Basically, I was hoping that <a class="url http outside" href="https://github.com/mid1221213/perldroid">perldroid project will come alive</a>, but now it seems like it is not going to happen.</p><p>When ProgArm project was starting, there was a quick (really dirty) prototype client written in Python. But later I decided that things will go more smoothly with Perl (CPAN was one of the reasons to switch). Anyway, neither Python or Perl don't work well enough on Android.</p><p><a class="url http outside" href="http://perldoc.perl.org/5.20.0/perldelta.html#New-Platforms">Perl v5.20</a> has Android support, which means that there shouldn't be any problems with compiling. However, if you want to put it in an application you still have to write some code in Java (or any other language supported by java machine). So in the end we have two options:<br /></p><ul><li>Write a separate android-oriented client in Java. However, it would not work nicely on other platforms, which means that any effort will be doubled since we will have to support two clients at the same time. This is a real problem. ProgArm has a decent hardware (a lot of effort was put into that), but software is pretty much not done due to the lack of development power (it's just 1 software developer!).</li><li>Embed Perl client into an Android application, write a thin layer in java so that Perl client can communicate with the phone (e.g. run some actions). That's what we should do, I think.</li></ul><p>But in the end, Android is a real pain to work with. It all starts with the lack of decent support for a broad range of languages, but OK, even if you choose Java, then what? <a class="url http outside" href="http://stackoverflow.com/questions/15481524/how-to-programatically-answer-end-a-call-in-android-4-1">Still you cannot accept a goddamn call meaningfully</a>… And it's full of such limitations and half-broken workarounds for them.</p><p>Regarding programming languages, <a class="url http outside" href="https://en.wikipedia.org/wiki/Perl_6">Perl6</a> is coming this Christmas. JVM support is not promised, but it will be done sooner or later. I have no idea how soon we will be able to run Perl6 apps on Android though (if ever), but it seems like porting the [[Clients|client]] to Perl6 is a good idea <strong>in the long run</strong> (but the code base is really small anyway, so feel free to start Java thing from scratch!).</p><p>But that's not the only thing that is making our development pace slower. In [[ProgArm 0.3]] we decided to use a chip that has Bluetooth LE (only!). That is, you cannot use it if your phone has Bluetooth v2.1 (still you can connect HC-05 and use that instead, that's what I do…). The idea was (and still is) that all new phones are manufactured with Bluetooth 4.0+ built in, so there shouldn't be any problems. In reality, it is still hard to find a cheap (used) phone that would support Bluetooth LE, and personally I'm not willing to spend much for a phone that I'm not going to use anyway (I'm using <a class="url http outside" href="https://en.wikipedia.org/wiki/Nokia_N900">Nokia N900</a>. Although it is old, still it has a full-blown GNU/Linux operating system). Again, it's a good decision <strong>in the long run</strong>, but it definitely does not help us right now.</p><p>Finally, although there is not much activity on this project we are still working on Free/Open-Source hardware designs! :)<br />The project we are working on right now is associated with robotic vacuum cleaners. We will setup the website really soon.</p><p>If you have any interest in ProgArm, please ask us anything! We will try to help you as much as we can. If you want to contribute any code then I can give you full admin access to everything.</p><p>-- AlexDaniel 2015-10-30 00:18 UTC</p> </div>
diff-minor: <p><strong>Changed:</strong></p>
<div class="old"><p>< When ProgArm project was starting, there was a quick (really dirty) prototype client written in Python. But later I decided that things will go more smoothly with Perl (CPAN was one of the reasons to switch). Anyway, <strong class="changes">either</strong> Python or Perl<strong class="changes">, both</strong> don't work well enough on Android.<br />< [[http://perldoc.perl.org/5.20.0/perldelta.html#New-Platforms Perl v5.20]] has Android support, which means that there <strong class="changes">should</strong> be <strong class="changes">no</strong> problems with compiling. However, if you want to put it in an application<strong class="changes">,</strong> you still have to write some code in Java (or any other language supported by java machine). So in the end we have two options:<br />< * Write a separate android-oriented client in Java. <strong class="changes">The problem is</strong>, it <strong class="changes">wont</strong> work nicely on other platforms<strong class="changes">. Which</strong> means that any effort will be doubled since we will have to support two clients at the same time. This is a real problem. ProgArm has a decent hardware (a lot of effort was put into that), but software is pretty much not done due to the lack of development power (it's just 1 software developer!).</p></div><p><strong>to</strong></p>
<div class="new"><p>> When ProgArm project was starting, there was a quick (really dirty) prototype client written in Python. But later I decided that things will go more smoothly with Perl (CPAN was one of the reasons to switch). Anyway, <strong class="changes">neither</strong> Python or Perl don't work well enough on Android.<br />> [[http://perldoc.perl.org/5.20.0/perldelta.html#New-Platforms Perl v5.20]] has Android support, which means that there <strong class="changes">shouldn't</strong> be <strong class="changes">any</strong> problems with compiling. However, if you want to put it in an application you still have to write some code in Java (or any other language supported by java machine). So in the end we have two options:<br />> * Write a separate android-oriented client in Java. <strong class="changes">However</strong>, it <strong class="changes">would not</strong> work nicely on other platforms<strong class="changes">, which</strong> means that any effort will be doubled since we will have to support two clients at the same time. This is a real problem. ProgArm has a decent hardware (a lot of effort was put into that), but software is pretty much not done due to the lack of development power (it's just 1 software developer!).</p></div><p><strong>Changed:</strong></p>
<div class="old"><p>< But that's not the only thing that is making our development pace slower. In [[ProgArm 0.3]] we decided to use a chip that has Bluetooth LE (only!). That is, you cannot use it if your phone has Bluetooth v2.1 (still you can connect HC-05 and use that instead, that's what I do…). The idea was (and still is) that all new phones are manufactured with Bluetooth 4.0+ built in, so there <strong class="changes">should</strong> be <strong class="changes">no problem</strong>. In reality, it is still hard to find a cheap (used) phone that would support Bluetooth LE, and personally I'm not willing to spend much for a phone that I'm not going to use anyway (I'm using [[https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900]]. Although it is old, still it has a full-blown GNU/Linux operating system). Again, it's a good decision **in the long run**, but it definitely does not help us right now.<br />< Finally, although there is not much activity on this project<strong class="changes">,</strong> we are still working on Free/Open-Source hardware designs! :)</p></div><p><strong>to</strong></p>
<div class="new"><p>> But that's not the only thing that is making our development pace slower. In [[ProgArm 0.3]] we decided to use a chip that has Bluetooth LE (only!). That is, you cannot use it if your phone has Bluetooth v2.1 (still you can connect HC-05 and use that instead, that's what I do…). The idea was (and still is) that all new phones are manufactured with Bluetooth 4.0+ built in, so there <strong class="changes">shouldn't</strong> be <strong class="changes">any problems</strong>. In reality, it is still hard to find a cheap (used) phone that would support Bluetooth LE, and personally I'm not willing to spend much for a phone that I'm not going to use anyway (I'm using [[https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900]]. Although it is old, still it has a full-blown GNU/Linux operating system). Again, it's a good decision **in the long run**, but it definitely does not help us right now.<br />> Finally, although there is not much activity on this project we are still working on Free/Open-Source hardware designs! :)</p></div><p><strong>Changed:</strong></p>
<div class="old"><p>< If you have any interest in ProgArm, please ask us anything! We will try to help you as much as we can. If you want to contribute any code<strong class="changes">,</strong> then I can give you full admin access to everything.</p></div><p><strong>to</strong></p>
<div class="new"><p>> If you have any interest in ProgArm, please ask us anything! We will try to help you as much as we can. If you want to contribute any code then I can give you full admin access to everything.</p></div>
lastmajorsummary: Hi! Sorry for the late answer. Indeed, it seems like [[https://groups.google.com/forum/#!topic/android-scripting/rXDVgLdyTBw SL4A is not working . . .
ts: 1446167087
minor:
host: 80.62.116.123
username: Yuno
revision: 3
diff-major: 1
summary: Hi! Sorry for the late answer. Indeed, it seems like [[https://groups.google.com/forum/#!topic/android-scripting/rXDVgLdyTBw SL4A is not working . . .
languages:
text: Just wondering, I was following the steps you outlined in your Perl Client on Android page and tried running the android_launcher.pl script but the editor window opens up the script with no launch. I'm pressing the "right turn" arrow to Run the script. Is that correct ? Also, it looks like the sl4a folder was installed on my sdcard. Is that where it's supposed to go ? Also, when I press the terminal button on the menu, all I get is a black screen and I can't type anything. My phone is rooted and I've been looking to use Perl on my phone, luv your work.
Keep it up, YOU GUYS ROCK !!
-- colstelhml 2015-10-11 15:05 UTC
----
Hi! Sorry for the late answer.
Indeed, it seems like [[https://groups.google.com/forum/#!topic/android-scripting/rXDVgLdyTBw SL4A is not working on android 5+]]. In fact, SL4A is abandoned for almost 4 years, just look at the [[https://github.com/damonkohler/sl4a/graphs/contributors activity graph on GitHub]]. [[https://github.com/damonkohler/sl4a/network There are some forks]] but none of them is active enough.
Basically, I was hoping that [[https://github.com/mid1221213/perldroid perldroid project will come alive]], but now it seems like it is not going to happen.
When ProgArm project was starting, there was a quick (really dirty) prototype client written in Python. But later I decided that things will go more smoothly with Perl (CPAN was one of the reasons to switch). Anyway, neither Python or Perl don't work well enough on Android.
[[http://perldoc.perl.org/5.20.0/perldelta.html#New-Platforms Perl v5.20]] has Android support, which means that there shouldn't be any problems with compiling. However, if you want to put it in an application you still have to write some code in Java (or any other language supported by java machine). So in the end we have two options:
* Write a separate android-oriented client in Java. However, it would not work nicely on other platforms, which means that any effort will be doubled since we will have to support two clients at the same time. This is a real problem. ProgArm has a decent hardware (a lot of effort was put into that), but software is pretty much not done due to the lack of development power (it's just 1 software developer!).
* Embed Perl client into an Android application, write a thin layer in java so that Perl client can communicate with the phone (e.g. run some actions). That's what we should do, I think.
But in the end, Android is a real pain to work with. It all starts with the lack of decent support for a broad range of languages, but OK, even if you choose Java, then what? [[http://stackoverflow.com/questions/15481524/how-to-programatically-answer-end-a-call-in-android-4-1 Still you cannot accept a goddamn call meaningfully]]… And it's full of such limitations and half-broken workarounds for them.
Regarding programming languages, [[https://en.wikipedia.org/wiki/Perl_6 Perl6]] is coming this Christmas. JVM support is not promised, but it will be done sooner or later. I have no idea how soon we will be able to run Perl6 apps on Android though (if ever), but it seems like porting the [[Clients|client]] to Perl6 is a good idea **in the long run** (but the code base is really small anyway, so feel free to start Java thing from scratch!).
But that's not the only thing that is making our development pace slower. In [[ProgArm 0.3]] we decided to use a chip that has Bluetooth LE (only!). That is, you cannot use it if your phone has Bluetooth v2.1 (still you can connect HC-05 and use that instead, that's what I do…). The idea was (and still is) that all new phones are manufactured with Bluetooth 4.0+ built in, so there shouldn't be any problems. In reality, it is still hard to find a cheap (used) phone that would support Bluetooth LE, and personally I'm not willing to spend much for a phone that I'm not going to use anyway (I'm using [[https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900]]. Although it is old, still it has a full-blown GNU/Linux operating system). Again, it's a good decision **in the long run**, but it definitely does not help us right now.
Finally, although there is not much activity on this project we are still working on Free/Open-Source hardware designs! :)
The project we are working on right now is associated with robotic vacuum cleaners. We will setup the website really soon.
If you have any interest in ProgArm, please ask us anything! We will try to help you as much as we can. If you want to contribute any code then I can give you full admin access to everything.
-- AlexDaniel 2015-10-30 00:18 UTC
lastmajor: 3
keep-ts: 1446167087