From mint-bounce@lists.fishpool.fi Wed Jul 20 09:10:42 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <42DDF84C.10409@asrael.franken.de> Date: Wed, 20 Jul 2005 09:07:56 +0200 From: =?ISO-8859-1?Q?Andreas_B=E4r?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7.2.0 X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: MiNT List Subject: Re: [MiNT] WCOWORK implementation : conclusions. References: <1121808544.5660.30.camel@linuxbox> <20050719215349.6dlkrcbl47c4g88s@coolrunningconcepts.com> In-Reply-To: <20050719215349.6dlkrcbl47c4g88s@coolrunningconcepts.com> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: asbaer@asrael.franken.de 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=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j6K7AfYR026451 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I followed the thread all the time and as there was the question for some comments, so here are my thougths on the topic. I understand the need for the WCOWORK-mode and i second it. As i started to code some smaller programs i found it quite anoying to convert between FULL an WORK-areas. WORK area was/is the area i cared about, FULL was what the AES told my about the windows. If there is a function-mode where a application only has to care about the WORK-area, i think this would be a clarifying and easier to handle step. What i see in the discussion is that there is a misunderstanding between the two partiesand i really can't understand it. As Ozk stated several times: a app that deals the normal/old-way (not using the WCOWORK-mode) will function as known, no need to care about it. But if, and _only then_, a app wants to run in the WCOWORK-mode, it will get the new returns. To get in the new mode - the app has to turn it on, its like Pdomain(). If i got it right and its functioning that way - great! No problem for me, all i can say is 'Good Job'. > I mostly agree, but it is concievable that a library would want to > simply open a > window. Assume that windom will manage all the events for this window > and send > the library just redraws, and tell the library when the window is closed. > This isn't all that unclean, but the parameters to wind_create are > suddenly not > what the library expected if you are in WCOWORK mode. As i stated above - the app has to turn the mode on - so it knows about the mode and has to handle it in the right way. Just my thoughts, Andi - -- Andreas Bär asbaer@asrael.franken.de PGP-key available on request! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC3fhM4DhmfzHiEH0RAl+nAJ4sj0HbY3Zcg9vZr2izKoE3Pk/iygCg1C/2 e6tRTCxJxIMMeW4EdpqNNOA= =SoCq -----END PGP SIGNATURE-----