HTML Form Entry Designer - Development Tracking


Contents

This is the Development Tracking page for the WYSIWYG Form Designer Project. You are encouraged to add suggestions and bugs directly to this page.

Known Bugs

  1. "Text after the field" isn't working for numeric/boolean widgets. When entered, it doesn't add that code to the editor - Agnor
  2. ADD YOURS HERE

Improvements

Functionality

  1. Add support for labelNameTag. The user should be able to see a list of the concept names for each locale and choose between one of those, or enter free text (labelText) - Agnor
  2. Add support for Obs Groups (obsgroup tag) - Agnor
  3. Add support for velocity expressions - Agnor
  4. Add support for the repeat tag - Agnor
  5. Add support for macros (See Discussion #3 ) - Agnor
  6. Fix some inconsistencies in the generateHtml() for some widgets. For instance, if no labelText is entered, it should not enter a labelText attribute instead of entering labelText="" - Agnor
  7. Add support for version 1.4 of htmlformentry module - Agnor
  8. ADD YOURS HERE

UI

  1. Allow the editing of widgets - Agnor
  2. Use a context menu for eliminating and editing widgets - Agnor
  3. Widgets should be recognizable in the editor (maybe a light background and a dashed border) - Agnor
  4. The dialogs should be more "beautiful" and well structured, possibly following some of the tinymce dialogs - Agnor
  5. The dialogs should have some inline validation and maybe show inline help - Agnor
  6. Add a "Cancel" button in the dialog and change the "Submit" button name to "Add" - Agnor
  7. Improve integration between htmlformentry and htmlformentrydesigner - Agnor
  8. ADD YOURS HERE

Code

  1. Refactor method and variable names to follow a consistent standard - Agnor
  2. The widgets scripts should be loaded automatically by DesignerScript.js, instead of being loaded in the .jsp pages - Agnor
  3. spring:message should be used more often - Agnor
  4. Add Concept should be refactored to Add Observation - Agnor
  5. ADD YOURS HERE

Discussion

  1. Should "Text after the field" be removed from the dialogs for numeric/boolean widgets? - Agnor
  2. Should "Text before the field" be changed to "Label:" or "Question label:"? - Agnor
  3. I think support for macros should, at least at first stages, only hide the text inside the "macros" tag - Agnor
  4. ADD YOURS HERE

Release Log

[Version 1.0 - Beta (2009-08-17)]