Enhancement
PWA: include all adjunct forms for offline use
Issue description
There is two kinds of counter players in a form (for a new topic) which affect how the input is performed. Simple options (= topics which can play this role infinitely often) and adjuncts (= topic s which can play this role only once). Options are selected. Adjuncts are created with a form. This played a minor role up to now, but gains importance when the form should work offline. Since it is necessary that the constraints for adjuncts are shipped with main form. Adjuncts already have a quirky name in the code base. They are called "always new".
Developer comments
The name adjuncts is a bit misleading at first, as from a formal point of view, in a situation where both topics depend on each other, both are adjuncts if their respective form is used. In practise users have a clear mental hierachy. A simple example: given an order with order positions. A user regards the order much higher than the order position. It is usually the topic types with more constraints which "weigh" more in the users mind.
Why is it not necessary to include the constraints for options? In most cases users working offline do not create these, they just select one. In any case it is only power users who actually create options on the fly. Most, just fill out a form. That said there is exceptions to this rule.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.