batkinson / oxdformdesignermockup Goto Github PK

The way rules are represented in the object model allows for multiple target questions for a single rule. However, when translated to xforms constraints, each becomes a separate rule. This manifests as some strange behavior in the editor in that a form that is built, exported to xml and then re-imported can start with 1 multi-target rule, and turns into many single target rules with the same constraint.

It should be possible to analyze the rules once constructed and consolidate them back into a single rule. It should probably be fixed in the xml-to-model parser if it works.

Currently, the instance name is pulled in from the existing xform definition and there is no way to change it in the editor. Editing the xml and re-importing is the only way to do it now. Care should be taken to ensure that variable names referring to the old instance name are rewritten.

Currently, when you add questions they start with empty binding values. So the form will work properly when translated to/from xforms and so that the users have an example to change if they desire, valid binding values should be assigned to items created by the designer.

For some reason, dragging the pages around to reorder doesn't accept the drop target. There may have been some change in the drop policy that is causing this, or perhaps it was done intentionally?

For whatever reason, the support for rendering tab characters in Pivot is limited. Convert to using spaces for indenting. As part of this, it should parametrized.

I believe the older openxdata xform format didn't use namespaces. The model converter should be able to generate xforms that would work in this case.

Currently, the designer can generate working models that xml model converter doesn't properly generate.