RE: [flexcoders] Re: Flex Project Struture
That sounds like a good path to follow -- especially if you set up automated ANT builds for your flex library project, perhaps once or twice a day. That way, any apps consuming the library will always be referencing a current build. This could result in runtime errors for older projects though if you begin changing the interfaces for the components contained in the library. At that point you could try checking out the flex library project from the SVN, building, and then linking the flex library project to your main flex project. This should allow you to have a snapshot of the library that you know will work with the flex project at that point in time. HTH, Ryan From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Howard Fore Sent: Wednesday, September 17, 2008 1:05 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Flex Project Struture Have you tried making a linked folder in the src directory? File New Folder Advanced Link to Folder in file system. This creates an alias in your project to that folder. Haven't tried it myself, not sure how the compiler is going to like it. The other option would be to put the alias in the operating system, using junctions in Windows or aliases/symlinks in OS X/Linux. I would expect the compiler to have no issues with those as the operating system should make them appear as real directories to the program. On Wed, Sep 17, 2008 at 3:51 PM, flexaustin [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: What about sharing components. For instance, we have a project just completed with several as components. We want to use some of those same AS components, but don't want to copy them to our new projects directory since when changes are made in the AS components for the old project we need them to show up in our new project. So we want to point to the same library or folder for both applications. -- Howard Fore, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] The universe tends toward maximum irony. Don't push it. - Jeff Atwood This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
RE: [flexcoders] Re: Flex Project Struture
If you are using Subclipse in Flex Builder, it does a pretty good job of automatically leaving out said files. Here are some for example in a standard Flex Project folder: * .settings folder * .actionScriptProperties * .flexProperties * .project HTH, Ryan From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of flexaustin Sent: Tuesday, September 16, 2008 8:25 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Flex Project Struture Thanks Ryan. You mentioned Flex Builders specific files...what would those be? --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com , Ryan Graham [EMAIL PROTECTED] wrote: If you're using a framework like Cairngorm or Cairngorm with Extensions, there are already recommended project structures. If you aren't using an existing framework, then everyone will have to be on the same page with the dev methodologies and conventions that you all have agreed upon as a team. There should be no issues using a flex project with your given setup, but it may be worth noting that you may want to stay away from including any flex builder specific files in the SVN, as everyone has their own dev environment setup the way they like it as far as workspaces and such are concerned, and that leaves the project open to developers who may be using the sdk and command line to compile by reducing flex builder dependencies. Aside from that, I'd say it's good to keep all your view components and sealed classes for your model together (minimally), and any external or embedded assets in a separate folder defined as an additional source folder so they will still get copied to the bin when building. All this could of course be accomplished through ANT though if you want to go that route. Brief example: etc --assets --config src --components --view --model ... The possibilities are really endless, but as long as everyone agrees on the project structure, you shouldn't have any problems. This is where existing frameworks can help take the headache out of things -- by providing a known structure up front. HTH, Ryan From: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com [mailto:flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com ] On Behalf Of flexaustin Sent: Tuesday, September 16, 2008 4:11 PM To: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com Subject: [flexcoders] Flex Project Struture Can anyone recommend a project structure? Maybe a tut or blog post on the topic? We have several components (as and mxml) that we want to use throughout several projects and by several team members, but not sure the best way to structure the files and package them up. How do we all share the files? Is a Flex Project the best way? We are using subversion + Flex 3 + Ant. Would like to build an Ant task that fetches all the files and builds the structure once we establish what that structure should be. Thanks in advance. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
[flexcoders] Re: Flex Project Struture
What about sharing components. For instance, we have a project just completed with several as components. We want to use some of those same AS components, but don't want to copy them to our new projects directory since when changes are made in the AS components for the old project we need them to show up in our new project. So we want to point to the same library or folder for both applications. --- In flexcoders@yahoogroups.com, Ryan Graham [EMAIL PROTECTED] wrote: If you are using Subclipse in Flex Builder, it does a pretty good job of automatically leaving out said files. Here are some for example in a standard Flex Project folder: * .settings folder * .actionScriptProperties * .flexProperties * .project HTH, Ryan From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of flexaustin Sent: Tuesday, September 16, 2008 8:25 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Flex Project Struture Thanks Ryan. You mentioned Flex Builders specific files...what would those be? --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com , Ryan Graham Ryan.Graham@ wrote: If you're using a framework like Cairngorm or Cairngorm with Extensions, there are already recommended project structures. If you aren't using an existing framework, then everyone will have to be on the same page with the dev methodologies and conventions that you all have agreed upon as a team. There should be no issues using a flex project with your given setup, but it may be worth noting that you may want to stay away from including any flex builder specific files in the SVN, as everyone has their own dev environment setup the way they like it as far as workspaces and such are concerned, and that leaves the project open to developers who may be using the sdk and command line to compile by reducing flex builder dependencies. Aside from that, I'd say it's good to keep all your view components and sealed classes for your model together (minimally), and any external or embedded assets in a separate folder defined as an additional source folder so they will still get copied to the bin when building. All this could of course be accomplished through ANT though if you want to go that route. Brief example: etc --assets --config src --components --view --model ... The possibilities are really endless, but as long as everyone agrees on the project structure, you shouldn't have any problems. This is where existing frameworks can help take the headache out of things -- by providing a known structure up front. HTH, Ryan From: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com [mailto:flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com ] On Behalf Of flexaustin Sent: Tuesday, September 16, 2008 4:11 PM To: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com Subject: [flexcoders] Flex Project Struture Can anyone recommend a project structure? Maybe a tut or blog post on the topic? We have several components (as and mxml) that we want to use throughout several projects and by several team members, but not sure the best way to structure the files and package them up. How do we all share the files? Is a Flex Project the best way? We are using subversion + Flex 3 + Ant. Would like to build an Ant task that fetches all the files and builds the structure once we establish what that structure should be. Thanks in advance. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
Re: [flexcoders] Re: Flex Project Struture
Have you tried making a linked folder in the src directory? File New Folder Advanced Link to Folder in file system. This creates an alias in your project to that folder. Haven't tried it myself, not sure how the compiler is going to like it. The other option would be to put the alias in the operating system, using junctions in Windows or aliases/symlinks in OS X/Linux. I would expect the compiler to have no issues with those as the operating system should make them appear as real directories to the program. On Wed, Sep 17, 2008 at 3:51 PM, flexaustin [EMAIL PROTECTED] wrote: What about sharing components. For instance, we have a project just completed with several as components. We want to use some of those same AS components, but don't want to copy them to our new projects directory since when changes are made in the AS components for the old project we need them to show up in our new project. So we want to point to the same library or folder for both applications. -- Howard Fore, [EMAIL PROTECTED] The universe tends toward maximum irony. Don't push it. - Jeff Atwood
[flexcoders] Re: Flex Project Struture
My thought exactly. Guess I will give it whirl. THanks! --- In flexcoders@yahoogroups.com, Howard Fore [EMAIL PROTECTED] wrote: Have you tried making a linked folder in the src directory? File New Folder Advanced Link to Folder in file system. This creates an alias in your project to that folder. Haven't tried it myself, not sure how the compiler is going to like it. The other option would be to put the alias in the operating system, using junctions in Windows or aliases/symlinks in OS X/Linux. I would expect the compiler to have no issues with those as the operating system should make them appear as real directories to the program. On Wed, Sep 17, 2008 at 3:51 PM, flexaustin [EMAIL PROTECTED] wrote: What about sharing components. For instance, we have a project just completed with several as components. We want to use some of those same AS components, but don't want to copy them to our new projects directory since when changes are made in the AS components for the old project we need them to show up in our new project. So we want to point to the same library or folder for both applications. -- Howard Fore, [EMAIL PROTECTED] The universe tends toward maximum irony. Don't push it. - Jeff Atwood
Re: [flexcoders] Re: Flex Project Struture
these .files suck for distributed teams though, unless you force all your devs to use the same exact resource setup, something I'm loathed to here any manager tell me :) use svn:ignore to ignore files and not include them in your SVN repos. In Subclipse, right click the file or dir and choose Team add to svn:ignore. Of course you can't have already added this file or dir to SVN. If you have already added it and want to pull it out and ignore it, you can copy it elsewhere, delete, commit, copy back, then ignore it. One trick I picked up recently from a co-worker was to rename these files and add them to SVN, this way they can be used as templates. eg rename .actionScriptProperties to .actionscriptProperties_Template. DK On Wed, Sep 17, 2008 at 7:03 PM, Josh McDonald [EMAIL PROTECTED] wrote: FWIW, I usually include .actionscriptPropertis in SVN, as it holds compiler flags that are often required to build. -J On Thu, Sep 18, 2008 at 8:05 AM, flexaustin [EMAIL PROTECTED] wrote: My thought exactly. Guess I will give it whirl. THanks! --- In flexcoders@yahoogroups.com, Howard Fore [EMAIL PROTECTED] wrote: Have you tried making a linked folder in the src directory? File New Folder Advanced Link to Folder in file system. This creates an alias in your project to that folder. Haven't tried it myself, not sure how the compiler is going to like it. The other option would be to put the alias in the operating system, using junctions in Windows or aliases/symlinks in OS X/Linux. I would expect the compiler to have no issues with those as the operating system should make them appear as real directories to the program. On Wed, Sep 17, 2008 at 3:51 PM, flexaustin [EMAIL PROTECTED] wrote: What about sharing components. For instance, we have a project just completed with several as components. We want to use some of those same AS components, but don't want to copy them to our new projects directory since when changes are made in the AS components for the old project we need them to show up in our new project. So we want to point to the same library or folder for both applications. -- Howard Fore, [EMAIL PROTECTED] The universe tends toward maximum irony. Don't push it. - Jeff Atwood -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. http://flex.joshmcdonald.info/ :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it?
Re: [flexcoders] Re: Flex Project Struture
Yeah that trick's not bad, that's what we're doing for build.properties etc. I find in *most* cases there's nothing system-specific in our .actionscriptProperties (mainly defines and keep-as3-metadata, etc), so we get away with it :) What isn't any fun, is that there's *something*, *somewhere* that will cause Player/Builder to not put your app into the priviledged list if you copy or import too much into your project :( And that nobody seems to know exactly what it is that causes it doesn't help much. -Josh On Thu, Sep 18, 2008 at 10:15 AM, Douglas Knudsen [EMAIL PROTECTED]wrote: these .files suck for distributed teams though, unless you force all your devs to use the same exact resource setup, something I'm loathed to here any manager tell me :) use svn:ignore to ignore files and not include them in your SVN repos. In Subclipse, right click the file or dir and choose Team add to svn:ignore. Of course you can't have already added this file or dir to SVN. If you have already added it and want to pull it out and ignore it, you can copy it elsewhere, delete, commit, copy back, then ignore it. One trick I picked up recently from a co-worker was to rename these files and add them to SVN, this way they can be used as templates. eg rename .actionScriptProperties to .actionscriptProperties_Template. DK On Wed, Sep 17, 2008 at 7:03 PM, Josh McDonald [EMAIL PROTECTED] wrote: FWIW, I usually include .actionscriptPropertis in SVN, as it holds compiler flags that are often required to build. -J On Thu, Sep 18, 2008 at 8:05 AM, flexaustin [EMAIL PROTECTED] wrote: My thought exactly. Guess I will give it whirl. THanks! --- In flexcoders@yahoogroups.com, Howard Fore [EMAIL PROTECTED] wrote: Have you tried making a linked folder in the src directory? File New Folder Advanced Link to Folder in file system. This creates an alias in your project to that folder. Haven't tried it myself, not sure how the compiler is going to like it. The other option would be to put the alias in the operating system, using junctions in Windows or aliases/symlinks in OS X/Linux. I would expect the compiler to have no issues with those as the operating system should make them appear as real directories to the program. On Wed, Sep 17, 2008 at 3:51 PM, flexaustin [EMAIL PROTECTED] wrote: What about sharing components. For instance, we have a project just completed with several as components. We want to use some of those same AS components, but don't want to copy them to our new projects directory since when changes are made in the AS components for the old project we need them to show up in our new project. So we want to point to the same library or folder for both applications. -- Howard Fore, [EMAIL PROTECTED] The universe tends toward maximum irony. Don't push it. - Jeff Atwood -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. http://flex.joshmcdonald.info/ :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it? -- Therefore, send not to know For whom the bell tolls. It tolls for thee. http://flex.joshmcdonald.info/ :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
[flexcoders] Re: Flex Project Struture
Thanks Ryan. You mentioned Flex Builders specific files...what would those be? --- In flexcoders@yahoogroups.com, Ryan Graham [EMAIL PROTECTED] wrote: If you're using a framework like Cairngorm or Cairngorm with Extensions, there are already recommended project structures. If you aren't using an existing framework, then everyone will have to be on the same page with the dev methodologies and conventions that you all have agreed upon as a team. There should be no issues using a flex project with your given setup, but it may be worth noting that you may want to stay away from including any flex builder specific files in the SVN, as everyone has their own dev environment setup the way they like it as far as workspaces and such are concerned, and that leaves the project open to developers who may be using the sdk and command line to compile by reducing flex builder dependencies. Aside from that, I'd say it's good to keep all your view components and sealed classes for your model together (minimally), and any external or embedded assets in a separate folder defined as an additional source folder so they will still get copied to the bin when building. All this could of course be accomplished through ANT though if you want to go that route. Brief example: etc --assets --config src --components --view --model ... The possibilities are really endless, but as long as everyone agrees on the project structure, you shouldn't have any problems. This is where existing frameworks can help take the headache out of things -- by providing a known structure up front. HTH, Ryan From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of flexaustin Sent: Tuesday, September 16, 2008 4:11 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Flex Project Struture Can anyone recommend a project structure? Maybe a tut or blog post on the topic? We have several components (as and mxml) that we want to use throughout several projects and by several team members, but not sure the best way to structure the files and package them up. How do we all share the files? Is a Flex Project the best way? We are using subversion + Flex 3 + Ant. Would like to build an Ant task that fetches all the files and builds the structure once we establish what that structure should be. Thanks in advance. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
