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 it is
instead loaded as last; and in fact it extends some of the code from other
application components: I suspect that the component contains some artifacts
that we should moved elsewhere (e.g. to specialpurpose or to other
applications, as mentioned by Pierre).
This goal should be rather easy to achieve (but I still need to study the
details of it) and we should be able to implement an architecture like the
following (some stupid ascii art):
accounting | order | product | ...
------------------------------------------
commonext
------------------------------------------
framework
The above should be inline with your description of it.
Regards,
Jacopo
On Nov 23, 2014, at 8:48 AM, Taher Alkhateeb <[email protected]> wrote:
> 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 name="ApplicationDecorator"
> location="component://commonext/widget/CommonScreens.xml"/>
> </widgets>
>
> It also provides data essential to theme headers and footers, and provides
> additional resources including UI labels for all components and it is also
> responsible for the contextual help system. I think removing it will break
> your applications unless you do a lot of rewiring. I think this is not a
> simple folder move.
>
> Taher Alkhateeb
>
> On Sun, Nov 23, 2014 at 10:26 AM, Jacopo Cappellato <
> [email protected]> wrote:
>
>> 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
>>
>>
