search

ezsystems / specs

CLOSED, moved to another repo. Please visit:
https://ezplatform.com/product-feedback
Other
4 stars 1 forks source link

POC Hybrid SF app loading YUI modules from 1.x #9

Closed DavidLiedle closed 7 years ago

DavidLiedle commented 7 years ago

As we transition to a Modern Architecture, we need to explore ways in which we can still use some modules from YUI during the transition.

The deliverable for this Spike will be an estimated Story or Stories, to include: "As a Developer, I want a roadmap from v1/YUI to v2/TBD, so that I can contribute to v2 in an iterative transition", related to Epic https://jira.ez.no/browse/EZP-26866

The timebox for this Spike is up to X hours (X.x days). (Final timebox number TBD w/Engineer(s).)

Postponed pending Engineer availability.

This Spike is authorization to explore and pursue the proposal given here: https://github.com/ezsystems/PlatformUIBundle/blob/poc_subitem_udw_sf_app/docs/subitem-udw-in-sf-app.md

DavidLiedle commented 7 years ago

Migrates https://jira.ez.no/browse/EZP-26866 here.

DavidLiedle commented 7 years ago

As a SPIKE, this should probably be moved to an issue in ezsystems/ezplatform when we have bandwidth to pick it up, and then an issue on https://github.com/ezsystems/PlatformUIBundle when development work begins.

dpobel commented 7 years ago

As a SPIKE, this should probably be moved to an issue in ezsystems/ezplatform when we have bandwidth to pick it up, and then an issue on https://github.com/ezsystems/PlatformUIBundle when development work begins.

do we abandon JIRA ?

dpobel commented 7 years ago

Besides the tools question, it seems like the purpose of EZP-26866 has changed while being moved here.

EZP-26866, #4 and the beginning of this issue seems to imply that we want to reuse some identified components of the current application (UDW, subitems, ...) but then we can read so that I can contribute to v2 in an iterative transition which can be interpreted as we want to be able to reuse any components. That's very different and the later interpretation is clearly more complicated. @DavidLiedle can you clarify ?

Note: The Web Component based sandbox proposal (to be technically tested/validated) was made with the first interpretation in mind and relies on the fact that the component to port are already quite isolated/independent (ex. UDW, SubitemList, Tree, ...) both technically and its behavior.

DavidLiedle commented 7 years ago

Not abandoning JIRA - just trying GitHub Projects/Issues for v2-stuff-only. Once everyone has a chance to get their hands dirty in here, we'll know better if it meets our needs or not.

Nothing implied - we need to discover what is possible as we get into it more. Taking the first baby steps in should start to shed light on what's difficult and what's low hanging fruit. The hybrid approach will require a lot of experimentation to find the line between what is back end, what is front end, and what may or may not be reusable from the existing v1. Spikes and prototypes will definitely precede any clear vision on what that can even look like.

The sandbox idea is yours, so you know best what that entails. It sounds like it has a lot of potential, and everyone agrees it should be given adequate time to explore when you're available. The wording on the GitHub issues can be updated if it doesn't mesh well with what you have in mind. I don't mean to limit your Spike at all by writing anything down differently than what you had in mind originally. :)

These questions, observations, and conversations will help us to refine our direction, for sure. Thank you for taking the time to get a head start on the conversation here! I'm very excited for the phase where the v2 tasks will begin full steam ahead!

rolandbenedetti commented 7 years ago

About the question

EZP-26866, #4 and the beginning of this issue seems to imply that we want to reuse some identified components of the current application (UDW, subitems, ...) but then we can read so that I can contribute to v2 in an iterative transition which can be interpreted as we want to be able to reuse any components. That's very different and the later interpretation is clearly more complicated. @DavidLiedle can you clarify ?

To me clearly the top priority is to explore how to reuse identified components. Being able to reuse "any" component would also be valuable (thinking about someone who actually did something with 1.x and YUI and who wants to move to 2.x), so it's also something this prototype should touch on. It's however less critical. If more complex, why not splitting in two spikes but clearly both options are interesting.

DavidLiedle commented 7 years ago

Closing this thread and repository. Conversations may continue in the new repo here: https://github.com/ezsystems/requirements/pull/13