Am 18.02.2007 um 16:02 schrieb Tim Jones:
On Feb 18, 2007, at 4:55 AM, Stefan wrote:
What's the point? That the .Net framework is as big as a big RB app?
Don't understand, since you need to download the framework only once.
And this is something that we've needed in the RB world - a way to
deliver a generic RB framework that can be installed and made
available to all RB apps. While the total of an RB app would still
be as large as it is, what the customer sees in a download will be
much smaller on an application instance. I took a look at one of
my Mach-O UB RB tools and found that if the framework was globally
placed and published on the system, the resulting download from the
user perspective would be 7.5MB instead of 13MB (MBS and rbframework).
So, while the RB frameworks only add between 5.7MB and 10MB to each
app (unlike .NET's 20MB+), we wouldn't be populating users' systems
with potentially hundreds of copies of rbframework.dylib (at the
least).
Are all copies of the rbframework.dylib different?
If so, the question comes to mind, if we could build an RB app, which
forces RB to
generate a VERY big rbframework.dylib, which includes all code of all
RB framework parts.
Then we could deploy this one once and remove each instance of
rbframework.dylib from each
compiled app. In case RB uses OS X' default dylib resolve pathes.
Well, this is a workaround only. I'd prepare RS to provide such a
rbframework.dylib
instance.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
