Using RB's late binding [soft declares], you could prepare e.g. a
Cocoa framework
and call functions of the framework.
With a bit extra work, you might prepare a wrapper, which allows to
call any function
of a Cococa framework [I'd call it a plugin] though certain
intermediate function.
If you speak of RB itself, a GUI app and several console apps might
be of help.
If console apps support networking - don't know if - you might use
sockets
to communicate between your master and the 'client plugin apps‘.
Although this
model wouldn't be suitable for any kind of app, the approach might be
of for
certain app types.
Am 25.05.2006 um 00:30 schrieb Deane Venske:
Hi Guys,
Just wondering, is there a way to modularize your code in order to
bring file sizes down? I'm thinking something like a parent app
containing the realbasic framework that then calls smaller compiled
apps that contain the compiled code for each module which can then
in turn call other modules etc. Would just be a very nice way of
keeping update sizes down. I do this with director, where my main
projector is just a shell and immediately calls the first (login/
menu) module when it opens. To give you an idea director projectors
are around 2.5mb min, and my dcrs (Compiled code) are between 20k
and 250k.
Is there any other methods that people use to do this?
Regards,
Deane
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
