mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-07 23:32:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update wikipage Graphics with concurrency. (Signed-off-by:jocelyn).

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1439 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2015-09-28 11:49:03 +00:00
parent 2df3763fa1
commit 99f2ac2dc2
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/trunk/solutions/concurrent-computing/Graphics-with-concurrency.wiki
View File

@@ -1,4 +1,4 @@
[[Property:uuid|C881D4E8-4C3C-4AEB-8005-8315E743EC26]] [[Property:uuid|41367400-CA34-4121-853B-035B8C15FE53]]
[[Property:weight|0]] [[Property:weight|0]]
[[Property:title|Graphics with concurrency]] [[Property:title|Graphics with concurrency]]
How can I build a concurrent graphical in application in Eiffel? How can I build a concurrent graphical in application in Eiffel?
@@ -18,21 +18,21 @@ Since your application uses SCOOP, somewhere it creates a separate object. Let t
where s is of a separate type (e.g. separate T). where s is of a separate type (e.g. separate T).
In the "make" creation procedure, create an EV_APPLICATION object, using an instruction such as In the "make" creation procedure, create an EV_APPLICATION object, using an instruction such as
create my_app create my_app
with my_app of type EV_APPLICATION. with my_app of type EV_APPLICATION.
Still in "make", create all the GUI elements. They will all be in the same processor that created the EV_APPLICATION object. Still in "make", create all the GUI elements. They will all be in the same processor that created the EV_APPLICATION object.
Also in "make", start the application, using Also in "make", start the application, using
my_app.launch my_app.launch
In the pre-SCOOP world, launch would start the event loop. Here it only creates a separate object (of type EV_APPLICATION_HANDLER), which will run the event loop, forwarding events to the EV_APPLICATION object. In the pre-SCOOP world, launch would start the event loop. Here it only creates a separate object (of type EV_APPLICATION_HANDLER), which will run the event loop, forwarding events to the EV_APPLICATION object.
This is all the make procedure should do. Make sure it terminates with the preceding step. Otherwise, the event loop will never run! This is all the make procedure should do. Make sure it terminates with the preceding step. Otherwise, the event loop will never run!
Now you can start using EiffelVision as you are used to, by sending GUI requests to the EV_APPLICATION object: Now you can start using EiffelVision as you are used to, by sending GUI requests to the EV_APPLICATION object:
o For requests coming from the same processor as s, just use the EV_APPLICATION object directly. * For requests coming from the same processor as s, just use the EV_APPLICATION object directly.
o For requests coming from another processor, you need access to that object; you can get it for example by through the feature ev_separate_application of class EV_SHARED_APPLICATION}. * For requests coming from another processor, you need access to that object; you can get it for example by through the feature ev_separate_application of class EV_SHARED_APPLICATION}.
That's all! Happy concurrent Eiffeling. That's all! Happy concurrent Eiffeling.