From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C2CSy-00037i-P7 for qemu-devel@nongnu.org; Tue, 31 Aug 2004 13:30:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C2CSw-00036z-Fg for qemu-devel@nongnu.org; Tue, 31 Aug 2004 13:30:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C2CSw-00036k-8U for qemu-devel@nongnu.org; Tue, 31 Aug 2004 13:30:42 -0400 Received: from [213.146.130.142] (helo=trantor.org.uk) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1C2CNy-0007Ex-F0 for qemu-devel@nongnu.org; Tue, 31 Aug 2004 13:25:34 -0400 Subject: Re: [Qemu-devel] Qemu development schedule? From: Gianni Tedesco In-Reply-To: <1C8FBBB0-FB2F-11D8-8B6F-000A95D874F4@mac.com> References: <000501c48eda$a026ab40$20649c3f@computername> <200408310107.07350.hetz@witch.dyndns.org> <002101c48ee5$46b2e280$20389c3f@computername> <1093908872.26682.76.camel@aragorn> <1C8FBBB0-FB2F-11D8-8B6F-000A95D874F4@mac.com> Content-Type: text/plain Date: Tue, 31 Aug 2004 18:23:29 +0100 Message-Id: <1093973009.29476.16.camel@sherbert> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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 Tue, 2004-08-31 at 05:21 -0400, Kai Cherry wrote: > On Aug 30, 2004, at 7:34 PM, John R. Hogerhuis wrote: > > > Polish (nice frontend) is something that can be thrown on later once > > the > > core functionality is in (that means speed, accuracy, and hardware > > emulation, in that order, IMHO...) > > I think this is actually a *failing* of most FOSS projects...the > afterthought of how "regular" folks will *use* the thing. Technically, if the primitives and operations the programmer exposes to the uppermost level of API are sound, an effective UI that makes sense *can* be quite simply "bolted on". The real failing of such projects is identifying what are the primitives, and how do they interact. The confused low level design leads to confused top level design. The same applies in reverse with a top-down design. That is to say, if the top level design is confused, then the core functionality will never work right. > Then again, I'm a mac developer; we learn to design the solution around > people ;) > > (thats a friendly jab folks... :)) That must mean you find that task of adapting software to users requirements fun? Or you wouldn't develop in that environment right? If so, then you are in a good position to make these kinds of changes happen in qemu for example... ;) -- // Gianni Tedesco (gianni at scaramanga dot co dot uk) lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import 8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D