Skip to content
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.

Menu creation mechanism #1

Open
mlopezFC opened this issue Jul 2, 2021 · 1 comment
Open

Menu creation mechanism #1

mlopezFC opened this issue Jul 2, 2021 · 1 comment
Assignees
Milestone

Comments

@mlopezFC
Copy link
Contributor

mlopezFC commented Jul 2, 2021

These are the guidelines that we should follow in order to implement a mechanism for building a menu for an application:

  • The menu should be assembled in the client side, but obtaining the menu options from the server side
  • It should be a mechanism for adding menu items from the client side (for pure client side functionalities) in a project that is using commons-vaadin
  • The mechanism for obtaining the menus from the server side should be provided by commons-vaadin
  • If for some reason the server side items cannot be obtained the menu should be displayed anyway
  • Components like dynamic-menu should be able to contribute to building the menu obtaining the items from other places (ie: db)
@mlopezFC mlopezFC self-assigned this Jul 2, 2021
@mlopezFC mlopezFC added this to the Sprint 3 milestone Jul 2, 2021
@mlopezFC
Copy link
Contributor Author

mlopezFC commented Jul 2, 2021

One idea that pops into my mind, is that maybe we could leverage the menu generation to AppLayout.
Maybe we could build a new version (v4 or v5?) of that addon with the following features:

  • Use the new webcomponents
  • Maintain the old API and old way of using it, so migration from previous version could be easy
  • Provide a clientCallable or fusion endpoint to provide server side items to a almost stand alone client side version (the new way of using it)

@mlopezFC mlopezFC modified the milestones: Sprint 3, Sprint 4 Jul 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant