You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Nathan Bubna (JIRA)" <ji...@apache.org> on 2010/01/18 17:56:44 UTC

[jira] Created: (TILES-491) Tiles-Velocity tool APIis a bit verbose

Tiles-Velocity tool APIis a bit verbose
---------------------------------------

                 Key: TILES-491
                 URL: https://issues.apache.org/struts/browse/TILES-491
             Project: Tiles
          Issue Type: Improvement
          Components: tiles-velocity
    Affects Versions: 2.2.x
            Reporter: Nathan Bubna
            Priority: Trivial


that is, the method names are verbose, 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. :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (TILES-491) Tiles-Velocity tool APIis a bit verbose

Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/TILES-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Petrelli closed TILES-491.
----------------------------------

    Resolution: Fixed

> Tiles-Velocity tool APIis a bit verbose
> ---------------------------------------
>
>                 Key: TILES-491
>                 URL: https://issues.apache.org/struts/browse/TILES-491
>             Project: Tiles
>          Issue Type: Improvement
>          Components: tiles-velocity
>    Affects Versions: 2.2.x
>            Reporter: Nathan Bubna
>            Assignee: Antonio Petrelli
>            Priority: Trivial
>             Fix For: 2.2.2
>
>
> that is, the method names are verbose, 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. :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (TILES-491) Tiles-Velocity tool APIis a bit verbose

Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/TILES-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Petrelli reassigned TILES-491:
--------------------------------------

    Assignee: Antonio Petrelli

> Tiles-Velocity tool APIis a bit verbose
> ---------------------------------------
>
>                 Key: TILES-491
>                 URL: https://issues.apache.org/struts/browse/TILES-491
>             Project: Tiles
>          Issue Type: Improvement
>          Components: tiles-velocity
>    Affects Versions: 2.2.x
>            Reporter: Nathan Bubna
>            Assignee: Antonio Petrelli
>            Priority: Trivial
>
> that is, the method names are verbose, 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. :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TILES-491) Tiles-Velocity tool APIis a bit verbose

Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/TILES-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Petrelli updated TILES-491:
-----------------------------------

    Fix Version/s: 2.2.2

Modified VelocityStyleTilesTool to make the API simpler.

> Tiles-Velocity tool APIis a bit verbose
> ---------------------------------------
>
>                 Key: TILES-491
>                 URL: https://issues.apache.org/struts/browse/TILES-491
>             Project: Tiles
>          Issue Type: Improvement
>          Components: tiles-velocity
>    Affects Versions: 2.2.x
>            Reporter: Nathan Bubna
>            Assignee: Antonio Petrelli
>            Priority: Trivial
>             Fix For: 2.2.2
>
>
> that is, the method names are verbose, 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. :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.