All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Ulmer <lionel.ulmer@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU feature idea: simple macros/scripting
Date: Fri, 1 Oct 2004 09:09:23 +0200	[thread overview]
Message-ID: <20041001090923.A10836@bbland> (raw)
In-Reply-To: <Pine.LNX.4.58.0410010216020.5953@wgmdd8.biozentrum.uni-wuerzburg.de>; from Johannes.Schindelin@gmx.de on Fri, Oct 01, 2004 at 02:19:39AM +0200

On Fri, Oct 01, 2004 at 02:19:39AM +0200, Johannes Schindelin wrote:
> > Macros/Scripting. For the most part, on my machines Windows is a very
> > manual labor intensive peripheral.
> 
> I started to write a vnc frontend for QEmu. On the other end, I started to
> write a scriptable vnc viewer. The use of this? Macros/Scripting for QEmu,
> but also Macros/Scripting for everything which can be controlled by a
> vncviewer. For now, I use an adaption of vncrec, which just records inputs
> and timestamps, and play those inputs back later.

What could also be investigated is the 'regression' tool supposedly written
by CodeWeavers for Wine (I never played with it so I do not know the current
status - i.e. freely distributable or not) but it looks similar to what you
want to do: automatic button presses on dialog buttons, checking of results,
...

The problem is that I have no idea if it works at a pure 'bitmap' level or
if it needs to have knowledge of the window hierarchy and stuff like that
(i.e. hooks into Win32 or X11 via some API calls).

     Lionel

-- 
		 Lionel Ulmer - http://www.bbrox.org/

  parent reply	other threads:[~2004-10-01  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 23:55 [Qemu-devel] QEMU feature idea: simple macros/scripting John R. Hogerhuis
2004-10-01  0:19 ` Johannes Schindelin
2004-10-01  3:40   ` John R. Hogerhuis
2004-10-01  9:54     ` Johannes Schindelin
2004-10-02  4:58       ` John R. Hogerhuis
2004-10-01  7:09   ` Lionel Ulmer [this message]
2004-10-01 10:08     ` Johannes Schindelin

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=20041001090923.A10836@bbland \
    --to=lionel.ulmer@free.fr \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.