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 : A
On 1/10/14 3:24 PM, "Maurice Amsellem" 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
>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
On 1/10/14 3:02 PM, "Mark Kessler" 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 pai
Hi,
> Hmm. That wouldn't be my preference. Do other projects do this?
In general yes but each project is different and can do what they want
basically.
> JIRA is not my favorite tool. Regarding history, the commit logs should be
> sufficient.
For people not familiar with the code or who are
Hmm. That wouldn't be my preference. Do other projects do this? JIRA is
not my favorite tool. Regarding history, the commit logs should be
sufficient.
What kind of information are you really looking for? Was it not clear
that I've been working on the installer and ant_on_air for a while now?
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 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
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 f
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 th
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
Hi,
I've noticed that Alex and Peter tend to work on something for a while and then
the first we know about it is when it's checked in.
A possibly better process would be to raise each change as a new
feature/improvement in JIRA, that way there would be better visibility to
what's been worked
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" wrote:
>Hi,
>
>> So, basically, the current licensing dialog would have one
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
Hi,
I've just pushed some changes to FlexJS DataGrid that adds DataGridColumn. This
work was primarily to allow custom itemRenderers per column. The changes I've
pushed are initial work - there are properties that aren't implemented or do
nothing right now, but the code should be safe to use. N
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
Please file a bug with a simple test case and include the skin that you
used as a workaround.
There was a prior discussion about something like this that was not
resolved. We're still trying to determine if there are different default
fonts on the device, if it matters if it is AIR 3.9 or an earl
Yeah, seems like a Flex bug, probably a DPI or TLF releated bug.
At 2014-01-10 18:07:20,Sunny wrote:
>Hi,All:
>
>Today I met a trouble, In android 4.4.2 OS(Nexus7 2rd) , air 3.9.0.141 and
>Flex SDK 4.11, the Button,ButtonBar and headText of MobileGrid can't display
>Chinese characters, but the Eng
Hi,All:
Today I met a trouble, In android 4.4.2 OS(Nexus7 2rd) , air 3.9.0.141 and
Flex SDK 4.11, the Button,ButtonBar and headText of MobileGrid can't display
Chinese characters, but the English characters works very well. The most
puzzling problem that I add a skin(Only set the rationX) for the
Mustella just ran in to this same RTE again, so we can pretty much
rule out coincidence, I think.
Can someone please look at this?
Here is the trace in full:
TypeError: Error #1009: Cannot access a property or method of a null
object reference.
at
mx.resources::ResourceManagerImpl/findResourceB
Hi, all:
The button, buttonBar and mobileDataGrid components can't display the
simplified Chinese, but English is well. Happened in android 4.4.2 OS (Nexus7
2rd), but works well in 4.2 OS.
Do you have the same issues?
2014-01-10
Sunny
20 matches
Mail list logo
