From mint-bounce@lists.fishpool.fi Thu Jul 21 01:08:55 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <20050720170631.nsxp3chxtpz444kg@coolrunningconcepts.com> Date: Wed, 20 Jul 2005 17:06:31 -0600 From: evan@coolrunningconcepts.com To: Jo Even Skarstein Cc: MiNT Mailing List Subject: Re: [MiNT] WCOWORK implementation : conclusions. References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - esc14.midphase.com X-AntiAbuse: Original Domain - fishpool.com X-AntiAbuse: Originator/Caller UID/GID - [32001 502] / [47 12] X-AntiAbuse: Sender Address Domain - coolrunningconcepts.com X-Source: X-Source-Args: X-Source-Dir: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: evan@coolrunningconcepts.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-0.4 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, NO_REAL_NAME X-Spam-Level: Quoting Jo Even Skarstein : > Another variant of this argument was related to WINDOW and WINDOM > components. It was claimed that WINDOW will get all confused if some > components use WCOWORK and other's don't. If this is the case then this is a > weakness in the design and specification of WINDOM (remember, all protocols > and interfaces must be clearly defined and documented), or a result of > sloppy programmers who doesn't read and respect specifications. It comes down to - can any lib other than windom perform a wind_creat() ? windom will pass it all the events. If the 3rd-party lib uses WCOWORK and Windom doesn't, then Windom gets the events wrong. If the 3rd party library doesn't use WCOWORK, and Windom does, then the window is created wrong. I can't say in all honestly that dividing the event handling code from the code that actually opens windows and works with them is a bad thing, and I don't think it is. Can we have the all benefits of WCOWORK without this restriction? > I sincerely hope Ozk continues his work and adds more functionality to > XaAES. I want to see the above multipage forms and multiline editfields for > example. Now that's something that will significantly simplify development > of useful applications! Now, if I only could get my dead Milan fixed I could > start programming again... Multiline editfields is okay. In fact, "Notepad" is just that, a big multiline edit field. Multipage forms ... tabbed windows I like, but tabbed dialogs I don't care for much.