Hi Christofer, I think that what you are referring is a rethink from Adobe about how much sense has to have developer tools into a creative suite (from the Fb stand point since Fc really has been discontinued). Nothing to do about the effort behind the tool (Fb).
As Alex said, Adobe is working in take Apache Flex into account and that means a new release cycle. They will do as best as they can in order to get a competitive Fb. But this is something we don't have to worry about. They are a business and for that reason we are today here in Apache. They will move based in business strategies that could be comprensible by us...or not... what is clear to me is that we have a need and our responsability here is to solve that need. And that Adobe has its own needs and are belong to them to solve them. Normaly they will serve their users if they want to maintain the sales, and this means to go with the flow, in this specific case the flow marked by Apache Flex. 2012/5/25 christofer.d...@c-ware.de <christofer.d...@c-ware.de> > It seems that the new Creative Suite Web Premium followup ships without > Catalyst and FlashBuilder ... I think that is a pretty good statement > towards how much effort Adobe will be putting into maintaining those tools. > > Chris > > -----Ursprüngliche Nachricht----- > Von: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] Im Auftrag > von Carlos Rovira > Gesendet: Donnerstag, 24. Mai 2012 21:50 > An: flex-dev@incubator.apache.org > Betreff: Re: Apache Flex structure to be BMS compliant (was Re: Library > Versions used in Flex SDK) > > I think IntelliJ will update quickly since they are > "maven-gradle-whatever-bms-oriented". > Flash Builder never took into account BMS, but they will update due that > technology requeriments....or are you saying that they will abandon Flex > development? > > moreover...are you saying that we must stay with what we have now? > so...that's what we can expect for the future of flex? stay with the same > problems we ever had during all years? What kind of changes can we expect? > only cosmetic changes? > > Michel, you and Alex were talking about agresive changes in the SDK...i.e: > a completely new set of flex components and arqutecture, isn't it?...so > changes like that will not obligate Adobe to update Fb in order to make it > Apache Flex compliant? > > > > 2012/5/24 Michael A. Labriola <labri...@digitalprimates.net> > > > >I think the tool refactors implied in tools like Fb or Intellij will > > >be > > of low impact and should not be a problem to stop evolution, since is > > re-structure of the sdk to be a more standard piece of software... > > maybe I'm talking from a >feeling that this not should be a huge > showstopper. > > > > So, you think Adobe will refactor Flash Builder to make us happy? What > > about the thousands of copies in use already that people won't pay to > > update and won't work with a refactored sdk? > > > > > > > > > -- > Carlos Rovira > Director de Tecnología > M: +34 607 22 60 05 > F: +34 912 35 57 77 > <http://www.codeoscopic.com> > CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 > Planta 10, Puertas P-Q > 28020 Madrid > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 <http://www.codeoscopic.com> CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
