You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Scott Gray <sc...@hotwaxmedia.com> on 2009/07/01 00:50:17 UTC
Re: Proposal for adding an alternate-target element to the form's widget submit element
+1
Here's another approach that might be nice, have something similar to
the use-when attribute except that it is evaluated at (form) runtime,
e.g.:
<form name="FindOrders" type="single" target="SearchOrdersScreen">
<alt-target use-when-runtime="outputFormat='PDF'"
target="SearchOrdersScreenPdf"/>
<alt-target use-when-runtime="outputFormat='CSV'"
target="SearchOrdersScreenCsv"/>
<field name="outputFormat">
<radio>
<option key="SCREEN" description="Screen"/>
<option key="PDF" description="PDF"/>
<option key="CSV" description="CSV"/>
</radio>
</field>
<field name="submitButton" title="Search"><submit button-
type="button"/></field>
</form>
It could also be used to dynamically show/hide other fields on the form.
Regards
Scott
On 1/07/2009, at 9:54 AM, Jacopo Cappellato wrote:
> I would like to make it easier to get different type of exports
> (pdf, csv etc...) for the same search form widget. Right now we can
> add 'export' links to the screen, but it is tricky to keep the
> search parameters when you click on them.
>
> What about adding an "alternate-target" attribute to the "submit"
> element? This will be used to specify an alternate target for the
> form (behind the lines it will use Javascript to change the form's
> target)
> For example:
>
> <form name="FindOrders" type="single" target="SearchOrdersScreen">
> ... (search parameters)
> <field name="submitButton" title="Search"><submit button-
> type="button"/></field>
> <field name="submitButtonPdf" title="Export (PDF)"><submit button-
> type="button" alt-target="SearchOrdersScreenPdf"/></field>
> <field name="submitButtonCsv" title="Export (CSV)"><submit button-
> type="button" alt-target="SearchOrdersScreenCsv/></field>
> </form>
>
> It will render three buttons, one for the standard html screen, one
> for PDF version and one for csv exports.
>
> What do you think?
>
> Jacopo
Re: Proposal for adding an alternate-target element to the form's
widget submit element
Posted by Malin Nicolas <ma...@librenberry.net>.
It's really usefull idea,
+1 :)
Ashish Vijaywargiya a écrit :
> +1
>
> --
> Ashish
>
> On Wed, Jul 1, 2009 at 4:47 AM, Jacopo Cappellato <
> jacopo.cappellato@hotwaxmedia.com> wrote:
>
>
>> +1
>>
>> this too could be very useful.
>>
>> Or even (more concise but less clear and probably more difficult to
>> implement):
>>
>> <form name="FindOrders" type="single" target="${outputFormat}">
>> <field name="outputFormat">
>> <radio>
>> <option key="SearchOrdersScreen" description="Screen"/>
>> <option key="SearchOrdersScreenPdf" description="PDF"/>
>> <option key="SearchOrdersScreenCsv" description="CSV"/>
>> </radio>
>> </field>
>> <field name="submitButton" title="Search"><submit
>> button-type="button"/></field>
>> </form>
>>
>> Jacopo
>>
>>
>>
>>
>
>
--
Nicolas MALIN
Consultant
Tél : 06.17.66.40.06
Site projet : http://www.neogia.org/
-------
Société LibrenBerry
Tél : 02.48.02.56.12
Site : http://www.librenberry.net/
Re: Proposal for adding an alternate-target element to the form's
widget submit element
Posted by Ashish Vijaywargiya <vi...@gmail.com>.
+1
--
Ashish
On Wed, Jul 1, 2009 at 4:47 AM, Jacopo Cappellato <
jacopo.cappellato@hotwaxmedia.com> wrote:
> +1
>
> this too could be very useful.
>
> Or even (more concise but less clear and probably more difficult to
> implement):
>
> <form name="FindOrders" type="single" target="${outputFormat}">
> <field name="outputFormat">
> <radio>
> <option key="SearchOrdersScreen" description="Screen"/>
> <option key="SearchOrdersScreenPdf" description="PDF"/>
> <option key="SearchOrdersScreenCsv" description="CSV"/>
> </radio>
> </field>
> <field name="submitButton" title="Search"><submit
> button-type="button"/></field>
> </form>
>
> Jacopo
>
>
>
Re: Proposal for adding an alternate-target element to the form's widget submit element
Posted by Jacopo Cappellato <ja...@hotwaxmedia.com>.
+1
this too could be very useful.
Or even (more concise but less clear and probably more difficult to
implement):
<form name="FindOrders" type="single" target="${outputFormat}">
<field name="outputFormat">
<radio>
<option key="SearchOrdersScreen" description="Screen"/>
<option key="SearchOrdersScreenPdf" description="PDF"/>
<option key="SearchOrdersScreenCsv" description="CSV"/>
</radio>
</field>
<field name="submitButton" title="Search"><submit button-
type="button"/></field>
</form>
Jacopo
On Jun 30, 2009, at 4:50 PM, Scott Gray wrote:
> +1
>
> Here's another approach that might be nice, have something similar
> to the use-when attribute except that it is evaluated at (form)
> runtime, e.g.:
> <form name="FindOrders" type="single" target="SearchOrdersScreen">
> <alt-target use-when-runtime="outputFormat='PDF'"
> target="SearchOrdersScreenPdf"/>
> <alt-target use-when-runtime="outputFormat='CSV'"
> target="SearchOrdersScreenCsv"/>
> <field name="outputFormat">
> <radio>
> <option key="SCREEN" description="Screen"/>
> <option key="PDF" description="PDF"/>
> <option key="CSV" description="CSV"/>
> </radio>
> </field>
> <field name="submitButton" title="Search"><submit button-
> type="button"/></field>
> </form>
>
> It could also be used to dynamically show/hide other fields on the
> form.
>
> Regards
> Scott
>
> On 1/07/2009, at 9:54 AM, Jacopo Cappellato wrote:
>
>> I would like to make it easier to get different type of exports
>> (pdf, csv etc...) for the same search form widget. Right now we can
>> add 'export' links to the screen, but it is tricky to keep the
>> search parameters when you click on them.
>>
>> What about adding an "alternate-target" attribute to the "submit"
>> element? This will be used to specify an alternate target for the
>> form (behind the lines it will use Javascript to change the form's
>> target)
>> For example:
>>
>> <form name="FindOrders" type="single" target="SearchOrdersScreen">
>> ... (search parameters)
>> <field name="submitButton" title="Search"><submit button-
>> type="button"/></field>
>> <field name="submitButtonPdf" title="Export (PDF)"><submit button-
>> type="button" alt-target="SearchOrdersScreenPdf"/></field>
>> <field name="submitButtonCsv" title="Export (CSV)"><submit button-
>> type="button" alt-target="SearchOrdersScreenCsv/></field>
>> </form>
>>
>> It will render three buttons, one for the standard html screen, one
>> for PDF version and one for csv exports.
>>
>> What do you think?
>>
>> Jacopo
>