...
Info |
---|
This document presents sample goals for OpenLMIS v3.3 — This page is a conversation starter, and shouldn't be used an official reference |
UI Documentation
The OpenLMIS-UI Styleguide has a couple of problems
- Login required on start-up if not ui-components
...
- KSS focused documentation style really isn't helpful and is hard to edit
- Would remove KSS
- Move content to markdown files
- Add "generic workflow" documentation page to UI-Styleguide (would use standardized terms)
- Incorporate JSDocs into same styleguide
...
- Change page loading structure, so code examples are "run-able" using the Javascript framework of the UI
...
- Make JSDocs Components pages have executable examples, so UI components can be debugged/demo'd outside of business logic in screens
UI Extension
- Move OpenLMIS branding to reference-ui — which will then act as demo for implementers about how to extend the OpenLMIS-UI
v7 Architecture
Remaining work aside from documentation is:
-
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3799 - Making changes outlined in this ticket is probably a good idea (even if the v7 architecture isn't deemed valuable)
-
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3800 -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3801 -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2443 -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3802
Batch Requisition Screen
...
Use period & district to select requisitions to approve- Figure out horizontal virtual scroll
Technical Debt
- Fix technical debt in navigation component
- Issue is navigation component implementation is flawed
- Auth built into navigation
- Navigation only shows top level
- Need for menu content customization
- This is important because being able to add new tabs is currently done by manually updating HTML — where as dynamically creating navigation menus is much better for extendability
- Issue is navigation component implementation is flawed
- Remove code that uses local storage — replace with PouchDB
- Remove/Deprecate openlmis-ui-layout repository since v7 architecture shows separation of presentation and logic
Batch Requisition Screen
This feature is currently really badly designed and created. Here are some changes that need to be made
- Use period & district to select requisitions to approve
- Figure out horizontal virtual scroll