You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/01/28 22:52:59 UTC

[jira] Closed: (TAP5-477) Allow shorter, better to read attribute passings in MarkupWriter.element()

     [ https://issues.apache.org/jira/browse/TAP5-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-477.
-------------------------------------

    Resolution: Won't Fix
      Assignee: Howard M. Lewis Ship

Tapestry already has too many cases of two ways to do the same thing.  The current syntax is simple, its also flexible (you can easily switch between literals and dynamically calculated values).

> Allow shorter, better to read attribute passings in MarkupWriter.element()
> --------------------------------------------------------------------------
>
>                 Key: TAP5-477
>                 URL: https://issues.apache.org/jira/browse/TAP5-477
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: manuel aldana
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> Currently adding attributes ends up with a bit lengthy parameter list, which isn't intuitive:
> writer.element("elementName","attr1","value1", "attr2", "value2")
> a nicer and shorter option could for instance be:
> writer.element("elementName","attr1:value1","attr2:value2")
> Of course this should not break existing var-args list and down-compatible (maybe by using unusual attribute name char like : or >). '>' is prohibited and ':'  afaik is only used for xml namespace declarations.

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