Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (hermes.apache.org: domain of diwakergupta@gmail.com
 designates 64.233.184.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=SsZVsRJFdV57DlZO0iXKCr6XvWD/7uDaQaAMhVbrQzT9TevV7BkLgv/83XaLX6JTPHCZSPf93fNJ+OjnW5zZS5I+7lFGlC4CEcYjnZkaJ2mD0xde8Fwe7eLU1z1mSzw7dnFVBIxiWDo3U7C6OcwQFvBF6fmDZjvJ3l3pBSYzwR0=
Message-ID: <1b0b4557050609130626ee6e88@mail.gmail.com>
Date: Thu, 9 Jun 2005 13:06:08 -0700
From: Diwaker Gupta <diwakergupta@gmail.com>
Reply-To: Diwaker Gupta <diwakergupta@gmail.com>
To: dev@forrest.apache.org
Subject: Re: [views] forrest:contracts - naming convention
In-Reply-To: <1118344589.5082.47.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <1118281527.28039.32.camel@localhost.localdomain>
	 <1b0b4557050609012328e31632@mail.gmail.com>
	 <1118344589.5082.47.camel@localhost.localdomain>

> I agree again with a small addition. The idea is that contracts are
> within groups:
> - branding
> - nav
> - search
> - content
> - siteinfo
>=20
> That makes it easier to group the contracts by this functionalities and
> adding new contracts based on the above mentioned categories. Using your
> input I recommend:
> content-pdf-link
>=20
> The advantage I see is that the designer nows that he can choose from
> this categories and directly knows what kind of contract he will get in
> return. I do not know whether I can explain it right, keep on throwing
> your thoughts.

Perfecto! I'm +1 on this.

--=20
Diwaker Gupta
http://resolute.ucsd.edu/diwaker