This is great, I followed the instructions in the following references and
able to extend an OOTB component with a custom component, and limit the
fields displayed on screen by changing code in my custom component ONLY,
Following are the steps, that i had to do to change a ftl file e.g.
Hi Info.integrin,
We, at ORRTIZ.COM, follow the same principle as outlined by Jacques. This
ensures that we deliver the best solution possible to each of our clients.
Unfortunately, some OOTB can't be made hidden for the average user without
major customizations..
My advice: take the latest
Richard,
Adding an additional layer of functionality to hide other functionality
might increase performance degradation.
Regards,
Pierre Smits
*ORRTIZ.COM http://www.orrtiz.com*
Services Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail Trade
http://www.orrtiz.com
Hi Integrin
In our company we use the ofbiz addon manager. It keeps things isolated and
easy to upgrade.
Either way, best practice in my opinion is to isolate framework
modification code from your own new code.
Regards,
Taher Alkhateeb
On Jun 20, 2014 5:32 PM, Anil Patel
This is good, you can even go further.
Most of the OFBiz parts can be overridden in a hot-deploy component.
This prevents you to have even to maintain patches...
When you always try to apply this idea you really understand the genius behind
OFBiz...
Jacques
Le 20/06/2014 16:31, Anil Patel a
Thanks all the quick responses and Anil for sharing the link it is very
helpful, As i have to change most of the forms/screens to limit the fields,
i will create a custom component in hot-deploy by extending the
corresponding Ofbiz OOTB component and will keep my customization here.
Regards
On
Let me just suggest the approach of using display:none in a custom CSS
file to suppress display of the screen elements you don't want to see. I
don't know if it would actually meet Integrin's requirements.
You would not use this approach normally since you have control over the
HTML
