From owner-freebsd-hackers Thu Apr 29 6:23:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from excalibur.oceanis.net (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id 3300015838 for ; Thu, 29 Apr 1999 06:23:19 -0700 (PDT) (envelope-from pixel@excalibur.oceanis.net) Received: (from pixel@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id NAA06412; Thu, 29 Apr 1999 13:23:05 GMT From: Emmanuel DELOGET Message-Id: <199904291323.NAA06412@excalibur.oceanis.net> Subject: Re: Adding desktop support (please don't) In-Reply-To: from Thomas Valentino Crimi at "Apr 29, 1999 8:45:22 am" To: tcrimi+@andrew.cmu.edu (Thomas Valentino Crimi) Date: Thu, 29 Apr 1999 15:23:05 +0200 (MET DST) Cc: hackers@FreeBSD.ORG (FreeBSD Hackers Mail List) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As the well known Thomas Valentino Crimi said... -> -> One alternative I'd like to propose is an icons.db file, laid out for ->optimum keysearch, with the .ICON elf section possibly containing a ->unique identifier for the binary. The .db file could contain multiple ->versions of each icon, in all the popular styles, and the user could ->have his/her own .icons.db file which is searched prior to the system ->list. Next comes /usr/local/share/icons.db where the administrator ->could install 'icon packages' to override system-default binaries as ->well as icons for the ports. Now, from here we would need to add in some ->pkg_add, pkg_delete like utilties icon_add, icon_delete which access ->this db.. the syntax could look like -> -> icon_add [stylename:iconfile]... -> ->where icon_add could extract the unique identifier from the binary, and ->then add in the iconfile. The user can then always retrieve icons of ->any style type from the db, and everyone can have the interface they ->want. -> ->I volunteer to send patches if people want this :) I think this idea is far more better than putting ressources into the executable. Those magic could be generated by md5 or something else. In addition to icons, we could have a generic way to handle any kind of ressources (dtd for usage and so on). It just need a decent interface, a way to avoid duplication of ressources, and we have it. -> -> icond? anyone? -> ->Thomas -- __________________________________________________________________________ Emmanuel DELOGET [pixel] pixel@{dotcom.fr,epita.fr} ---- DotCom SA http://www.epita.fr/~pixel | http://www.dotcom.fr/~pixel "On the last day, God created Linux. And Microsoft won its antitrust case" -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message