From mint-bounce@lists.fishpool.fi Thu Jan 7 02:23:28 2010 Message-ID: <816BC8A5FA274D309A679DA4D22B3041@mercatus.local> From: "Jo Even Skarstein" To: References: <4B44ED09.8030503@atari-source.org> <00223362.01a816d6397e@smtp.freeola.net> <4B4513BD.9080107@atari-source.org> In-Reply-To: <4B4513BD.9080107@atari-source.org> Subject: Re: [MiNT] QED Date: Thu, 7 Jan 2010 08:20:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-EsetScannerBuild: 6345 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: -------------------------------------------------- From: "Mark Duckworth" Sent: Wednesday, January 06, 2010 11:50 PM To: Subject: Re: [MiNT] QED > Seems I forgot the core of the question ;) > > 1. Would you like and use this (you already answered that)? Maybe, depending on how good it is ;-) For a big project like FreeMiNT/qed I would probably use something like this. For a small project I'm very happy with the PureC IDE. It's fast, simple and gets the job done. > 2. Should I build this into QED or fork QED to keep QED small and lean? a) Fork qed. b) Don't fork, but make it possible to compile a plain text-editor as well as the complete IDE. c) Don't integrate everything into one binary, but create several tools and tie them together with a clever protocol. Personally I'd prefer (c). It's easier to create several small tools than one huge program. And it's easier to debug and easier to maintain. You will get the project to a usable state quicker, and it would be easier to extend it with new tools later on. Jo Even __________ Information from ESET NOD32 Antivirus, version of virus signature database 4749 (20100106) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com