Using the Gofer Pattern
Issue: 8.6 (September/October 2010)
Author: Jens Bendig jens.bendig-at-void.de
Article Description: No description available.
Article Length (in bytes): 15,248
Starting Page Number: 29
RBD Number: 8607
Resource File(s): None
Related Link(s): None
Known Limitations: None
Excerpt of article text...
What I call "everyday" programming can lead to serious confusion. As a small application grows, it gets more and more windows and you need control between those windows to manage the overall workflow. You need to keep the overview without being distracted by tiny details. That's easy... if you have a focus on this right from the beginning!
How do you solve the issue where you have a window open and then you need to open another window for user input, and then you re-open the first window? Do the windows call each other to perform the overall task? Do we need some kind of "window controller" to have the correct window open at the right time? And what if the first window has some data thatpersists that has been edited within the second window -- and we learn that this data should not have been saved? This is what I mean when I say "everyday" programming. Sooner or later, problems like this come up within a growing application, especially if you are coding for a company's workflows.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.