Re: Building the SDK
Okay. Thanks. I'll give it another go later today… On Sep 2, 2013, at 9:22 AM, Alex Harui wrote: > > > On 9/1/13 10:57 PM, "Harbs" wrote: > >> I'm going around in circles hereŠ >> >> I have two problems. One with playerglobal.swc and another with >> textLayout.swc >> >> 1) When I link the develop SDK to a project, I get two swc links: >> playerglobal.swc and "11.1". It can't find either of those. I can manage >> to get the SDK to work by unlinking those and linking to a valid copy of >> playerglobal on my machine. This is workable, but I'm concerned by why I >> need to do that. It's also a pain to do this every time I want to use the >> dev sdkŠ > I just realized that this sort of thing is why we don't use the git repo > folders as-is in FB. That's why we have the Installer and those scripts > like makeApacheFlexForFLexBuilder. And why I don't use FB and just use > the command line for MXMLC and FDB. > > I guess I'd suggest using the Installer to set up a working SDK then copy > textLayout.swc into the working SDK's frameworks/libs folder. But even > then, I think you have to worry about FB caching the SWC. > > HTH, > -Alex > >
Re: Building the SDK
Hi, > I guess I'd suggest using the Installer to set up a working SDK then copy > textLayout.swc into the working SDK's frameworks/libs folder. But even > then, I think you have to worry about FB caching the SWC. From my experience it doesn't cache the framework swcs that often (generally a ant in a project directory will be picked up by FB). On the rare occasion it does changing the project's SDK to another and then back again refreshes/resets the cache. Justin
Re: Building the SDK
On 9/1/13 10:57 PM, "Harbs" wrote: >I'm going around in circles hereŠ > >I have two problems. One with playerglobal.swc and another with >textLayout.swc > >1) When I link the develop SDK to a project, I get two swc links: >playerglobal.swc and "11.1". It can't find either of those. I can manage >to get the SDK to work by unlinking those and linking to a valid copy of >playerglobal on my machine. This is workable, but I'm concerned by why I >need to do that. It's also a pain to do this every time I want to use the >dev sdkŠ I just realized that this sort of thing is why we don't use the git repo folders as-is in FB. That's why we have the Installer and those scripts like makeApacheFlexForFLexBuilder. And why I don't use FB and just use the command line for MXMLC and FDB. I guess I'd suggest using the Installer to set up a working SDK then copy textLayout.swc into the working SDK's frameworks/libs folder. But even then, I think you have to worry about FB caching the SWC. HTH, -Alex
Re: Building the SDK
On 9/1/13 10:59 PM, "Harbs" wrote: >Okay. How do I do that? > >You are referring to build.xml in the tlf folder. Right? No. I've tried to do that and never figured it out. Instead: 1) Go to Project/Properties/Build Paths 2) Open the SDK folder 3) Open the textLayout.swc entry 4) Click on Source Attachment 5) Click Edit button on the right and set it properly. > >On Sep 2, 2013, at 8:50 AM, Alex Harui wrote: > >> On second thought, you may need to set up the source attachment in your >> build properties. >
Re: Building the SDK
Here's what I see in the build.xml: IMXMLObject Where is the source directory defined? On Sep 2, 2013, at 8:59 AM, Harbs wrote: > Okay. How do I do that? > > You are referring to build.xml in the tlf folder. Right? > > On Sep 2, 2013, at 8:50 AM, Alex Harui wrote: > >> On second thought, you may need to set up the source attachment in your >> build properties. >
Re: Building the SDK
Okay. How do I do that? You are referring to build.xml in the tlf folder. Right? On Sep 2, 2013, at 8:50 AM, Alex Harui wrote: > On second thought, you may need to set up the source attachment in your > build properties.
Re: Building the SDK
I'm going around in circles here… I have two problems. One with playerglobal.swc and another with textLayout.swc 1) When I link the develop SDK to a project, I get two swc links: playerglobal.swc and "11.1". It can't find either of those. I can manage to get the SDK to work by unlinking those and linking to a valid copy of playerglobal on my machine. This is workable, but I'm concerned by why I need to do that. It's also a pain to do this every time I want to use the dev sdk… 2) textLayout.swc works, but I does not get linked to source. When I try to jump to the source of any TLF classes I get an error that the source cannot be found. I tried linking to textLayout.swc in the tlf folder instead and I have the same problem. I'm able to recompile and test my changes, but I can't do any real debugging if it does not link to the source… Any ideas on how I can fix this? Harbs On Sep 2, 2013, at 8:30 AM, Alex Harui wrote: > > > On 9/1/13 10:21 PM, "Harbs" wrote: > >> Okay. Makes sense. >> >> And how do you set breakpoints in the code? > I'm not using FB. FDB allows me to set breakpoints just fine. FB should > too given that it will use the path in the SWC that you built on your > machine so it should be an exact match. >> >> Does it make sense to include the swcs in the TLF folder instead of the >> ones in the sdk folder? > The build script in flex-sdk/frameworks/projects/textLayout should copy > the SWCs from wherever flex-tlf puts it. > > -Alex >
Re: Building the SDK
On 9/1/13 10:30 PM, "Alex Harui" wrote: > > >On 9/1/13 10:21 PM, "Harbs" wrote: > >>Okay. Makes sense. >> >>And how do you set breakpoints in the code? >I'm not using FB. FDB allows me to set breakpoints just fine. FB should >too given that it will use the path in the SWC that you built on your >machine so it should be an exact match. On second thought, you may need to set up the source attachment in your build properties. >> >>Does it make sense to include the swcs in the TLF folder instead of the >>ones in the sdk folder? >The build script in flex-sdk/frameworks/projects/textLayout should copy >the SWCs from wherever flex-tlf puts it. > >-Alex >
Re: Mailing Forums
Hi, Nice one. BTW Still waiting on Nabble to import the archives but they have them now. Justin
Re: Mailing Forums
Nice! I didn't know you could control the final fragment. On 9/1/13 10:22 PM, "OmPrakash Muppirala" wrote: >I have created shortened urls using s.apache.org for these two forums: > >http://s.apache.org/flex-dev-forum > >http://s.apache.org/flex-users-forum > >Thanks, >Om
Re: Building the SDK
On 9/1/13 10:21 PM, "Harbs" wrote: >Okay. Makes sense. > >And how do you set breakpoints in the code? I'm not using FB. FDB allows me to set breakpoints just fine. FB should too given that it will use the path in the SWC that you built on your machine so it should be an exact match. > >Does it make sense to include the swcs in the TLF folder instead of the >ones in the sdk folder? The build script in flex-sdk/frameworks/projects/textLayout should copy the SWCs from wherever flex-tlf puts it. -Alex
Re: Mailing Forums
I have created shortened urls using s.apache.org for these two forums: http://s.apache.org/flex-dev-forum http://s.apache.org/flex-users-forum Thanks, Om
Re: Building the SDK
Okay. Makes sense. And how do you set breakpoints in the code? Does it make sense to include the swcs in the TLF folder instead of the ones in the sdk folder? On Sep 2, 2013, at 6:29 AM, Alex Harui wrote: > > > On 9/1/13 3:07 PM, "Harbs" wrote: > >> So how does Flash Builder know where the source is? > IIRC, when we package up everything for a release, we copy the TLF code > into the frameworks/projects/textLayout folder. > > But because we had problems with Git handling the mapping of source from > the flex-tlf repo into the flex-sdk repo, when developing, we leave the > source separate. > > FWIW, my workflow in the TLF work I did was to make changes in > flex-tlf/textLayout/src, run ant from the > flex-sdk/frameworks/projects/textLayout then re-compile the test case. Of > course, I wasn't using FB which might cache the SWC and require restarts > after each ant run. > >> >> On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote: >> >>> Hi, >>> Is the TLF source files supposed to be copied to the flex sdk folder when building the sdk? >>> No, it's left where it is. >>> >>> Justin >>> >> >
Re: Building the SDK
On 9/1/13 3:07 PM, "Harbs" wrote: >So how does Flash Builder know where the source is? IIRC, when we package up everything for a release, we copy the TLF code into the frameworks/projects/textLayout folder. But because we had problems with Git handling the mapping of source from the flex-tlf repo into the flex-sdk repo, when developing, we leave the source separate. FWIW, my workflow in the TLF work I did was to make changes in flex-tlf/textLayout/src, run ant from the flex-sdk/frameworks/projects/textLayout then re-compile the test case. Of course, I wasn't using FB which might cache the SWC and require restarts after each ant run. > >On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote: > >> Hi, >> >>> Is the TLF source files supposed to be copied to the flex sdk folder >>>when building the sdk? >> No, it's left where it is. >> >> Justin >> >
Re: Build failed in Jenkins: flex-sdk_mustella #282
On 9/1/13 6:42 PM, "Justin Mclean" wrote: >Hi, > >> [java] = >> [java] Failed: >> [java] = >> [java] >>gumbo/components/DataGrid/Properties/DataGrid_Properties_editable >>Editable_startItemEditorSesision_inValidParams Failed Timed out >> [java] >> [java] >> [java] = >> [java] Passes: 6 >> [java] Fails: 1 >> [java] = >> [java] >> [java] >> [java] Wrote summary to results.txt >> [java] Wrote failures to failures.txt > >This test is failing because it's (correctly) throwing an out of range >RTE (It's passing columns.length to startItemEditorSession which uses >getItemAt and length is out of range). Can't recall any changes recently >to this code, either startItemEditorSession or getItemAt so does anyone >know how this test passed previously? Check past results. I believe this test started to fail when you checked in a change suggested by someone at 360|Stack. -Alex
Re: Build failed in Jenkins: flex-sdk_mustella #282
Hi, > [java] = > [java]Failed: > [java] = > [java] gumbo/components/DataGrid/Properties/DataGrid_Properties_editable > Editable_startItemEditorSesision_inValidParams Failed Timed out > [java] > [java] > [java] = > [java] Passes: 6 > [java] Fails: 1 > [java] = > [java] > [java] > [java] Wrote summary to results.txt > [java] Wrote failures to failures.txt This test is failing because it's (correctly) throwing an out of range RTE (It's passing columns.length to startItemEditorSession which uses getItemAt and length is out of range). Can't recall any changes recently to this code, either startItemEditorSession or getItemAt so does anyone know how this test passed previously? Thanks, Justin
Re: Building the SDK
So how does Flash Builder know where the source is? On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote: > Hi, > >> Is the TLF source files supposed to be copied to the flex sdk folder when >> building the sdk? > No, it's left where it is. > > Justin >
Re: Building the SDK
Hi, > Is the TLF source files supposed to be copied to the flex sdk folder when > building the sdk? No, it's left where it is. Justin
Re: Building the SDK
I think so. I added it to the env.properties file. I believe it's working because otherwise I would not get the textLayout.swc files. No? Here's my env.properties file (in flex-sdk -- minus all the comments…) env.AIR_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/AdobeAIRSDK/ env.TLF_HOME=/Users/harbs/Documents/ApacheFlex/git/flex-tlf/ env.PLAYERGLOBAL_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/player/ env.PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ Is the TLF source files supposed to be copied to the flex sdk folder when building the sdk? On Sep 2, 2013, at 12:47 AM, Justin Mclean wrote: > HI, > >> I redid everything from scratch. Everything went smoother this time, but I >> still can not connect to the TLF source. > > Probably a silly question but is TLF_HOME correctly set? > > Justin
Re: Building the SDK
HI, > I redid everything from scratch. Everything went smoother this time, but I > still can not connect to the TLF source. Probably a silly question but is TLF_HOME correctly set? Justin
RE: Building the SDK
Look good to me, see
https://fisheye6.atlassian.com/browse/flex-sdk/frameworks/projects/textLayou
t/build.xml?r=4f20635628acdc09e8739c5f94ec644d20cbd959
-Message d'origine-
De : Harbs [mailto:harbs.li...@gmail.com]
Envoyé : dimanche 1 septembre 2013 23:35
À : dev@flex.apache.org
Objet : Re: Building the SDK
I redid everything from scratch. Everything went smoother this time, but I
still can not connect to the TLF source.
Here's what I have:
git
flex-tlf
--etc...
flex-sdk
frameworks
libs
textLayout.swc (along with all the other swcs)
player
(all the versions)
locale
en_US
textLayout_rb.swc (along with all the other rb swcs)
projects
textLayout (with no source -- all other projects have source.)
That seems logical to me since TLF is in another repro, but how is the SDK
supposed to find the TLF source?
Harbs
On Sep 1, 2013, at 11:09 PM, Harbs wrote:
> I have a feeling my problems might stem from the fact that my git repro is
named differently.
>
> I'm re-downloading the whole repro and starting from scratch with the
> standard names
>
> Tomorrow is another day
>
> On Sep 1, 2013, at 10:55 PM, Harbs wrote:
>
>> Okay. I solved this one, but I'm only getting source for core Flex
components. (i.e. I get source for Spark components, but I don't get source
for TLF stuff:
>> "Source could not be found for flashx.textLayout.edit.EditManager in
\Users\harbs\blabla\textLayout.swc"
>>
>> How do I properly link TLF to the rest of the SDK?
>>
>> On Sep 1, 2013, at 9:56 PM, Harbs wrote:
>>
>>> When specifying the paths in env.protperties, the spaces don't cause any
problems.
>>>
>>> But it looks like my issues are not finished. I get this error when I
try to actually use the SDK:
>>> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
SDK/frameworks//Users/harbs/Documents/Apache
Flex/Dependencies/player//11.1/playerglobal.swc'
>>>
>>> I'm not sure where I'm supposed to fix this (really wonky) path
>>>
>>> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>>>
I set all the variables in the env.properties file instead of via
the command line and that seems to have resolved the problem.
Weird
Next time I'll try with the spaces and see what happens.
Harbs
On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
> Use set command to dump environment. Maybe a hidden char in there?
>
>
>
>
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Harbs wrote:
>
>
> Still no go:
>
> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>
> check-playerglobal-home:
> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME} [echo]
> playerglobal.version is 11.1
>
> BUILD FAILED
> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
> environment variable PLAYERGLOBAL_HOME is not set to a directory
>
> Total time: 0 seconds
>
> It's been a while since I felt like such an idiot
;-)
>
> Maybe I'll try to restart my machine a bit later
>
> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>
>> Hi,
>>
>> There's still a space in the path - try removing that? I know it was
an issue early on but thought it had been fixed - perhaps not.
>>
>>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>
>> Thanks,
>> Justin
>>
>>
>
>>>
>>
>
Re: Building the SDK
I redid everything from scratch. Everything went smoother this time, but I
still can not connect to the TLF source.
Here's what I have:
git
flex-tlf
--etc...
flex-sdk
frameworks
libs
textLayout.swc (along with all the other swcs)
player
(all the versions)
locale
en_US
textLayout_rb.swc (along with all the other rb swcs)
projects
textLayout (with no source -- all other projects have source.)
That seems logical to me since TLF is in another repro, but how is the SDK
supposed to find the TLF source?
Harbs
On Sep 1, 2013, at 11:09 PM, Harbs wrote:
> I have a feeling my problems might stem from the fact that my git repro is
> named differently.
>
> I'm re-downloading the whole repro and starting from scratch with the
> standard names…
>
> Tomorrow is another day…
>
> On Sep 1, 2013, at 10:55 PM, Harbs wrote:
>
>> Okay. I solved this one, but I'm only getting source for core Flex
>> components. (i.e. I get source for Spark components, but I don't get source
>> for TLF stuff:
>> "Source could not be found for flashx.textLayout.edit.EditManager in
>> \Users\harbs\blabla\textLayout.swc"
>>
>> How do I properly link TLF to the rest of the SDK?
>>
>> On Sep 1, 2013, at 9:56 PM, Harbs wrote:
>>
>>> When specifying the paths in env.protperties, the spaces don't cause any
>>> problems.
>>>
>>> But it looks like my issues are not finished. I get this error when I try
>>> to actually use the SDK:
>>> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
>>> SDK/frameworks//Users/harbs/Documents/Apache
>>> Flex/Dependencies/player//11.1/playerglobal.swc'
>>>
>>> I'm not sure where I'm supposed to fix this (really wonky) path…
>>>
>>> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>>>
I set all the variables in the env.properties file instead of via the
command line and that seems to have resolved the problem. Weird…
Next time I'll try with the spaces and see what happens.
Harbs
On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
> Use set command to dump environment. Maybe a hidden char in there?
>
>
>
>
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Harbs wrote:
>
>
> Still no go:
>
> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>
> check-playerglobal-home:
> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
> [echo] playerglobal.version is 11.1
>
> BUILD FAILED
> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
> environment variable PLAYERGLOBAL_HOME is not set to a directory
>
> Total time: 0 seconds
>
> It's been a while since I felt like such an idiot… ;-)
>
> Maybe I'll try to restart my machine a bit later…
>
> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>
>> Hi,
>>
>> There's still a space in the path - try removing that? I know it was an
>> issue early on but thought it had been fixed - perhaps not.
>>
>>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>
>> Thanks,
>> Justin
>>
>>
>
>>>
>>
>
Re: Building the SDK
I have a feeling my problems might stem from the fact that my git repro is
named differently.
I'm re-downloading the whole repro and starting from scratch with the standard
names…
Tomorrow is another day…
On Sep 1, 2013, at 10:55 PM, Harbs wrote:
> Okay. I solved this one, but I'm only getting source for core Flex
> components. (i.e. I get source for Spark components, but I don't get source
> for TLF stuff:
> "Source could not be found for flashx.textLayout.edit.EditManager in
> \Users\harbs\blabla\textLayout.swc"
>
> How do I properly link TLF to the rest of the SDK?
>
> On Sep 1, 2013, at 9:56 PM, Harbs wrote:
>
>> When specifying the paths in env.protperties, the spaces don't cause any
>> problems.
>>
>> But it looks like my issues are not finished. I get this error when I try to
>> actually use the SDK:
>> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
>> SDK/frameworks//Users/harbs/Documents/Apache
>> Flex/Dependencies/player//11.1/playerglobal.swc'
>>
>> I'm not sure where I'm supposed to fix this (really wonky) path…
>>
>> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>>
>>> I set all the variables in the env.properties file instead of via the
>>> command line and that seems to have resolved the problem. Weird…
>>>
>>> Next time I'll try with the spaces and see what happens.
>>>
>>> Harbs
>>>
>>> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>>>
Use set command to dump environment. Maybe a hidden char in there?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Harbs wrote:
Still no go:
Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
environment variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
It's been a while since I felt like such an idiot… ;-)
Maybe I'll try to restart my machine a bit later…
On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
> Hi,
>
> There's still a space in the path - try removing that? I know it was an
> issue early on but thought it had been fixed - perhaps not.
>
>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>
> Thanks,
> Justin
>
>
>>>
>>
>
Re: Building the SDK
Okay. I solved this one, but I'm only getting source for core Flex components.
(i.e. I get source for Spark components, but I don't get source for TLF stuff:
"Source could not be found for flashx.textLayout.edit.EditManager in
\Users\harbs\blabla\textLayout.swc"
How do I properly link TLF to the rest of the SDK?
On Sep 1, 2013, at 9:56 PM, Harbs wrote:
> When specifying the paths in env.protperties, the spaces don't cause any
> problems.
>
> But it looks like my issues are not finished. I get this error when I try to
> actually use the SDK:
> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
> SDK/frameworks//Users/harbs/Documents/Apache
> Flex/Dependencies/player//11.1/playerglobal.swc'
>
> I'm not sure where I'm supposed to fix this (really wonky) path…
>
> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>
>> I set all the variables in the env.properties file instead of via the
>> command line and that seems to have resolved the problem. Weird…
>>
>> Next time I'll try with the spaces and see what happens.
>>
>> Harbs
>>
>> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>>
>>> Use set command to dump environment. Maybe a hidden char in there?
>>>
>>>
>>>
>>>
>>> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>>>
>>> Harbs wrote:
>>>
>>>
>>> Still no go:
>>>
>>> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>>>
>>> check-playerglobal-home:
>>> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
>>> [echo] playerglobal.version is 11.1
>>>
>>> BUILD FAILED
>>> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
>>> environment variable PLAYERGLOBAL_HOME is not set to a directory
>>>
>>> Total time: 0 seconds
>>>
>>> It's been a while since I felt like such an idiot… ;-)
>>>
>>> Maybe I'll try to restart my machine a bit later…
>>>
>>> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>>>
Hi,
There's still a space in the path - try removing that? I know it was an
issue early on but thought it had been fixed - perhaps not.
> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
Thanks,
Justin
>>>
>>
>
Re: Building the SDK
When specifying the paths in env.protperties, the spaces don't cause any
problems.
But it looks like my issues are not finished. I get this error when I try to
actually use the SDK:
unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
SDK/frameworks//Users/harbs/Documents/Apache
Flex/Dependencies/player//11.1/playerglobal.swc'
I'm not sure where I'm supposed to fix this (really wonky) path…
On Sep 1, 2013, at 8:20 PM, Harbs wrote:
> I set all the variables in the env.properties file instead of via the command
> line and that seems to have resolved the problem. Weird…
>
> Next time I'll try with the spaces and see what happens.
>
> Harbs
>
> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>
>> Use set command to dump environment. Maybe a hidden char in there?
>>
>>
>>
>>
>> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>>
>> Harbs wrote:
>>
>>
>> Still no go:
>>
>> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>>
>> check-playerglobal-home:
>>[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
>>[echo] playerglobal.version is 11.1
>>
>> BUILD FAILED
>> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
>> variable PLAYERGLOBAL_HOME is not set to a directory
>>
>> Total time: 0 seconds
>>
>> It's been a while since I felt like such an idiot… ;-)
>>
>> Maybe I'll try to restart my machine a bit later…
>>
>> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>>
>>> Hi,
>>>
>>> There's still a space in the path - try removing that? I know it was an
>>> issue early on but thought it had been fixed - perhaps not.
>>>
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>>
>>> Thanks,
>>> Justin
>>>
>>>
>>
>
Re: Building the SDK
I set all the variables in the env.properties file instead of via the command
line and that seems to have resolved the problem. Weird…
Next time I'll try with the spaces and see what happens.
Harbs
On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
> Use set command to dump environment. Maybe a hidden char in there?
>
>
>
>
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Harbs wrote:
>
>
> Still no go:
>
> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>
> check-playerglobal-home:
> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
> [echo] playerglobal.version is 11.1
>
> BUILD FAILED
> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
> variable PLAYERGLOBAL_HOME is not set to a directory
>
> Total time: 0 seconds
>
> It's been a while since I felt like such an idiot… ;-)
>
> Maybe I'll try to restart my machine a bit later…
>
> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>
>> Hi,
>>
>> There's still a space in the path - try removing that? I know it was an
>> issue early on but thought it had been fixed - perhaps not.
>>
>>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>
>> Thanks,
>> Justin
>>
>>
>
Re: Shift Enter in TLF
On Sep 1, 2013, at 5:59 PM, Alex Harui wrote: > If not static how will someone change the value? Something like this: var em:EditManager = new EditManager(new UndoManager()); em.tlf_internal::handleShiftAsSoftReturn = false; textFlow.interactionManager = em; (or it can be a proper attribute) > Redo key seems platform specific. Y is default on windows? Command+Shift Z is default on Mac… > > > > Sent via the PANTECH Discover, an AT&T 4G LTE smartphone. > > Harbs wrote: > > > Okay. As soon as I manage to build the SDK I'll be able to test my changes… > > I'm putting the flag into EditManager rather than ContainerController. That > seems to make more sense to me. Please raise objections if you disagree. > Also, should the flag be static, or does it make sense to make it a property > of the class instance? (That way different EditManagers in the same app could > have different behaviors.) I don't really see a use case to having different > behaviors in the same app… (but then again I don't see why someone wouldn't > want to allow soft returns…) ;-) > > Once I'm making changes to EditManager, what about enabling shift+ > command/control Z for redo? Currently, you need to use command/control y > instead of the more standard shift modifier. Is there any reason that I'm not > aware of that makes enabling the shift modifier a bad idea? > > Harbs > > On Sep 1, 2013, at 7:52 AM, Alex Harui wrote: > >> OK, pushed my changes. Have fun. >> >> On 8/31/13 9:40 PM, "Alex Harui" wrote: >> >>> >>> >>> On 8/31/13 9:31 PM, "Harbs" wrote: >>> Do you mean the user would have to manually set back the version number when they compile? That does sound like a bitter pill to swallow. Setting internal variables sounds much more palatable to me. I'll create an internal bool handleShiftAsSoftReturn which will default to true. Makes sense? >>> Yep, that's what I would do. >>> >>> >>> Let me check in my most recent changes to support discretionary hyphens >>> before you get started so we don't get merge conflicts. >>> >>> -Alex >>> >> >
Re: Shift Enter in TLF
If not static how will someone change the value? Redo key seems platform specific. Y is default on windows? Sent via the PANTECH Discover, an AT&T 4G LTE smartphone. Harbs wrote: Okay. As soon as I manage to build the SDK I'll be able to test my changes… I'm putting the flag into EditManager rather than ContainerController. That seems to make more sense to me. Please raise objections if you disagree. Also, should the flag be static, or does it make sense to make it a property of the class instance? (That way different EditManagers in the same app could have different behaviors.) I don't really see a use case to having different behaviors in the same app… (but then again I don't see why someone wouldn't want to allow soft returns…) ;-) Once I'm making changes to EditManager, what about enabling shift+ command/control Z for redo? Currently, you need to use command/control y instead of the more standard shift modifier. Is there any reason that I'm not aware of that makes enabling the shift modifier a bad idea? Harbs On Sep 1, 2013, at 7:52 AM, Alex Harui wrote: > OK, pushed my changes. Have fun. > > On 8/31/13 9:40 PM, "Alex Harui" wrote: > >> >> >> On 8/31/13 9:31 PM, "Harbs" wrote: >> >>> Do you mean the user would have to manually set back the version number >>> when they compile? >>> >>> That does sound like a bitter pill to swallow. Setting internal variables >>> sounds much more palatable to me. >>> >>> I'll create an internal bool handleShiftAsSoftReturn which will default >>> to true. >>> >>> Makes sense? >> Yep, that's what I would do. >> >> >> Let me check in my most recent changes to support discretionary hyphens >> before you get started so we don't get merge conflicts. >> >> -Alex >> >
Re: Building the SDK
Use set command to dump environment. Maybe a hidden char in there?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Harbs wrote:
Still no go:
Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
It's been a while since I felt like such an idiot… ;-)
Maybe I'll try to restart my machine a bit later…
On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
> Hi,
>
> There's still a space in the path - try removing that? I know it was an issue
> early on but thought it had been fixed - perhaps not.
>
>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>
> Thanks,
> Justin
>
>
Re: Building the SDK
Still no go:
Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
It's been a while since I felt like such an idiot… ;-)
Maybe I'll try to restart my machine a bit later…
On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
> Hi,
>
> There's still a space in the path - try removing that? I know it was an issue
> early on but thought it had been fixed - perhaps not.
>
>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>
> Thanks,
> Justin
>
>
Re: Building the SDK
Hi, There's still a space in the path - try removing that? I know it was an issue early on but thought it had been fixed - perhaps not. > /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml Thanks, Justin
Re: Building the SDK
Never mind. I was missing Documents from the path. Removing the space helps,
but it is still not working:
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
Gavriels-MacBook-Air:Flex SDK harbs$ ls $PLAYERGLOBAL_HOME
11.1
Gavriels-MacBook-Air:Flex SDK harbs$ ls $PLAYERGLOBAL_HOME/11.1
playerglobal.swc
On Sep 1, 2013, at 4:08 PM, Harbs wrote:
> Bah. Removing the space did not help:
>
> check-playerglobal-home:
> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
> [echo] playerglobal.version is 11.1
>
> BUILD FAILED
> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml:168: The environment
> variable PLAYERGLOBAL_HOME is not set to a directory
>
> Total time: 0 seconds
>
> Gavriels-MacBook-Air:Flex SDK harbs$ echo $PLAYERGLOBAL_HOME
> /Users/harbs/ApacheFlex/Dependencies/player/
>
> I have other work I need to do. I'll come back to this later…
>
> On Sep 1, 2013, at 4:00 PM, Justin Mclean wrote:
>
>> Hi,
>>
>> Your structure looks fine, double check the env variable are full paths not
>> relative, otherwise it may be that there's still an issue with spaces in
>> paths in the build files.
>>
>> Justin
>
Re: Building the SDK
Bah. Removing the space did not help:
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
Gavriels-MacBook-Air:Flex SDK harbs$ echo $PLAYERGLOBAL_HOME
/Users/harbs/ApacheFlex/Dependencies/player/
I have other work I need to do. I'll come back to this later…
On Sep 1, 2013, at 4:00 PM, Justin Mclean wrote:
> Hi,
>
> Your structure looks fine, double check the env variable are full paths not
> relative, otherwise it may be that there's still an issue with spaces in
> paths in the build files.
>
> Justin
Re: Building the SDK
Nope. Escaping the paths does not help. (The variable cannot be set at all.) I guess I'll remove the space in the paths… On Sep 1, 2013, at 4:00 PM, Harbs wrote: > Okay. Getting somewhere… > > It looks like it's splitting the space into two separate paths: > ls: /Users/harbs/Apache: No such file or directory > ls: Flex/Dependencies/player/: No such file or directory > > Does the build script not support vars with spaces? Do I need to double > escape the variable? > > I'm setting it like this: > PLAYERGLOBAL_HOME=/Users/harbs/Apache\ Flex/Dependencies/player/ > > I'll try to double escape the spaces and see if that helps… > > On Sep 1, 2013, at 3:54 PM, Justin Mclean wrote: > >> Hi, >> >>> The variable is set: >>> echo $PLAYERGLOBAL_HOME >>> /Users/harbs/Apache Flex/Dependencies/player/ >>> >>> And the file structure looks like this: >>> /Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc >>> (I only added 11.1) >> >> Looks OK to me but try this: >> ls $PLAYERGLOBAL_HOME >> >> I get: >> 10.0 10.110.210.311.011.111.211.311.411.5 >> 11.611.711.8 >> >> And in each directory is a playerglobal.swc. eg >> ls $PLAYERGLOBAL_HOME/11.5 >> gives: >> playerglobal.swc >> >> You might want to check frameworks/flex-config.xml and see what that >> target-player is set to 11.1 like so " 11.1". >> >> Justin >> >
Re: Building the SDK
Okay. Getting somewhere… It looks like it's splitting the space into two separate paths: ls: /Users/harbs/Apache: No such file or directory ls: Flex/Dependencies/player/: No such file or directory Does the build script not support vars with spaces? Do I need to double escape the variable? I'm setting it like this: PLAYERGLOBAL_HOME=/Users/harbs/Apache\ Flex/Dependencies/player/ I'll try to double escape the spaces and see if that helps… On Sep 1, 2013, at 3:54 PM, Justin Mclean wrote: > Hi, > >> The variable is set: >> echo $PLAYERGLOBAL_HOME >> /Users/harbs/Apache Flex/Dependencies/player/ >> >> And the file structure looks like this: >> /Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc >> (I only added 11.1) > > Looks OK to me but try this: > ls $PLAYERGLOBAL_HOME > > I get: > 10.0 10.110.210.311.011.111.211.311.411.5 > 11.611.711.8 > > And in each directory is a playerglobal.swc. eg > ls $PLAYERGLOBAL_HOME/11.5 > gives: > playerglobal.swc > > You might want to check frameworks/flex-config.xml and see what that > target-player is set to 11.1 like so " 11.1". > > Justin >
Re: Building the SDK
Hi, Your structure looks fine, double check the env variable are full paths not relative, otherwise it may be that there's still an issue with spaces in paths in the build files. Justin
Re: Building the SDK
Hi, > The variable is set: > echo $PLAYERGLOBAL_HOME > /Users/harbs/Apache Flex/Dependencies/player/ > > And the file structure looks like this: > /Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc > (I only added 11.1) Looks OK to me but try this: ls $PLAYERGLOBAL_HOME I get: 10.010.110.210.311.011.111.211.311.411.5 11.611.711.8 And in each directory is a playerglobal.swc. eg ls $PLAYERGLOBAL_HOME/11.5 gives: playerglobal.swc You might want to check frameworks/flex-config.xml and see what that target-player is set to 11.1 like so " 11.1". Justin
Re: Building the SDK
I'm really not having a lot of luck today… I tried building TLF separately just to see what happens and it seems to be looking for "flex-sdk" one level up from TLF: Buildfile: /Users/harbs/Documents/Apache Flex/git/TLF/build.xml [echo] FLEX_HOME is /Users/harbs/Documents/Apache Flex/git/TLF/../flex-sdk BUILD FAILED /Users/harbs/Documents/Apache Flex/git/TLF/build.xml:65: /Users/harbs/Documents/Apache Flex/git/flex-sdk does not exist. My structure looks like this: Documents Apache Flex git Flex SDK (the full sdk repro) TLF Is this wrong? On Sep 1, 2013, at 2:50 PM, Justin Mclean wrote: > Hi, > >> It's been a while since I tried to build the SDK from source and I don't >> remember the details. > > Just follow the README, basically check out the sdk and tlf repos and then > set up the required environment vars and do an "ant main". > > Example environment vars on OSX > ANT_HOME=/usr/share/ant > AIR_HOME=/Users/justinmclean/Documents/air/mac/AdobeAIRSDK/ > PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ > PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel > Bender Toolkit 2/ > TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ > > May also need this if doing a full release. > ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe > Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 > > Hope that helps, > Justin >
Re: FlexUnit
Does flexUnit plan on making a mocking framework built in? The documentation on Mockolate and other frameworks seems to have just died mid devleopment, and the code doesn't match the docs or the forums anymore. :( brought to you by the letters A, V, and I and the number 47 On Fri, Aug 30, 2013 at 4:24 PM, Michael A. Labriola wrote: >>It was 6 now it's 7 still failing :-( > > Okay, the only thing that makes sense though is a mismatch. Possible there > are two JDKs on the box, one that is in your JAVA_HOME but another being used > for the compilation? I ask because this error is fairly well documented in > the Java community for other projects as a version mismatch. > > Mike >
Re: Building the SDK
I'm getting this error:
heck-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/Apache Flex/git/Flex SDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
The variable is set:
echo $PLAYERGLOBAL_HOME
/Users/harbs/Apache Flex/Dependencies/player/
And the file structure looks like this:
/Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc
(I only added 11.1)
Any suggestions on what I'm doing wrong?
On Sep 1, 2013, at 3:03 PM, Justin Mclean wrote:
> Hi,
>
> BTW building the SDK and even making it a usable SDK leaves git reasonably
> clean. That way you don't always need to do a full build but just build the
> project you need (taking under a minute compared to 7-8 minutes for a full
> build).
>
> Thanks,
> Justin
Re: Building the SDK
Ah. The readme… :-X Thanks for the list of envoronment vars. That was helpful. Thanks! Harbs On Sep 1, 2013, at 2:50 PM, Justin Mclean wrote: > Hi, > >> It's been a while since I tried to build the SDK from source and I don't >> remember the details. > > Just follow the README, basically check out the sdk and tlf repos and then > set up the required environment vars and do an "ant main". > > Example environment vars on OSX > ANT_HOME=/usr/share/ant > AIR_HOME=/Users/justinmclean/Documents/air/mac/AdobeAIRSDK/ > PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ > PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel > Bender Toolkit 2/ > TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ > > May also need this if doing a full release. > ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe > Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 > > Hope that helps, > Justin >
Re: Building the SDK
Hi, BTW building the SDK and even making it a usable SDK leaves git reasonably clean. That way you don't always need to do a full build but just build the project you need (taking under a minute compared to 7-8 minutes for a full build). Thanks, Justin
Re: Building the SDK
Hi, > It's been a while since I tried to build the SDK from source and I don't > remember the details. Just follow the README, basically check out the sdk and tlf repos and then set up the required environment vars and do an "ant main". Example environment vars on OSX ANT_HOME=/usr/share/ant AIR_HOME=/Users/justinmclean/Documents/air/mac/AdobeAIRSDK/ PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ May also need this if doing a full release. ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 Hope that helps, Justin
Re: Building the SDK
I run such a different setup then the majority here, not sure how much config I can give... but as for keeping your Git Repositories clean, I use one way file syncing. Meaning I sync the files from Git to my SDK build folder. The only downside is having to rebuild the SDK (6-7 mins) after you do that. It does keep your environment clean though. -Mark On Sun, Sep 1, 2013 at 6:29 AM, Harbs wrote: > It's been a while since I tried to build the SDK from source and I don't > remember the details. > > Assuming I have the git repository on my machine, what's the recommended > process for building the SDK while retaining the ability to debug the > source? (without messing up the git directories…) > > I tried looking around the wiki, but did not see instructions (sorry if I > missed it). Any pointers would be very much appreciated! > > Harbs
Re: Shift Enter in TLF
Okay. As soon as I manage to build the SDK I'll be able to test my changes… I'm putting the flag into EditManager rather than ContainerController. That seems to make more sense to me. Please raise objections if you disagree. Also, should the flag be static, or does it make sense to make it a property of the class instance? (That way different EditManagers in the same app could have different behaviors.) I don't really see a use case to having different behaviors in the same app… (but then again I don't see why someone wouldn't want to allow soft returns…) ;-) Once I'm making changes to EditManager, what about enabling shift+ command/control Z for redo? Currently, you need to use command/control y instead of the more standard shift modifier. Is there any reason that I'm not aware of that makes enabling the shift modifier a bad idea? Harbs On Sep 1, 2013, at 7:52 AM, Alex Harui wrote: > OK, pushed my changes. Have fun. > > On 8/31/13 9:40 PM, "Alex Harui" wrote: > >> >> >> On 8/31/13 9:31 PM, "Harbs" wrote: >> >>> Do you mean the user would have to manually set back the version number >>> when they compile? >>> >>> That does sound like a bitter pill to swallow. Setting internal variables >>> sounds much more palatable to me. >>> >>> I'll create an internal bool handleShiftAsSoftReturn which will default >>> to true. >>> >>> Makes sense? >> Yep, that's what I would do. >> >> >> Let me check in my most recent changes to support discretionary hyphens >> before you get started so we don't get merge conflicts. >> >> -Alex >> >
Building the SDK
It's been a while since I tried to build the SDK from source and I don't remember the details. Assuming I have the git repository on my machine, what's the recommended process for building the SDK while retaining the ability to debug the source? (without messing up the git directories…) I tried looking around the wiki, but did not see instructions (sorry if I missed it). Any pointers would be very much appreciated! Harbs
Re: Installer stats
Hi, > You're right. I was just looking at the 'stats' page and didn't make > the distinction. Still... a million dollars, baby! I like the stats on this page: https://www.ohloh.net/p/ApacheFlex 160,000 odd commits made by 50 contributors in 14 million lines of code and 4,340 years of effort! (of course most of that was Adobe). Justin
Re: Installer stats
You're right. I was just looking at the 'stats' page and didn't make the distinction. Still... a million dollars, baby! ;-) EdB On Sun, Sep 1, 2013 at 9:13 AM, Justin Mclean wrote: > Hi, > >> We're closing in on 10.000... within one month, no less! > By my count from google analytics we passed the 10,000 mark for all time a > while ago but we are only(!) around the 4200 mark since the 4.10 release. > There's been 15,000 total installs since we starting tracking installs. > > Of course this doesn't count downloads from the mirrors, manual installs, > installs from other sites, or someone packaging up the SDK and sharing it > about. > > Thanks, > Justin > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Installer stats
Hi, > We're closing in on 10.000... within one month, no less! By my count from google analytics we passed the 10,000 mark for all time a while ago but we are only(!) around the 4200 mark since the 4.10 release. There's been 15,000 total installs since we starting tracking installs. Of course this doesn't count downloads from the mirrors, manual installs, installs from other sites, or someone packaging up the SDK and sharing it about. Thanks, Justin
Re: Installer stats
Greate news .. ) On Aug 22, 2013 10:09 AM, "Justin Mclean" wrote: > Hi, > > Just an update on the installer stats (from this morning about 6 hours > ago), there have been over 2500 successful installs. > > Windows 4.10 - 1820 downloads (69%) > Mac 4.10 - 633 downloads (24%) > Windows 4.9.1 - 78 installs (3%) > Linux 4.10 - 16 installs (1%) > Mac 4.9.1 -16 installs (1%) > > Of course the total number of installs could be much larger, due to > installs from the mirrors or other places (eg softpedia) > > Thanks, > Justin
Re: Installer stats
We're closing in on 10.000... within one month, no less! If the SDK was sold for $99, we'd be close to making making our first million, how cool is that ;-) All kidding aside, this should make a pretty compelling business case that Apache Flex IS NOT DEAD. Let's make some noise on the interwebs about this! EdB On Thu, Aug 22, 2013 at 9:08 AM, Justin Mclean wrote: > Hi, > > Just an update on the installer stats (from this morning about 6 hours ago), > there have been over 2500 successful installs. > > Windows 4.10 - 1820 downloads (69%) > Mac 4.10 - 633 downloads (24%) > Windows 4.9.1 - 78 installs (3%) > Linux 4.10 - 16 installs (1%) > Mac 4.9.1 -16 installs (1%) > > Of course the total number of installs could be much larger, due to installs > from the mirrors or other places (eg softpedia) > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
