From mint-bounce@lists.fishpool.fi Thu Aug 5 17:19:17 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=Bw1/jU3VE1AwOokGD1BTSFkBFZfKh31rz/2eDihSeBg=; b=IzViE05kRFfxGbmT1D5aV23/9oKk0maav5O9xyKlYxnoWiPiWLrqZYvI7+Invq/KoH 8BeOqeItZhZA6ulm5hi/wuZ/jR+Qagz10AMVqNhetpXThLqUHEsbboP73pxfGzu+qjTy 1mNvYcXQGJwgn6LlEGkq+j/J+RcfrQlioyY3c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=NMg/UDfLhM1ErNkmrPuRQfKrxQfT27I1ZDL5IieRI8+3vGH63cPGC2xl1lZISNlxDN PXZYr1jd0TivfhuqJ839MIS510hosbXPKpwIOhI6S3ibmgdJdz9mNEoML3JVdOvSUd2Y Wp3WvlwMDL4bgdPoMzR3uXQM/agSgFWQfUXz8= Subject: Re: [MiNT] XaAES Gradients Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Peter Persson In-Reply-To: Date: Thu, 5 Aug 2010 23:17:16 +0200 Cc: mint@lists.fishpool.fi Message-Id: <5499E7FB-67C6-4E2E-A139-3F16E5D82C2D@gmail.com> References: To: Helmut Karlowski X-Mailer: Apple Mail (2.1081) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o75LJGRR024437 5 aug 2010 kl. 22.35 skrev Helmut Karlowski: > Am 05.08.2010, 19:06 Uhr, schrieb Paul Wratt : > >> I know that there is a hold on new additions to MiNT/XaAES, but could ---- snip ---- >> I also propose a change to the default gradients for this release >> dedicated to Frank, I think the G_YELLOW.C would produce the best >> result. > > I do not understand anything on this topic. > > I think it's better to do this when there's more time. Shouldn't this be solved by providing an external API to it all? My impression is that XaAES has fairly sophisticated theme handling internally, but right now all we have is hardcoded coder-colours. Extended texture patches and new patches for new hard coded themes doesn't really feel like the answer to it all. Feels like a waste of resources for something that in the end is a matter of taste for each user. -- PeP