...
These pages (legacy patient dashboard, patient search, dictionary, reporting, and administration) and the extension hooks they provided represent the majority of OpenMRS' legacy UI. Looking under the hood, you would find that several of these (patient dashboard, dictionary management, and reporting) are already hooking into a legacy home page that provides the basic structure used by all of these pages and is hidden (replaced with the new home page) in OpenMRS 2.0+. Creating a module that includes the legacy home page structure and supports the legacy approach to web page extension points will be the bulk of the work involved in this project. Once that is achieved, then you should be able to migrate most of the code for the legacy UI into it without making major changes to the code.To Do:
Move admin UIMove admin UI related controllers(few)Update the beans in web module application context(few)- Build and Run the module to display the page respective to the controller
- Move other UI components one by one such as:
- patient dashboard
- dictionary, etc.
Move the related controllers and update the beans to get the UI working
+JIRA project alloted here.
Requirements
- Good Java skills
- Familiarity with J2EE web programming (e.g., JSPs)
- Familiarity with Spring Framework will help
...