Failed.
Result:
[0]: 4 votes
[+1]: 2 votes
So we leave anything as it is.
Thanks for voting!
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
, January 19, 2019 8:42:42 PM
To: dev@flex.apache.org
Subject: Re: [Vote] Moving JIRA issues and Confluence Wiki to GitHub
+1
In 2018, 15 issues were created by using JIRA.
So I don't expect too many duplicates for the future.
If it is possible, we would set JIRA and the Conflucence Wiki read
+1
In 2018, 15 issues were created by using JIRA.
So I don't expect too many duplicates for the future.
If it is possible, we would set JIRA and the Conflucence Wiki read-only.
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
+1
El El vie, 18 ene 2019 a las 22:12, Tom Chiverton
escribió:
> Vote: -0
>
> I don't see there is much benefit, and it creates two streams of bugs. If
> it's
> true that Jira will be closed to new bugs but otherwise stay open, my vote
> changes to +0.
>
>
> --
> Tom
> Q. According to Intel the
Vote: -0
I don't see there is much benefit, and it creates two streams of bugs. If it's
true that Jira will be closed to new bugs but otherwise stay open, my vote
changes to +0.
--
Tom
Q. According to Intel the Pentium conforms to I.E.E.E. stnd. 754 and 854 for
floating point arithmetic. If y
Hi,
+0, as long as we won't make JIRA and Confluence read only.
Thanks,
Piotr
pt., 18 sty 2019 o 00:19 Justin Mclean napisał(a):
> Hi,
>
> +0 I see little reason to change and split where you need to look at
> things in two places.
>
> I assume that JIRA and Confluence will not be made read on
Hi,
+0 I see little reason to change and split where you need to look at things in
two places.
I assume that JIRA and Confluence will not be made read only?
Thanks,
Justin
Hi,
this is the official vote thread to approve the move from JIRA issues to
GitHub issues and to move the Confluence Wiki to the Github Wiki.
As discussed here [1], the idea is to don't migrate the JIRA issues to
GitHub. Instead, we want a clean restart at GitHub issues. The JIRA issues
wi
@Justin
> i’m that sure that it is. JIRA has a number of significant benefits over
> GitHub issues including better searching and querying. (Yes I use both).
Just to make sure that I got it right:
Does that mean that you basically support the idea of moving from JIRA to
GitHub issues or
+1
Especially those old Adobe issues that were imported. To me they are mostly
clutter because of the quantity, age, and missing attachments. I would much
rather have a clean start. But brining in any new (from a given time range x
number of months) wouldn't be a bonus, unless that
ases...
>
> We maybe could set or treat or freeze JIRA as read-only and could link to
> the entire Flex-JIRA from GitHub in order to not losing the history.
> If somebody is going to fix one of those existing JIRA issues we could
> simply recreate it manually as a GitHub issue.
&
is going to fix one of those existing JIRA issues we could
simply recreate it manually as a GitHub issue.
If somebody will file a new GitHub issue we may want to check if there's a
JIRA duplicate in order to link it from the GitHub issue.
But on the other hand, I don't believe when somebo
> Do we know if it possible it import all historical JIRA issues ...
I don't know it this is possible.
> JIRA has a number of significant benefits over GitHub issues including
> better searching and querying
JIRA is probably more powerful but I guess the simplicity of GitHub
Hi,
> I think it would be easier and more transparent for folks to handle future
> development (if it will happen) by using GitHub.
i’m that sure that it is. JIRA has a number of significant benefits over GitHub
issues including better searching and querying. (Yes I use both).
Do we k
Are we going to say that we won't fix any of the bugs currently open in JIRA?
That might be ok. It would help prioritize and make more clear what folks are
still interested in. My concern is having two active bug bases. You may still
end up referencing the JIRA bugs when marking new bugs as
I was thinking more like a cut of the old Wiki and JIRA than a migration of
the existing stuff.
I think it would be easier and more transparent for folks to handle future
development (if it will happen) by using GitHub.
We may migrate some wiki stuff someday, don't know.
Thanks,
Olaf
--
Sent
ribió:
> Hi,
> I would like to create an INFRA Jira in order to ask them to enable GitHub
> "Issues" and the "Wiki" for following repositories:
>
> - flex-tlf.git
> - flex-utilities.git
> - flex-flexunit.git
e to create an INFRA Jira in order to ask them to enable GitHub
> "Issues" and the "Wiki" for following repositories:
>
> - flex-tlf.git
> - flex-utilities.git
> - flex-flexunit.git
> - flex-site.git
> - flex-external.git
> - flex-sdk.git
> - f
Hi,
I would like to create an INFRA Jira in order to ask them to enable GitHub
"Issues" and the "Wiki" for following repositories:
- flex-tlf.git
- flex-utilities.git
- flex-flexunit.git
- flex-site.git
- flex-external.git
- flex-sdk.git
- flex-blazeds.git
-
Hi,
It looks like GitHub Issues has been enabled on the new Royale repos. The
Royale folks will no longer be watching Apache JIRA for issues related to
FlexJS and Royale. Existing FlexJS JIRA issues will not be automatically
migrated to GitHub Issues. If you have an open FlexJS issue in Apache
I just created a couple of JIRAs on compiler issues that have been bugging me
for a while.[1][2] Neither of these are super-important, but it would be nice
if it worked better.
Harbs
[1]https://issues.apache.org/jira/browse/FLEX-35340
<https://issues.apache.org/jira/browse/FLEX-35340&
t;
> > - Josh
> >
> > On Wed, Jul 5, 2017 at 6:13 PM, Nicholas Kwiatkowski
> > wrote:
> >
> > > Is anybody actually addressing the issues people have been reporting
> > about
> > > the installer and/or ANT script for Flex SDK 4.16.0?
> &g
le too.
>
> - Josh
>
> On Wed, Jul 5, 2017 at 6:13 PM, Nicholas Kwiatkowski
> wrote:
>
> > Is anybody actually addressing the issues people have been reporting
> about
> > the installer and/or ANT script for Flex SDK 4.16.0?
> >
> > Right now I see two ma
t;Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-VS-Code-dual-issues-tp62894p6
>2929.html&data=02
%40mail.gmail.com%3E
I looked into MD5 with PowerShell, and from what I could tell from a quick
search, that should be possible too.
- Josh
On Wed, Jul 5, 2017 at 6:13 PM, Nicholas Kwiatkowski
wrote:
> Is anybody actually addressing the issues people have been reporting about
> the install
p directive, but the
> >other way complains that it doesn't know how to deal with a dmg file, so
> >the ant script errors out. That one is an easy fix.
> >
> >-Nick
> >
> >
> >On Fri, Jul 7, 2017 at 1:54 AM, Alex Harui
> >wrote:
> >
>
t;
>On Fri, Jul 7, 2017 at 1:54 AM, Alex Harui
>wrote:
>
>> Maybe I wasn't clear enough:
>>
>> I don't think the version of Ant will affect the SSL issues. The SSL
>> issues should be solvable via the JCE upgrade:
>>
>>
>>https://na01.saf
e, but the
other way complains that it doesn't know how to deal with a dmg file, so
the ant script errors out. That one is an easy fix.
-Nick
On Fri, Jul 7, 2017 at 1:54 AM, Alex Harui wrote:
> Maybe I wasn't clear enough:
>
> I don't think the version of Ant will affec
ement
>> and other browser APIs here? I just want to be sure so that I test the
>> right thing when I make changes.
>>
>> - Josh
>>
>> On Thu, Jul 6, 2017 at 2:16 PM, Harbs wrote:
>>
>>> Since updating to “dual”has been reporting lots of errors. Whe
.nabble.com/4-16-0-Install-issues-tp62855p62930.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
-issues-tp62894p62929.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
794aed2c178decee1%7C0%7C0%7C63635001583
>1422210&sdata=ps7%2Fd3pmBt%2FY2pFquS9vvO5Dj2rJ8EohmcV7hfgU9F8%3D&reserved=
>0
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.n
Maybe I wasn't clear enough:
I don't think the version of Ant will affect the SSL issues. The SSL
issues should be solvable via the JCE upgrade:
http://stackoverflow.com/questions/38203971/javax-net-ssl-sslhandshakeexcep
tion-received-fatal-alert-handshake-failure/38264878#38264878
f
[1]https://issues.apache.org/jira/browse/FLEX-35315
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/4-16-0-Install-issues-tp62855p62919.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
of Ant.
>
> Thanks,
> -Alex
>
> On 7/5/17, 6:13 PM, "Nicholas Kwiatkowski" wrote:
>
> >Is anybody actually addressing the issues people have been reporting about
> >the installer and/or ANT script for Flex SDK 4.16.0?
> >
> >Right now I see
o be clear, are you referring to DOM classes like
>>HTMLButtonElement
>> and other browser APIs here? I just want to be sure so that I test the
>> right thing when I make changes.
>>
>> - Josh
>>
>> On Thu, Jul 6, 2017 at 2:16 PM, Harbs wrote:
>>
&
ts is specifically JSFlex.
>>
>> > a. I’m not getting JS specific classes recognized.
>>
>> Just to be clear, are you referring to DOM classes like
>>HTMLButtonElement
>> and other browser APIs here? I just want to be sure so that I test the
>> right thi
r APIs here? I just want to be sure so that I test the
> right thing when I make changes.
>
> - Josh
>
> On Thu, Jul 6, 2017 at 2:16 PM, Harbs wrote:
>
>> Since updating to “dual”has been reporting lots of errors. When I build,
>> both the debug and release builds buil
t 2:16 PM, Harbs wrote:
> Since updating to “dual”has been reporting lots of errors. When I build,
> both the debug and release builds build correctly, but the PROBLEMS window
> and the live code hinting report lots of (non) issues. I’m not sure what
> the source of the errors are, b
Since updating to “dual”has been reporting lots of errors. When I build, both
the debug and release builds build correctly, but the PROBLEMS window and the
live code hinting report lots of (non) issues. I’m not sure what the source of
the errors are, but here are the details:
I’ve tried a few
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/4-16-0-Install-issues-tp62855p62869.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
ski" wrote:
>Is anybody actually addressing the issues people have been reporting about
>the installer and/or ANT script for Flex SDK 4.16.0?
>
>Right now I see two major issues that are preventing even people who are
>familiar with the SDK from doing installs :
>
> - In
Is anybody actually addressing the issues people have been reporting about
the installer and/or ANT script for Flex SDK 4.16.0?
Right now I see two major issues that are preventing even people who are
familiar with the SDK from doing installs :
- In the installer, selecting AIR 25.0 gives users
Ah, I misunderstood which asdoc-config file.
On 6/30/17, 1:31 PM, "Alex Harui" wrote:
>The asdoc target doesn't work because we've extended ActionScript for
>FlexJS. We only care about the ASDoc Example. I guess we should comment
>out the asdoc target for now. Also, it looks like the ASDoc ex
The asdoc target doesn't work because we've extended ActionScript for
FlexJS. We only care about the ASDoc Example. I guess we should comment
out the asdoc target for now. Also, it looks like the ASDoc example uses
its own asdic-config.xml file in its src/main/config folder.
-Alex
On 6/30/17,
I'm running the asdoc target in flex-asjs and it has rejected a couple of
things in Core/main/flex/Promise.as such as:
[asdoc]
/Users/pent/dev/flex-asjs/frameworks/projects/Core/src/main/flex/Promise.as(270):
col: 19 Error: Syntax error: expecting identifier before catch.
[asdoc]
[a
The only 100% safe option in my opinion would be to create a tool to do the
patching. This tool might simply be a wrapper around some open-source patch
tool with a suitable license and provide a Maven goal to do the patching. For
Ant a matching wrapper should make sure the patches are applied eq
Hi,
> I think others may have experienced this also, at least I have seen similar
> things mentioned previously.
I’ve run into this issue before on OSX and it been discussed on list - was not
able to find the root cause however.
Thanks,
Justin
Nope … don’t have any issues on a Mac.
I wouldn’t say that I am really happy with the patching and all, the way it’s
done today. We are relying on an external executable. As you might have
noticed, I don’t like executing Things outside the VM and like to have Things
inside the Java world and
I have had a few issues with maven build of typedefs (in develop) over recent
times.
I think others may have experienced this also, at least I have seen similar
things mentioned previously.
For me this seems to be related to patches being applied when the content that
is being downloaded is
"lib"
],
"external-library-path": [
"typedefs"
]
},
"copySourcePathAssets": true,
"additionalOptions": "-remove-circulars
-js-output-optimization=skipAsCoercions
-html-template=src/resources/mdl-j
Are you setting debug in an argument passed to asconfigc, like this?
asconfigc --debug=false
Or is it specified in asconfig.json in the compilerOptions section?
Both will work, but the asconfigc command line option will always override
whatever is in asconfig.json. In VSCode, the generated tasks
For me, the Ant build calls the "compile" target in
examples/build_example.xml and sets the config_arg to use
frameworks/js-config.xml which has targets set to just JS.
A better example might be examples/flexjs/MDLExample. For Ant, it has a
src/main/config/compile-app-config.xml which specifies:
That is using -js-output-type=FLEXJS
My understanding is that we are supposed to use -targets=JSFlex now.
Is that not right?
> On Jun 4, 2017, at 5:43 PM, Alex Harui wrote:
>
> The examples/native/ButtonExample does not produce a SWF for me, so maybe
> compare that setup against yours.
>
> HT
The examples/native/ButtonExample does not produce a SWF for me, so maybe
compare that setup against yours.
HTH,
-Alex
On 6/4/17, 12:56 AM, "Harbs" wrote:
>Good news: Prior to the switch to dual, I was not getting a minified
>release build working. That’s now working.
>Bad news: It takes much l
I’m seeing similar times using both ant and asconfig for debug. (Both are good.)
asconfig is not compiling a release build at all — even if I specify
debug=false.
I have not tried with Maven.
> On Jun 4, 2017, at 12:06 PM, Justin Mclean wrote:
>
> Hi,
>
>> Justin you are compiling by Maven ?
Hi,
> Justin you are compiling by Maven ?
Yep and Debug builds are noticeably slower for me.
Justin
To be clear:
Debug builds are as fast if not faster than they used to be.
Release build are much slower.
I’m getting a debug build (with remove circulars) of my (complex) app taking
about 10 seconds.
The release build takes about 3 minutes.
> On Jun 4, 2017, at 11:57 AM, Justin Mclean wrote:
>
As I remember Harbs is compiling it by ANT ? Am I right ? Justin you are
compiling by Maven ?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/dual-issues-tp61955p62070.html
Sent from the Apache Flex
Hi,
> Bad news: It takes much longer than it used to, and I’m getting a swf file
> even though I’m only using -targets=JSFlex
Compiles are also taking a lot longer for me and I’m also only using the JSFlex
target.
Thanks,
Justin
Ahh..That's not good. Another thing for resolve in release definitly.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/dual-issues-tp61955p62066.html
Sent from the Apache Flex Development mailing
Good news: Prior to the switch to dual, I was not getting a minified release
build working. That’s now working.
Bad news: It takes much longer than it used to, and I’m getting a swf file even
though I’m only using -targets=JSFlex
Harbs
Objects like Promise, Map, Set etc. are available by default in pretty much all
modern browsers.
Things like await, arrow functions, let, etc. are being added by browsers all
the time. I’m not sure exactly which ones have what right now, but they are
pretty far along already, so that article is
I thought es6 wasn't always on by default?
https://thenextweb.com/dd/2016/03/09/6-reasons-need-learn-javascript-es6-no
w-not-later/#.tnw_5KKUOOPX
I haven't been paying attention so maybe all browsers are fully compliant
now?
-Alex
On 6/4/17, 12:01 AM, "Harbs" wrote:
>Not sure what you mean he
Not sure what you mean here.
> On Jun 4, 2017, at 8:52 AM, Alex Harui wrote:
>
> Does FlexJS emit the right code to enable es6 APIs?
On 6/3/17, 2:02 PM, "Harbs" wrote:
>I just ran into another issue.
>
>I’m not sure why dual would have changed this, but I’m now getting an
>(erroneous) error when trying to use Promises:
>
>Incorrect number of arguments. Expected no more than 0
>
> return new Promise(fun
{
^
> On Jun 1, 2017, at 10:39 AM, Harbs wrote:
>
> My bad. I accidentally overwrote my copy of BasicJS.swc.
>
> After fixing some issues, I got my app to run using the latest dual changes.
>
> All in all, switching to dual went a lot better than I expe
When they're defined in the *-config.xml files, they'll be picked up
automatically without any special code in VSCode. However, now that you
mention it, I need to allow app developers to customize these in
asconfig.json too.
- Josh
On Jun 1, 2017 12:04 AM, "Alex Harui" wrote:
Josh, there are ne
Hi Harbs,
Great news! This approach us to release!
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/dual-issues-tp61955p61988.html
Sent from the Apache Flex Development mailing list archive at
My bad. I accidentally overwrote my copy of BasicJS.swc.
After fixing some issues, I got my app to run using the latest dual changes.
All in all, switching to dual went a lot better than I expected.
Great work, Alex!
I think the switch to the dual approach was the right one. There’s still
Josh, there are new compiler options like js-external-library-path,
js-library-path, swf-library-path, swf-external-library-path. Does your
VSCode integration handle these?
-Alex
On 5/31/17, 8:42 PM, "Josh Tynjala" wrote:
>As I understand it, the compiler should just take care of differences
>
If targets only has JSFlex, there shouldn't be any SWF compile at all.
The console should spit out what it thinks it needs to do.
Keep in mind that there are now SWCs for SWFs and SWCs for JS. Prior to
dual, there was a main SWC with SWF APIs that the compiler saw, and JS
that it substituted in t
As I understand it, the compiler should just take care of differences
between JS and SWF, as long as your targets option is correct. VSCode
shouldn't need to do anything special except to pass in the correct
options.
There's nothing related to dual changes on my to-do list at this time, but
maybe
Another weird issue:
> /Users/harbs/Documents/git/PrintUI/printui-flexjs/PortedPrintUI/src/com/printui/dummy/view/Image.as(12):
> col: 15 interface method imageElement in interface IImage not implemented by
> class Image
>
> public class Image extends BinaryImage
>^
>
Josh,
VS Code is now reporting lots of errors in the Problems window. I’m guessing it
does not know how to differentiate between JS and SWF builds using dual?
Is that something on your to-do list?
Thanks,
Harbs
> On Jun 1, 2017, at 5:10 AM, Harbs wrote:
>
> Bingo. Thanks!
>
> SWF output sti
Bingo. Thanks!
SWF output still gets all kinds of errors, but the JS output is pretty error
free. I still have some fixing up to do before I can see how well it actually
works, but at least the compiler is not complaining now.
> On Jun 1, 2017, at 4:45 AM, Josh Tynjala wrote:
>
> Try replacin
The examples I see seem to use COMPILE blocks.
I’m not sure how this translates to the app level. Is there a way to define a
single method which overrides a SWF one and implements a new JS one (without
using COMPILE blocks)? That seems to me like a pretty common use case for
migrated apps.
> O
Hi,
> I’m using asconfig in VSCode to compile with these settings:
> "config": "flex",
> "compilerOptions": {
> "debug": false,
> "js-output-type": "flexjs",
> "source-map": false,
> "library-path": [
> "lib"
> ],
I’ve not used VSCode but perhaps try “
Try replacing the js-output-type compiler option with:
"targets": ["JSFlex"]
- Josh
On May 31, 2017 6:26 PM, "Harbs" wrote:
> I’m using asconfig in VSCode to compile with these settings:
> "config": "flex",
> "compilerOptions": {
> "debug": false,
> "js-output-type": "f
In case I wasn’t clear, I’m not outputting SWF — only JS output.
> On Jun 1, 2017, at 4:26 AM, Harbs wrote:
>
> I’m using asconfig in VSCode to compile with these settings:
> "config": "flex",
> "compilerOptions": {
> "debug": false,
> "js-output-type": "flexjs",
>
I’m using asconfig in VSCode to compile with these settings:
"config": "flex",
"compilerOptions": {
"debug": false,
"js-output-type": "flexjs",
"source-map": false,
"library-path": [
"lib"
],
> On Jun 1, 2017, at 1:04 AM, Justin Mclean w
On 5/31/17, 2:38 PM, "Harbs" wrote:
>I just switched to dual and I’m getting lots of errors. These errors seem
>to be exactly what I was afraid of, and I’m not sure how to resolve
>without being restricted by naming of properties and methods.
>
>1. I’m using a mask setter and getter for images
HI,
> Am I missing something?
Perhaps try JSFlex in your pom.xml? I believe the name
changed from pre to post dual branch.
Justin
I just switched to dual and I’m getting lots of errors. These errors seem to be
exactly what I was afraid of, and I’m not sure how to resolve without being
restricted by naming of properties and methods.
1. I’m using a mask setter and getter for images it’s now giving override
errors.
2. contai
just add option to select mirror, rise and eu mirror did not work for me,
but us did
http://www-eu.apache.org/dist/flex/4.16.0/binaries/apache-flex-sdk-4.16.0-bin.zip
http://mirror.rise.ph/apache/flex/4.16.0/binaries/apache-flex-sdk-4.16.0-bin.zip
while this worked
http://www-us.apache.org/dist/
On 3/25/17, 9:19 AM, "piotrz" wrote:
>I was referring to the idea where we stay with current installer as is and
>popup with the message to the user if problems during download occurs.
>
>Message could contains link to the zip.
I don't think the current installer knows how to pop up a message.
-development.247.n4.nabble.com/4-16-0-Windows-Install-issues-was-Re-ANNOUNCE-Apache-Flex-4-16-0-released-tp60626p60768.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 3/25/17, 9:05 AM, "piotrz" wrote:
>Alex,
>
>Can we exact specify if user face this problem ? Maybe we could do this
>zip
>file, and notify user by popup - Hey you have to download 64 bit
>installer.
>
>In the other words zip file is best option for me.
I'm not sure what kind of popup you ar
context:
http://apache-flex-development.247.n4.nabble.com/4-16-0-Windows-Install-issues-was-Re-ANNOUNCE-Apache-Flex-4-16-0-released-tp60626p60766.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Can you explain in more detail what steps you would take?
Thanks,
-Alex
On 3/20/17, 1:30 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>We could do a patch release that does not add any new feature for the 64
>bit installer binary.
>
>We would need to bump up the version so th
We could do a patch release that does not add any new feature for the 64
bit installer binary.
We would need to bump up the version so that the auto update functionality
would be triggered.
In this we probably don't even need a source release as we will only be
modifying the convenience binaries.
Renaming thread. On next post I will drop the [ANNOUNCE] tag so we don't
fill the inboxes of those using an Announce filter.
So, I have heard back from my internal contacts. There is no plan to
allow the packaging of a 64-bit app the way we package the 32-bit
Installer. Essentially, that means
You can use
FP/AIR 23 and older then use one of the upgrade scripts.
+1 for this approach.
I think we should add these steps to a wiki page and keep it handy for
folks who want this.
In fact, simply copying over a different AIR SDK should work as well.
Thanks,
Om
On 3/16/17, 12:25 PM, "Nicholas Kwiatkowski"
wrote:
>I think there is some reason to use very old versions of AIR ( < 4), but
>between AIR 4 and 23 it should be ok. Do you know if it effects the old
>ones (which still support some older OSs)?
Probably. The issue is the installer script trie
I think there is some reason to use very old versions of AIR ( < 4), but
between AIR 4 and 23 it should be ok. Do you know if it effects the old
ones (which still support some older OSs)?
-Nick
On Thu, Mar 16, 2017 at 2:54 PM, Alex Harui wrote:
> Adding dev@...
>
> I just noticed that there i
Adding dev@...
I just noticed that there is a bug in the installer.xml and the Installer
will not install 4.16.0 on Mac with FP/AIR 23 and older. It will only
work with FP/AIR 24 and newer. I haven't tried Windows, but it should be
ok.
I am hopeful very few people will want to install 4.16 with
On 3/14/17, 11:33 PM, "Justin Mclean" wrote:
>Hi,
>
>> In order to determine which steps I had to go through to try to donate
>>the
>> CreateJS Externs to the CreateJS community, it turns out I had to get a
>> ruling from the Adobe legal team about who owned the "externs" files we
>> generate f
Hi,
> In order to determine which steps I had to go through to try to donate the
> CreateJS Externs to the CreateJS community, it turns out I had to get a
> ruling from the Adobe legal team about who owned the "externs" files we
> generate from CreateJS source. The Adobe legal team determined tha
Hi,
> In order to determine which steps I had to go through to try to donate the
> CreateJS Externs to the CreateJS community, it turns out I had to get a
> ruling from the Adobe legal team about who owned the "externs" files we
> generate from CreateJS source. The Adobe legal team determined tha
Justin's fix for CreateJS typedefs on Unix reminded me...
In order to determine which steps I had to go through to try to donate the
CreateJS Externs to the CreateJS community, it turns out I had to get a
ruling from the Adobe legal team about who owned the "externs" files we
generate from CreateJ
1 - 100 of 495 matches
Mail list logo
