You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/04/27 14:31:48 UTC
[jira] [Created] (FLEX-53) Clarify usage of playerglobal.swc and
airglobal.swc
Bertrand Delacretaz created FLEX-53:
---------------------------------------
Summary: Clarify usage of playerglobal.swc and airglobal.swc
Key: FLEX-53
URL: https://issues.apache.org/jira/browse/FLEX-53
Project: Apache Flex
Issue Type: Task
Components: Project Management
Reporter: Bertrand Delacretaz
Assignee: Carol Frampton
As discussed in [1], Flex requires
1) playerglobal.swc to compile the majority of the Flex components
2) airglobal.swc to compile the Flex components targeted at AIR
3) many pieces of the AIR Integration kit which are need to do Flex mobile development
We might need clarification for 3), but for now we need to find out how to use these files while abiding by their license requirements and complying with the ASF's restrictions on incompatible license (http://www.apache.org/legal/resolved.html).
According to Alex in [1] those two files are covered by this license:
http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf
And it seems like they're only needed at build time, so users of Flex could get them independently.
[1] http://markmail.org/thread/muckogic3f2zwd7o
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Created] (FLEX-53) Clarify usage of playerglobal.swc and airglobal.swc
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Apr 27, 2012 at 2:40 PM, David Coleman
<da...@hotmail.com> wrote:
>... If I read it correctly, this license provides the right to re-distribute these binaries. And it also grants the right in (c) to *reproduce* them! Seems to cover the scope of actions which this group wishes to take to me....
That might be correct but there's a number of places that mention
"internal use", and Flex redistributing these files would not be
internal use IMO, so it seems safer to avoid doing that.
The key thing for an Apache project is that we don't want to put any
restriction on users of our code beyond the Apache License. Having
parts of a distribution that are for "internal use only" does not
work.
-Bertrand
>
> See excerpt below:
>
> Subject to the terms and conditions of this Agreement, Adobe grants You a non-exclusive, nontransferable license to: (a) modify those Flex Framework Binaries that have not been digitally signed (signed binaries are denoted by an “.SWZ” extension); (b) internally use and reproduce the Flex Framework Binaries (in modified or unmodified form) for the purpose of developing Developer Programs,
>
> (c) internally use and reproduce the Flex Framework Binaries (in modified or unmodified form) as part of Your internal website for the purpose of compiling the Developer Programs,
>
> (d) copy and distribute the Flex Framework Binaries (in modified or unmodified form) as compiled into Developer Programs;
>
> (e) copy and distribute, through multiple tiers of distribution, the Flex Framework Binaries (in modified or unmodified form) with a Developer Program for use at runtime of such Developer Program, and
>
> (f) copy and include the Flex Framework Binaries (in modified or unmodified form) as part of Your public website for use at runtime by the Developer Programs that are distributed from Your website(s). You may in no instance modify Flex Framework Binaries that have been digitally signed.
>
>
>
>
>> Date: Fri, 27 Apr 2012 12:31:48 +0000
>> From: jira@apache.org
>> To: flex-dev@incubator.apache.org
>> Subject: [jira] [Created] (FLEX-53) Clarify usage of playerglobal.swc and airglobal.swc
>>
>> Bertrand Delacretaz created FLEX-53:
>> ---------------------------------------
>>
>> Summary: Clarify usage of playerglobal.swc and airglobal.swc
>> Key: FLEX-53
>> URL: https://issues.apache.org/jira/browse/FLEX-53
>> Project: Apache Flex
>> Issue Type: Task
>> Components: Project Management
>> Reporter: Bertrand Delacretaz
>> Assignee: Carol Frampton
>>
>>
>> As discussed in [1], Flex requires
>>
>> 1) playerglobal.swc to compile the majority of the Flex components
>> 2) airglobal.swc to compile the Flex components targeted at AIR
>> 3) many pieces of the AIR Integration kit which are need to do Flex mobile development
>>
>> We might need clarification for 3), but for now we need to find out how to use these files while abiding by their license requirements and complying with the ASF's restrictions on incompatible license (http://www.apache.org/legal/resolved.html).
>>
>> According to Alex in [1] those two files are covered by this license:
>> http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf
>>
>> And it seems like they're only needed at build time, so users of Flex could get them independently.
>>
>> [1] http://markmail.org/thread/muckogic3f2zwd7o
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>
Re: [jira] [Created] (FLEX-53) Clarify usage of playerglobal.swc
and airglobal.swc
Posted by Alex Harui <ah...@adobe.com>.
On 4/27/12 5:40 AM, "David Coleman" <da...@hotmail.com> wrote:
>
> If I read it correctly, this license provides the right to re-distribute these
> binaries. And it also grants the right in (c) to *reproduce* them! Seems to
> cover the scope of actions which this group wishes to take to me.
>
> See excerpt below:
>
> Subject to the terms and conditions of this Agreement, Adobe grants You a
> non-exclusive, nontransferable license to: (a) modify those Flex Framework
> Binaries that have not been digitally signed (signed binaries are denoted by
> an ³.SWZ² extension); (b) internally use and reproduce the Flex Framework
> Binaries (in modified or unmodified form) for the purpose of developing
> Developer Programs,
>
> (c) internally use and reproduce the Flex Framework Binaries (in modified or
> unmodified form) as part of Your internal website for the purpose of compiling
> the Developer Programs,
>
> (d) copy and distribute the Flex Framework Binaries (in modified or unmodified
> form) as compiled into Developer Programs;
>
> (e) copy and distribute, through multiple tiers of distribution, the Flex
> Framework Binaries (in modified or unmodified form) with a Developer Program
> for use at runtime of such Developer Program, and
>
> (f) copy and include the Flex Framework Binaries (in modified or unmodified
> form) as part of Your public website for use at runtime by the Developer
> Programs that are distributed from Your website(s). You may in no instance
> modify Flex Framework Binaries that have been digitally signed.
>
This is correct, and was what we were assuming until recently, when I
discovered in the readme that we can't really consider playerglobal to be a
FLEX framework binary.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: [jira] [Created] (FLEX-53) Clarify usage of playerglobal.swc
and airglobal.swc
Posted by David Coleman <da...@hotmail.com>.
If I read it correctly, this license provides the right to re-distribute these binaries. And it also grants the right in (c) to *reproduce* them! Seems to cover the scope of actions which this group wishes to take to me.
See excerpt below:
Subject to the terms and conditions of this Agreement, Adobe grants You a non-exclusive, nontransferable license to: (a) modify those Flex Framework Binaries that have not been digitally signed (signed binaries are denoted by an “.SWZ” extension); (b) internally use and reproduce the Flex Framework Binaries (in modified or unmodified form) for the purpose of developing Developer Programs,
(c) internally use and reproduce the Flex Framework Binaries (in modified or unmodified form) as part of Your internal website for the purpose of compiling the Developer Programs,
(d) copy and distribute the Flex Framework Binaries (in modified or unmodified form) as compiled into Developer Programs;
(e) copy and distribute, through multiple tiers of distribution, the Flex Framework Binaries (in modified or unmodified form) with a Developer Program for use at runtime of such Developer Program, and
(f) copy and include the Flex Framework Binaries (in modified or unmodified form) as part of Your public website for use at runtime by the Developer Programs that are distributed from Your website(s). You may in no instance modify Flex Framework Binaries that have been digitally signed.
> Date: Fri, 27 Apr 2012 12:31:48 +0000
> From: jira@apache.org
> To: flex-dev@incubator.apache.org
> Subject: [jira] [Created] (FLEX-53) Clarify usage of playerglobal.swc and airglobal.swc
>
> Bertrand Delacretaz created FLEX-53:
> ---------------------------------------
>
> Summary: Clarify usage of playerglobal.swc and airglobal.swc
> Key: FLEX-53
> URL: https://issues.apache.org/jira/browse/FLEX-53
> Project: Apache Flex
> Issue Type: Task
> Components: Project Management
> Reporter: Bertrand Delacretaz
> Assignee: Carol Frampton
>
>
> As discussed in [1], Flex requires
>
> 1) playerglobal.swc to compile the majority of the Flex components
> 2) airglobal.swc to compile the Flex components targeted at AIR
> 3) many pieces of the AIR Integration kit which are need to do Flex mobile development
>
> We might need clarification for 3), but for now we need to find out how to use these files while abiding by their license requirements and complying with the ASF's restrictions on incompatible license (http://www.apache.org/legal/resolved.html).
>
> According to Alex in [1] those two files are covered by this license:
> http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf
>
> And it seems like they're only needed at build time, so users of Flex could get them independently.
>
> [1] http://markmail.org/thread/muckogic3f2zwd7o
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
[jira] [Resolved] (FLEX-33089) Clarify usage of playerglobal.swc
and airglobal.swc
Posted by "Carol Frampton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carol Frampton resolved FLEX-33089.
-----------------------------------
Resolution: Fixed
Fix Version/s: Apache Flex 4.8 (parity release)
The Adobe AIR SDK and Adobe Flash playerglobal.swc are system requirements for Flex. They are found via the AIR_HOME and PLAYERGLOBAL_HOME environment variables or setting the equivalents in the env.properties file in the root of the SDK.
> Clarify usage of playerglobal.swc and airglobal.swc
> ---------------------------------------------------
>
> Key: FLEX-33089
> URL: https://issues.apache.org/jira/browse/FLEX-33089
> Project: Apache Flex
> Issue Type: Task
> Components: Project Management
> Reporter: Alex Harui
> Fix For: Apache Flex 4.8 (parity release)
>
>
> As discussed in [1], Flex requires
> 1) playerglobal.swc to compile the majority of the Flex components
> 2) airglobal.swc to compile the Flex components targeted at AIR
> 3) many pieces of the AIR Integration kit which are need to do Flex mobile development
> We might need clarification for 3), but for now we need to find out how to use these files while abiding by their license requirements and complying with the ASF's restrictions on incompatible license (http://www.apache.org/legal/resolved.html).
> According to Alex in [1] those two files are covered by this license:
> http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf
> And it seems like they're only needed at build time, so users of Flex could get them independently.
> [1] http://markmail.org/thread/muckogic3f2zwd7o
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (FLEX-33089) Clarify usage of playerglobal.swc and
airglobal.swc
Posted by "Carol Frampton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-33089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carol Frampton closed FLEX-33089.
---------------------------------
> Clarify usage of playerglobal.swc and airglobal.swc
> ---------------------------------------------------
>
> Key: FLEX-33089
> URL: https://issues.apache.org/jira/browse/FLEX-33089
> Project: Apache Flex
> Issue Type: Task
> Components: Project Management
> Reporter: Alex Harui
> Fix For: Apache Flex 4.8 (parity release)
>
>
> As discussed in [1], Flex requires
> 1) playerglobal.swc to compile the majority of the Flex components
> 2) airglobal.swc to compile the Flex components targeted at AIR
> 3) many pieces of the AIR Integration kit which are need to do Flex mobile development
> We might need clarification for 3), but for now we need to find out how to use these files while abiding by their license requirements and complying with the ASF's restrictions on incompatible license (http://www.apache.org/legal/resolved.html).
> According to Alex in [1] those two files are covered by this license:
> http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf
> And it seems like they're only needed at build time, so users of Flex could get them independently.
> [1] http://markmail.org/thread/muckogic3f2zwd7o
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-53) Clarify usage of playerglobal.swc and
airglobal.swc
Posted by "Alex Harui (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266268#comment-13266268 ]
Alex Harui commented on FLEX-53:
--------------------------------
The Flash runtime provides a set of APIs for things like Array and String manipulation, XML and RegExp handling, network I/O, drawing graphics, handling mouse and keyboard input, and more. These capabilities are part of the FlashPlayer or AIR runtimes. Applications are typically delivered without any code to perform the above mentioned APIs because those APIs are resolved at launch time into entry points into the runtime (There is a capability to combine the AIR runtime into the same deliverable as the application).
At compile time, any application that wants to use the runtimes needs to have playerglobal.swc or airglobal.swc in the library path in order for the compiler to resolve those APIs, but no code from those swc files are linked into the output SWF.
I am not an expert in Java, but to me, this is the equivalent of some of the files in a JDK and the Flash or AIR runtime is similar to a JRE.
In addition to playerglobal.swc and airglobal.swc, the AIR SDK also includes additional utilities to package applications for different target devices like Android or IOS. These utilities are not distributed with the application.
> Clarify usage of playerglobal.swc and airglobal.swc
> ---------------------------------------------------
>
> Key: FLEX-53
> URL: https://issues.apache.org/jira/browse/FLEX-53
> Project: Apache Flex
> Issue Type: Task
> Components: Project Management
> Reporter: Bertrand Delacretaz
> Assignee: Carol Frampton
>
> As discussed in [1], Flex requires
> 1) playerglobal.swc to compile the majority of the Flex components
> 2) airglobal.swc to compile the Flex components targeted at AIR
> 3) many pieces of the AIR Integration kit which are need to do Flex mobile development
> We might need clarification for 3), but for now we need to find out how to use these files while abiding by their license requirements and complying with the ASF's restrictions on incompatible license (http://www.apache.org/legal/resolved.html).
> According to Alex in [1] those two files are covered by this license:
> http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf
> And it seems like they're only needed at build time, so users of Flex could get them independently.
> [1] http://markmail.org/thread/muckogic3f2zwd7o
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-53) Clarify usage of playerglobal.swc and
airglobal.swc
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLEX-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266423#comment-13266423 ]
Bertrand Delacretaz commented on FLEX-53:
-----------------------------------------
Thanks for the explanation! That clarifies things.
The equivalent in Java would be API classes then - binary files that describe APIs and are required to compile code that uses those APIs.
I think it is now clear that those .swc files are only needed at compile time, and people will not need to redistribute them with applications that they build with Apache Flex.
I suggest that we leave the other AIR SDK utilities out of this for now, let's create a separate issue for those if needed.
> Clarify usage of playerglobal.swc and airglobal.swc
> ---------------------------------------------------
>
> Key: FLEX-53
> URL: https://issues.apache.org/jira/browse/FLEX-53
> Project: Apache Flex
> Issue Type: Task
> Components: Project Management
> Reporter: Bertrand Delacretaz
> Assignee: Carol Frampton
>
> As discussed in [1], Flex requires
> 1) playerglobal.swc to compile the majority of the Flex components
> 2) airglobal.swc to compile the Flex components targeted at AIR
> 3) many pieces of the AIR Integration kit which are need to do Flex mobile development
> We might need clarification for 3), but for now we need to find out how to use these files while abiding by their license requirements and complying with the ASF's restrictions on incompatible license (http://www.apache.org/legal/resolved.html).
> According to Alex in [1] those two files are covered by this license:
> http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit-combined-20110916_0930.pdf
> And it seems like they're only needed at build time, so users of Flex could get them independently.
> [1] http://markmail.org/thread/muckogic3f2zwd7o
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira