Article Preview
Buy Now
| PDF: |
Inside REALbasic
Runtime vs. Internal Plugins vs. Code
How the framework is implemented
Issue: 6.6 (September/October 2008)
Author: Christian Schmitz
Article Description: No description available.
Article Length (in bytes): 4,932
Starting Page Number: 52
RBD Number: 6619
Resource File(s): None
Related Link(s): None
Known Limitations: None
Excerpt of article text...
Every REALbasic application uses the runtime framework. Depending on what your application does, different parts are compiled into your application.
There are three cases for framework code: The runtime library, Internal Plugins, and functionality written in REALbasic source code.
In the following code all sizes are specified for REALbasic 2008r1 and Mac OS X universal targets. Those values may change for a future version.
Runtime Library
First there is code which all REALbasic applications include. This is a library written in C which contains the basic functions like the string handling or the application class. The runtime library for Mac OS X universal is 5.6 MB in size and basically defines the minimum size of a REALbasic universal application on Mac OS X.
As this runtime library is written in C, it uses the C runtime library and gets optimizations from the C compiler used.
Internal Plugins
Second, there are internal plugins. Those plugins are added to the application and are written in C. Over time REALsoftware created more and more of these internal plugins to keep the runtime library growing at a slower rate. If you don't use the methods or classes they implement, the code won't be compiled into your application. REALbasic currently contains 16 internal plugins:
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.
|
