Changes between Version 9 and Version 10 of level1

Timestamp:

01/09/10 00:28:15 (8 months ago)

Author:

http://nedko.arnaudov.name/

Comment:

--

level1

@@ -24 +24 @@
  * on first SIGUSR1 received, the file containing the internal state gets created.
 
-The second approach looks definitively better from user experience point of view. But it must be implemented carefully because users may expect default behaviour to be to refuse startup when supplied file path is not valid. IMO, this is quite common and natural for non-ladish workflows. It will be wise to refuse startup when path does not exist but behave in ladish friendly way if a special commandline options is supplied too.
+The second approach is definitively better from user experience point of view, but it must be implemented carefully because users may expect default behaviour to be to refuse startup when supplied file path is not valid. This is quite common and natural for non-ladish workflows. It will be wise to refuse startup when path does not exist but behave in ladish friendly way if a special commandline option is supplied too.
 
-If there is no file path supplied, app is free to decide what to do. Best would be to show "save as" dialog. If this is not possible, user could be informed that save will not be performed. As last possibility, SIGUSR1 can be just ignored and user will have to be more careful.
+If SIGUSR1 is received but there is no file path supplied, app is free to decide what to do. Best would be to show a "save as" dialog. If this is not possible, user could be informed that save will not be performed. As last possibility, SIGUSR1 can be just ignored and user will have to be more careful.
 
 = Examples =