Modules, play nice
31 October 2008, 08:30 by Chad Reynoldson
What do I mean by play nice? It is simply the fact that modules must be developed with a consideration of integration with a larger system full of multiplicity and complexity.
First off, you begin a module as usual, viewing it as an individual component. There will be a core implementation that is generally un-changed, things like transport controls, list controls, etc that tightly bind the GUI with the 3rd party device.
This second part is often overlooked by module developers and this is the play nice area. You must consider how this individual component will work in a larger context. Generally this play nice area is isolated in the GUI implementation. Here are some questions to ask when developing the GUI:
- In the context of GUI code:
- Have you implemented a code mechanism to connect and disconnect this device from any single GUI?
- Have you limited the amount of ONLINE traffic required to sync up a GUI?
- Do you keep a cache for variable text and only update it when you detect changes?
- Have you optimized the feedback?
- In the context of GUI design:
- Does your GUI implement a standard layout design?
- Have you named your pages and popups with a unique pre-text identifier (i.e. [max]Playlist)?
- Have you grouped your popups?
- Do you utilize basic touch panel functionality (channel codes, variable text fields, levels) and avoid complex internal touch panel functionality?
- Do you use standard fonts, graphics, and icons?
- Will your GUI be easily copy/pasted into a larger touch panel file (ignoring the graphic changes required)?
Comments
Comments are turned off for this article.