From mint-bounce@lists.fishpool.fi Mon Jan 11 14:57:22 2010 Message-ID: <4B4B821C.7070706@online.no> Date: Mon, 11 Jan 2010 20:55:08 +0100 From: Jo Even Skarstein User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: mint Subject: Re: [MiNT] HRD's & RSC's References: <1263235930.16683.4223.camel@jetpack.demon.co.uk> <11a6f2b11001111117q274f2e98k69aa7b8162fcbec3@mail.gmail.com> <11a6f2b11001111138g3cb4fcclf1dcbe2ec37f0f1c@mail.gmail.com> In-Reply-To: <11a6f2b11001111138g3cb4fcclf1dcbe2ec37f0f1c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Paul Wratt wrote: > as long as people remember that any even if the resource can be output > as c code, that will need a specific make line to recreate, and that > the resource itself needs to be easy maintained and adjustable, which > is inherantly not the case when converting resource files to a source > code format (C or ASM) Another solution is to create a RSC editor that loads and saves ASCII files. Then the metadata (HRD-files) could be saved together with the resource data, and the ASCII files could be converted to RSC-files with a small tool while building XaAES. This could be useful in an IDE too, because you can store references to code as metadata in the ASCII RSC. Then it would be possible to create a "Visual GEM" IDE. Jo Even