Proposal for adding an alternate-target element to the form's widget submit element

[Jacopo Cappellato-4]

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

[Scott Gray-2]

+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

[Jacopo Cappellato-4]

+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
>

[BJ Freeman]

how about making A content that can be used to list the type of exports.
this would open the exports based on dataresources.
Just a thought.

Jacopo Cappellato sent the following on 6/30/2009 2:54 PM:

> 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

--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.

[Bruno Busco]

+1
it should be possible to set the export alt-target in a base form and
have it consistently in all extended ones.
I think this will be possible with all of the suggested solutions.

-Bruno

2009/7/1 BJ Freeman <[hidden email]>:

> how about making A content that can be used to list the type of exports.
> this would open the exports based on dataresources.
> Just a thought.
>
> Jacopo Cappellato sent the following on 6/30/2009 2:54 PM:
>> 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
>
> --
> BJ Freeman
> http://www.businessesnetwork.com/automation
> http://bjfreeman.elance.com
> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
> Systems Integrator.
>
>

[Ashish Vijaywargiya]

+1

--
Ashish

On Wed, Jul 1, 2009 at 4:47 AM, Jacopo Cappellato <
[hidden email]> 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
>
>
>

[Malin Nicolas]

It's really usefull idea,

+1 :)


Ashish Vijaywargiya a écrit :

> +1
>
> --
> Ashish
>
> On Wed, Jul 1, 2009 at 4:47 AM, Jacopo Cappellato <
> [hidden email]> 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 : [phone]
Site projet : http://www.neogia.org/
-------
Société LibrenBerry
Tél : [phone]
Site : http://www.librenberry.net/