From: Hetz Ben Hamo <hetzbh@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] news on the OS X cocoa port
Date: Thu, 21 Jul 2005 12:12:17 +0200 [thread overview]
Message-ID: <41e41e7a0507210312259ae3d5@mail.gmail.com> (raw)
In-Reply-To: <42DF6E93.3010705@kberg.ch>
I just looked at the screenshots, and if you don't mind, I want to
offer few suggestions for your GUI:
1. RAM size - how about adding up/down arrows (in addition to what you
have right now) to increase RAM?
2. Instead of Radio buttons in the Floppy/CDROM/Hard drive, I would
suggest to replace it with Check Boxes, so the ones that are not
needed by the user, will be grayed out until the check boxes will be
marked.
3. I would also suggest to add a "Boot from" pull down menu - to
select from which device to boot (useful for CD installation etc..)
Thanks,
Hetz
On 7/21/05, Mike Kronenberg <mike.kronenberg@kberg.ch> wrote:
> Based on experiences with Q, I rewrote the cocoa port.
>
> It features now:
> - Keyboard
> - Mouse
> - Full screen
> - Hardware CD-Rom support
> - Possibility to create/save guest PC profiles
> - Toolbar to load images for fd/cd and save/shutdown/reset guest PC
> - graphic interface to create/change/delete/start guest PCs
> - new command line options (only for the cocoa port)
>
> At the moment it lacks:
> - Sound
> - possibility to start multiple guest PCs
>
> The diff is rather large (~800kb). You find diff and binaries at:
> http://www.kberg.ch/q
>
> It compiles on 10.2.x (search this list for questions on poll.h) and 10.3.x
> The binaries provided should run on 10.3.x and 10.4.x
>
>
> At the moment I got stuck with cleaning up after a guest PC, so I can
> start a new one or even multiple guest PCs. (this is still perfectly
> possible with multiple instances of QEMU)
>
> I create a new Object (cocoaQemu.m) for the guest PC, then I start the
> guest PC with a new NSThread. After completion, I can create a new
> Object, but the guest PC won't start. (I called/rewrote the functions
> in atexit but there must be some more things to be cleaned up before)
>
> There are some Problems with multiple guest PCs at the same time, too.
> For Example: '-smb' creates a temp directory with the PID. This makes
> multiple smb configurations impossible. It might be better to use a
> timestamp.
>
> I'm not sure whether that was ever intended.
> So if you have an Idea, please drop a note.
>
>
>
> Mike
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2005-07-21 10:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 9:44 [Qemu-devel] news on the OS X cocoa port Mike Kronenberg
2005-07-21 10:12 ` Hetz Ben Hamo [this message]
2005-07-21 12:33 ` Mike Kronenberg
2005-07-21 13:46 ` Hetz Ben Hamo
2005-07-21 17:33 ` Stealth Dave
2005-07-21 18:21 ` Natalia Portillo
2005-07-22 9:58 ` Pierre d'Herbemont
2005-07-22 11:28 ` Mike Kronenberg
2005-07-21 14:00 ` René Korthaus
2005-07-21 15:20 ` Jim C. Brown
2005-07-22 7:51 ` Mike Kronenberg
2005-07-22 8:44 ` René Korthaus
2005-07-22 9:42 ` Mike Kronenberg
2005-08-04 7:36 ` Mike Kronenberg
2005-08-04 18:39 ` Natalia Portillo
2005-08-05 11:45 ` Mike Kronenberg
2005-08-14 19:18 ` Mike Kronenberg
-- strict thread matches above, loose matches on Subject: below --
2005-07-22 2:05 Joshua Root
2005-07-22 7:28 ` Mike Kronenberg
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=41e41e7a0507210312259ae3d5@mail.gmail.com \
--to=hetzbh@gmail.com \
--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.