On Thu, Oct 05, 2017 at 07:44:06AM +0200, Alexander Burger wrote:
> Yes, sorry, the TGZ contains only the pre-built binary and the required *.l
> libraries.
>
> Just download the rolling release software-lab.de/picoLisp.tgz, it is (as well
> as software-lab.de/PilBox.tgz) up to date.
Now I upload
On Wed, Oct 04, 2017 at 09:59:50PM +0200, Richard Z wrote:
> > If it is an ARMv7, then you must build 'emu', yes.
>
> my copy of PilBox.tgz has the timestamp Sep 22th 10:07 and does
> not appear to have the sources of the lisp engine?
Yes, sorry, the TGZ contains only the pre-built binary and the
On Wed, Oct 04, 2017 at 06:46:50PM +0200, Alexander Burger wrote:
> Hi,
>
> > > Since 22th of September a pre-build Lisp env should be included.
> >
> > well I assume I need to compile my own since my Moto G identifies
> > itself as ARM 7?
>
> I thought you wrote
>
> > I have a Moto G4+ which h
Hi,
> > Since 22th of September a pre-build Lisp env should be included.
>
> well I assume I need to compile my own since my Moto G identifies
> itself as ARM 7?
I thought you wrote
> I have a Moto G4+ which has a 64 bit cpu
but maybe I mixed up the thread?
If it is an ARMv7, then you must bu
Hi,
> > I have an even older Moto G and was going to try various things.. now
> > it seems https://software-lab.de/PilBox.tgz doesn't include the actual
> > lisp engine sources. Which one should I take?
>
> Since 22th of September a pre-build Lisp env should be included.
well I assume I need to
Hi Richard,
> I have an even older Moto G and was going to try various things.. now
> it seems https://software-lab.de/PilBox.tgz doesn't include the actual
> lisp engine sources. Which one should I take?
Since 22th of September a pre-build Lisp env should be included.
In any case, if unsure, al
On Sun, Sep 24, 2017 at 08:44:12AM +0200, Alexander Burger wrote:
> Hi Paul,
>
> > Is there any chance of a version that works with 32-bit Android? I have
> > a Moto G4+ which has a 64 bit cpu (Snapdragon 617 iirc) but uses a 32
> > bit Android build, so Pilbox sees it as an ARM 7l and won't run.
Hi Paul,
> Is there any chance of a version that works with 32-bit Android? I have
> a Moto G4+ which has a 64 bit cpu (Snapdragon 617 iirc) but uses a 32
> bit Android build, so Pilbox sees it as an ARM 7l and won't run.
Strange setup. As the CPU is 64 bit, it may well run if you just remove t
On Sat, Sep 23, 2017 at 08:51:54AM +0200, pd wrote:
> I saw a message from you talking about not including arm binaries but in
> last tgz I got there's a binary include, should I remove it?
I don't know what the build process at F-Droid needs and can handle, so I think
it is better to leave it ins
It would great if Pilbox goes on F-droid. That would get it exposure to
users who don't trust Google Play.
Is there any chance of a version that works with 32-bit Android? I have
a Moto G4+ which has a 64 bit cpu (Snapdragon 617 iirc) but uses a 32
bit Android build, so Pilbox sees it as an ARM
Yes, I'll try and will post here my experience in order to help with any
trouble.
I saw a message from you talking about not including arm binaries but in
last tgz I got there's a binary include, should I remove it?
On Sat, Sep 23, 2017 at 8:32 AM, Alexander Burger
wrote:
> On Sat, Sep 23, 2017
On Sat, Sep 23, 2017 at 08:06:44AM +0200, pd wrote:
> I've created a github repository in https://github.com/pepdiz/pilbox and I
> can keep it synchronized to PilBox.tgz versions if you want
Yes, that would be nice!
The next task would be to publish it ad F-Droid. I haven't studied the
requireme
I've created a github repository in https://github.com/pepdiz/pilbox and I
can keep it synchronized to PilBox.tgz versions if you want
regards
On Thu, Sep 21, 2017 at 1:02 PM, Alexander Burger
wrote:
> On Thu, Sep 21, 2017 at 12:43:02PM +0200, Richard Z wrote:
> > assuming it is OpenSource, ho
I also vote +1 for submitting to f-droid.
Whoever takes care of the git repo, please **do not** include the arm64
binaries as part of the repo, otherwise over time it will grow quite
large (versioning) and become impossible to clone.
AW
On 17-09-21 11:02 AM, Alexander Burger wrote:
On Thu,
On Thu, Sep 21, 2017 at 01:02:32PM +0200, Alexander Burger wrote:
> On Thu, Sep 21, 2017 at 12:43:02PM +0200, Richard Z wrote:
> > assuming it is OpenSource, how about submitting to f-droid.org?
>
> This would be a good thing. F-Droid requires a git repo, perhaps of our
> maintainers likes to take
On Thu, Sep 21, 2017 at 12:43:02PM +0200, Richard Z wrote:
> assuming it is OpenSource, how about submitting to f-droid.org?
This would be a good thing. F-Droid requires a git repo, perhaps of our
maintainers likes to take care of it? It would follow the same principles as we
have with the PicoLis
On Mon, Sep 18, 2017 at 02:56:44PM +0200, Alexander Burger wrote:
> Hi all,
>
> finally, an official version of PilBox is out - and a Wiki article:
>
>https://picolisp.com/wiki/?PilBox
>
>
> PilBox ("PicoLisp Box") is a generic Android App which allows to write Apps in
> pure PicoLisp, with
On Wed, Sep 20, 2017 at 10:16:19AM +, Alexander Williams wrote:
> Also note, I had to "force stop" PilBox for the calculator to appear,
> otherwise I get "Not Found" page (404?).
That's right. The ZIP archive is only extracted on start of the App. I'm not
sure at the moment where the "Not Foun
I'm running LineageOS 14.1 (Android 7.1) and successfully installed
PilBox and the demo "calc.zip".
As Olaf mentioned, PilBox does not appear in the "Share" menu, and i'm
not sure why.
However when I download the file from https://software-lab.de/calc.zip
(Firefox), I get a notification from
Hi,
On Wed, Sep 20, 2017 at 10:49:59AM +0200, pd wrote:
> should be possible to interface with native android code? I suppose it
Not "native" in the PicoLisp sense (i.e. calling the 'native' function) as there
are C libraries accessible in Android. But with the Android toolbox, yes.
> would be
should be possible to interface with native android code? I suppose it
would be similar to interface with java in common picolisp. The goal would
be to have native app rather than web apps inside an html content
On Wed, Sep 20, 2017 at 10:22 AM, O.Hamann wrote:
> Hello,
>
> short update:
>
> on
Hello,
short update:
on dtek50/Android 6.01 Pilbox works as expected, I think (though I did
not go through all demo buttons).
Don't know, why this did not work yesterday, possibly a system update
was interfering while trying Pilbox. I did not change anything, just
after restart of the mobil
Hi Olaf,
> But no luck so far.
Hmm, too bad!
For me it worked without problems in both ways (via "Downloads" as well as
'termux-share'). How is the experience of others here?
> I'm using a SM-T719 tablet, which some day got the update to android 7
> (german language) and I do not have any clue
Thank you very much for that quick reply, Alex.
But no luck so far.
Thanks for your hints and explanations. Another install approach by
downloading the apk from the softlab url finishes in the same result.
I'm using a SM-T719 tablet, which some day got the update to android 7
(german languag
Hi Olaf,
> I'm very excited about your announcement, so I tried it out immediately :-)
Great! :)
> Unfortunately I had no luck so far to 'pass the zip to the Pilbox kernel' -
> tried it out with the provided hello.zip and calc.zip.
The PilBox App needs permission to access storage. Did you ena
Hi Alex,
I'm very excited about your announcement, so I tried it out immediately :-)
Installation via Google Play worked without problems after searching for
de.software_lab.pilbox
Pilbox starts as documented in the wiki and repl eval works for e.g.
'(version)' and '$ pwd'
Unfortunately I
Back when I played with it, it could also run ARM apks via
emulation.
On 2017-09-18 19:52, Alexander Burger wrote:
> On Mon, Sep 18, 2017 at 07:10:01PM +0200, Jakob Eriksson wrote:
>> What went of Android x86?
>
> Would work if somebody compiles the bin/picolisp binary for x86-64 with the
> Andro
On Mon, Sep 18, 2017 at 07:10:01PM +0200, Jakob Eriksson wrote:
> What went of Android x86?
Would work if somebody compiles the bin/picolisp binary for x86-64 with the
Android NDK.
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
What went of Android x86?
> 18 sep. 2017 kl. 18:19 skrev Alexander Burger :
>
> Hi Rick,
>
>> BTW, since I don't have an Android device, I assume that there is a way
>> to VM my way to glory and fame in PilBox dev. :)
>
> The closest thing I can think of is using the emulator(s) that come with
Hi Rick,
> BTW, since I don't have an Android device, I assume that there is a way
> to VM my way to glory and fame in PilBox dev. :)
The closest thing I can think of is using the emulator(s) that come with Android
Studio. Haven't tried though ...
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@softwa
On Mon, 18 Sep 2017 14:56 +0200, Alexander Burger wrote:
> Hi all,
>
> finally, an official version of PilBox is out - and a Wiki article:
>
>https://picolisp.com/wiki/?PilBox
Ah! This is wonderful! Thank you! (BTW, in sharing this with a friend
today, I characterized this as "a way to de
Hi all,
finally, an official version of PilBox is out - and a Wiki article:
https://picolisp.com/wiki/?PilBox
PilBox ("PicoLisp Box") is a generic Android App which allows to write Apps in
pure PicoLisp, without touching Java, and without the need of an Android SDK.
You can get the App (the
32 matches
Mail list logo