Mailing-List: contact dev-help@tiles.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tiles.apache.org
Received-SPF: pass (athena.apache.org: domain of oleg.goro@gmail.com
 designates 64.233.182.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=t7wKNcQl+SKraN2e0zRf6hu4hj/fFiWhhRK9LdWnF38T095HLtOZNxopHo2vRiLuEF
         zpgpzogI5h6PAgnmKnjssROojbNd/1K947vmNFJlYr2ZNxWjfUUEY53uoyztnYg0E9Ef
         uYbKRW2jHDtCXZ9ba6xrGHHh1OxB3gS7DvbCo=
Message-ID: <48E3A61D.7080809@gmail.com>
Date: Wed, 01 Oct 2008 19:32:29 +0300
From: Oleg Gorobets <oleg.goro@gmail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: dev@tiles.apache.org
Subject: Attribute names in tiles 2.1
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello all,

I've noticed that in new tiles 2.1 name is deprecated in Attribute 
class. I'm trying to figure out the reasons why this decision was made..

We are constructing a portal solution based on tiles and probably many 
other developers do the same thing. The key point here is being able to 
handle attribute rendering and track their names (which currently serve 
like window ids for portlets). I really appreciate adding attribute 
renderers in 2.1 however I think that attribute renderer should be aware 
of all attribute features. I guess the logic here should be the 
following: the "renderer" should know everything of the object it 
renders. What do you think about this? If you have other points on this 
please let me know.

Sincerely,
Oleg Gorobets