Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[suggestion] Abstraction of plugin UI and styling #6

Open
mdfalkow opened this issue Nov 11, 2018 · 0 comments
Open

[suggestion] Abstraction of plugin UI and styling #6

mdfalkow opened this issue Nov 11, 2018 · 0 comments
Assignees

Comments

@mdfalkow
Copy link
Collaborator

mdfalkow commented Nov 11, 2018

Problem

Currently the plugin view is made explicitly, as opposed to dynamically. This makes for a bulkier code.

Suggestion

  1. Break down the UI into the component type, each with specific styling.
  2. Create modules for each component. (Research modules if necessary)
  3. Include each module in FastForwardView.
  4. Construct those components in FastForwardView.

Notes

  • You could also store the desired properties, classes, attributes, etc. in a JSON object then use a method in FastForwardView to generate the desired components using the specified data.
@mdfalkow mdfalkow changed the title [suggestionAbstraction of plugin UI and styling [suggestion] Abstraction of plugin UI and styling Nov 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants