Beaneditor is nice, but not meant as a catch-all. What I would probably do is
beanedit the properties above the custom needs, then directly insert the fields
you need, then beanedit the rest. Like:
<beaneditor object="myobj" include="a,b"/>
<div><t:textfield .../><t:textfield .../></div>
<beaneditor object="myobj" include="e,f"/>
Robert
GATAATGCTATTTCTTTAATTTTCGAA
On Jun 25, 2011, at 6:53 AM, Muhammad Mohsen <m.gelb...@gmail.com> wrote:
> Hello everyone,
>
> I've been searching for a while but I'm facing difficulties solving this
> situation.
>
> I have a page. This page contains a form component, then this form embeds
> multiple beaneditor components.
> I need to change how a specific beaneditor component of these renders it's
> fields. I found that the beaneditor puts each of it's input fields and label
> in one div element which causes the fields to be rendered vertically.
>
> I just need to put some fields in one div element so that they are rendered
> next to each other.
>
> Here is my page's code:
>
> public class ConfigureTclTest {
> @Component
> private Form configureTclTest;
> @Property
> private boolean overridePortParameters;
> @Component
> private BeanEditor commonTestDataEditor; //The editor can work without
> this declaration. But this is my current version.
> @Property
> private CommonTestData commonTestData;
> .
> .
> .
> }
>
> My tml file:
> <t:form t:id="configureTclTest">
> <h2>Chassis information</h2>
> <div class="t-beaneditor-row">
> <label for="overridePortParameters">Override</label>
> <t:checkbox t:id="overridePortParameters" />
> </div>
> <t:beaneditor t:id="commonTestDataEditor" object="commonTestData"
> exclude="chassisIp">
> <t:parameter name="ipAddress">
> <t:label for="ipAddress" />
> <t:textfield t:id="ipAddress"
> value="${message:default.ipAddress}" disabled="true" />
> </t:parameter>
> <t:parameter name="prefix">
> <t:label for="prefix" />
> <t:textfield t:id="prefix" value="${message:default.prefix}"
> disabled="true" />
> </t:parameter>
> </t:beaneditor>
> .
> .
> .
>
> So how should I intercept a specific event for a beaneditor located as
> mentioned above ?
> According to my understanding of event bubbling, should I handle event for
> the form component instead ?
> Moreover, as I understand that at some point I'll use the MarkupWriter
> interface. I have no clear idea about how it behaves.
>
> Am I clear explaining this ?
>
> If the needed is mentioned somewhere, links will be enough.
> Thanks a lot in advance :)
>
> --
> *Regards,*
> *Muhammad Gelbana
> Java Developer*
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
