Re: How to use CSS buttons outside of forms

On Wed, Dec 27, 2017 at 12:16 AM, Christopher Dodunski < chrisfromtapes...@christopher.net.nz> wrote: > Hi Chris & Bob, > Hello! > I had wrongly assumed that Tapestry left the HTML markup as is, parsing > only the t:xxx markup for 'wiring' webpage components to Java code. > Well, most of the

Re: How to use CSS buttons outside of forms

Hi Chris & Bob, Thanks, yes, it's all part of the learning process. :-) Now that I know that Tapestry ActionLink and EventLink only emit tags, I'll in future style all my buttons as a.xxx rather than input.xxx (style.css). I had wrongly assumed that Tapestry left the HTML markup as is, parsing

Re: How to use CSS buttons outside of forms

I think the EventLink component did the only thing it could reasonably be expected to do. When you add t:type=foo to an HTML tag you're telling Tapestry to change the tag to a foo component. In the case of t:type=eventlink, the EventLink component emits an tag. That's the only type of tag it

Re: How to use CSS buttons outside of forms

Hi Chris, Yes, you were absolutely correct. Tapestry was changing my tags to tags, and then of course the input.opto-button CSS code got totally ignored. Modifying the CSS from 'input' to 'anchor' type wasn't so trivial, particulary with vertically centreing button labels, which is easy with

Re: How to use CSS buttons outside of forms

I mostly use elements styled as buttons for this - A standard bootstrap thing. It sounds like your CSS is off if your elements disappear when rendering them with tapestry, take a look at the generated HTML to see what is going on. Maybe your is rendered as (It is "link" components so it could

Re: How to use CSS buttons outside of forms

This problem has proved trickier to solve than expected. The below tag produces a displayed button, but obviously without any functionality, as the tag contains no Tapestry-specific elements. The problem comes on adding Tapestry markup, with the intention of invoking a deleteUser() method in

Re: How to use CSS buttons outside of forms

Thanks Geoff. Are you in Aus? Greetings from NZ. Your tag... ...looks like it should do the trick. I assume that the t:context parameter is optional, in this case just for passing onNextPage() a literal string as argument? Also, to keep the website designers happy, it might be preferable

Re: How to use CSS buttons outside of forms

A working example: http://jumpstart.doublenegative.com.au/jumpstart/examples/styling/linksandsubmits1 Geoff > On 24 Dec 2017, at 6:33 am, Christopher Dodunski > wrote: > > Concerning use of the button HTML tag, I read the following... > >

Re: How to use CSS buttons outside of forms

Concerning use of the button HTML tag, I read the following... "Definition and Usage The tag defines a clickable button. Inside a element you can put content, like text or images. This is the difference between this element and buttons created with the element. Tip: Always specify the type

Re: How to use CSS buttons outside of forms

Oh, I thought I had tried that but the button didn't render. Hence my post. Nevermind, I'll try it again in case the problem was elsewhere. If ActionLink and Eventlink indeed accept 'class' parameter, it should go easily. Thanks, Chris.

Re: How to use CSS buttons outside of forms

Hi, All the link types extends AbstractLink which supports informal parameters... So basically just add a class="" parameter and it will pass through to the html. -- Chris On Sat, Dec 23, 2017 at 8:31 AM, Christopher Dodunski < chrisfromtapes...@christopher.net.nz> wrote: > Hi all, > > The

How to use CSS buttons outside of forms

Hi all, The Tapestry 'submit' component allows use of buttons defined in CSS by way of the 'class' parameter. This is perfect for form buttons. But now I want to use these same CSS buttons outside of forms. The natural choice is Tapestry's ActionLink or EventLink component. But these