Le 17/12/2019 à 15:12, Gil Portenseigne a écrit :
> Hello Taher,
>
> The proposition you saw with your first glance is
.....
>
> In that vision implementing a theme for SPA application should be
> possible, but in our opinion a gigantic task to support the screen
> engine. We think that for back office application, we should stay with
> the classic way to implement screens, and improve it to get more
> efficient.
>
The implementation of a theme for a SPA application is a big task and should be
studied from an agile perspective.
POC-VueJs was initiated and realized in this perspective.
The POC should allow to :
* to be able to test a simple conversion from macro.ftl to the vuejs component
(or other SPA framework)
* be able to test the advanced functionalities of the SPA framework from the
point of view of an ERP back office application
* to be able to test new uses of the graphical interface linked to the SPA
concept
I think this is only possible if there are enough screens / components
available in the POC.
We chose Party because it will be possible to derive it to HR / CRM B2C /
eCommerce Profile pages / CRM B2B / facilities workers.
Currently, only the main screens of Party are working, it is possible to play
with them at
https://ofbiz-selenium.ofbizextra.org/partymgrfjs/control/main (vuejs is in dev
mode so it is possible to view components and store areas)
https://demo-vuejs.ofbizextra.org/partymgrfjs/control/main (vuejs is in prod
mode)
POC-VueJs is not a theme but there are already very similar points and we
should work in this direction too.
Even if some modifications should be made on a component before using this
"kind of theme", we should consider rendering it - component VueJs as a theme.
POC will have several steps before it is possible to choose and validate the
right solutions.
During POC we store the "migration time" per component / screens to be able to
have an evaluation of the migration ofbiz applications in the future.
