Re: Design Patterns
dougmmika@gmail.com writes:
When I write EventListeners I write them in seperate classes
(and seperate files) for reasons of clearity.
This expresses the underlying assumption that writing them
in separate classes and files is more clear. I am not so
sure about this!
But these event listeners I want to modify other classes that
aren't defined in the EventListeners.
In Java SE, you usually do not modify classes at runtime.
The problem I have is how best to get these eventlisteners to
know of these classes (which are also in seperate files)?
Well, by ?class?, I assume, you mean reference values
(vulgo: objects).
Usually, this results from the OOD, for example:
- you can give static or non-static idenfiers or getter
methods public visibility (which you do not seem to like)
- you can pass the references when creating the instances
(as arguments of the instance creating expressions)
- you can insert them later via setters or
dependency injection
- or you an write the event listeners as inner
classes of the classes they need to access
(which you also do not seem to like, but which
I like)
You might look up Swing code from Oracles Java examples
and tutorials and see how those things are solved there.
You might read the book Applying UML and Patterns by Craig
Larman.