Thu 14 Apr 2011 08:56:54 PM UTC, comment #2:
I don't think it's appropriate that a plugin be able to interfere with a user's use of the Bo-Keep shell. I don't want hooks for that.
Or, at least this case hasn't convinced me.
The "Bo-Keep way" is to disable interactive widgets when context means they make no sense -- so if entered information is just going to be lost the user shouldn't be able to enter it in the first place.
The other side of the "Bo-Keep way" (well, in the main window...) is that we never take data from a user and toss it. If they get the chance to enter it, retainment is automatic, no "we'll only keep it if you do these other things stuff" and "if you don't do it the right we annoy you with pop up stuff"
So two ways to do this
1. a Trust transaction can be associated with no trustor and the user can edit everything else and everthing else is automatically retained. But, the get_financial_transactions function could refuse to pass it on to the backend if no trustor is selected.
2. We say that all trust transactions must be associated with a trustor and we don't let the user edit anything else (by disabling the other widgets) until a trustor is selected.
The other thing to figure out -- when there is at least one trustor available do we automatically default to it (meaning this issues only applies when no trustors are available), or do we default to no trustor and make the user choose one (before anything else).
|