Tapestry
  1. Tapestry
  2. TAPESTRY-165

Allow control over attribute name for components in templates

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.3, 3.0, 3.0.1, 3.0.2, 4.0
    • Fix Version/s: 4.0
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Operating System: All
      Platform: All

      Description

      From a discussion in the newsgroup I would like to request a feature. That
      feature would be to change the way Tapestry embeds its tags from:

      <span jwcid="insertStuff">this gets replaced</span>

      To (something like this):

      <span tap:jwcid="insertStuff">this gets replaced</span>

      This allows for several things to happen. The first is that Tapestry now
      create XHMTL compliant templates at EDIT time so that developers and HTML
      coders can validate the XHTML. The second is more nebulous. But I believe the
      change to using a namespace would allow Tapestry more flexibility as future
      HTML changes come down the pipe to ensure Tapestry meets those specifications.

      Howard: What we really want is the ability to control the exact id, so that people can use 'id' (if they like), or
      use whatever namespace is convienient for them.

        Activity

        Hide
        Richard Lewis-Shell added a comment -

        if we have a tapestry namespace (which sounds like a good idea to me),
        the 'jwc' part is a bit redundant isn't it:

        <span tap:id="insertStuff">this gets replaced</span>

        or, better:

        <span jwc:id="insertStuff">this gets replaced</span>

        Show
        Richard Lewis-Shell added a comment - if we have a tapestry namespace (which sounds like a good idea to me), the 'jwc' part is a bit redundant isn't it: <span tap:id="insertStuff">this gets replaced</span> or, better: <span jwc:id="insertStuff">this gets replaced</span>
        Hide
        Howard M. Lewis Ship added a comment -

        We'll see about addressing this in 3.1. It isn't a bug, its a new feature/enhancement. Just because it doesn't do exactly what you want doesn't make it broken.

        Show
        Howard M. Lewis Ship added a comment - We'll see about addressing this in 3.1. It isn't a bug, its a new feature/enhancement. Just because it doesn't do exactly what you want doesn't make it broken.
        Hide
        Howard M. Lewis Ship added a comment -

        All too easily ... even I was surprised that the Tapestry template parser would accept "t:id" as an attribute name without requiring a code change.

        Show
        Howard M. Lewis Ship added a comment - All too easily ... even I was surprised that the Tapestry template parser would accept "t:id" as an attribute name without requiring a code change.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Robert Hicks
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development