From: llandre <r&d2@dave-tech.it>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC] Host tool to perform semiautomatic updates
Date: Fri, 14 Mar 2008 17:18:30 +0100 [thread overview]
Message-ID: <47DAA556.5070904@dave-tech.it> (raw)
In-Reply-To: <47DA8A69.6000700@gmail.com>
> How about expect? This should get you started:
> http://en.wikipedia.org/wiki/Expect
>
> If you want to use Windows I'd go with expect through cygwin rather than
> the native Windows port of expect.
>
> You can of course do all of this in something more modern like Python,
> but that might be a steeper learning curve.
I thought about expect/cygwin but in my opinion is too hard to use for
the average Windows operator who expects just to:
- install the application by running an .exe or unzipping a .zip
- launching the application
- press a couple of buttons on GUI and see the result.
I think Python could be a very good solution. Since I never worked with
it, I ask just few questions:
1) for Windows platform, is possible to generate one single .exe file
taht includes all the required stuff (such as libraries and runtime
components)? If not, it is possible to group all of them in one single
.zip file?
2) What about serial ports support? Is this really platform independent?
3) What about graphical interface? Is it possible to use the same
library (and consequently have similar look&feel) on Windows and Linux?
Cheers,
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave.eu
email: r&d2 at dave-tech.it
next prev parent reply other threads:[~2008-03-14 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 14:10 [U-Boot-Users] [RFC] Host tool to perform semiautomatic updates llandre
2008-03-14 14:18 ` Øyvind Repvik
2008-03-14 14:23 ` Ben Warren
2008-03-14 16:18 ` llandre [this message]
2008-03-14 17:58 ` Nicolas Colombain
2008-03-14 19:31 ` Hoi-Ho Chan
2008-03-14 19:32 ` Hoi-Ho Chan
2008-03-15 9:25 ` llandre
2008-03-15 12:20 ` Markus Klotzbücher
2008-03-16 18:18 ` Robert Schwebel
2008-03-14 15:33 ` Wolfgang Denk
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=47DAA556.5070904@dave-tech.it \
--to=r&d2@dave-tech.it \
--cc=u-boot@lists.denx.de \
/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