Mailing-List: contact dev-help@tiles.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tiles.apache.org
Received-SPF: pass (nike.apache.org: domain of nbubna@gmail.com designates
 209.85.211.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=wPBYQTYq1NPrDCWDxw8Ia0tTr6ycdMZc1sOO061yi9gWNu5O0TElwxzmrdrsrK/qO+
         QoBoI1btcTnPT1R8KuGd6UyGwjcguFk5t53QwrISLPZZfP1ceoPR4slT3JY8lf8GZauM
         ogc6YsTi5uux+kq1/8sa/Kp7NaAxH/dp733Kc=
MIME-Version: 1.0
In-Reply-To: <aae96ca1001161142g5f096a13u5f8f69fb503ec43@mail.gmail.com>
References: <aae96ca1001161107i280e468er1f2b1cc212eb8da2@mail.gmail.com>
	 <4d651da51001161132m80212aah18f710d155825dd1@mail.gmail.com>
	 <aae96ca1001161142g5f096a13u5f8f69fb503ec43@mail.gmail.com>
Date: Sat, 16 Jan 2010 14:08:05 -0800
Message-ID: <4d651da51001161408n7d8d7292s7415ffde963ac31e@mail.gmail.com>
Subject: Re: Velocity support: I was completely wrong
From: Nathan Bubna <nbubna@gmail.com>
To: dev@tiles.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 16, 2010 at 11:42 AM, Antonio Petrelli
<antonio.petrelli@gmail.com> wrote:
> 2010/1/16 Nathan Bubna <nbubna@gmail.com>:
>>> Note that the VelocityStyleTilesTool is ok, since it is a *real* tool:
>>> http://tiles.apache.org/framework/apidocs/org/apache/tiles/velocity/tem=
plate/VelocityStyleTilesTool.html
>>
>> yep. =A0even if it's API is a bit verbose. ;)
>
> Why verbose? It's got only 11 methods and 0 or 1 parameter. What are
> you referring to?

the method names, not the size or complexity of the API.
specifically, 9 of 11 methods include the word 'Attribute'.
Personally, i would leave that to be implied, especially with things
like renderAttribute(Attribute) or cloneAttribute(Attribute) where it
is clearly redundant, and shrinking getAttribute(String) to
get(String) would enable the much cleaner $tiles.myAttrKey syntax.

granted, the explicitness of the current method names offers extra
mental clarity/simplicity.  i know enough people who prefer that to
short and/or overloaded method names, that i'm not dogmatic.  i just
can't help making comments sometimes. :)

>>> IMHO the best thing to do is to delete it, though we released a beta
>>> version of the 2.2 series.
>>
>> i have no love for it. =A0but beta is not alpha. =A0can we deprecate for=
 a
>> version and delete in the subsequent one?
>
> Sure, it will be deleted in 3.0
>
> Thanks
> Antonio
>