Re: Warning a user based on input on action invocation

2019-06-16 Thread Dan Haywood
Cleaning up ... I've raised https://issues.apache.org/jira/browse/ISIS-2122 for this idea. On Fri, 23 Nov 2018 at 20:43, Andi Huber wrote: > You can solve this by adding a boolean parameter to the action, not as > pretty as a yellobackground advise, but at least works with what we already >

Re: Warning a user based on input on action invocation

2018-11-23 Thread Andi Huber
You can solve this by adding a boolean parameter to the action, not as pretty as a yellobackground advise, but at least works with what we already have: import org.apache.isis.applib.annotation.Action; import org.apache.isis.applib.annotation.Mixin; import

Re: Warning a user based on input on action invocation

2018-11-23 Thread Vladimir Nišević
Yes, this feature would be great one! In one application (non Isis but Eclipse RCP) we developed times ago, we had UI style guide where each input field can have warning/information/error depending on current user input (ideally giving feedback on each keystroke or when list selection happened).

Re: Warning a user based on input on action invocation

2018-11-23 Thread Dan Haywood
Yeah, I think this is a great idea. How about "advise" as a prefix to me; as in we are providing advice. Also sounds "softer" in tone than "warn". I guess it'll introduce a new phase ... hide, disable, validate, advise, executing, executed. So might be quite a bit of work to implement, but I

AW: Warning a user based on input on action invocation

2018-11-23 Thread Rade, Joerg / Kuehne + Nagel / HAM GI-DP
Good point! highlight/notify/raise/alertXxx ? -j -Ursprüngliche Nachricht- Von: Sander Ginn [mailto:san...@ginn.it] Gesendet: Freitag, 23. November 2018 16:46 An: users@isis.apache.org Betreff: Warning a user based on input on action invocation Hi, We’ve had a number of support

Warning a user based on input on action invocation

2018-11-23 Thread Sander Ginn
Hi, We’ve had a number of support requests relating to new users of our application that are not yet fully familiar with their business process. We do not wish to invalidate input as many business rules are not clearly defined in a ‘correct/incorrect’ fashion, with many exceptions and special