From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fr0hL-0001K8-9S for qemu-devel@nongnu.org; Thu, 15 Jun 2006 18:52:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fr0hJ-0001J7-Ic for qemu-devel@nongnu.org; Thu, 15 Jun 2006 18:52:22 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fr0hJ-0001J4-FG for qemu-devel@nongnu.org; Thu, 15 Jun 2006 18:52:21 -0400 Received: from [199.80.85.4] (helo=library.beau.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Fr0qn-0006E0-Ok for qemu-devel@nongnu.org; Thu, 15 Jun 2006 19:02:10 -0400 Received: from mjolnir.library.beau.org (mjolnir.library.beau.org [199.80.85.12]) (authenticated bits=0) by library.beau.org (8.12.11.20060308/8.12.11) with ESMTP id k5FMqE8u016702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 15 Jun 2006 17:52:14 -0500 From: John Morris In-Reply-To: <4491DF66.2090304@gmx.de> References: <44902362.2000406@gmail.com> <200606141601.59936.paul@codesourcery.com> <4490310D.7060303@gmail.com> <44903504.1070707@gmx.de> <1150357642.5679.7.camel@excellence.kicks-ass.net> <9b0d5f320606150618q25cd2b51v6a2ee6fc951f26b9@mail.gmail.com> <44916C36.50505@gmail.com> <4491C457.2080402@gmail.com> <4491DF66.2090304@gmx.de> Content-Type: text/plain Message-Id: <1150411933.3016.26.camel@mjolnir> Mime-Version: 1.0 Date: Thu, 15 Jun 2006 17:52:14 -0500 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Doing a Tcl/Tk based frontend Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Thu, 2006-06-15 at 17:29, Oliver Gerlich wrote: > If you are familiar with Tcl/Tk, maybe you could give some hints on how > to embed the Qemu window into such an app? Embedding the emulator's window might not be the best way to attack the problem. Especially since you would need to be able to detach it to be able to go full screen. I have pondered the Tk frontend idea before so lemme dump my random thoughts on the subject and see how many holes get punched in em. How about one Tk window as a 'master controller' for all VMs and each running VM opens a new window. The master window gets a tab for each running VM and a seperate interpreter spawned to monitor the console (running on stdin/stdout piped back to Tcl) for events and update the widgets and send commands in response to user input. That gets you media insert/remove, serial port attachment, etc. Doing it that way means QEMU itself requires no modifications, but might in reality need some small adjustment to make the console interface more rigid, otherwise I suspect expect would need to get involved to deal with communications with with the existing console. -- John M. http://www.beau.org/~jmorris This post is 100% M$Free! Geekcode 3.1:GCS C+++ UL++++$ P++ L+++ W++ w--- Y++ b++ 5+++ R tv- e* r