Article Preview
Buy Now
| PDF: |
Feature
Article
Issue: 7.5 (July/August 2009)
Author: Thomas Tempelmann
(Revised by Marc Zeedar)
Article Description: No description available.
Article Length (in bytes): 14,230
Starting Page Number: 27
RBD Number: 7511
Resource File(s):
7511 project.zip Updated: Wednesday, July 1, 2009 at 1:23 PM
Related Web Link(s):
http://www.tempel.org/PluginArchitectureWithREALbasic
http://www.tempel.org/ftp/pub/REALbasic/EventDrivenScript.zip
http://www.tempel.org/ftp/pub/REALbasic/RbScript_201.pdf
Known Limitations: None
Excerpt of article text...
This article will give some ideas on how to use REALbasic's RBScript feature to add plugins to a REALbasic application. A plugin is hereby defined as a program that can be added to the already-built application and executed at the app's discretion.
An example
In the next paragraphs I will suggest some ideas based on the following example: design for a search app similar to Apple's "Spotlight" feature.
The app shall be a tool to search for text in many files. While the app has hard-coded routines to search for text in a single file, it wants to allow plugins to convert binary files into text files where appropriate. Imagine documents from applications such as Word (.doc), Acrobat (.pdf), and even REALbasic (.rbp), which, when opened in a plain text editor, show a lot of gibberish that you don't want to have searched. Instead, you want it all readable.
Hence, the plugins for this search app will basically function like this: the app will pass each file (before looking at it) to the plugins so that the plugins can convert the file to text if necessary. Each plugin gets to look at the file and decide whether it can understand it. If it can, it returns the readable text, which the app then searches for the contents the user wants to find.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.
|
