-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async exec refactoring #815
Conversation
|
121e29a
to
2241f82
Compare
Great this is green again! |
|
e2f2de5
to
3a21ccc
Compare
… everything uses it In order to have a single point of failure, all the calls to display.asyncExec and display.syncExec are now pointing to the DisplayUtil class. This required some refactoring of both .java and .clj files: in particular some code that originally was in eclipse.clj now has been moved to swt.clj (there was a TODO about it).
Some change was necessary in order for the tests to work again. Together with it, ClojureEditorTests has been removed as it seemed duplicated code, residual of some test.
This one should be ready, but I would like to merge the |
Ok but please not in master. I'd like to prepare a release and stabilize things ! :-) — On Fri, Jul 17, 2015 at 7:16 PM, Andrea Richiardi
|
Sure thing! Of course I will be waiting your approval 😉 |
Hello Laurent, what about this PR, have you had time to have a look at it? It would also solve the SmokeTests issue and we would have all green again.. |
Sure I need to review it, it was not on my radar, sorry |
👍 Thanks, just because I was taking up coding the partitions and I noticed this (that I refactored out from there) was not in yet... 😄 |
@@ -352,8 +352,8 @@ | |||
"Updates the observable-hovers part of the state. Returns new state." | |||
[old-state descriptors] | |||
(let [observable-hovers ^ObservableList (:observable-descriptors old-state) | |||
realm (SWTObservables/getRealm (workbench-display))] | |||
(.exec realm #(do (.clear observable-hovers) | |||
realm (SWTObservables/getRealm (swt/display))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering whether we should keep workbench-display and swt/display ... ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prolly not 😄
If you don't mind, I will first test commit 1e3819e and add (after some bed time) the additional modifications I brainstormed on the comments. I don't understand everything in the second commit (related to SmokeTests), but this can be done as a separate work not preventing me from integrating the work on ui. |
we'll keep the PR around for the time being, as it includes interesting comments/discussions |
Ok I saw the other PR, I will probably just integrate the second commit in |
(y) ok. So as soon as I've done a new pass across the comments on this PR, I will close it. |
Hello Laurent,
I was really really bothered by the tests not succeeding and therefore I refactored all the .asyncExec functions in one place (
DisplayUtil
) so that we can check fornull
andisDisposed
before executing any asyncExec/syncExec code onDisplay
.I hope I did not break anything and I still need to check that all the functionalities are working (especially the Outline). In the meantime I am putting this PR up so that I can check if Travis has green tests like me on my machine.
I also would like to ask you some question in the code that I refactored.
👍