search

ezsystems / specs

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

Hybrid Prototype Requirements #4

Open DavidLiedle opened 7 years ago

DavidLiedle commented 7 years ago

REQUIREMENTS: https://github.com/ezsystems/specs/blob/v2-prototype-symfony3hybrid/eZ%20Platform/Admin%20UI/REQUIREMENTS.md

USE_CASE: https://github.com/ezsystems/specs/blob/v2-prototype-symfony3hybrid/eZ%20Platform/Admin%20UI/USE_CASE.md

dpobel commented 7 years ago

As a developer I want to extend the hybrid app with a React-based module. As a developer I want to extend the hybrid app with a Polymer-based module. As a developer I want to extend the hybrid app with a Angular-based application

before talking about any framework, it would be nice to define (at least roughly) what do we expect for the future admin interface in terms of UI/behavior/navigation... As I wrote in https://github.com/ezsystems/specs/issues/7, the community expects the application to be a Symfony application enhanced with some JavaScript. It's a completely different approach compared to current PlatformUI.

Technically speaking, that means our basis would be an application where you have a full page refreshes between pages. So from that basis, what do you expect ? Are those refreshes ok, sometimes ok, never ok ? Should we try to replicate PlatformUI current behavior in terms of navigation ?

Once this is defined, we can analyze which framework/technologies/architecture is the best fit. Also, trying to reuse PlatformUI components before having at least defined where we want to go does not seem to be the correct order to me. So #9 is kind of blocked by those questions (Also #9 is not super clear on its purpose but I'll comment there for that)

DavidLiedle commented 7 years ago

before talking about any framework, it would be nice to define (at least roughly) what do we expect for the future admin interface in terms of UI/behavior/navigation...

This is very true. Those are exactly the kinds of questions we need to be asking right now. Some of the answers won't come until we throw a few lines of code into the prototypes and poke them with a stick.

Progressive Enhancement is an excellent term to resurrect, as you mentioned in #7 @dpobel . There's a sweet spot between SPA and MPA where AJAX can request views from the back end when appropriate and innerHTML the heck out of the UI's divs. Just a brainstorm, but I think we can land on something like that where we're not looking at a boolean choice between UI behaviors.

DavidLiedle commented 7 years ago

Starting to put together requirements here: https://github.com/ezsystems/specs/blob/v2-prototype-symfony3hybrid/eZ%20Platform/Admin%20UI/REQUIREMENTS.md

Pull requests may be made to that branch.

Here's my first one to demonstrate: #21

https://github.com/ezsystems/specs/tree/v2-prototype-symfony3hybrid

DavidLiedle commented 7 years ago

Moved description for this issue into tracked md files in the working branch.

dpobel commented 7 years ago

Pull requests may be made to that branch.

any reason to not open it right now? That way we could really start discussing this topic.

andrerom commented 7 years ago

any reason to not open it right now? That way we could really start discussing this topic.

@dpobel for technical specs for possible solutions? That is more for you to drive isn't it?

dpobel commented 7 years ago

@dpobel for technical specs for possible solutions? That is more for you to drive isn't it?

I realize I misread @DavidLiedle's sentence, sorry for that.

my point is: why not opening a pull request against master so that we have the opportunity to discuss/approve those documents (the requirements and use case files), getting precision and so on. Once those are approved, the pull request can be merged and then another one can be open for technical spec if needed

DavidLiedle commented 7 years ago

Ping @dpobel PR opened: #24

It's a draft and needs some iterations, but ready for initial feedback and guidance in that PR