It just doesn't make sense to support a read-only mode for certain components
(buttons, spinners, sliders, etc.). However, adding a read-only flag to
Calendar would be OK.
On Tuesday, June 16, 2009, at 05:42AM, "Sandro Martini"
<[email protected]> wrote:
>Hi to all,
>et voilà some ideas for the Read-Only mode (or maybe at the opposite,
>a !editable mode ...):
>
>- i imagine elements in read-only fully working and active, they only
>doesn't respond to user for modifying their values, but they respond
>to mouse/keystroke events, and fully updates the graphics (and by code
>i can modify their values).
> Disabled elements instead doesn't respond to user events nor to
>graphics update events until they are enabled, I'm not sure if by
>code i can modify their values (but i think yes), so new values should
>not appear until next refresh (when enabled) and I don't know if in
>this case listener events shouldn't be fired, for consistency.
>
>For example, a read-only Date Picker should expand at mouse click, but
>doesn't change its value.
>
>I hope this is not too different from the current working mode of
>Pivot components ...
>
>
>- i like the Text Input in read-only mode, but if Text Area can have
>it (and if we can constrain text area to a single line, and to work
>like a text input) for me is enough ...
> The plus in this case is to have a control like others in the same
>form (usually forms have many text inputs), visually similar, but for
>many reason in some moments not editable ... then when it will be
>editable i haven't to change a label to text input (or other strange
>tricks), i could only change its read-only status.
>
>- other elements that could have the read-only state are (buttons no, ok):
> Lists (at the moment all lists haven't this) all types including
>list buttons,
> DatePicker (or Calendar Buttons) and Calendars (if not in their
>spinners, at least in the date sheet),
> and other minor cases like Spinners and Sliders, and Splitters ?,
> why not also Checkboxes and maybe Radio Buttons (we should see if
>others GUI toolkit have this feature, i don't remember) ? ... but i
>agree, we can live without this.
>
>Oh, a TimePicker component could be useful, at the moment is missing
>(we can do it with spinners, ok), but a custom version could help. For
>the 1.4 ?
>
>- i agree with you that many components are already read-only
>components (from the user point of view), like Grid, Tree, etc ... i
>have to look better at the Demo "Table Row Editor" on how to edit a
>table row.
>
>- an interesting feature could be also to have a Style for read-only
>elements (or an optional style for any read-only type of elements),
>for example in Substance by default there is an optional lock icon
>near the read-only element.
>
>
>I hope to be clear, if not tell me, but in any case, what do you think ?
>
>
>
>Ah, sorry, one last thing:
>in the Kitchen Sink Demo from the site (
>http://cwiki.apache.org/PIVOT/kitchen-sink-demo.html ), i got a
>Javascript error (Win XP, IE6):
>Line: 35 , Char: 278 , Error: Expected ')'
>and today Firefox hangs on this page ...
>
>
>Bye,
>Sandro
>
>
