Re: [flexcoders] Flex Project Struture
Ryan, I'm curious about how you separate the Flex Builder project files from the source code (and asset files) in your projects so that the former doesn't get into SVN with the later. I've tried various ways of setting up links etc and FB doesn't seem to like any of them. On Tue, Sep 16, 2008 at 7:57 PM, Ryan Graham [EMAIL PROTECTED]wrote: 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. -- Howard Fore, [EMAIL PROTECTED] The universe tends toward maximum irony. Don't push it. - Jeff Atwood
Re: [flexcoders] Flex Project Struture
but it may be worth noting that you may want to stay away from including any flex builder specific files in the SVN, He's talking about the . dot files that are hidden; .flexProperties .actionScriptProperties .project .settings .flexLibSettings etc. Mike On Wed, Sep 17, 2008 at 11:44 AM, Howard Fore [EMAIL PROTECTED] wrote: Ryan, I'm curious about how you separate the Flex Builder project files from the source code (and asset files) in your projects so that the former doesn't get into SVN with the later. I've tried various ways of setting up links etc and FB doesn't seem to like any of them. On Tue, Sep 16, 2008 at 7:57 PM, Ryan Graham [EMAIL PROTECTED]wrote: 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. -- Howard Fore, [EMAIL PROTECTED] The universe tends toward maximum irony. Don't push it. - Jeff Atwood -- Teoti Graphix, LLC http://www.teotigraphix.com Teoti Graphix Blog http://www.blog.teotigraphix.com You can find more by solving the problem then by 'asking the question'.
RE: [flexcoders] Flex Project Struture
Usually this is setup through the Project Properties. I add another top-level folder for anything the app needs to consume at runtime (like an etc folder) and perhaps another that the app needs to consume at compile time like embedded assets (like an includes folder -- it's up to you): Project Properties Flex Build Path Source Path Add Folder... To have files copied to the bin when building, don't forget to check: Project Properties Flex Compiler Copy non-embedded files to output folder Then you have the option of including these folders in SVN or leaving them local to the working copy... In my experience though, when another dev checks out the project, they have to set up these folder associations for their working copy in FB, so I might put a README.txt in the root of the project detailing the expected setup. This seems kinda clunky though -- if anyone knows what to do to persist these settings through the SVN, I'd love to know. I know ANT is always an option, but sometimes its nice to not have to muck with it. HTH, Ryan From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Howard Fore Sent: Wednesday, September 17, 2008 8:44 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Flex Project Struture Ryan, I'm curious about how you separate the Flex Builder project files from the source code (and asset files) in your projects so that the former doesn't get into SVN with the later. I've tried various ways of setting up links etc and FB doesn't seem to like any of them. On Tue, Sep 16, 2008 at 7:57 PM, Ryan Graham [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: 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. -- 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.
[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.
RE: [flexcoders] Flex Project Struture
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.
