Hey, 1.9 is almost out. I'd like to start a discussion on what to include in 1.10.
Let's have a better module support! Module management needs to be improved. We're saying OpenMRS is a modular architecture, but it's hard to acknowledge working with the Manage Modules page. I'm asking for a feature that allows to pack a few modules together in a single omod which can be installed and managed as one. Let's say we have HTML Form Entry and HTML Form Entry Designer. There's no point in distributing HTML Form Entry Designer alone since it requires HTML Form Entry to run. The other example is still hypothetical. Let's say you want to share reports from the Reporting module using the Metadata Sharing module. For that to work you would need the ReportingMDSSupport module. Why you need to know that? It should be packaged and managed by the Reporting module. It's the Reporting module that should know that if the Metadata Sharing module is started, it should start the RerportingMDSSupport. Going further, there's a great new feature in 1.9: visists. In order for the HTML Form Entry module to make use of that you would need HTML Form Entry 1.9 Compatibility module. And then comes 1.10 with even better visits and you need yet another HTML Form Entry 1.10 Compatibility module. It's a management nightmare to install all those modules and keep them running, but should be easily managed by the HTML Form Entry itself which when installed on 1.9 should simply start the 1.9 Compatibility feature. Hope I explained the idea good enough! I'm waiting for thumbs up or down for this idea! -Rafal _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
