orbeon / orbeon-forms

Orbeon Forms is an open source web forms solution. It includes an XForms engine, the Form Builder web-based form editor, and the Form Runner runtime.
http://www.orbeon.com/
GNU Lesser General Public License v2.1
512 stars 220 forks source link

UI to configure properties #2238

Open ebruchez opened 9 years ago

ebruchez commented 9 years ago

Right now, admins have to use properties-local(-(dev|prod))?.xml. Some configuration properties really are the domain of an administrator, for the other properties, we should have a UI instead.

Questions

Where should the configuration be stored?

avernet commented 9 years ago

+1 from customer for suffix and digits after the decimal

acspike commented 9 years ago

Could sharing of properties between servers accessing the same DB be optional? Perhaps you could add a new property server-id and each property setting could include a column to store server-id. The default would be '*' causing all properties to be shared, but if a property needed to be targeted to a single server the server-id could be entered. Similar to how properties target Forms and Apps now.

ebruchez commented 9 years ago

@avernet See my comments wrt "digits after decimal". #2118 and #2281 are also relevant.

ebruchez commented 9 years ago

@acspike That sounds like a reasonable idea!

avernet commented 8 years ago

+1 from customer, specifically for:

ebruchez commented 8 years ago

+1 from customer

ebruchez commented 8 years ago

Following #2239, it is now possible to enable/disable the wizard on a per-form basis in the Form Builder UI.

avernet commented 7 years ago

+1 from customer

ebruchez commented 5 years ago

+1 from evaluator

ebruchez commented 5 years ago

+ 1 from latest product meeting as a support issue

ebruchez commented 5 years ago

+1 from customer for:

This said, for these, it probably would be better to have a setting in Form Builder directly.

avernet commented 4 years ago

+1 from customer for:

ykowalewski commented 4 years ago

+1 from customer for:

  • oxf.epilogue.xforms.inspector

any chance to have it in 2020.1?

ebruchez commented 4 years ago

@ykowalewski Sorry this is not going to be in 2020.1.

ebruchez commented 4 years ago

+1 from customer for a custom property

ebruchez commented 4 years ago

For XBL component configurations that use fr:component-param-value(), we store form-level values in fr-form-metadata, and then we check the property files. For example:

oxf.xforms.xbl.fr.dropdown-date.start-year

is stored as:

<xbl>
    <fr:dropdown-date start-year=""/>
</xbl>

Is there any reason other form-level properties couldn't be stored in the form definition as well? Maybe as:

<properties>
    <default-language>fr</default-language>
</properties>

Some space for custom properties is also needed.

One benefit is that you can set this directly in Form Builder. One drawback is that this is tied to the form definition.

avernet commented 2 years ago

+1 from customer