Greg Lafrance wrote: > Now that I've been laid off from Adobe (along with 700 others), I would like > to seek Flex consulting opportunities, and one possibility is with web > designers/developers wishing to offer their clients value added components. > > My question is that I heard you don't want for example three separate Flex > apps on one web page, as it results in three instances of the Flash Player > generated, or something like that. > > So is it necessary to group multiple Flex components into one Flex app to > each web page? This can limit placement of Flex components on a web page, > because the web page will not be completely done in Flex, as the page must be > searchable. > I don't think it's necessary - it would be an informed design decision depending on what you were intending to achieve. Part of the decision might also relate to how the components were related and if they needed to communicate. I think there's no definitive answer - it depends on what your components are and how they are driven.
I hate it when people post identical questions on multiple lists - it gets so messy. > Any insight on this, particularly from Alex and others on the Flex product > team at Adobe. > > Anyone new to Flex needs help on Flex components/applications, I'm available: > [email protected] > > Thanks! > Greg > > > > > ------------------------------------ > > -- > 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 > > > > >
