Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

These are the requirements for the “Improve the HTML Form Entry Module (Designer + Schemas)” project, which are presented in a list format, using natural language, and represent the improvements to be done, over the course of Google Summer of Code 2011. This project can be considered as a success if all the requirements are implemented, with some margin for reasonable unforeseen circumstances.

The project is composed by two subprojects:

  • Use Schemas in HTML Form Entry module
  • Update the WYSIWYG HTML Form Entry Designer module

List of Requirements

Use Schemas in HTML Form Entry module

Goal: Have the HTML Form Entry module use the Form Schema data model in OpenMRS, in order to update it, or generate HTML forms based on them.

Requirements:

The system should be prepared:

  • to update the form schema tables, when a HTML form is saved
  • to generate a HTML form, based on an existing form schema

This project should add some level of compatibility between the HTML Form Entry module and other Form Entry technologies in OpenMRS (a form can be started in Infopath and the edited as a HTML form and vice-versa).

Update the WYSIWYG HTML Form Entry Designer module

Goal: Provide an up-to-date WYSIWYG solution for designing HTML forms in OpenMRS.

Requirements:

The system should be prepared:

  • to allow WYSIWYG editing of the most usual HTML elements and styling
  • to allow WYSIWYG editing of specific elements provided by the HTML Form Entry module
  • to offer a easy, documented way of adding new elements
  • to integrate seamlessly with the existing HTML Form Entry module
  • No labels