Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
jvx:reference [2020/06/24 15:37] cduncan […and why do I need to handle them?] |
jvx:reference [2020/06/24 15:42] cduncan [Method references] |
||
|---|---|---|---|
| Line 1765: | Line 1765: | ||
| ===== Terminology ===== | ===== Terminology ===== | ||
| - | For [[https://sourceforge.net/projects/jvx/|JVx]] the following terminology applies: An event is a property of an object, you can register listeners on that event which will get invoked if the event is dispatched (fired). Every event consists of the ''%%EventHandler%%'' which allows to register, remove and manage the listeners and also dispatches the events, meaning invoking the listeners and notifying them that the event occurred. There is no single underlying listener interface. | + | For [[https://sourceforge.net/projects/jvx/|JVx]] the following terminology applies: an event is a property of an object. You can register listeners on that event that will get invoked if the event is dispatched (fired). Every event consists of the ''%%EventHandler%%'', which allows ypi to register, remove, and manage the listeners and also dispatches the events, meaning it invokes the listeners and notifies them that the event occurred. There is no single underlying listener interface. |
| - | Within the [[https://sourceforge.net/projects/jvx/|JVx]] framework, every event-property of an object does start with the prefix “event” to make it easily searchable and identifiable. But enough dry talk, let’s get started. | + | Within the [[https://sourceforge.net/projects/jvx/|JVx]] framework, every event property of an object starts with the prefix “event” to make it easily searchable and identifiable. But enough dry talk, let’s get started. |
| - | ===== Attaching listeners ===== | + | ===== Attaching Listeners ===== |
| We will now look at all the ways on how to attach a listener to an event. | We will now look at all the ways on how to attach a listener to an event. | ||
| Line 1775: | Line 1775: | ||
| ==== Class ==== | ==== Class ==== | ||
| - | The easiest way to get notified of events is to attach a class (which is implementing the listener interface) to an event as listener, like this: | + | The easiest way to get notified of events is to attach a class (that is implementing the listener interface) to an event as listener, like this: |
| <code java> | <code java> | ||
| Line 1800: | Line 1800: | ||
| } | } | ||
| </code> | </code> | ||
| - | ==== Inlined class ==== | + | ==== Inlined Class ==== |
| - | Of course we can inline this listener class: | + | Of course, we can inline this listener class: |
| <code java> | <code java> | ||
| Line 1825: | Line 1825: | ||
| } | } | ||
| </code> | </code> | ||
| - | ==== JVx style ==== | + | ==== JVx Style ==== |
| - | So far, so normal. But in [[https://sourceforge.net/projects/jvx/|JVx]] we have support to attach listeners based on reflection, like this: | + | So far, so good. However, in [[https://sourceforge.net/projects/jvx/|JVx]] we have support to attach listeners based on reflection, like this: |
| <code java> | <code java> | ||
| Line 1849: | Line 1849: | ||
| } | } | ||
| </code> | </code> | ||
| - | What is happening here is that, internally, a listener is created which references the given object and the named method. This allows to easily add and remove listeners from events and keeping the classes clean by allowing to have all related event listeners in one place and without additional class definitions. | + | What is happening here is that, internally, a listener is created that references the given object and the named method. This allows us to easily add and remove listeners from events and keeps the classes clean by allowing us to have all related event listeners in one place without additional class definitions. |
| ==== Lambdas ==== | ==== Lambdas ==== | ||
| - | Yet there is more, we can of course attach [[https://docs.oracle.com/javase/tutorial/java/javaOO/lambdaexpressions.html|lambdas]] to the events as listeners, too: | + | Yet there is more. We can, of course, attach [[https://docs.oracle.com/javase/tutorial/java/javaOO/lambdaexpressions.html|lambdas]] to the events as listeners too: |
| <code java> | <code java> | ||
| Line 1870: | Line 1870: | ||
| } | } | ||
| </code> | </code> | ||
| - | ==== Method references ==== | + | ==== Method References ==== |
| - | And last but not least, thanks to the new capabilities of Java 1.8, we can also use [[https://docs.oracle.com/javase/tutorial/java/javaOO/methodreferences.html|method references]]: | + | Lastly, thanks to the new capabilities of Java 1.8, we can also use [[https://docs.oracle.com/javase/tutorial/java/javaOO/methodreferences.html|method references]]: |
| <code java> | <code java> | ||