You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@pivot.apache.org by Sandro Martini <sa...@gmail.com> on 2010/01/26 00:47:40 UTC
Optional Auto-close on Alerts and Prompts
Hi to all,
for a prototype I'm starting to develop, I'm thinking on adding a
simple feature that could be very useful to enhance a little the User
Experience:
an auto-close feature on (modal but maybe not only) dialog boxes with
only 1 button, usually the OK button (but could be applied also if the
dialog has n buttons, going with the default selection), where after n
milliseconds if the dialog is still open, it will close (or fade or
other ...).
Of course this feature would be off by default, and with a default for
example of 1000 msec.
I've tried this feature is some web frameworks with data-entry
applications, and it's very interesting.
For example after a successful Insert of data, the user would be
notified of the success or the failure, but without having to move
with the mouse and click to close the button.
What do you think ?
I can add this to JIRA, maybe for the 1.4.1, tell me.
Here could be applied to Alerts and Prompts, to have a sort of
Notification dialog boxes.
Or if not here, in a subclass ... ideas ?
Bye,
Sandro
Re: Optional Auto-close on Alerts and Prompts
Posted by Sandro Martini <sa...@gmail.com>.
Hi Greg,
and thanks for the (very fast) and clear answer :-) .
Bye
Re: Optional Auto-close on Alerts and Prompts
Posted by Sandro Martini <sa...@gmail.com>.
Hi Greg,
and thanks for the (very fast) and clear answer :-) .
Bye
Re: Optional Auto-close on Alerts and Prompts
Posted by Greg Brown <gk...@mac.com>.
When the dialog opens, you can set a timer using ApplicationContext.scheduleCallback(). In the callback, close the dialog.
On Jan 26, 2010, at 6:54 PM, Sandro Martini wrote:
> Ok, but in this case what approach you suggest:
> add a new Component class (derived from one of our dialogs) with this
> feature, or simply add a thread that at the given timeout will close
> automatically the dialog ? Or other ?
>
> Thanks,
> Sandro
Re: Optional Auto-close on Alerts and Prompts
Posted by Greg Brown <gk...@mac.com>.
When the dialog opens, you can set a timer using ApplicationContext.scheduleCallback(). In the callback, close the dialog.
On Jan 26, 2010, at 6:54 PM, Sandro Martini wrote:
> Ok, but in this case what approach you suggest:
> add a new Component class (derived from one of our dialogs) with this
> feature, or simply add a thread that at the given timeout will close
> automatically the dialog ? Or other ?
>
> Thanks,
> Sandro
Re: Optional Auto-close on Alerts and Prompts
Posted by Sandro Martini <sa...@gmail.com>.
Ok, but in this case what approach you suggest:
add a new Component class (derived from one of our dialogs) with this
feature, or simply add a thread that at the given timeout will close
automatically the dialog ? Or other ?
Thanks,
Sandro
Re: Optional Auto-close on Alerts and Prompts
Posted by Sandro Martini <sa...@gmail.com>.
Ok, but in this case what approach you suggest:
add a new Component class (derived from one of our dialogs) with this
feature, or simply add a thread that at the given timeout will close
automatically the dialog ? Or other ?
Thanks,
Sandro
Re: Optional Auto-close on Alerts and Prompts
Posted by Greg Brown <gk...@mac.com>.
Sounds like a reasonable feature, but one that I would probably delegate to the application (not the framework).
On Jan 25, 2010, at 6:47 PM, Sandro Martini wrote:
> Hi to all,
> for a prototype I'm starting to develop, I'm thinking on adding a
> simple feature that could be very useful to enhance a little the User
> Experience:
>
> an auto-close feature on (modal but maybe not only) dialog boxes with
> only 1 button, usually the OK button (but could be applied also if the
> dialog has n buttons, going with the default selection), where after n
> milliseconds if the dialog is still open, it will close (or fade or
> other ...).
> Of course this feature would be off by default, and with a default for
> example of 1000 msec.
>
> I've tried this feature is some web frameworks with data-entry
> applications, and it's very interesting.
> For example after a successful Insert of data, the user would be
> notified of the success or the failure, but without having to move
> with the mouse and click to close the button.
>
> What do you think ?
> I can add this to JIRA, maybe for the 1.4.1, tell me.
>
> Here could be applied to Alerts and Prompts, to have a sort of
> Notification dialog boxes.
> Or if not here, in a subclass ... ideas ?
>
>
> Bye,
> Sandro
Re: Optional Auto-close on Alerts and Prompts
Posted by Greg Brown <gk...@mac.com>.
Sounds like a reasonable feature, but one that I would probably delegate to the application (not the framework).
On Jan 25, 2010, at 6:47 PM, Sandro Martini wrote:
> Hi to all,
> for a prototype I'm starting to develop, I'm thinking on adding a
> simple feature that could be very useful to enhance a little the User
> Experience:
>
> an auto-close feature on (modal but maybe not only) dialog boxes with
> only 1 button, usually the OK button (but could be applied also if the
> dialog has n buttons, going with the default selection), where after n
> milliseconds if the dialog is still open, it will close (or fade or
> other ...).
> Of course this feature would be off by default, and with a default for
> example of 1000 msec.
>
> I've tried this feature is some web frameworks with data-entry
> applications, and it's very interesting.
> For example after a successful Insert of data, the user would be
> notified of the success or the failure, but without having to move
> with the mouse and click to close the button.
>
> What do you think ?
> I can add this to JIRA, maybe for the 1.4.1, tell me.
>
> Here could be applied to Alerts and Prompts, to have a sort of
> Notification dialog boxes.
> Or if not here, in a subclass ... ideas ?
>
>
> Bye,
> Sandro