Difference between revisions of "User:Frank Schönheit/ODF ToDo"
(→proposals in the queue) |
|||
| Line 1: | Line 1: | ||
| − | {{DISPLAYTITLE:ODF Action Items}} | + | {{DISPLAYTITLE:Frank Schönheit's ODF Action Items}} |
Usually, when I implement a minor feature, I prefer finishing the mere feature implementation without an actually approved file format change. That is, introducing (e.g.) a new attribute to some already-specified ODF elements is a time-consuming task, since you need to write a proposal, which needs to be discussed and approved in the respective [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office Oasis TC], and finally become part of an upcoming ODF standard. | Usually, when I implement a minor feature, I prefer finishing the mere feature implementation without an actually approved file format change. That is, introducing (e.g.) a new attribute to some already-specified ODF elements is a time-consuming task, since you need to write a proposal, which needs to be discussed and approved in the respective [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office Oasis TC], and finally become part of an upcoming ODF standard. | ||
| Line 15: | Line 15: | ||
This section collects proposals already in the queue. That is, they're passed to a TC member, asking for submission to the TC (even if this submission didn't happen, yet) | This section collects proposals already in the queue. That is, they're passed to a TC member, asking for submission to the TC (even if this submission didn't happen, yet) | ||
| − | * Extending the <code>style:repeat</code> attribute with a <code>scale</code> value | + | * [[User:Frank_Schönheit/ODF_Proposals/Image_Control_Scale|Extending the <code>style:repeat</code> attribute with a <code>scale</code> value]] |
* [[User:Frank_Schönheit/ODF_Proposals/Mouse_Wheel_Scroll|An attribute controlling the mouse wheel scroll behavior for form controls.]] | * [[User:Frank_Schönheit/ODF_Proposals/Mouse_Wheel_Scroll|An attribute controlling the mouse wheel scroll behavior for form controls.]] | ||
Revision as of 20:14, 1 July 2009
Usually, when I implement a minor feature, I prefer finishing the mere feature implementation without an actually approved file format change. That is, introducing (e.g.) a new attribute to some already-specified ODF elements is a time-consuming task, since you need to write a proposal, which needs to be discussed and approved in the respective Oasis TC, and finally become part of an upcoming ODF standard.
This page is dedicated to collecting my action items resulting from this habit.
proposals to write
This section collects items where a file format change proposal is to be written and submitted to the Oasis ODF TC.
-
form:input-required: Currently, the value of the InputRequired property of a data-aware form control is stored in an attribute calledform:input-required. This attribute is not yet specified - need write a proposal for it. - CWS dba32c introduced a
EnableVisibleproperty for form controls, which currently is stored in an attributeform:visible. Need to write a proposal for this. Probably, the property needs to be stored as style, as it is usually done for other visibility properties in ODF.
proposals in the queue
This section collects proposals already in the queue. That is, they're passed to a TC member, asking for submission to the TC (even if this submission didn't happen, yet)
