May I ask your rationale for avoiding interfaces?  If you use concrete implementations, you'll generally need to do a lot more recompilation..
 
-rg


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Anatole Tartakovsky
Sent: Monday, March 27, 2006 4:51 PM
To: [email protected]
Subject: Re: [flexcoders] Large App Architecture

Tom,
    Partitioning of the application is the must, and thanks to the advise from Roger, it is not hard. However, I would advocate to not to use interfaces, but rather use small applications  and shared framework AND loosely bounded resources for UI/server interaction code approach. I should provide link to an article on the subject next week.
Thank you,
Anatole Tartakovsky
 
----- Original Message -----
Sent: Monday, March 27, 2006 4:19 PM
Subject: RE: [flexcoders] Large App Architecture

Yes, it can.  Multiple SWFs.  Tradeoffs are increased potential for
errors, a bit more architecture work needed up front, and the potential
that the Flex frameworks isn't fully designed for this case, so you
might run into some tricky (but not unsolvable) issues.  (It works
pretty well for pure-AS apps.)

My suggestion is to start building your app with interfaces connecting
the modules, and try to avoid concrete implementation dependencies.

After that, by the time we ship, I should have an article out describing
how to set things up.

-rg

> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Sobut
> Sent: Monday, March 27, 2006 11:16 AM
> To: [email protected]
> Subject: [flexcoders] Large App Architecture
>
> We're looking at possibly developing a large Flex application
> which could have 50+ screens
> and lots of sub views on those screens.
>
> We will have users with various connection speeds, including
> dialup, so we'd like to minimize
> initial download time of the app.
>
> We also have the situation where some user types use only a
> subset of the screens.
>
> Our concern is that deployed as a monolithic app, initial
> load times could be painful over
> slow connections.
>
> Can a Flex application be architected so that modules would
> be programatically loaded as
> needed?  Would this be done as separate .swf's?  Are there
> tradeoffs in this type of approach?
>
> Thanks in advance.
>
> Tom
>
>
>
>
>
>
> --
> 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
>
>
>

>
>
>
>


--
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
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to