RE: [flexcoders] Re: Best practices for setting up large applications?
We've got quite a good build system thanks ;-) This was in reply to another poster... The dependency issues we have is to do with code in a module that's required by a another module, rather than loading in the entire module, we pull the code out into a library and load that in instead, unless Maven has gotten way better of late, it aint doing that! Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk blocked::http://www.inps.co.uk/ The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of VELO Sent: 29 February 2008 13:39 To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Best practices for setting up large applications? U can use maven to help you to handle dependencies. http://code.google.com/p/israfil-mojo/ http://code.google.com/p/israfil-mojo/ VELO On Fri, Feb 29, 2008 at 9:38 AM, Gregor Kiddie [EMAIL PROTECTED] mailto:gkiddie%40inpses.co.uk wrote: We have 52 modules / libraries split roughly 1/3 to 2/3s, and a single main application. Dozens of views, and dozens of custom components. Our biggest problem is dependency management between the libraries and modules. There is frequent refactoring of a module to pull code out into a library when its identified as being needed. Full build, including generating vos, compiling java code, compiling flex code, and deploying to the server is roughly 16 minutes. Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] mailto:is.helpdesk%40inps.co.uk From: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com [mailto:flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com ] On Behalf Of tomeuchre Sent: 28 February 2008 23:03 To: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com Subject: [flexcoders] Re: Best practices for setting up large applications? --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com , Geoffrey [EMAIL PROTECTED] wrote: We currently have a master project that links in 25 other projects to build our overall application. The problem with this is that there seems to be a lot of inner dependencies b/w the projects (i.e. one project is a collection of utilities, and several other projects use these utilities). Builds also seem to take forever when you change a project that is linked to many other projects. We initially thought that this would be a good way to set up our application so we could take out certain parts to customize our offerings to customers. Just not sure that it's really giving the advantages we initially thought. Any thought on this? I am looking for something similar: I want to get an idea of what some of the largest Flex apps ever built (and utilized on a routine basis) are. I have one with 11 different views, and about 35 components, and it is about 1.5mb to load. Anybody have examples of larger ones? If so, what kind of issues do you run into?
RE: [flexcoders] Re: Best practices for setting up large applications?
We have 52 modules / libraries split roughly 1/3 to 2/3s, and a single main application. Dozens of views, and dozens of custom components. Our biggest problem is dependency management between the libraries and modules. There is frequent refactoring of a module to pull code out into a library when its identified as being needed. Full build, including generating vos, compiling java code, compiling flex code, and deploying to the server is roughly 16 minutes. Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk blocked::http://www.inps.co.uk/ The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of tomeuchre Sent: 28 February 2008 23:03 To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Best practices for setting up large applications? --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com , Geoffrey [EMAIL PROTECTED] wrote: We currently have a master project that links in 25 other projects to build our overall application. The problem with this is that there seems to be a lot of inner dependencies b/w the projects (i.e. one project is a collection of utilities, and several other projects use these utilities). Builds also seem to take forever when you change a project that is linked to many other projects. We initially thought that this would be a good way to set up our application so we could take out certain parts to customize our offerings to customers. Just not sure that it's really giving the advantages we initially thought. Any thought on this? I am looking for something similar: I want to get an idea of what some of the largest Flex apps ever built (and utilized on a routine basis) are. I have one with 11 different views, and about 35 components, and it is about 1.5mb to load. Anybody have examples of larger ones? If so, what kind of issues do you run into?
Re: [flexcoders] Re: Best practices for setting up large applications?
U can use maven to help you to handle dependencies. http://code.google.com/p/israfil-mojo/ VELO On Fri, Feb 29, 2008 at 9:38 AM, Gregor Kiddie [EMAIL PROTECTED] wrote: We have 52 modules / libraries split roughly 1/3 to 2/3s, and a single main application. Dozens of views, and dozens of custom components. Our biggest problem is dependency management between the libraries and modules. There is frequent refactoring of a module to pull code out into a library when its identified as being needed. Full build, including generating vos, compiling java code, compiling flex code, and deploying to the server is roughly 16 minutes. Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of tomeuchre Sent: 28 February 2008 23:03 To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Best practices for setting up large applications? --- In flexcoders@yahoogroups.com, Geoffrey [EMAIL PROTECTED] wrote: We currently have a master project that links in 25 other projects to build our overall application. The problem with this is that there seems to be a lot of inner dependencies b/w the projects (i.e. one project is a collection of utilities, and several other projects use these utilities). Builds also seem to take forever when you change a project that is linked to many other projects. We initially thought that this would be a good way to set up our application so we could take out certain parts to customize our offerings to customers. Just not sure that it's really giving the advantages we initially thought. Any thought on this? I am looking for something similar: I want to get an idea of what some of the largest Flex apps ever built (and utilized on a routine basis) are. I have one with 11 different views, and about 35 components, and it is about 1.5mb to load. Anybody have examples of larger ones? If so, what kind of issues do you run into?
[flexcoders] Re: Best practices for setting up large applications?
Yes, we use Maven to handle dependencies. We also use Cruiseconrol for automated builds, SVN for version control, and WTP for pushing all the stuff to our web server. So far, the all in one project sounds the best. --- In flexcoders@yahoogroups.com, VELO [EMAIL PROTECTED] wrote: U can use maven to help you to handle dependencies. http://code.google.com/p/israfil-mojo/ VELO On Fri, Feb 29, 2008 at 9:38 AM, Gregor Kiddie [EMAIL PROTECTED] wrote: We have 52 modules / libraries split roughly 1/3 to 2/3s, and a single main application. Dozens of views, and dozens of custom components. Our biggest problem is dependency management between the libraries and modules. There is frequent refactoring of a module to pull code out into a library when its identified as being needed. Full build, including generating vos, compiling java code, compiling flex code, and deploying to the server is roughly 16 minutes. Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of tomeuchre Sent: 28 February 2008 23:03 To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Best practices for setting up large applications? --- In flexcoders@yahoogroups.com, Geoffrey gtb104@ wrote: We currently have a master project that links in 25 other projects to build our overall application. The problem with this is that there seems to be a lot of inner dependencies b/w the projects (i.e. one project is a collection of utilities, and several other projects use these utilities). Builds also seem to take forever when you change a project that is linked to many other projects. We initially thought that this would be a good way to set up our application so we could take out certain parts to customize our offerings to customers. Just not sure that it's really giving the advantages we initially thought. Any thought on this? I am looking for something similar: I want to get an idea of what some of the largest Flex apps ever built (and utilized on a routine basis) are. I have one with 11 different views, and about 35 components, and it is about 1.5mb to load. Anybody have examples of larger ones? If so, what kind of issues do you run into?
[flexcoders] Re: Best practices for setting up large applications?
We had the same problem in AS2, where we basically build the whole Flex engine in AS2 / XML, plus everything else the application needed to do, more than 50k lines of code. Flash 7 was compiling it for 3 minutes. We couldn't move or change anything without destroying things somewhere else. We also thought that's the best way compared to what other teams were doing, we were really proud of it in the beginning :) It basically depends how you structure classes, libraries, so they can be used independently in different projects. Less inheritance, more composition, domain objects, decorator objects, Cairngorm also helps, and above all experience. I don't know, it depends on project to project, I doubt there is one single recipe you could follow to have everything in order. Alen --- In flexcoders@yahoogroups.com, Geoffrey [EMAIL PROTECTED] wrote: We currently have a master project that links in 25 other projects to build our overall application. The problem with this is that there seems to be a lot of inner dependencies b/w the projects (i.e. one project is a collection of utilities, and several other projects use these utilities). Builds also seem to take forever when you change a project that is linked to many other projects. We initially thought that this would be a good way to set up our application so we could take out certain parts to customize our offerings to customers. Just not sure that it's really giving the advantages we initially thought. Any thought on this?
