That's a bloody good point aYo www.ayobinitie.com mrbinitie.blogspot.com On 15 Dec 2013 15:52, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote:
> Understood. > > Is there also a goal with FlexJS to remove dependencies to Adobe > proprietary software? > In which case, would it make sense that the installer won't be based > solely on Adobe technology? > > Maurice > > -----Message d'origine----- > De : Alex Harui [mailto:aha...@adobe.com] > Envoyé : dimanche 15 décembre 2013 16:35 > À : dev@flex.apache.org > Objet : Re: Installer Revisited > > Ah, sorry, missed seeing that earlier. > > My personal goal is that, someday, a newbie's initial experience when > coming to Apache Flex to learn about Flex is a showcase for Flex. That our > current landing page is fully replicated by FlexJS, and our installer is an > example of an AIR app. > > So, I would not want to go down the Java UI path. But if it turns out it > is impossible/impractical to accomplish something in AIR, we can certainly > consider native process or native extensions to run some java code. That > would also be an example of how to write an AIR app. > > -Alex > > On 12/15/13 4:50 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> > wrote: > > >Any reaction to the Java-based installer proposition below (Point B) ? > > > >Maurice > > > >-----Message d'origine----- > >De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] > >Envoyé : jeudi 12 décembre 2013 09:17 > >À : dev@flex.apache.org > >Objet : RE: Installer Revisited > > > >(Point A) > > > >>I thought Air followed redirects. There must be code in the installer > >>that does the right thing. Feel free to find it and add it if it > >>needs it. > > > >I don't know either if AIR follows redirects or not, but the way it > >does was not enough for downloading from sourceforge and we had to > >implement a specific solution. > >My concern is that it's really specific, and difficult to make generic. > > > >Another point is that current Installer has conditional logic ( eg. if > >already downloaded, don't download again) that will need to be > >implemented in ant_on_air. > >It's also missing <parallel> functionality, that would speed up downloads. > >And I am sure that we will discover other things... > >As you say, it's brand new stuff. > > > >------ > >(Point B) > >So may I open the discussion on an alternative approach: > > > >After all, do we absolutely need that the installer be and AIR app? > >The ant "core" lib is not that big (a few MB) so maybe we could build > >the installer as a JAVA GUI app instead of an AIR app, that embeds the > >ANT lib. > > > >I am not saying this will be easy, but at least it will be guaranteed > >to have the same behavior, and opens up a full range of possibilities. > > > >Thoughts ? > > > >Maurice > > > > > >
