| | 1 | = Molgenis UI components = |
| | 2 | |
| | 3 | One of the User Stories in Sprint 2 is to create UI components so people can easily create a User Interface using only Molgenis components, so no Freemarker templates anymore. |
| | 4 | |
| | 5 | On Tuesday 15th, Robert, Jessica, George and Erik had a discussion on what components we need. |
| | 6 | |
| | 7 | UI needs from George and Alex: |
| | 8 | * Add/edit data |
| | 9 | * View data, progress |
| | 10 | |
| | 11 | Example projects/code-bases to apply the new components: |
| | 12 | * Alex' and George's current project: GccCompute |
| | 13 | * Andre's and George's old project: LifeLinesImpute |
| | 14 | |
| | 15 | Suggested agenda: |
| | 16 | * Refactor RunButtonPlugin from Alex and George, showing how to seperate out logic (more object oriented, perhaps), and how to better communicate between template/java/database (MVC) |
| | 17 | * Refactor RunButtonPlugin UI from freemarker to new ui components (in gcc project, under plugins) |
| | 18 | * Refactor BackendPlugin backend (and freemarker) (in job_admin package, in sandbox) |
| | 19 | * Show how to use standard molgenis screen components in new UI form (table? list?) |
| | 20 | * Show how to make a component from scratch |
| | 21 | * Components wanted: |
| | 22 | - Progress Bar |
| | 23 | - Table |
| | 24 | - larger components with logic behind them inside a screen? I.e. shopping cart |
| | 25 | - xref input (advanced with ability to input stuff) |
| | 26 | - Conditional input logic (if I click on 'A', I want 'C', 'D', and 'E' to show, if I click on 'B' I want 'G' to show.) I.e. hide/show/modify input/options from a select box |
