OFBiz › OFBiz - User

Extend forms.xml

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 4 messages Options
yogi84
Reply | Threaded
Open this post in threaded view
♦
♦
|

Extend forms.xml

yogi84
Extend forms.xml

 

Hi I have a short question. What is the best way to extend for example the ProductForms?

I found two ways but both don´t look ideal.

The first way is to put the new field in the existing ProductForms.xml

The second way I found is to edit the controller.xml or the ProductScreens.xml to link to a second ProductForms.xml in my hot-deploy.

The problem is that both ways look very uncomfortable for updating the OFBiz software in the future.

Is there any alternative to extend the Forms.xml without editing the original source code? Maybe in a similar way I can put with extend-entity fields to an entity without touch the original code?






































Scott Gray-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Extend forms.xml

Scott Gray-2
Use a form definition like the following in your hot-deploy app:
<form name="MyEditProduct" extends="EditProduct" extends-
resource="component://product/webapp/catalog/product/ProductForms.xml>
...
</form>

If you search around there are a few examples of how it is used.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 21/07/2009, at 8:49 PM, yogi84 wrote:

>
> Extend forms.xml
>
>
>
> Hi I have a short question. What is the best way to extend for  
> example the
> ProductForms?
>
> I found two ways but both don´t look ideal.
>
> The first way is to put the new field in the existing ProductForms.xml
>
> The second way I found is to edit the controller.xml or the
> ProductScreens.xml to link to a second ProductForms.xml in my hot-
> deploy.
>
> The problem is that both ways look very uncomfortable for updating  
> the OFBiz
> software in the future.
>
> Is there any alternative to extend the Forms.xml without editing the
> original source code? Maybe in a similar way I can put with extend-
> entity
> fields to an entity without touch the original code?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> View this message in context: http://www.nabble.com/Extend-forms.xml-tp24583963p24583963.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>


smime.p7s (3K) Download Attachment
Sumit Pandit-3
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Extend forms.xml

Sumit Pandit-3
Hi Yogi,

You can find the same example what Scott suggest in -
InvoiceForms.xml, where form - FindApInvoices extends form -  
FindInvoice.

--
Regards
Sumit Pandit

On Jul 21, 2009, at 2:32 PM, Scott Gray wrote:

> Use a form definition like the following in your hot-deploy app:
> <form name="MyEditProduct" extends="EditProduct" extends-
> resource="component://product/webapp/catalog/product/ProductForms.xml>
> ...
> </form>
>
> If you search around there are a few examples of how it is used.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 21/07/2009, at 8:49 PM, yogi84 wrote:
>
>>
>> Extend forms.xml
>>
>>
>>
>> Hi I have a short question. What is the best way to extend for  
>> example the
>> ProductForms?
>>
>> I found two ways but both don´t look ideal.
>>
>> The first way is to put the new field in the existing  
>> ProductForms.xml
>>
>> The second way I found is to edit the controller.xml or the
>> ProductScreens.xml to link to a second ProductForms.xml in my hot-
>> deploy.
>>
>> The problem is that both ways look very uncomfortable for updating  
>> the OFBiz
>> software in the future.
>>
>> Is there any alternative to extend the Forms.xml without editing the
>> original source code? Maybe in a similar way I can put with extend-
>> entity
>> fields to an entity without touch the original code?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://www.nabble.com/Extend-forms.xml-tp24583963p24583963.html
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>

yogi84
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Extend forms.xml

yogi84
In reply to this post by Scott Gray-2

first thank you for your quick response,
 
but this althoug required to change the location in ProductScreens.xml / <screen name="EditProduct">
so that the <include-form name="MyEditProduct" points to the hot-deploy??
or is there a mistake in my thinking?
 
sorry for my bad english but i´m no native speaker




<quote author="Scott Gray-2">
Use a form definition like the following in your hot-deploy app:
<form name="MyEditProduct" extends="EditProduct" extends-
resource="component://product/webapp/catalog/product/ProductForms.xml>
...
</form>

If you search around there are a few examples of how it is used.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 21/07/2009, at 8:49 PM, yogi84 wrote:

>
> Extend forms.xml
>
>
>
> Hi I have a short question. What is the best way to extend for  
> example the
> ProductForms?
>
> I found two ways but both don´t look ideal.
>
> The first way is to put the new field in the existing ProductForms.xml
>
> The second way I found is to edit the controller.xml or the
> ProductScreens.xml to link to a second ProductForms.xml in my hot-
> deploy.
>
> The problem is that both ways look very uncomfortable for updating  
> the OFBiz
> software in the future.
>
> Is there any alternative to extend the Forms.xml without editing the
> original source code? Maybe in a similar way I can put with extend-
> entity
> fields to an entity without touch the original code?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> View this message in context: http://www.nabble.com/Extend-forms.xml-tp24583963p24583963.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>


 

Free forum by Nabble Edit this page