From: Bzzzz <lazyvirus@gmx.com>
To: Sebastiaan Stoffels <seb@sebastiaan-stoffels.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: silly (?) questions
Date: Tue, 8 Aug 2017 16:06:43 +0200 [thread overview]
Message-ID: <20170808160643.48db441c@msi.defcon1> (raw)
In-Reply-To: <4447c9b3-29c1-b439-3a2f-f9e218e3423e@sebastiaan-stoffels.com>
On Tue, 8 Aug 2017 21:05:57 +1000
Sebastiaan Stoffels <seb@sebastiaan-stoffels.com> wrote:
Your post:
* doesn't address ANY of my questions,
* sounds more like a Bud commercial, minus the fun,
so, thanks, but no thanks.
JY
> Jean-Yves,
>
> I just got back from Pycon AU and there was a session on Beeware which
> has a great bunch of tools for cross platform GUI development (
> including Android ). Well worth a look:
>
> https://pybee.org/project/using/android-app/
>
> You could then use the same code to package up an app for other
> platforms. It even does installers and packaging!
next prev parent reply other threads:[~2017-08-08 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 5:23 Bzzzz
2017-08-08 11:05 ` Sebastiaan Stoffels
2017-08-08 14:06 ` Bzzzz [this message]
2017-08-08 16:06 ` Jason A. Donenfeld
2017-08-08 16:38 ` Bzzzz
2017-08-08 21:13 seb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170808160643.48db441c@msi.defcon1 \
--to=lazyvirus@gmx.com \
--cc=seb@sebastiaan-stoffels.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).