You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2014/01/10 22:34:45 UTC
Installer Workflow
Hi folks,
I'm starting in on plugging in the ant_on_air stuff into the Installer.
I realized that we may need to change the Installer's workflow in order to
support this.
Right now, the Installer knows up front the set of optional and required
components and that is the third UI panel offered to folks. With
ant_on_air, we want to discover the set of components from the binary
package. So, the workflow would change to something more like:
Panel1: Choose a package, FP and AIR versions like we do now
Panel2: Choose folder
Panel3: Accept license for package and download package
Panel4: See license dialog for other required and optional pieces
Panel5: Download those pieces.
So, basically, the current licensing dialog would have one less entry (the
SDK and its license since it is already downloaded) and there is an extra
step before that as we download the package.
Thoughts? Better Ideas?
Thanks,
-Alex
Re: Installer Workflow
Posted by Alex Harui <ah...@adobe.com>.
On 1/10/14 3:02 PM, "Mark Kessler" <ke...@gmail.com> wrote:
>Would that mean we could tweak the installer xml file independently of the
>installer?
Yes. That's the main goal. That the next installer release is the last
one and all new installer capability is in the installer.xml file.
Installer releases are painful because we have to make executables for
each platform. It should save all of us time to put more logic in a
script.
-Alex
Re: Installer Workflow
Posted by Mark Kessler <ke...@gmail.com>.
Would that mean we could tweak the installer xml file independently of the
installer?
-Mark
On Fri, Jan 10, 2014 at 5:57 PM, Alex Harui <ah...@adobe.com> wrote:
> I thought about that. But in theory, you should accept the license before
> the bits hit your computer. Once we've uncompressed the package to get at
> the installer.xml, we've essentially done a lot of the install and you
> could kill the installer at that point and never see the license dialog.
>
> So far, I'm liking Justin's idea of having the installer.xml sit alongside
> the binary packages.
>
>
RE: Installer Workflow
Posted by Maurice Amsellem <ma...@systar.com>.
AFAIU, licence agreements are about "using" the software, not installing it.
So it should really not be a problem to have the licence after the download.
But never mind, you seem to have found the answer to your question, with the separate xml file...
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : samedi 11 janvier 2014 00:30
À : dev@flex.apache.org
Objet : Re: Installer Workflow
On 1/10/14 3:24 PM, "Maurice Amsellem" <ma...@systar.com> wrote:
>>we've essentially done a lot of the install and you could kill the
>>installer at that point and never see the license dialog.
>But if you kill the installer before the end and don't read the
>licence, the SDK won't be installed anyway.
>So where is the problem?
If we have to download and uncompress the binary package on your machine in order to access the installer.xml inside it, then we have "installed"
it. It just won't work in your IDE.
Re: Installer Workflow
Posted by Alex Harui <ah...@adobe.com>.
On 1/10/14 3:24 PM, "Maurice Amsellem" <ma...@systar.com> wrote:
>>we've essentially done a lot of the install and you could kill the
>>installer at that point and never see the license dialog.
>But if you kill the installer before the end and don't read the licence,
>the SDK won't be installed anyway.
>So where is the problem?
If we have to download and uncompress the binary package on your machine
in order to access the installer.xml inside it, then we have "installed"
it. It just won't work in your IDE.
RE: Installer Workflow
Posted by Maurice Amsellem <ma...@systar.com>.
>we've essentially done a lot of the install and you could kill the installer at that point and never see the license dialog.
But if you kill the installer before the end and don't read the licence, the SDK won't be installed anyway.
So where is the problem?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : vendredi 10 janvier 2014 23:57
À : dev@flex.apache.org
Objet : Re: Installer Workflow
I thought about that. But in theory, you should accept the license before the bits hit your computer. Once we've uncompressed the package to get at the installer.xml, we've essentially done a lot of the install and you could kill the installer at that point and never see the license dialog.
So far, I'm liking Justin's idea of having the installer.xml sit alongside the binary packages.
On 1/10/14 2:51 PM, "Maurice Amsellem" <ma...@systar.com> wrote:
>Question: why is it necessary to accept the license before downloading
>in step 3 ?
>
>Wouldn't it be possible to download the package first in step 3, then
>accept the license in step 4.
>Of course, if the user does not accept the license, the whole process
>is cancelled and the files removed, so there is no license breaking.
>
>WDYT ?
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : vendredi 10 janvier
>2014 22:35 À : dev@flex.apache.org Objet : Installer Workflow
>
>Hi folks,
>
>I'm starting in on plugging in the ant_on_air stuff into the Installer.
>
>I realized that we may need to change the Installer's workflow in order
>to support this.
>
>Right now, the Installer knows up front the set of optional and
>required components and that is the third UI panel offered to folks.
>With ant_on_air, we want to discover the set of components from the
>binary package. So, the workflow would change to something more like:
>
>Panel1: Choose a package, FP and AIR versions like we do now
>Panel2: Choose folder
>Panel3: Accept license for package and download package
>Panel4: See license dialog for other required and optional pieces
>Panel5: Download those pieces.
>
>So, basically, the current licensing dialog would have one less entry
>(the SDK and its license since it is already downloaded) and there is
>an extra step before that as we download the package.
>
>Thoughts? Better Ideas?
>
>Thanks,
>-Alex
>
Re: Installer Workflow
Posted by Alex Harui <ah...@adobe.com>.
I thought about that. But in theory, you should accept the license before
the bits hit your computer. Once we've uncompressed the package to get at
the installer.xml, we've essentially done a lot of the install and you
could kill the installer at that point and never see the license dialog.
So far, I'm liking Justin's idea of having the installer.xml sit alongside
the binary packages.
On 1/10/14 2:51 PM, "Maurice Amsellem" <ma...@systar.com> wrote:
>Question: why is it necessary to accept the license before downloading
>in step 3 ?
>
>Wouldn't it be possible to download the package first in step 3, then
>accept the license in step 4.
>Of course, if the user does not accept the license, the whole process is
>cancelled and the files removed, so there is no license breaking.
>
>WDYT ?
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : vendredi 10 janvier 2014 22:35
>À : dev@flex.apache.org
>Objet : Installer Workflow
>
>Hi folks,
>
>I'm starting in on plugging in the ant_on_air stuff into the Installer.
>
>I realized that we may need to change the Installer's workflow in order
>to support this.
>
>Right now, the Installer knows up front the set of optional and required
>components and that is the third UI panel offered to folks. With
>ant_on_air, we want to discover the set of components from the binary
>package. So, the workflow would change to something more like:
>
>Panel1: Choose a package, FP and AIR versions like we do now
>Panel2: Choose folder
>Panel3: Accept license for package and download package
>Panel4: See license dialog for other required and optional pieces
>Panel5: Download those pieces.
>
>So, basically, the current licensing dialog would have one less entry
>(the SDK and its license since it is already downloaded) and there is an
>extra step before that as we download the package.
>
>Thoughts? Better Ideas?
>
>Thanks,
>-Alex
>
RE: Installer Workflow
Posted by Maurice Amsellem <ma...@systar.com>.
Question: why is it necessary to accept the license before downloading in step 3 ?
Wouldn't it be possible to download the package first in step 3, then accept the license in step 4.
Of course, if the user does not accept the license, the whole process is cancelled and the files removed, so there is no license breaking.
WDYT ?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : vendredi 10 janvier 2014 22:35
À : dev@flex.apache.org
Objet : Installer Workflow
Hi folks,
I'm starting in on plugging in the ant_on_air stuff into the Installer.
I realized that we may need to change the Installer's workflow in order to support this.
Right now, the Installer knows up front the set of optional and required components and that is the third UI panel offered to folks. With ant_on_air, we want to discover the set of components from the binary package. So, the workflow would change to something more like:
Panel1: Choose a package, FP and AIR versions like we do now
Panel2: Choose folder
Panel3: Accept license for package and download package
Panel4: See license dialog for other required and optional pieces
Panel5: Download those pieces.
So, basically, the current licensing dialog would have one less entry (the SDK and its license since it is already downloaded) and there is an extra step before that as we download the package.
Thoughts? Better Ideas?
Thanks,
-Alex
Re: Installer Workflow
Posted by Alex Harui <ah...@adobe.com>.
Congratulations.
I do need to change to a new sdk-installer-config-4.0 because the format
needs to change to make it Ant compatible. I'll look to see what the
badge needs to know in order to handle that.
Thanks for the head up,
-Alex
On 1/12/14 3:21 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>Haven't been able to follow this thread much (at the hospital with my
>newborn :-) )
>
>Just wanted to remind folks that installer config .xml drives the website
>badge installer as well as enables the auto-update mechanism for the
>Installer.
>
>Thanks,
>Om
>On Jan 11, 2014 10:58 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>> Update: I've adjusted this plan a bit. There were issues like the
>> installer.xml wants a basedir. I could copy it into the destination
>> directory and run it from there, but then I have to not overwrite it
>>when
>> expanding the package. Also, the installer.xml wants to load some
>> properties from files.
>>
>> However, what I want to know before the package is expanded is the
>> licensing information which shouldn't rely on basedir. So my new plan
>>is
>> to create installer-config.xml files with the licensing info and we'll
>>put
>> those next to the release packages. Then the installer can pick that up
>> early, offer up the licenses, then expand the package and run the
>> installer script inside.
>>
>> Let me know if you see any problems with this approach,
>>
>> -Alex
>>
>> On 1/10/14 2:25 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>
>> >Hi,
>> >
>> >> Interesting. So we'd put the installer.xml files up separately on a
>> >> server somewhere as part of release distribution?
>> >
>> >Could be either - but outside the zip with the release distribution
>> >seems fine to me.
>> >
>> >Thanks,
>> >Justin
>>
>>
RE: Installer Workflow
Posted by Maurice Amsellem <ma...@systar.com>.
Congraulations!
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala
Envoyé : dimanche 12 janvier 2014 12:21
À : dev@flex.apache.org
Objet : Re: Installer Workflow
Haven't been able to follow this thread much (at the hospital with my newborn :-) )
Just wanted to remind folks that installer config .xml drives the website badge installer as well as enables the auto-update mechanism for the Installer.
Thanks,
Om
On Jan 11, 2014 10:58 PM, "Alex Harui" <ah...@adobe.com> wrote:
> Update: I've adjusted this plan a bit. There were issues like the
> installer.xml wants a basedir. I could copy it into the destination
> directory and run it from there, but then I have to not overwrite it
> when expanding the package. Also, the installer.xml wants to load
> some properties from files.
>
> However, what I want to know before the package is expanded is the
> licensing information which shouldn't rely on basedir. So my new plan
> is to create installer-config.xml files with the licensing info and
> we'll put those next to the release packages. Then the installer can
> pick that up early, offer up the licenses, then expand the package and
> run the installer script inside.
>
> Let me know if you see any problems with this approach,
>
> -Alex
>
> On 1/10/14 2:25 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
> >Hi,
> >
> >> Interesting. So we'd put the installer.xml files up separately on
> >> a server somewhere as part of release distribution?
> >
> >Could be either - but outside the zip with the release distribution
> >seems fine to me.
> >
> >Thanks,
> >Justin
>
>
Re: Installer Workflow
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Congrats, Om!
I'll keep an eye on the badge, it's really simple, so we can either use a
different configuration, or, when the installer_on_ant stabilizes, hard
code the data.
EdB
On Sunday, January 12, 2014, OmPrakash Muppirala wrote:
> Haven't been able to follow this thread much (at the hospital with my
> newborn :-) )
>
> Just wanted to remind folks that installer config .xml drives the website
> badge installer as well as enables the auto-update mechanism for the
> Installer.
>
> Thanks,
> Om
> On Jan 11, 2014 10:58 PM, "Alex Harui" <aharui@adobe.com <javascript:;>>
> wrote:
>
> > Update: I've adjusted this plan a bit. There were issues like the
> > installer.xml wants a basedir. I could copy it into the destination
> > directory and run it from there, but then I have to not overwrite it when
> > expanding the package. Also, the installer.xml wants to load some
> > properties from files.
> >
> > However, what I want to know before the package is expanded is the
> > licensing information which shouldn't rely on basedir. So my new plan is
> > to create installer-config.xml files with the licensing info and we'll
> put
> > those next to the release packages. Then the installer can pick that up
> > early, offer up the licenses, then expand the package and run the
> > installer script inside.
> >
> > Let me know if you see any problems with this approach,
> >
> > -Alex
> >
> > On 1/10/14 2:25 PM, "Justin Mclean" <justin@classsoftware.com<javascript:;>>
> wrote:
> >
> > >Hi,
> > >
> > >> Interesting. So we'd put the installer.xml files up separately on a
> > >> server somewhere as part of release distribution?
> > >
> > >Could be either - but outside the zip with the release distribution
> > >seems fine to me.
> > >
> > >Thanks,
> > >Justin
> >
> >
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: Installer Workflow
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Congrats!
-Mark
-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash Muppirala
Sent: Sunday, January 12, 2014 6:56 AM
To: dev@flex.apache.org
Subject: Re: Installer Workflow
On Jan 12, 2014 3:49 AM, "Paul Hastings" <pa...@gmail.com> wrote:
>
> On 1/12/2014 6:21 PM, OmPrakash Muppirala wrote:
>>
>> Haven't been able to follow this thread much (at the hospital with my
>> newborn :-) )
>
>
> well congratulations! boy or girl?
>
Thank you! It's a boy :-)
Om
Re: Installer Workflow
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Jan 12, 2014 3:49 AM, "Paul Hastings" <pa...@gmail.com> wrote:
>
> On 1/12/2014 6:21 PM, OmPrakash Muppirala wrote:
>>
>> Haven't been able to follow this thread much (at the hospital with my
>> newborn :-) )
>
>
> well congratulations! boy or girl?
>
Thank you! It's a boy :-)
Om
Re: Installer Workflow
Posted by Paul Hastings <pa...@gmail.com>.
On 1/12/2014 6:21 PM, OmPrakash Muppirala wrote:
> Haven't been able to follow this thread much (at the hospital with my
> newborn :-) )
well congratulations! boy or girl?
Re: Installer Workflow
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Haven't been able to follow this thread much (at the hospital with my
newborn :-) )
Just wanted to remind folks that installer config .xml drives the website
badge installer as well as enables the auto-update mechanism for the
Installer.
Thanks,
Om
On Jan 11, 2014 10:58 PM, "Alex Harui" <ah...@adobe.com> wrote:
> Update: I've adjusted this plan a bit. There were issues like the
> installer.xml wants a basedir. I could copy it into the destination
> directory and run it from there, but then I have to not overwrite it when
> expanding the package. Also, the installer.xml wants to load some
> properties from files.
>
> However, what I want to know before the package is expanded is the
> licensing information which shouldn't rely on basedir. So my new plan is
> to create installer-config.xml files with the licensing info and we'll put
> those next to the release packages. Then the installer can pick that up
> early, offer up the licenses, then expand the package and run the
> installer script inside.
>
> Let me know if you see any problems with this approach,
>
> -Alex
>
> On 1/10/14 2:25 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
> >Hi,
> >
> >> Interesting. So we'd put the installer.xml files up separately on a
> >> server somewhere as part of release distribution?
> >
> >Could be either - but outside the zip with the release distribution
> >seems fine to me.
> >
> >Thanks,
> >Justin
>
>
Re: Installer Workflow
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I'll take a look at Checkintest, that sounds like a worthwhile challenge ;-)
EdB
On Sun, Jan 12, 2014 at 4:44 PM, Alex Harui <ah...@adobe.com> wrote:
> OTOH, things that might be worth doing include:
>
> More FlexJS Components: "Easy" ones like DateChooser, ColorPicker. Hard
> ones like Tree and PieChart.
>
> FlexJS Mobile Components: Mimic the ones in Flex mobile.
>
> FlexJS Mobile Publishing: Do what is needed to generate Cordova/PhoneGap
> projects or applications from FalconJX
>
> FlexJS Effects: Try to get some sort of Effects components to work.
>
> FlexJS ASDoc: Integrate it into the build, make sure everything has a
> comment.
>
> FlexJS Checkintest: Port the Flex SDK BasicTest. Comment out what we
> don't have in the component set. Try to get it to run.
>
> FlexJS and Falcon Release: Rat found a couple of dozen files in both
> FlexJS and Falcon that need headers.
>
> Installer Resource Management: I still don't understand why we hard code
> resources into the Installer in RuntimeLocale.as. Since I hope to make
> this the "last" installer release, it makes sense to me to un-hard-code
> the resources so that new resources can be added post release. We could
> use ResourceModules or simply read in properties files since all resources
> are currently text.
>
> I'm sure I'll think of moreŠ
>
> Thanks,
> -Alex
>
> On 1/12/14 12:24 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
>>That sounds like a good plan.
>>
>>Alex, I don't have any inspiration for my next 'project'. Is there
>>anything on your list I might be able to help with?
>>
>>EdB
>>
>>
>>
>>On Sun, Jan 12, 2014 at 7:55 AM, Alex Harui <ah...@adobe.com> wrote:
>>> Update: I've adjusted this plan a bit. There were issues like the
>>> installer.xml wants a basedir. I could copy it into the destination
>>> directory and run it from there, but then I have to not overwrite it
>>>when
>>> expanding the package. Also, the installer.xml wants to load some
>>> properties from files.
>>>
>>> However, what I want to know before the package is expanded is the
>>> licensing information which shouldn't rely on basedir. So my new plan
>>>is
>>> to create installer-config.xml files with the licensing info and we'll
>>>put
>>> those next to the release packages. Then the installer can pick that up
>>> early, offer up the licenses, then expand the package and run the
>>> installer script inside.
>>>
>>> Let me know if you see any problems with this approach,
>>>
>>> -Alex
>>>
>>> On 1/10/14 2:25 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>>
>>>>Hi,
>>>>
>>>>> Interesting. So we'd put the installer.xml files up separately on a
>>>>> server somewhere as part of release distribution?
>>>>
>>>>Could be either - but outside the zip with the release distribution
>>>>seems fine to me.
>>>>
>>>>Thanks,
>>>>Justin
>>>
>>
>>
>>
>>--
>>Ix Multimedia Software
>>
>>Jan Luykenstraat 27
>>3521 VB Utrecht
>>
>>T. 06-51952295
>>I. www.ixsoftware.nl
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Installer Workflow
Posted by Alex Harui <ah...@adobe.com>.
OTOH, things that might be worth doing include:
More FlexJS Components: "Easy" ones like DateChooser, ColorPicker. Hard
ones like Tree and PieChart.
FlexJS Mobile Components: Mimic the ones in Flex mobile.
FlexJS Mobile Publishing: Do what is needed to generate Cordova/PhoneGap
projects or applications from FalconJX
FlexJS Effects: Try to get some sort of Effects components to work.
FlexJS ASDoc: Integrate it into the build, make sure everything has a
comment.
FlexJS Checkintest: Port the Flex SDK BasicTest. Comment out what we
don't have in the component set. Try to get it to run.
FlexJS and Falcon Release: Rat found a couple of dozen files in both
FlexJS and Falcon that need headers.
Installer Resource Management: I still don't understand why we hard code
resources into the Installer in RuntimeLocale.as. Since I hope to make
this the "last" installer release, it makes sense to me to un-hard-code
the resources so that new resources can be added post release. We could
use ResourceModules or simply read in properties files since all resources
are currently text.
I'm sure I'll think of moreŠ
Thanks,
-Alex
On 1/12/14 12:24 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>That sounds like a good plan.
>
>Alex, I don't have any inspiration for my next 'project'. Is there
>anything on your list I might be able to help with?
>
>EdB
>
>
>
>On Sun, Jan 12, 2014 at 7:55 AM, Alex Harui <ah...@adobe.com> wrote:
>> Update: I've adjusted this plan a bit. There were issues like the
>> installer.xml wants a basedir. I could copy it into the destination
>> directory and run it from there, but then I have to not overwrite it
>>when
>> expanding the package. Also, the installer.xml wants to load some
>> properties from files.
>>
>> However, what I want to know before the package is expanded is the
>> licensing information which shouldn't rely on basedir. So my new plan
>>is
>> to create installer-config.xml files with the licensing info and we'll
>>put
>> those next to the release packages. Then the installer can pick that up
>> early, offer up the licenses, then expand the package and run the
>> installer script inside.
>>
>> Let me know if you see any problems with this approach,
>>
>> -Alex
>>
>> On 1/10/14 2:25 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>
>>>Hi,
>>>
>>>> Interesting. So we'd put the installer.xml files up separately on a
>>>> server somewhere as part of release distribution?
>>>
>>>Could be either - but outside the zip with the release distribution
>>>seems fine to me.
>>>
>>>Thanks,
>>>Justin
>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
Re: Installer Workflow
Posted by Erik de Bruin <er...@ixsoftware.nl>.
That sounds like a good plan.
Alex, I don't have any inspiration for my next 'project'. Is there
anything on your list I might be able to help with?
EdB
On Sun, Jan 12, 2014 at 7:55 AM, Alex Harui <ah...@adobe.com> wrote:
> Update: I've adjusted this plan a bit. There were issues like the
> installer.xml wants a basedir. I could copy it into the destination
> directory and run it from there, but then I have to not overwrite it when
> expanding the package. Also, the installer.xml wants to load some
> properties from files.
>
> However, what I want to know before the package is expanded is the
> licensing information which shouldn't rely on basedir. So my new plan is
> to create installer-config.xml files with the licensing info and we'll put
> those next to the release packages. Then the installer can pick that up
> early, offer up the licenses, then expand the package and run the
> installer script inside.
>
> Let me know if you see any problems with this approach,
>
> -Alex
>
> On 1/10/14 2:25 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
>>Hi,
>>
>>> Interesting. So we'd put the installer.xml files up separately on a
>>> server somewhere as part of release distribution?
>>
>>Could be either - but outside the zip with the release distribution
>>seems fine to me.
>>
>>Thanks,
>>Justin
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Installer Workflow
Posted by Alex Harui <ah...@adobe.com>.
Update: I've adjusted this plan a bit. There were issues like the
installer.xml wants a basedir. I could copy it into the destination
directory and run it from there, but then I have to not overwrite it when
expanding the package. Also, the installer.xml wants to load some
properties from files.
However, what I want to know before the package is expanded is the
licensing information which shouldn't rely on basedir. So my new plan is
to create installer-config.xml files with the licensing info and we'll put
those next to the release packages. Then the installer can pick that up
early, offer up the licenses, then expand the package and run the
installer script inside.
Let me know if you see any problems with this approach,
-Alex
On 1/10/14 2:25 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> Interesting. So we'd put the installer.xml files up separately on a
>> server somewhere as part of release distribution?
>
>Could be either - but outside the zip with the release distribution
>seems fine to me.
>
>Thanks,
>Justin
Re: Installer Workflow
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Interesting. So we'd put the installer.xml files up separately on a
> server somewhere as part of release distribution?
Could be either - but outside the zip with the release distribution seems fine to me.
Thanks,
Justin
Re: Installer Workflow
Posted by Alex Harui <ah...@adobe.com>.
Interesting. So we'd put the installer.xml files up separately on a
server somewhere as part of release distribution?
I'd be ok with that. How do other folks feel about that?
-Alex
On 1/10/14 2:13 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> So, basically, the current licensing dialog would have one less entry
>>(the
>> SDK and its license since it is already downloaded) and there is an
>>extra
>> step before that as we download the package.
>
>You could keep the steps the same order if you just downloaded the XML
>file right?
>
>Justin
Re: Installer Workflow
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> So, basically, the current licensing dialog would have one less entry (the
> SDK and its license since it is already downloaded) and there is an extra
> step before that as we download the package.
You could keep the steps the same order if you just downloaded the XML file right?
Justin