On Fri, 13 Jun 2014 10:41:45 -0300, Barry Books wrote:
Personally I think mixins combined with workers are one of Tapestry
hidden gems.
Agreed 200%. :)
In my case I need a title on every pagelink . With a mixin applied to
pagelink by a worker I can easily lookup a title in the message cat
Personally I think mixins combined with workers are one of Tapestry hidden
gems. In my case I need a title on every pagelink . With a mixin applied to
pagelink by a worker I can easily lookup a title in the message catalog and
add it. Maybe 30 minutes of coding and it's automatically applied to eve
On Thu, 12 Jun 2014 18:45:21 -0300, Lance Java
wrote:
Mixins are always a bit harder since you're usually manipulating the dom
after the default impl.
For something a trivial as pagelink, I'd argue that starting from scratch
would be easier.
In this case, I agree. But, as a more general sol
Thanks,
Those links are very helpful. I had not seen the Kawwa components before.
On Thu, Jun 12, 2014 at 11:51 PM, Basile Chandesris wrote:
> It seems that Kawwa Components tries to support W3C/WAI (Web Accessibility
> Initiative):
>
> https://kawwa.atosworldline.com/accessibility
> https://k
It seems that Kawwa Components tries to support W3C/WAI (Web
Accessibility Initiative):
https://kawwa.atosworldline.com/accessibility
https://kawwa.atosworldline.com/componentapproach
https://kawwa.atosworldline.com/components
--
http://www.jimthatcher.com/sidebyside.htm
http://www.jimthatcher.
Mixins are always a bit harder since you're usually manipulating the dom
after the default impl.
For something a trivial as pagelink, I'd argue that starting from scratch
would be easier.
On 12 Jun 2014 16:02, "Thiago H de Paula Figueiredo"
wrote:
> On Thu, 12 Jun 2014 10:41:10 -0300, Lance Jav
On Thu, 12 Jun 2014 09:31:04 -0300, Barry Books wrote:
Lastly some things might be better (like grid sort link titles) if they
were included in the base code. Would someone be willing to accept
patches
Of course! :)
and if so should they be enabled all the time or should 508 be a feature
On Thu, 12 Jun 2014 10:41:10 -0300, Lance Java
wrote:
Sounds like this issue would help you here
https://issues.apache.org/jira/browse/TAP5-1611
In Barry's case, I think creating a ComponentCclassTransformerWorker to
apply a mixin to all PageLink, ActionLink and EventLink instances is the
Sounds like this issue would help you here
https://issues.apache.org/jira/browse/TAP5-1611
BTW I had no idea what section 508 was. A link / description might help.
On 12 Jun 2014 13:31, "Barry Books" wrote:
> I need to make a Tapestry 5.4 site 508 compliant. I've looked thru the
> requirements
I need to make a Tapestry 5.4 site 508 compliant. I've looked thru the
requirements and what HTML is generated now and I don't see anything that
looks to difficult but I'd like to get Tapestry to do most/all the work.
My plan is to write mixins to handle thinks like access keys. For example
Wou
All,
Has anyone had any experience with using Tapestry in a Section 508 complicant
application?
thanks,
Mark
11 matches
Mail list logo
