From mint-bounce@lists.fishpool.fi Mon Jul 11 23:31:56 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Mon, 11 Jul 2005 23:31:14 +0200 From: Ingo Schmidt X-Mailer: The Bat! (v3.5) Professional Reply-To: Ingo Schmidt X-Priority: 3 (Normal) Message-ID: <14536671.20050711233114@der-ingo.de> To: MiNT-Liste Subject: [MiNT] Re[2]: Re[3]: usage of wind_calc() In-Reply-To: References: <200507110924.p64215@ll.maus.de> <1459271786.20050711221117@der-ingo.de> <981831656.20050711221403@der-ingo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:58e864169f3ef71bae3e2b831e61e1a6 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ich@der-ingo.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: Hi MiNT-Liste! > Who told about fixing a bug ??? I meant "working around a bug that no one seems to know". This is what I found strange. > I've never said that windom compute the WORK area that way and not another > way because of this bug ! No, but u said that there are buggy AESs. So far I still don't know which AES is buggy. And thats basically all I wanted to know. > There are for sure other reasons (internal to windom, to have a > simplier and easy-to-maintain design). Aha! Well, originally it sounded a bit like: "There is some bug that may or may not be there, that is why Windom totally handles everything itself". This is why I reacted like I did. Because here is my point of view: We should assume a working and flawless OS and use all the cool features it has! Should some OS be buggy or not have the feature at all, well, then we make a special workaround for this annyoing OS or we kick the devloppers arse until it has the feature or - in the case of MagiC, we just format our harddrive and install a decent OS ;-) Do you get my point? I dont know Windom good enough to tell if has super extra features for the toolbar. But my preferred way would be this: Implement decent toolbar support in the AES. And then USE that toolbar support. After all we have two active AESs. And make workarounds for AES that are buggy. Even though a lib like Windom is certainly a nice thing, I am not a fan of reinventing the wheel and bypassing the OS. And this is the impression I got espcially because u mentioned this bug that I have never seen. But now Evan has pointed it out. Well, it was a bug in the old AES! Thats another one! For how long are we going to support bloody old TOS? I think there are enough apps available for TOS. But I dont think we should make every app be able to run even under the oldest OS thinkable! I agree with Evan: Let's move forward! Throw the old stuff overboard. Set some standards! But I know, not everone thinks like that. This might end up in a bad discussion, I know ;-) Cheers, Ingo =;->