Hi Jacopo and Pierre,
I like the idea of the new design but it will represent some problems which
we need to think about. For example, the commonext prepares the UI labels
which are commonly used (content, party, etc ...) and makes them available
across all components. This makes a dependency
Le 23/11/2014 19:16, Jacopo Cappellato a écrit :
Thank you Taher,
you are right about these dependencies and it is important that we keep the
artifact that you have mentioned under applications.
What confuses me is the fact that this commonext component should be loaded
before the other
On Nov 24, 2014, at 10:21 AM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
Le 23/11/2014 19:16, Jacopo Cappellato a écrit :
Thank you Taher,
you are right about these dependencies and it is important that we keep the
artifact that you have mentioned under applications.
What
Hi Taher,
what you describe seems to be inline with the concept of having commonext as
the base component for all the applications (i.e. loaded first): all
applications will depend on it and would use (for example) its labels.
Am I missing something?
Jacopo
On Nov 24, 2014, at 10:19 AM, Taher
Hi Jacopo,
You are not missing anything! I am just stating that work needs to be done
to help implementing your vision. One such example being removing the UI
Label loading from the commonext to the upper application components. In
fact, if you wish to open a JIRA to that effect I can help with
Le 24/11/2014 10:34, Jacopo Cappellato a écrit :
On Nov 24, 2014, at 10:21 AM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
Le 23/11/2014 19:16, Jacopo Cappellato a écrit :
Thank you Taher,
you are right about these dependencies and it is important that we keep the
artifact that
This is a really positive step.
On 24/11/2014 5:15 AM, Jacques Le Roux wrote:
Le 24/11/2014 10:34, Jacopo Cappellato a écrit :
On Nov 24, 2014, at 10:21 AM, Jacques Le Roux
jacques.le.r...@les7arts.com wrote:
Le 23/11/2014 19:16, Jacopo Cappellato a écrit :
Thank you Taher,
you are
I agree with Taher, I already gave my thought here
https://issues.apache.org/jira/browse/OFBIZ-3329?focusedCommentId=14151214
BTW this also reminds me about http://markmail.org/message/7m5afdqhrszxuv3q I
hope someone will take care of it, Anil, Ashish?
Jacques
Le 23/11/2014 08:48, Taher
Hi all,
IIRW, components like commonext, securityext and entityext were constructed
and implemented by the community to enable developers (users/contributors)
to extend the functionalities in lower level components (services et al)
and create commonalities that can be shared between components on
Somewhere in my previous post I started a sentence with:
Like I initiated
This was incomplete and should have been:
Like I initiated with https://issues.apache.org/jira/browse/OFBIZ-5812
Regards,
Pierre Smits
*ORRTIZ.COM http://www.orrtiz.com*
Services Solutions for Cloud-
Based
Thank you Taher,
you are right about these dependencies and it is important that we keep the
artifact that you have mentioned under applications.
What confuses me is the fact that this commonext component should be loaded
before the other application components (because it is used by them) but
Thanks Pierre for the description.
My goal is not actually that of removing an unused component, but instead
trying to come up with an architecture that with little effort and no major
changes would let us deliver the following products:
*OFBiz framework*
Structure: it includes only the
Jacopo, All,
You and I are in sync here, with respect to how the components in the
various levels stack up to be the primary work of the OFBiz project. I also
agree that this can be achieved in a reasonable amount of time and effort
spent.
Having svn repositories per layer plays into this
On Nov 23, 2014, at 8:44 PM, Pierre Smits pierre.sm...@gmail.com wrote:
Jacopo, All,
You and I are in sync here, with respect to how the components in the
various levels stack up to be the primary work of the OFBiz project. I also
agree that this can be achieved in a reasonable amount of
Do you agree that specialpurpose would be a better fit for the commonext
component that is currently under the applications folder?
It extends the default data model adding new fields to the NoteData entity and
provides some special purpose features.
Jacopo
Hi Jacopo,
Almost all applications including core applications use the
ApplicationDecorator screen found in CommonExt. I believe many items depend
on CommonExt and you will find the below code snippet pretty much in all
CommonScreens.xml files.
widgets
include-screen
16 matches
Mail list logo
