Hi all,
Currently, compound widget tag is only used in Examples application. Propose to convert rest of the project to use compound widget, so that dependencies are grouped together. Regards, James |
Administrator
|
Hi James,
As a 1st thought I'd see no problem with that. Jacques Le 13/06/2020 à 14:32, James Yong a écrit : > Hi all, > > Currently, compound widget tag is only used in Examples application. > Propose to convert rest of the project to use compound widget, so that dependencies are grouped together. > > Regards, > James |
Hi Jacques,
Ok, I created OFBIZ-11821 for this. Regards, James On 2020/06/13 18:03:21, Jacques Le Roux <[hidden email]> wrote: > Hi James, > > As a 1st thought I'd see no problem with that. > > Jacques > > Le 13/06/2020 à 14:32, James Yong a écrit : > > Hi all, > > > > Currently, compound widget tag is only used in Examples application. > > Propose to convert rest of the project to use compound widget, so that dependencies are grouped together. > > > > Regards, > > James > > |
Administrator
|
Hi James,
I see you pushed changes for FindRequest. Maybe we should wait a bit feedback from others? Jacques Le 14/06/2020 à 05:18, James Yong a écrit : > Hi Jacques, > > Ok, I created OFBIZ-11821 for this. > > Regards, > James > > On 2020/06/13 18:03:21, Jacques Le Roux <[hidden email]> wrote: >> Hi James, >> >> As a 1st thought I'd see no problem with that. >> >> Jacques >> >> Le 13/06/2020 à 14:32, James Yong a écrit : >>> Hi all, >>> >>> Currently, compound widget tag is only used in Examples application. >>> Propose to convert rest of the project to use compound widget, so that dependencies are grouped together. >>> >>> Regards, >>> James >> |
Hi Jacques,
Ok sure. Will wait then. Regards, James On 2020/06/14 06:47:27, Jacques Le Roux <[hidden email]> wrote: > Hi James, > > I see you pushed changes for FindRequest. Maybe we should wait a bit feedback from others? > > Jacques > > Le 14/06/2020 à 05:18, James Yong a écrit : > > Hi Jacques, > > > > Ok, I created OFBIZ-11821 for this. > > > > Regards, > > James > > > > On 2020/06/13 18:03:21, Jacques Le Roux <[hidden email]> wrote: > >> Hi James, > >> > >> As a 1st thought I'd see no problem with that. > >> > >> Jacques > >> > >> Le 13/06/2020 à 14:32, James Yong a écrit : > >>> Hi all, > >>> > >>> Currently, compound widget tag is only used in Examples application. > >>> Propose to convert rest of the project to use compound widget, so that dependencies are grouped together. > >>> > >>> Regards, > >>> James > >> > |
In reply to this post by James Yong-2
Hi James,
It's a good idea, but question is, how to group ? I have tested compound Widget for the POC VueJs, and I use it with one compound widget file by resouceName (on a REST uri format point of view). In example, 4 files: Example, ExampleItem, ExampleFeature, ExampleFeatureAppl I'm waiting for more time using them to say if it's the correct group size or not. So I suggest to use compound Widget, but not convert all xml files immediately, we need more developer experience to find the correct group size. Regards, Olivier Le 13/06/2020 à 14:32, James Yong a écrit : > Hi all, > > Currently, compound widget tag is only used in Examples application. > Propose to convert rest of the project to use compound widget, so that dependencies are grouped together. > > Regards, > James > |
In reply to this post by Jacques Le Roux
Hi,
Compound widget is interesting from my view in final component, where your code is closer than business cover so limited to reuse. For the "middle-ware" component, I have a doubt about the must valuable to convert it or how to convert it. To organize by compound widget maybe introduce to globalize by process and not by functional entities. After review your first commit [1] my feeling were decreased code visibility with the namespace representation, swaying with regroup all element that simplify the code navigation. Finally is that the problem to improve the code navigation throw ide plugin and keep each xml as low as possible (for the middle-ware component) and exploit compound widget on plugin to indicate another way to concentrate business code ? Nicolas [1] https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;a=blob;f=applications/order/widget/ordermgr/FindRequestCompound.xml;h=114e9c6d071a192d80e6278ba3e2c713f9ca1b17;hb=28809d7 On 14/06/2020 08:47, Jacques Le Roux wrote: > Hi James, > > I see you pushed changes for FindRequest. Maybe we should wait a bit > feedback from others? > > Jacques > > Le 14/06/2020 à 05:18, James Yong a écrit : >> Hi Jacques, >> >> Ok, I created OFBIZ-11821 for this. >> >> Regards, >> James >> >> On 2020/06/13 18:03:21, Jacques Le Roux >> <[hidden email]> wrote: >>> Hi James, >>> >>> As a 1st thought I'd see no problem with that. >>> >>> Jacques >>> >>> Le 13/06/2020 à 14:32, James Yong a écrit : >>>> Hi all, >>>> >>>> Currently, compound widget tag is only used in Examples application. >>>> Propose to convert rest of the project to use compound widget, so >>>> that dependencies are grouped together. >>>> >>>> Regards, >>>> James >>> pEpkey.asc (2K) Download Attachment |
In reply to this post by holivier
Hi Oliver,
I would suggest grouping elements that are specific to the main screen being called by a particular requesturi. The example for compound widget is for showcasing the use of compound widgets using very simple forms. Regards, James On 2020/06/15 09:01:53, Olivier Heintz <[hidden email]> wrote: > Hi James, > > It's a good idea, but question is, how to group ? > I have tested compound Widget for the POC VueJs, and I use it with one compound widget file by resouceName (on a REST uri format point of view). In > example, 4 files: Example, ExampleItem, ExampleFeature, ExampleFeatureAppl > I'm waiting for more time using them to say if it's the correct group size or not. > > So I suggest to use compound Widget, but not convert all xml files immediately, we need more developer experience to find the correct group size. > > Regards, > Olivier > > Le 13/06/2020 à 14:32, James Yong a écrit : > > Hi all, > > > > Currently, compound widget tag is only used in Examples application. > > Propose to convert rest of the project to use compound widget, so that dependencies are grouped together. > > > > Regards, > > James > > > |
In reply to this post by Nicolas Malin-2
Hi Nicolas,
Removed the additional namespace as I agree they are a distraction. Agreed that plugin may be a better place to apply compound widgets, as they are less likely being overriden by existing implementation. Just find it to be troublesome moving between related elements while making changes. So I will leave it for custom implementation then. Regards, James On 2020/06/15 13:05:44, Nicolas Malin <[hidden email]> wrote: > Hi, > > Compound widget is interesting from my view in final component, where > your code is closer than business cover so limited to reuse. > > For the "middle-ware" component, I have a doubt about the must valuable > to convert it or how to convert it. To organize by compound widget maybe > introduce to globalize by process and not by functional entities. > > After review your first commit [1] my feeling were decreased code > visibility with the namespace representation, swaying with regroup all > element that simplify the code navigation. Finally is that the problem > to improve the code navigation throw ide plugin and keep each xml as low > as possible (for the middle-ware component) and exploit compound widget > on plugin to indicate another way to concentrate business code ? > > Nicolas > > [1] > https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;a=blob;f=applications/order/widget/ordermgr/FindRequestCompound.xml;h=114e9c6d071a192d80e6278ba3e2c713f9ca1b17;hb=28809d7 > > On 14/06/2020 08:47, Jacques Le Roux wrote: > > Hi James, > > > > I see you pushed changes for FindRequest. Maybe we should wait a bit > > feedback from others? > > > > Jacques > > > > Le 14/06/2020 à 05:18, James Yong a écrit : > >> Hi Jacques, > >> > >> Ok, I created OFBIZ-11821 for this. > >> > >> Regards, > >> James > >> > >> On 2020/06/13 18:03:21, Jacques Le Roux > >> <[hidden email]> wrote: > >>> Hi James, > >>> > >>> As a 1st thought I'd see no problem with that. > >>> > >>> Jacques > >>> > >>> Le 13/06/2020 à 14:32, James Yong a écrit : > >>>> Hi all, > >>>> > >>>> Currently, compound widget tag is only used in Examples application. > >>>> Propose to convert rest of the project to use compound widget, so > >>>> that dependencies are grouped together. > >>>> > >>>> Regards, > >>>> James > >>> > |
Hi James,
Thanks for your try, it's interesting to show involves generate by the compound widget. Your commit without namespace has been more readable, it's good point. After If you want to continue, I imagine that convert a plugin like projectmgr or scrum would be a good place Nicolas On 17/06/2020 17:49, James Yong wrote: > Hi Nicolas, > > Removed the additional namespace as I agree they are a distraction. > > Agreed that plugin may be a better place to apply compound widgets, > as they are less likely being overriden by existing implementation. > Just find it to be troublesome moving between related elements while making changes. > > So I will leave it for custom implementation then. > > Regards, > James > > On 2020/06/15 13:05:44, Nicolas Malin <[hidden email]> wrote: >> Hi, >> >> Compound widget is interesting from my view in final component, where >> your code is closer than business cover so limited to reuse. >> >> For the "middle-ware" component, I have a doubt about the must valuable >> to convert it or how to convert it. To organize by compound widget maybe >> introduce to globalize by process and not by functional entities. >> >> After review your first commit [1] my feeling were decreased code >> visibility with the namespace representation, swaying with regroup all >> element that simplify the code navigation. Finally is that the problem >> to improve the code navigation throw ide plugin and keep each xml as low >> as possible (for the middle-ware component) and exploit compound widget >> on plugin to indicate another way to concentrate business code ? >> >> Nicolas >> >> [1] >> https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;a=blob;f=applications/order/widget/ordermgr/FindRequestCompound.xml;h=114e9c6d071a192d80e6278ba3e2c713f9ca1b17;hb=28809d7 >> >> On 14/06/2020 08:47, Jacques Le Roux wrote: >>> Hi James, >>> >>> I see you pushed changes for FindRequest. Maybe we should wait a bit >>> feedback from others? >>> >>> Jacques >>> >>> Le 14/06/2020 à 05:18, James Yong a écrit : >>>> Hi Jacques, >>>> >>>> Ok, I created OFBIZ-11821 for this. >>>> >>>> Regards, >>>> James >>>> >>>> On 2020/06/13 18:03:21, Jacques Le Roux >>>> <[hidden email]> wrote: >>>>> Hi James, >>>>> >>>>> As a 1st thought I'd see no problem with that. >>>>> >>>>> Jacques >>>>> >>>>> Le 13/06/2020 à 14:32, James Yong a écrit : >>>>>> Hi all, >>>>>> >>>>>> Currently, compound widget tag is only used in Examples application. >>>>>> Propose to convert rest of the project to use compound widget, so >>>>>> that dependencies are grouped together. >>>>>> >>>>>> Regards, >>>>>> James pEpkey.asc (2K) Download Attachment |
Free forum by Nabble | Edit this page |