Hey Dimitrios,
I have tried using the 'compc' compiler that ships
with Flex2, but I
am still getting an SWC for cairngorm that's around 350k.
Using the
'compc' compiler, the syntax is a little different from your
file's
but I think it's all correct. I have noticed two
differences:
1. you include '${SDK_LIB}/fds.swc' which I'm
assuming is Flex Data
Services. I don't have that swc on my system, however
I do have
rpc.swc, which my library will not compile without.
2 you
use a config file
<arg
value="-load-config+=${basedir}/cairngorm2-config.xml"/>
which I also
can not find anywhere in the Cairngorm package I downloaded
from Adobe
labs. Is this a file you have created to exclude certain
classes?
Derrick
--- In [EMAIL PROTECTED]ups.com,
"Dimitrios Gianninas"
<dimitrios.giannina[EMAIL PROTECTED]>
wrote:
>
>
> Now that I am back in the office, here is the
full ant command we
use to compile cairngorm and exclude all unneccesary
libraries:
>
> <exec executable="${FLEX2_COMPC}"
> dir="${BUILD}"
> vmlauncher="false"
>
failonerror="true">
> <arg
value="-load-config+=${basedir}/cairngorm2-config.xml"/>
>
<arg value="-source-path=${SRC}"/>
>
<arg
value="-external-library-path+=${SDK_LIB}/playerglobal.swc,${SDK_LIB}/framework.swc,${SDK_LIB}/fds.swc"/>
>
<arg value="-output=cairngorm.swc" />
> </exec>
>
>
> Dimitrios Gianninas
> RIA Developer
>
Optimal Payments Inc.
>
> -----Original Message-----
>
From: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
Behalf Of Dimitrios Gianninas
> Sent: Tuesday, September 19, 2006 6:26
PM
> To: [EMAIL PROTECTED]ups.com
>
Subject: RE: [flexcoders] Architecting a large, modular Flex
application
>
> Hi,
>
> I think you have setup
things pretty much the same way I would.
Although I have never gone that
far... yet :)
>
> One thing I did notice which you can change is
that you said the
entire flex framework gets included in the cairngorm.swc
... doesn't
have to be. I build the carngorm.swc using the command-line
compiler
and made sure to exclude the framework.swc, this did reduce the
size
and is basically what I think you want to do. Don't remember the
exact
switch, will have to get that to you tomorrow once I'm back in the
office.
>
> Regards,
>
> Dimitrios Gianninas
>
Optimal Payments Inc.
>
>
> -----Original
Message-----
> From: [EMAIL PROTECTED]ups.com
on behalf of derrickgrigg
> Sent: Tue 9/19/2006 11:23 AM
> To: [EMAIL PROTECTED]ups.com
>
Subject: [flexcoders] Architecting a large, modular Flex application
>
> I just want to bounce this idea/concept off the larger
Flex
community to see if there are any holes or possibly better
solutions.
>
> I am currently working with a team of developers
on a large, modular
Flex application based on the Cairngorm framework. One
issue that we
are trying to get our heads around is creating the
application in a
modular fashion (ie seperate SWFs for application
modules). Each
module will only get loaded as needed by the main shell
application in
order to keep the overall size and memory use as small as
possible.
>
> The big issue that we are running into is how to
setup and develop
the module flex projects in Flex Builder. We need to give
the module
projects access to the models, value objects etc (especially
bindable
> properties) that they need from the main application without
having
the actual application implemented version of those classes
get
compiled into the module swfs and causing problems when they
get
loaded into the main application. Our current thinking is that
in
order to allow the modules to have full access to the models,
value
objects, etc that have been defined in the main application we
create
Abstract versions of those classes and put them in a seperate
flex
library project which will get compiled as an SWC and get
included
into the seperate modules as a runtime shared library (RSL),
basically
an library of Abstract classes only (and maybe some Interfaces).
The
module projects will also include the Cairngorm.swc as an RSL in
order
to have access to the interfaces etc that are defined there
and
provide the neccessary hooks into the main application.
>
> The main application will have all of it's models, value objects
etc
extend the abstract classes that are defined in the Abstract
RSL
library. The main application will also use the cairngorm.swc as
an
RSL to ensure that the module swfs load properly when called upon
(ie
they won't throw a run time shared library error because they
can't
find the cairngorm.swc). This results in a download hit because
the
entire flex framework gets downloaded in the cairngorm.swc but we
do
not see any way around that.
>
> Any feedback, comments,
etc from any of you would be greatly
appreciated.
>
>
Regards,
>
> Derrick
>
>
>
>
>
>
>
> --
> WARNING
> -------
> This
electronic message and its attachments may contain
confidential,
proprietary or legally privileged information, which is
solely for the use
of the intended recipient. No privilege or other
rights are waived by any
unintended transmission or unauthorized
retransmission of this message. If
you are not the intended recipient
of this message, or if you have received
it in error, you should
immediately stop reading this message and delete it
and all
attachments from your system. The reading, distribution, copying
or
other use of this message or its attachments by unintended
recipients
is unauthorized and may be unlawful. If you have received this
e-mail
in error, please notify the sender.
>
> AVIS
IMPORTANT
> --------------
> Ce message électronique et ses
pièces jointes peuvent contenir des
renseignements confidentiels, exclusifs
ou légalement privilégiés
destinés au seul usage du destinataire visé.
L'expéditeur original ne
renonce à aucun privilège ou à aucun autre droit
si le présent message
a été transmis involontairement ou s'il est
retransmis sans son
autorisation. Si vous n'êtes pas le destinataire visé
du présent
message ou si vous l'avez reçu par erreur, veuillez
cesser
immédiatement de le lire et le supprimer, ainsi que toutes ses
pièces
jointes, de votre système. La lecture, la distribution, la copie
ou
tout autre usage du présent message ou de ses pièces jointes par
des
personnes autres que le destinataire visé ne sont pas autorisés
et
pourraient être illégaux. Si vous avez reçu ce courrier
électronique
par erreur, veuillez en aviser
l'expéditeur.
>
