JADE Environment Development Ideas

Brian Johnstone 26/03/2018 5:42:45 PM
When we are going to perform a potentially long running task, we display a progress dialog and ensure that we do 'time based' refreshes of the progress dialog so that users can see it making progress without negatively impacting performance with large numbers of round-trips to the presentation client and back again to 'update the progress' or 'allow a repaint' to occur. This helps reduce/remove the risk of the users killing it with Task Manager. Having the application be 'non-blocking', by removing the blocking call on the main UI thread would mean that Jade would also need to ensure users can't interact with the form, such as clicking the close/terminate etc buttons, as you wouldn't want that happening either in the middle of your logic, nor would you want any interleaving of event methods being sent back to your logic as that could cause very interesting behaviour with the current/expected state of things at the time of events being fired. (It's already bad enough when you come across someone coding an app.doWindowEvents when what they really wanted to use was 'someWindow.doWindowEvents' to allow their progress dialog to refresh or a 'Cancel button' to be clicked or similar.)