Difference between revisions of "Modernization Roadmap"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) |
||
| Line 12: | Line 12: | ||
:#*Standard place for third party php packages (likely managed/organized via composer), which can be easily migrated when needed in the future. | :#*Standard place for third party php packages (likely managed/organized via composer), which can be easily migrated when needed in the future. | ||
:#Convert codebase to fully use model classes. | :#Convert codebase to fully use model classes. | ||
:#Integrate an MVC (community is | :#Integrate an MVC (community is considering Zend at this time). | ||
:#Complete the normalization of the directory structure. | :#Complete the normalization of the directory structure. | ||
:#Refactor codebase to use most modern version of each asset. | :#Refactor codebase to use most modern version of each asset. | ||
Revision as of 19:46, 3 July 2016
Overview
- Community is in midst of designing a strategy to modernize both the user interface(front end) and codebase(back end) of OpenEMR. These are basically notes from the ongoing discussions in the forum.
User interface
- Modern styles (first generation).
- Incorporate bootstrap.
- Modern styles (second generation).
- Remove frames (ie. convert to iframe).
Codebase
- Begin to normalize directory structure
- Standard place for static css/js assets (such as jquery), which can be easily migrating when needed in the future.
- Standard place for third party php packages (likely managed/organized via composer), which can be easily migrated when needed in the future.
- Convert codebase to fully use model classes.
- Integrate an MVC (community is considering Zend at this time).
- Complete the normalization of the directory structure.
- Refactor codebase to use most modern version of each asset.
- Begin to normalize directory structure
Ongoing Forum Discussions
- Ongoing forum discussions of the above roadmap can be found here.
