Re: [flexcoders] namespace/directory structure issue
Ok guys, so w/ Brian's suggestion I was able to get the compiler to
recognize the namespaces w/o changing the initial structure. I'm more
than halfway there, but I still get some issues w/ image locations.
Several components have embedded images that are located in an
assets directory one level below the main directory. So, for
example, one component contains a Link w/
icon=@Embed('assets/logo.swf'). This compiles fine for the main
app.mxml, but I get a resource not found error when trying to hit
one of the test apps. Do I have to create a variable at the app level
that prepends a prefix like ../../ for test apps and a blank string
for the main level app? Is there a better way to handle this, maybe a
default image root property?
Thanks,
Jaime
On 7/31/05, Brian Deitte [EMAIL PROTECTED] wrote:
I think what Matt was saying is having the components directory a level
deeper and then referencing this directory in actionscript-classpath in
flex-config.xml. You should be able to create references to components in
any directory you put in actionscript-classpath in the same manner that you
reference components in a subdirectory of the main application. I don't
think you necessarily need to move the components directory though- I think
it would also work to just put the main directory in actionscript-classpath.
-Brian
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jaime
Bermudez
Sent: Sunday, July 31, 2005 11:17 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] namespace/directory structure issue
Ok, so I think what you're suggesting is to restructure to something
like the following:
main
as
components
UI
test
test1
components
comp1
test2
components
comp2
If so, that kind of ruins my approach of dynamically adding components
to a Container in each testXmxml. I wanted to follow the approach
of having each test1...testN directory define a Components.as file
that lists the component references from the components directory that
will be added to the Container - that way I could share an appTest.as
file across each testXmxml declaration.
In any case, there is still the question of code changes and
check-ins. How would I keep comp1, for example, in synch w/ comp1 in
the main branch? Is there a way to make the components directories
under each testN directory a pointer to the main components directory?
Thanks,
Jaime
On 7/30/05, Matt Chotin [EMAIL PROTECTED] wrote:
I think what you're gonna need to do is create a different root directory
and then add it to your classpath in flex-config.xml. Put all the
components in that directory (create whatever subdirectories you desire).
Since you have the test directory it cannot easily refer to components in a
parallel directory unless the main MXML file is in main.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Jaime Bermudez
Sent: Saturday, July 30, 2005 5:23 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] namespace/directory structure issue
Hi Flexcoders,
I am working on a rather large FLEX app w/ a directory structure that
looks like this:
main
as
components
UI
...
test
test1
the main directory contains the project's app.mxml, which has custom
namespace declarations like xmlns:cc = components.UI.*, etc. That
works just fine b/c the components and as directories are below the
app directory.
Because of the size of the app, I created the test directory above,
which I hope will contain subdirectories of test applications to make
development compilation quicker (i.e. app.mxml may have 20 components
from the components directory, but test1.mxml will have just 1).
The reason I created a test directory is so that it can be easily
excluded from a production build. Anyway, in each testX.mxml file,
I need to be able to refer to components in the components directory
in an Application tag. Is there an easy way I can do this w/o having
to make SWC files? Note that the components directory is often
updated, so having to compile a SWC is not ideal.
Thanks,
Jaime
--
Flexcoders Mailing List
FAQ:
http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives:
http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Computer software testing Macromedia flex Development
Software developer
YAHOO! GROUPS LINKS
Visit your group flexcoders on the web.
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
Re: [flexcoders] namespace/directory structure issue
Still waiting for ideas on an approach, but I thought I'd set up the
problem a little better:
Here's the developer directory structure for my project:
main
app.mxml
as
app.as
appTest.as
assets (images, etc.)
components
test
test1
test1.mxml
as
Components.as
test2
test2.mxml
as
Components.as
I added the following path-element to the actionscript-classpath in
flex-config.xml:
path-element/main/path-element so I can use the same namespace
declarations in test1.mxml as I use in app.mxml. I reference
appTest.as in a Script block as Script source=../../as/appTest.as.
The appTest.as refers to the Components class, which I import in each
testX.mxml file.
The problem I'm seeing is that a handful of components have embedded
image files that are referenced in a source or icon parameter as
assets/image.xxx. I'm pretty sure that these are all paths relative
to the location of the app file being called, so the references are
only being found for app.mxml. Is my only and best option to define
some image root variable at the app level that I can prepend to each
image call (thereby forcing me to check-out and change every class
that embeds images)? Is there a standard approach to this problem?
Thanks.
On 8/1/05, Jaime Bermudez [EMAIL PROTECTED] wrote:
Ok guys, so w/ Brian's suggestion I was able to get the compiler to
recognize the namespaces w/o changing the initial structure. I'm more
than halfway there, but I still get some issues w/ image locations.
Several components have embedded images that are located in an
assets directory one level below the main directory. So, for
example, one component contains a Link w/
icon=@Embed('assets/logo.swf'). This compiles fine for the main
app.mxml, but I get a resource not found error when trying to hit
one of the test apps. Do I have to create a variable at the app level
that prepends a prefix like ../../ for test apps and a blank string
for the main level app? Is there a better way to handle this, maybe a
default image root property?
Thanks,
Jaime
On 7/31/05, Brian Deitte [EMAIL PROTECTED] wrote:
I think what Matt was saying is having the components directory a level
deeper and then referencing this directory in actionscript-classpath in
flex-config.xml. You should be able to create references to components in
any directory you put in actionscript-classpath in the same manner that you
reference components in a subdirectory of the main application. I don't
think you necessarily need to move the components directory though- I think
it would also work to just put the main directory in
actionscript-classpath. -Brian
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of
Jaime Bermudez
Sent: Sunday, July 31, 2005 11:17 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] namespace/directory structure issue
Ok, so I think what you're suggesting is to restructure to something
like the following:
main
as
components
UI
test
test1
components
comp1
test2
components
comp2
If so, that kind of ruins my approach of dynamically adding components
to a Container in each testXmxml. I wanted to follow the approach
of having each test1...testN directory define a Components.as file
that lists the component references from the components directory that
will be added to the Container - that way I could share an appTest.as
file across each testXmxml declaration.
In any case, there is still the question of code changes and
check-ins. How would I keep comp1, for example, in synch w/ comp1 in
the main branch? Is there a way to make the components directories
under each testN directory a pointer to the main components directory?
Thanks,
Jaime
On 7/30/05, Matt Chotin [EMAIL PROTECTED] wrote:
I think what you're gonna need to do is create a different root directory
and then add it to your classpath in flex-config.xml. Put all the
components in that directory (create whatever subdirectories you desire).
Since you have the test directory it cannot easily refer to components in
a
parallel directory unless the main MXML file is in main.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Jaime Bermudez
Sent: Saturday, July 30, 2005 5:23 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] namespace/directory structure issue
Hi Flexcoders,
I am working on a rather large FLEX app w/ a directory structure that
looks like this:
main
as
components
UI
...
test
test1
the main directory contains the project's app.mxml, which has custom
namespace
RE: [flexcoders] namespace/directory structure issue
Sorry, the image embedding is going to be
relative from the main file. You MIGHT be able to do /assets (starting slash)
but we do not have a search path for image locations I think.
From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Jaime Bermudez
Sent: Monday, August 01, 2005 8:58
AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders]
namespace/directory structure issue
Still waiting for ideas on an
approach, but I thought I'd set up the
problem a little better:
Here's the developer directory structure for my
project:
main
app.mxml
as
app.as
appTest.as
assets (images, etc.)
components
test
test1
test1.mxml
as
Components.as
test2
test2.mxml
as
Components.as
I added the following path-element to the
actionscript-classpath in
flex-config.xml:
path-element/main/path-element so
I can use the same namespace
declarations in test1.mxml as I use in
app.mxml. I reference
appTest.as in a Script block as Script
source=../../as/appTest.as.
The appTest.as refers to the Components class,
which I import in each
testX.mxml file.
The problem I'm seeing is that a handful of
components have embedded
image files that are referenced in a source or
icon parameter as
assets/image.xxx. I'm pretty
sure that these are all paths relative
to the location of the app file being called, so
the references are
only being found for app.mxml. Is my only
and best option to define
some image root variable at the app level that I
can prepend to each
image call (thereby forcing me to check-out and
change every class
that embeds images)? Is there a standard
approach to this problem?
Thanks.
On 8/1/05, Jaime Bermudez
[EMAIL PROTECTED] wrote:
Ok guys, so w/ Brian's suggestion I was able
to get the compiler to
recognize the namespaces w/o changing the
initial structure. I'm more
than halfway there, but I still get some
issues w/ image locations.
Several components have embedded images that
are located in an
assets directory one level below
the main directory. So, for
example, one component contains a Link w/
icon=@Embed('assets/logo.swf'). This compiles fine for the
main
app.mxml, but I get a resource not
found error when trying to hit
one of the test apps. Do I have to
create a variable at the app level
that prepends a prefix like ../../
for test apps and a blank string
for the main level app? Is there a
better way to handle this, maybe a
default image root property?
Thanks,
Jaime
On 7/31/05, Brian
Deitte [EMAIL PROTECTED] wrote:
I think what Matt was saying is having
the components directory a level deeper and then referencing this directory in
actionscript-classpath in flex-config.xml. You should be able to create
references to components in any directory you put in actionscript-classpath in
the same manner that you reference components in a subdirectory of the main
application. I don't think you necessarily need to move the components
directory though- I think it would also work to just put the main directory in
actionscript-classpath. -Brian
-Original Message-
From: flexcoders@yahoogroups.com
[mailto:flexcoders@yahoogroups.com]
On Behalf Of Jaime Bermudez
Sent: Sunday, July 31, 2005 11:17 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders]
namespace/directory structure issue
Ok, so I think what you're suggesting is
to restructure to something
like the following:
main
as
components
UI
test
test1
components
comp1
test2
components
comp2
If so, that kind of ruins my approach of
dynamically adding components
to a Container in each
testXmxml. I wanted to follow the approach
of having each test1...testN directory define
a Components.as file
that lists the component references from
the components directory that
will be added to the Container - that
way I could share an appTest.as
file across each testXmxml
declaration.
In any case, there is still the question
of code changes and
check-ins. How would I keep comp1,
for example, in synch w/ comp1 in
the main branch? Is there a way to
make the components directories
under each testN directory a pointer to
the main components directory?
Thanks,
Jaime
On 7/30/05, Matt Chotin
[EMAIL PROTECTED] wrote:
I think what you're gonna need to
do is create a different root directory
and then add it to your classpath
in flex-config.xml. Put all the
components in that directory
(create whatever subdirectories you desire).
Since you have the test directory
it cannot easily refer to components in a
parallel directory unless the main
MXML file is in main.
From: flexcoders@yahoogroups.com
[mailto:flexcoders@yahoogroups.com]
On
Behalf Of Jaime Bermudez
Sent: Saturday, July 30, 2005
5:23 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders]
namespace/directory structure issue
Hi Flexcoders,
I am working on a rather
RE: [flexcoders] namespace/directory structure issue
I think what Matt was saying is having the components directory a level deeper and then referencing this directory in actionscript-classpath in flex-config.xml. You should be able to create references to components in any directory you put in actionscript-classpath in the same manner that you reference components in a subdirectory of the main application. I don't think you necessarily need to move the components directory though- I think it would also work to just put the main directory in actionscript-classpath. -Brian -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jaime Bermudez Sent: Sunday, July 31, 2005 11:17 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] namespace/directory structure issue Ok, so I think what you're suggesting is to restructure to something like the following: main as components UI test test1 components comp1 test2 components comp2 If so, that kind of ruins my approach of dynamically adding components to a Container in each testXmxml. I wanted to follow the approach of having each test1...testN directory define a Components.as file that lists the component references from the components directory that will be added to the Container - that way I could share an appTest.as file across each testXmxml declaration. In any case, there is still the question of code changes and check-ins. How would I keep comp1, for example, in synch w/ comp1 in the main branch? Is there a way to make the components directories under each testN directory a pointer to the main components directory? Thanks, Jaime On 7/30/05, Matt Chotin [EMAIL PROTECTED] wrote: I think what you're gonna need to do is create a different root directory and then add it to your classpath in flex-config.xml. Put all the components in that directory (create whatever subdirectories you desire). Since you have the test directory it cannot easily refer to components in a parallel directory unless the main MXML file is in main. From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jaime Bermudez Sent: Saturday, July 30, 2005 5:23 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] namespace/directory structure issue Hi Flexcoders, I am working on a rather large FLEX app w/ a directory structure that looks like this: main as components UI ... test test1 the main directory contains the project's app.mxml, which has custom namespace declarations like xmlns:cc = components.UI.*, etc. That works just fine b/c the components and as directories are below the app directory. Because of the size of the app, I created the test directory above, which I hope will contain subdirectories of test applications to make development compilation quicker (i.e. app.mxml may have 20 components from the components directory, but test1.mxml will have just 1). The reason I created a test directory is so that it can be easily excluded from a production build. Anyway, in each testX.mxml file, I need to be able to refer to components in the components directory in an Application tag. Is there an easy way I can do this w/o having to make SWC files? Note that the components directory is often updated, so having to compile a SWC is not ideal. Thanks, Jaime -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Computer software testing Macromedia flex Development Software developer YAHOO! GROUPS LINKS Visit your group flexcoders on the web. To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links Yahoo! Groups Sponsor ~-- font face=arial size=-1a href=http://us.ard.yahoo.com/SIG=12hhdgth4/M=362335.6886445.7839731.1510227/D=groups/S=1705007207:TM/Y=YAHOO/EXP=1122842173/A=2894361/R=0/SIG=13jmebhbo/*http://www.networkforgood.org/topics/education/digitaldivide/?source=YAHOOcmpgn=GRPRTP=http://groups.yahoo.com/;In low income neighborhoods, 84% do not own computers. At Network for Good, help bridge the Digital Divide!/a./font ~- -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail
RE: [flexcoders] namespace/directory structure issue
I think what youre gonna need to do is create a different root directory and then add it to your classpath in flex-config.xml. Put all the components in that directory (create whatever subdirectories you desire). Since you have the test directory it cannot easily refer to components in a parallel directory unless the main MXML file is in main. From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jaime Bermudez Sent: Saturday, July 30, 2005 5:23 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] namespace/directory structure issue Hi Flexcoders, I am working on a rather large FLEX app w/ a directory structure that looks like this: main as components UI ... test test1 the main directory contains the project's app.mxml, which has custom namespace declarations like xmlns:cc = components.UI.*, etc. That works just fine b/c the components and as directories are below the app directory. Because of the size of the app, I created the test directory above, which I hope will contain subdirectories of test applications to make development compilation quicker (i.e. app.mxml may have 20 components from the components directory, but test1.mxml will have just 1). The reason I created a test directory is so that it can be easily excluded from a production build. Anyway, in each testX.mxml file, I need to be able to refer to components in the components directory in an Application tag. Is there an easy way I can do this w/o having to make SWC files? Note that the components directory is often updated, so having to compile a SWC is not ideal. Thanks, Jaime -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Computer software testing Macromedia flex Development Software developer YAHOO! GROUPS LINKS Visit your group "flexcoders" on the web. To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
