New "a" tag for the view taglib

[kurtwiersma]

I talked to Peter online and we thinking of building a new tag in view taglib for outputting links (a tags). This tag would support buildURL or buildRouteUrl and allow you to pass url parameters via sub tags.

[peterfarrell]

Here are a couple of examples of syntax I'm thinking about:

<cfimport prefix="view" taglib="/MachII/customtags/view" />
<view:a event="foo" p:productId="10">Check out product 10</view:a>
<view:a route="showProduct" p:productid="10">Check out product 10</view:a>

Optionally support a label attribute so you don't have to wrap the link text in the custom tag if you don't want to:

<view:a event="foo" p:productId="10" label="Check out product 10" />
<view:a route="showProduct" p:productid="10" label="Check out product 10" />

[peterfarrell]

[None] - Initial commit (still needs documentation)n- refs #239

[peterfarrell]

Jonah, FYI got a rough version of the a tag in the view tag library. Supports:

• All standard HTML attributes
• All event attributes
• Non-standard attributes via the x: namespace
• Adding url parameters using the p: namespace
• Adding query string parameters (when using routes) using the q: namespace

Still need to add attributes called x, p and q so we can support name / value pair pipe lists or structs (collections of attributes or parameters).

Special tag attributes:

• event indicates the event name
• module indicates the module name (optional)
• route indicates route name (cannot be used with event and/or module)
• label to indicate the link text if you use a self-closing tag instead of setting the link text between a opening and closing tag manually

[peterfarrell]

[None] - Added attributes for url params, for query string params and for non-standard attributesn- Feature complete and ready for user testing (Still need documentation)n- closes #239

[.jonah <jonah.mach-ii@…>]

Replying to peterfarrell:

* Non-standard attributes via the x: namespace

This is great when you're using functions like  http://prototypejs.org/api/element/readAttribute.

A question though: what version of (X)HTML are you supporting with the "standard HTML attributes"? Might this be a moving target?

Note: This affects the form tag library as well.

[peterfarrell]

Basically we have to support HTML and XHTML. Shooting for HTML 4.1 and XHTML 1 which are the standards at this point. For example, we support target attribute even though that is not valid XHTML. Basic I use what is listed on W3CSchools for each tag (which is accurate and easier to read than the W3C specs):

 http://www.w3schools.com/tags/tag_a.asp

For "standard" attributes (meaning these are the common attributes across most tags), I mean these:  http://www.w3schools.com/tags/ref_standardattributes.asp

For "event" attributes, I mean these (if applicable):  http://www.w3schools.com/tags/ref_eventattributes.asp

Thanks for a reminder on the non-standard attribute namespace for the form tags. I need to file a ticket to remind myself.

[peterfarrell]

FYI, support for non-standard attributes was added to the form tag lib in #243.

[peterfarrell]

We need to support using BuildCurrentUrl? as well. Kurt, since you're familiar with that API (the M2SFP doco needs to be updated with that info), I'm going to assign that ticket to you.

[peterfarrell]

During the team meeting we discussed adding support for adding buildCurrentUrl to the a tag. We decided on adding this via a boolean flag called useCurrentUrl.

[peterfarrell]

- refs #239

[peterfarrell]

Added in changeset:1385