Re: Dynamic form fields

Thanks, This works perfect for my use case :) Also when I want to trigger it by something else than a checkbox, for example a change in a select, I can probably add a hidden checkbox that I can check with javascript to toggle the FormFragment. Greetings, Nathan Op 14/12/2017 om 14:16 schre

Re: Dynamic form fields

That definitely works. You can also just add all the fields you’ll need to the form and then use JavaScript to hide fields that you don’t need at the time. This method is super simple, although you may need to validate some fields on the server side. Or set the values to null when you hide them.

Re: Dynamic form fields

On Thu, Dec 14, 2017 at 8:47 AM, Nathan Quirynen < nat...@pensionarchitects.be> wrote: > Hi, > Hi! > This subject has been spoken about more in the past, but I still have not > found a good solution to this and still struggle with this. > > What is the best practice (Tapestry 5.4+) to add field

Re: Dynamic form fields

Nathan, Have you tried the FormFragment component? See https://tapestry.apache.org/5.4/apidocs/org/apache/tapestry5/corelib/components/FormFragment.html On Dec 14, 2017 5:47 AM, "Nathan Quirynen" wrote: Hi, This subject has been spoken about more in the past, but I still have not found a goo

Re: Dynamic form

Why do I need a notification? the value encoder handles that stuff. Did you try to submit the form after removing SubmitNotifier? Try it out. Because all fields are bound to the same property you need a way to be notified when a field value is set. The SubmitNotifier component is the way to do it

Re: Dynamic form

On Fri, 17 Sep 2010 19:03:01 -0300, Антон Мезерный wrote: And what is the best way to create such a dynamic form? Provide DataTypeAnalyzer to define new BeanModel types (which are just names) and edition and viewing blocks for them. This way, BeanEditForm, BeanEditor, Grid, and BeanDisp

Re: Dynamic form

On Sat, 18 Sep 2010 11:45:19 -0300, Josh Canfield wrote: Is there any way to get component instance by its name even if this component is not used in any other page? The short answer is no. I don't remember the long answer off hand... The long answer is also no :). A component instance

Re: Dynamic form

Did you try to submit the form after removing SubmitNotifier? Try it out. Because all fields are bound to the same property you need a way to be notified when a field value is set. The SubmitNotifier component is the way to do it. Check out the documentation: http://tapestry.apache.org/tapestry5.1

Re: Dynamic form

> Is there any way to get component > instance by its name even if this component is not used in any other page? The short answer is no. I don't remember the long answer off hand... -- Josh On Sep 18, 2010, at 5:41 AM, Anton Mezerny wrote: > Looking on ComponentSource code I understood, that

Re: Dynamic form

Looking on ComponentSource code I understood, that it gets only components, that are already defined within some page. Is there any way to get component instance by its name even if this component is not used in any other page? 2010/9/18 Anton Mezerny > Igor, I am now trying to write something l

Re: Dynamic form

Igor, I am now trying to write something like in your book, but first of all I don't want to define blocks in one tml page, and a number or blocks in java-class. I try to get component instance dynamically using method componentSource.getComponent(String) but I have an exception on this method. o

Re: Dynamic form

Why would you need a submit notifier? I checked out your book and it works fine without one. What you need is a combination of Loop, Delegate, and SubmitNotifier components and a couple of blocks inside your template. Check this out: http://code.google.com/p/tapestrybook/source/browse/trunk/tap

Re: Dynamic form

What you need is a combination of Loop, Delegate, and SubmitNotifier components and a couple of blocks inside your template. Check this out: http://code.google.com/p/tapestrybook/source/browse/trunk/tapestry-dynamic-forms/src/main/webapp/ViewReport.tml http://code.google.com/p/tapestrybook/source/

Re: Dynamic form

And what is the best way to create such a dynamic form? Using Delegate component or modifying beaneditform? Or maybe there is better approach? I tried to write it using Delegate and I have a problem - I can't get component instance from ComponentSource - Exception: org.apache.tapestry5.internal.s

Re: Dynamic form

On Thu, 16 Sep 2010 19:09:05 -0300, Антон Мезерный wrote: Hello, Hi! I am trying to make a dynamic form component, something like beaneditform, but based not on bean field type, but on some property in database. I strongly advise you to read the BeanEditor sources and do something

Re: Dynamic form

On 9/29/2009 5:20 AM, Alfie Kirkpatrick wrote: I made a hashmap backed beaneditform for something similar, so the property conduit just read/writes from the hashmap and the model comes from somewhere else (this was a dynamic search form in my case where the model was a JCR repo). Happy to share

RE: Dynamic form

. -Original Message- From: Kevin White [mailto:kwh...@kevbo.org] Sent: 28 September 2009 20:41 To: users@tapestry.apache.org Subject: Re: Dynamic form On 9/28/2009 3:24 PM, Kalle Korhonen wrote: > I would look into using a BeanEditForm and making a BeanModel with all > synthetic prop

Re: Dynamic form

On 9/28/2009 3:24 PM, Kalle Korhonen wrote: I would look into using a BeanEditForm and making a BeanModel with all synthetic properties based on your XML configuration. If you have a definite set of parameter types and you can map each into some field type, then you should be able to do it. See h

Re: Dynamic form

Em Mon, 28 Sep 2009 16:08:52 -0300, Kevin White escreveu: Hello all... Hi! The only way I can see to do something like that is by using a Grid, where each parameter would be a row in the grid. I can't use a BeanEdit, because I can't define the Bean itself at compile time...it comes

Re: Dynamic form

Hi Kevin, I think you could also use AjaxFormLoop: http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components/AjaxFormLoop.html Cheers, Christian Kalle Korhonen schrieb: I would look into using a BeanEditForm and making a BeanModel with all synthetic prope

Re: Dynamic form

I would look into using a BeanEditForm and making a BeanModel with all synthetic properties based on your XML configuration. If you have a definite set of parameter types and you can map each into some field type, then you should be able to do it. See http://tapestry.apache.org/tapestry5/guide/bean