From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: ** X-Spam-Status: No, score=2.4 required=5.0 tests=AWL,DNS_FROM_RFC_ABUSE, DNS_FROM_SECURITYSAGE,SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 50D82BBAF for ; Wed, 5 Nov 2008 17:41:41 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As8BAHVbEUlDWxLCbmdsb2JhbACBd5IiPq1uhl6ELoNT X-IronPort-AV: E=Sophos;i="4.33,551,1220220000"; d="scan'208";a="31155024" Received: from ip67-91-18-194.z18-91-67.customer.algx.net (HELO server1.bertec.net) ([67.91.18.194]) by mail4-smtp-sop.national.inria.fr with ESMTP; 05 Nov 2008 17:41:40 +0100 Received: from kuba.bertec.net (kuba.bertec.net [192.168.2.16]) by server1.bertec.net (Postfix) with ESMTP id 2235E105735 for ; Wed, 5 Nov 2008 11:41:40 -0500 (EST) From: Kuba Ober To: caml-list@yquem.inria.fr Subject: Re: [Caml-list] What does Jane Street use/want for an IDE? What about you? Date: Wed, 5 Nov 2008 11:41:38 -0500 User-Agent: KMail/1.9.10 References: <200810200919.41561.ober.14@osu.edu> <200811051044.25761.ober.14@osu.edu> <200811051703.06578.jon@ffconsultancy.com> In-Reply-To: <200811051703.06578.jon@ffconsultancy.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811051141.39493.ober.14@osu.edu> X-Spam: no; 0.00; trolls:01 bug:01 trolls:01 bug:01 cheers:01 paints:98 feat:98 caml-list:01 hierarchical:01 hierarchical:01 implemented:02 implemented:02 hierarchy:03 hierarchy:03 evaluating:06 > > And neither QPainterPath nor QPicture are really hierarchical. About the > > only way to think of a hierarchy for Qt's drawing system is at the level > > of QPainter, which provides save() / restore() functionality for its > > state. All of this structure is implemented by the QPainter(), so as soon > > as a QPainter() paints on a QPaintDevice(), what little hierarchy was > > there is irretrieveably lost. > > There shouldn't even be any state. I agree, but in absence of hierarchy they resort to kludges like that... > > So Qt would benefit from having real, hierarchical display lists, which > > could then be expanded to include 3D functionality. Trolls may well be > > working on this (I hope they do!), but it's no small feat to have it done > > in a way which "just works" like most of Qt does. > > That is exactly what WPF already provides. Trolltech told me they were > working on it when I was evaluating buying the commercial Qt. That was at > least 5 years ago. I doubt Qt will live long enough to ever see it > implemented. At least they now have QPainterPath -- I wish they worked harder on ubiquitous display lists, though. > > Qt is not bug free, and a colleague of mine is hard at work bugging the > > trolls with a new (mostly event-related) bug every week (not kidding > > you). But he really runs into some corner/less-than-well-documented cases > > due to what he's trying to do. Yet that's still way better than dealing > > with a toolkit that's fairly new (MPC) or something that gives you 10% of > > the functionality you need. > > What is MPC? s/MPC/WPF/ My brain is playing tricks on me ;) Cheers, Kuba