They might already be translated being mostly standard lo open source
licences.
Examples would be great.
One thing we can do now is market what Flex *is* (we have that description
in a few places) and that *we are making it better*. That is that we fixing
bugs, adding new components, removing dependencies, setting up Mustella
tests, cutting new releases, working on the new
Mclean
> >> wrote:
> >>
> >>> I'd leave it where it is each imo you should be able to build each
> >>> project from its own trunk and not have to check out multiple trunks
> >>>
> >>
> >>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
make a copy under utilities/trunk/installer?
>>
>>
>> On Fri, Jan 4, 2013 at 2:11 PM, Justin Mclean
>> wrote:
>>
>>> I'd leave it where it is each imo you should be able to build each
>>> project from its own trunk and not have to check out multiple trunks
>>>
>>
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
BTW, this script does not work for me on windows (cygwin) This is what I
get:
$ ./sign_and_hash.sh
./sign_and_hash.sh: line 48: $'\r': command not found
./sign_and_hash.sh: line 49: $'\r': command not found
./sign_and_hash.sh: line 50: syntax error near unexpected token `$'do\r''
'/sign_and_hash.
So, should I just make a copy under utilities/trunk/installer?
On Fri, Jan 4, 2013 at 2:11 PM, Justin Mclean wrote:
> I'd leave it where it is each imo you should be able to build each project
> from its own trunk and not have to check out multiple trunks
>
t;New Revision: 1428687
>> >
>> >URL: http://svn.apache.org/viewvc?rev=1428687&view=rev
>> >Log:
>> >change version 2.0.0 to 2.0.1
>> >
>> >Modified:
>> >incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
>>
he.org" wrote:
>
> >Author: jmclean
> >Date: Fri Jan 4 00:43:22 2013
> >New Revision: 1428687
> >
> >URL: http://svn.apache.org/viewvc?rev=1428687&view=rev
> >Log:
> >change version 2.0.0 to 2.0.1
> >
> >Modified:
> >
ot; wrote:
>Author: jmclean
>Date: Fri Jan 4 00:43:22 2013
>New Revision: 1428687
>
>URL: http://svn.apache.org/viewvc?rev=1428687&view=rev
>Log:
>change version 2.0.0 to 2.0.1
>
>Modified:
>incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
>
>
chael Schmalle" wrote:
>>
>>>> Anything we say about the future right now is likely to be met with
>>>> suspicion anyway. I think this is a critical year for Flex. We have to
>>>> build a track record of releases that show that we are making progre
ake your life much easier. Please feel free to provide feedback
> on the app as well.
>
> Thanks,
> Om
>
> [1] https://issues.apache.org/jira/browse/FLEX-0
>
> On Fri, Jan 4, 2013 at 7:02 AM, Nick Tsitlakidis >wrote:
>
> > I always thought that some parts cant
Quoting Alex Harui :
On 1/4/13 9:37 AM, "Michael Schmalle" wrote:
Anything we say about the future right now is likely to be met with
suspicion anyway. I think this is a critical year for Flex. We have to
build a track record of releases that show that we are making progr
On 1/4/13 9:37 AM, "Michael Schmalle" wrote:
>> Anything we say about the future right now is likely to be met with
>> suspicion anyway. I think this is a critical year for Flex. We have to
>> build a track record of releases that show that we are making progres
] https://issues.apache.org/jira/browse/FLEX-0
On Fri, Jan 4, 2013 at 7:02 AM, Nick Tsitlakidis wrote:
> I always thought that some parts cant or shouldn't be translated in
> applications. One of these cases I think is the software licenses because
> there is room for a lot of error
solve problems for people and showing people that they can
solve their problems today.
Anything we say about the future right now is likely to be met with
suspicion anyway. I think this is a critical year for Flex. We have to
build a track record of releases that show that we are making progres
that solve problems for people and showing people that they can
solve their problems today.
Anything we say about the future right now is likely to be met with
suspicion anyway. I think this is a critical year for Flex. We have to
build a track record of releases that show that we are making p
Hi,
At Devoxx and Devoxx France (initially, Devoxx is an annual European Java,
Android and HTML5 conference which reached 3400 attendees from 40 different
countries in 2011), Flex is not represented since Adobe doesn't own it
anymore, I guess there are many other kinds of places like that
uot; wrote:
>
>> I'm not talking Roadmap here, Alex, but even Open Source projects done
>> the Apache way can have a direction and maybe even actual goals.
>>
>> One definition might be: "maintaining the project status quo by
>> preventing any discussion about
you an example of recent effective marketing being done today without
describing a future for Flex. It is the December 2012 Spoon Community Revue [1]
[1] http://www.spoon.as/2012/apache-flex-community-revue-december-2012-2/
venting any discussion about common goals"
>
> Another might be: "bringing the power of the Flex framework to
> multiple, vendor independent platforms"
>
> Or even: "one framework to rule them all" ;-)
>
> I'm not saying we need any kind of fixed
I'm not talking Roadmap here, Alex, but even Open Source projects done
the Apache way can have a direction and maybe even actual goals.
One definition might be: "maintaining the project status quo by
preventing any discussion about common goals"
Another might be: "bringing t
#x27;t, that doesn't mean we can't use better
marketing about what we have done or are doing.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
again. We ended up
talking about "marketing" Apache Flex to the rest of the world, in
order raise the visibility and create/maintain a broad(er) user base.
Someone brought up that in order to be able to do effective marketing,
we should first define the project's future...
So, wh
> >3. More translations made possible by Roland and Nick
> >4. Fixed README, RELEASE_NOTES, RELEASE_GUIDE and build.properties files
> >for more accuracy.
> >
> >Issues fixed in RC1:
> >1. UI of the components selection and license screen has been fixed to
ions made possible by Roland and Nick
>4. Fixed README, RELEASE_NOTES, RELEASE_GUIDE and build.properties files
>for more accuracy.
>
>Issues fixed in RC1:
>1. UI of the components selection and license screen has been fixed to
>use
>just checkboxes for selection
>2. All the various local
On 1/4/13 1 :12AM, "flexcapaci...@gmail.com"
wrote:
>I've read through some of the previous threads on this and the config xml
>and I don't know what was decided if anything. What I'd want to see in it
>is default to downloading the latest Flash Player, AIR and playerglobal
>swc. Is there are a
ies files
> > for more accuracy.
> >
> > Issues fixed in RC1:
> > 1. UI of the components selection and license screen has been fixed to
> use
> > just checkboxes for selection
> > 2. All the various locales have been enabled.
> > 3. By default, Apach
s files
> for more accuracy.
>
> Issues fixed in RC1:
> 1. UI of the components selection and license screen has been fixed to use
> just checkboxes for selection
> 2. All the various locales have been enabled.
> 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Fla
e text
>> 3. More translations made possible by Roland and Nick
>> 4. Fixed README, RELEASE_NOTES, RELEASE_GUIDE and build.properties files
>> for more accuracy.
>>
>> Issues fixed in RC1:
>> 1. UI of the components selection and license screen has been fixed
components selection and license screen has been fixed to use
> just checkboxes for selection
> 2. All the various locales have been enabled.
> 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player
> 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other
>
2. All the various locales have been enabled.
3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player
11.1 and Adobe AIR SDK 3.4. If you want to change it to any other
supported combination, you save a copy of the config file found at:
http://incubator.apache.org/flex/sdk
Leng Sheng Hong created FLEX-9:
--
Summary: List for mobile ios and android no longer scrolls
Key: FLEX-9
URL: https://issues.apache.org/jira/browse/FLEX-9
Project: Apache Flex
[
https://issues.apache.org/jira/browse/FLEX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Harui resolved FLEX-8.
---
Resolution: Fixed
submitted in SVN 1428469. Thanks Nick.
> Incomplete translat
[
https://issues.apache.org/jira/browse/FLEX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Harui reassigned FLEX-8:
-
Assignee: Alex Harui
> Incomplete translation and formatting when using Greek locale w
Nick Tsitlakidis created FLEX-8:
---
Summary: Incomplete translation and formatting when using Greek
locale with the installer.
Key: FLEX-8
URL: https://issues.apache.org/jira/browse/FLEX-8
; some more changes that can happen so as soon as I figure out how the
> process works I'll submit a patch with the new changes.
>
> Regarding the JIRA issue, what do you want me to include in there?
The list of strings you wanted us to change. Someday we may want to go back
and find
ve some guidance for
> this.
> >> I'm a total noob with patches since it's the first time I'm actively
> >> contributing something. I'm a member of the list since last year but
> never
> >> had the time to work on something until now.
> >
>>
>> Are there any guidelines or a page I can check to learn how to do this?
> There is some information on the Apache Flex web site. You have to check out
> the source, figure out how to build the installer, modify the files and
> generate the patch from the modified files. The
[
https://issues.apache.org/jira/browse/FLEX-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christofer Dutz updated FLEX-7:
---
Attachment: NumericInput.as
> Create a NumericInput compon
Christofer Dutz created FLEX-7:
--
Summary: Create a NumericInput component
Key: FLEX-7
URL: https://issues.apache.org/jira/browse/FLEX-7
Project: Apache Flex
Issue Type: New
t year but never
> had the time to work on something until now.
>
> Are there any guidelines or a page I can check to learn how to do this?
There is some information on the Apache Flex web site. You have to check out
the source, figure out how to build the installer, modify the files and
ΕΓΚΑΤΑΣΤΑΣΗΣ
> > NEXT -> ΕΠΟΜΕΝΟ
> > BROWSE -> ΑΝΑΖΗΤΗΣΗ
> > Select installation directory -> Επιλέξτε τον κατάλογο εγκατάστασης
> > The selected directory is not empty -> Ο κατάλογος που επιλέξατε δεν
> είναι
> > άδειος
> >
> >
> > 2nd
άδειος
>
>
> 2nd screen
> CLOSE -> ΕΞΟΔΟΣ
> INSTALL -> ΕΓΚΑΤΑΣΤΑΣΗ
>
> 3d screen
> Installing... -> Εγκατάσταση...
> OPEN APACHE FLEX FOLDER -> ΑΝΟΙΓΜΑ ΦΑΚΕΛΟΥ APACHE FLEX
>
>
> On Thu, Jan 3, 2013 at 10:33 AM, Om wrote:
>
> > Fixed RELEASE
ειος
2nd screen
CLOSE -> ΕΞΟΔΟΣ
INSTALL -> ΕΓΚΑΤΑΣΤΑΣΗ
3d screen
Installing... -> Εγκατάσταση...
OPEN APACHE FLEX FOLDER -> ΑΝΟΙΓΜΑ ΦΑΚΕΛΟΥ APACHE FLEX
On Thu, Jan 3, 2013 at 10:33 AM, Om wrote:
> Fixed RELEASE_NOTES and the issue that Carol raised with losing selections
> w
t;> >
> >> > On Wed, Jan 2, 2013 at 5:03 PM, Carol Frampton
> >> wrote:
> >> >
> >> >> Just gave this a try. Here are my comments regarding the
> installation
> >> and
> >> >> use:
> >> >>
> >> >>
[
https://issues.apache.org/jira/browse/FLEX-33122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OmPrakash Muppirala resolved FLEX-33122.
Resolution: Fixed
> MakeApacheFlexForFlashBuilder change language at runt
[
https://issues.apache.org/jira/browse/FLEX-33214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OmPrakash Muppirala resolved FLEX-33214.
Resolution: Fixed
> Fix UI of license scr
[
https://issues.apache.org/jira/browse/FLEX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bogdan Dinu updated FLEX-6:
---
Attachment: VDividerGroup.as
HDividerGroup.as
DividedGroup.as
Fixed
[
https://issues.apache.org/jira/browse/FLEX-33324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OmPrakash Muppirala closed FLEX-33324.
--
Assignee: OmPrakash Muppirala (was: Erik de Bruin)
Patched in Rev. 1428088
te:
>> >
>> >> Just gave this a try. Here are my comments regarding the installation
>> and
>> >> use:
>> >>
>> >> 1. When I tried to install it I got that "there is something wrong"
>> AIR
>> >> error which
[
https://issues.apache.org/jira/browse/FLEX-33308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542460#comment-13542460
]
Cyrill Zadra commented on FLEX-33308:
-
Yes ... adding the namespace and mani
lly unhelpful but I knew it meant I had to uninstall
> the
> >> old installer first. Why can't the old installer and the new installer
> >> co-exist since they are each installing a different version of Flex?
> >>
> >> 2. As Justin said, the DISCLAIMER
taller first. Why can't the old installer and the new installer
>> co-exist since they are each installing a different version of Flex?
>>
>> 2. As Justin said, the DISCLAIMER needs to be removed.
>>
>> 3. Depending on the locale, the text in some of the buttons
[
https://issues.apache.org/jira/browse/FLEX-33308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33308:
Description:
Falcon fails to compile the sparkskins project in test sparkskinsSWC
/Users/jbalsas
[
https://issues.apache.org/jira/browse/FLEX-33308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542306#comment-13542306
]
Chema Balsas edited comment on FLEX-33308 at 1/2/13 7:1
[
https://issues.apache.org/jira/browse/FLEX-33308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542306#comment-13542306
]
Chema Balsas commented on FLEX-33308:
-
Hi Cyril, yes, sorry, I did get those er
essed up that release. I thought the same source created the badge
> installer, but it got packaged differently before posting on the site.
>
>
We discussed this in the past and decided not to officially release the
badge. It was also decided to include a link to this disclaimer [1]
[
https://issues.apache.org/jira/browse/FLEX-33211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542258#comment-13542258
]
Michal Kolesár edited comment on FLEX-33211 at 1/2/13 6:0
[
https://issues.apache.org/jira/browse/FLEX-33211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542258#comment-13542258
]
Michal Kolesár commented on FLEX-33211:
---
I have the same pro
Yiotis Katsambas created FLEX-6:
---
Summary: HDividerGroup not resizing properly if the divider is not
in the initial position
Key: FLEX-6
URL: https://issues.apache.org/jira/browse/FLEX-6
On Jan 2, 2013 8:06 AM, "Carol Frampton" wrote:
>
>
>
> On 1/2/13 10 :44AM, "Om" wrote:
>
> >On Jan 2, 2013 6:37 AM, "Carol Frampton" wrote:
> >>
> >> flex/utilities/trunk/installer/build.properties needs updating
> >
, I think you're killing a nice tool in the
> process, one of the more successful tools in keeping the SDK 'alive and
> kicking' in the real world.
I'm not trying to kill the tool. In fact I have suggested ways to implement
the desired goals that I think conform to the Apache policy.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
On 1/2/13 10 :44AM, "Om" wrote:
>On Jan 2, 2013 6:37 AM, "Carol Frampton" wrote:
>>
>> flex/utilities/trunk/installer/build.properties needs updating
>>
>> FLEX_HOME_MAC still points to 4.8.0
>>
>>
>> and FLEX_HOME_WIN points
it meant I had to uninstall the
> old installer first. Why can't the old installer and the new installer
> co-exist since they are each installing a different version of Flex?
>
Did you try to install the RC or did you install from what you built
yourself?
The latter should give the p
On Jan 2, 2013 6:37 AM, "Carol Frampton" wrote:
>
> flex/utilities/trunk/installer/build.properties needs updating
>
> FLEX_HOME_MAC still points to 4.8.0
>
>
> and FLEX_HOME_WIN points to ApacheFlex4.9.0 (I'm not sure where this name
> comes from but the
he
> old installer first. Why can't the old installer and the new installer
> co-exist since they are each installing a different version of Flex?
>
> 2. As Justin said, the DISCLAIMER needs to be removed.
>
> 3. Depending on the locale, the text in some of the buttons is
ler and the new installer
co-exist since they are each installing a different version of Flex?
2. As Justin said, the DISCLAIMER needs to be removed.
3. Depending on the locale, the text in some of the buttons is truncated
which looks bad. For example, try French.
4. When I switch the language i
flex/utilities/trunk/installer/build.properties needs updating
FLEX_HOME_MAC still points to 4.8.0
and FLEX_HOME_WIN points to ApacheFlex4.9.0 (I'm not sure where this name
comes from but the formatting seems odd - I dislike names with spaces but
given the rest of the path why not Apache
I'm sorry I'm late to this discussion, but all I can say is: Wow! and:
Really?
The whole website is in SVN. It is source (mdtext), consumed by a compiler
(the buildbot), spit out as HTML and released outside the project on the
WWW. How is that different from our other sources? Do you suggest we ha
Hi,
> Well, that group would need approval from Apache to use Flex anywhere in the
> name of the installer, but yeah, an independent group of folks can certainly
> go off and create their own installer.
Seems less of an issue than the process that is currently being suggested.
Worse ca
HI,
> We are taking something from SVN and consuming it in a binary distribution
> that we've deployed to our site and telling the world to use it.
Not exactly it is optional - it's only used if you don't specify a config file
via the command line.
> But in this case, there is code involved
It's
gic. The config xml is placed on our
> >>> website which is completely under our control. Which means that we
don't
> >>> really 'release' it.
> >> We are taking something from SVN and consuming it in a binary
distribution
> >> that
and requires a vote before it happens.
> It published on the Flex web site by Flex committers give access by the ASF
> I'd read that as not being "beyond the group". Or are you saying we need to
> vote every time we make a change to the web site or wiki?
I mentioned in anoth
t part of a release and requires a vote before it
>> happens.
>>>
>>> I still don't agree with this logic. The config xml is placed on our
>>> website which is completely under our control. Which means that we don't
>>> really 'release'
On 1/1/13 11:13 PM, "Justin Mclean" wrote:
> Hi,
>
>> I'm not sure Apache Flex is allowed to use Github as a end-run around Apache
>> policy.
>
> The installer would not belong to Apache but be a separate project that is
> worked on by people who
this logic. The config xml is placed on our
> > website which is completely under our control. Which means that we don't
> > really 'release' it.
> We are taking something from SVN and consuming it in a binary distribution
> that we've deployed to our site an
u saying that we need to release the source for the
> badge as well?
IMO, absolutely. Did we not do this in the prior version? Then we really
messed up that release. I thought the same source created the badge
installer, but it got packaged differently before posting on the site.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Hi,
> -From [1], a release is "anything that is published beyond the group that
> owns it.". Putting the config.xml on the site to be consumed by one of our
> binaries makes it part of a release and requires a vote before it happens.
It published on the Flex web site by F
Hi,
> I'm not sure Apache Flex is allowed to use Github as a end-run around Apache
> policy.
The installer would not belong to Apache but be a separate project that is
worked on by people who want to give users of the Flex SDK an easy way to
install it. All it does it take the bina
> > What is the legal issue here? The installer will be voted on and
distributed
> > in the normal Apache Way (apache.org/dist). The XML file is also in SVN
at
> > svn.apage.org that only Apache committers can access and change. The
installer
> > will only download official Apache releases that have been voted on and
placed
> > in apache.org/dist.
> >
> > I guess worse case a committer could modify the file XML file in SVN to
> > download another Apache binary kit but I think we would notice that and
fix.
> >
> > Thanks,
> > Justin
> >
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
on to fix it so it complies with what you think the
> legal issue is - which I have to say I'm still unsure actually exists. If then
> we can't come up with a way around that then I suggest we host the installer
> exe/dmg files externally and move the code out of Apache SVN to
Anybody know wny we don't fetch the MD5 from the
>> apache.org DIST (sans Mirror as recommended by Apache).
>>
>
> The app is hardcoded to look at the apache site for the MD5 file. We don't
> get it from any mirrors.
Hmm. Then what is Nick's concern here?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
apage.org that only Apache committers can access and change. The installer
> will only download official Apache releases that have been voted on and placed
> in apache.org/dist.
>
> I guess worse case a committer could modify the file XML file in SVN to
> download another Apache binary kit but I think we would notice that and fix.
>
> Thanks,
> Justin
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
nsure actually exists. If then we can't
come up with a way around that then I suggest we host the installer exe/dmg
files externally and move the code out of Apache SVN to github.
This is just delaying the official 4.9 release announcement and stoping users
from installing the SDK.
>
>
The app is hardcoded to look at the apache site for the MD5 file. We don't
get it from any mirrors.
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
tomatically.
Right. If we are successful as a TLP, then somewhere in the world at any
given time some developer will be installing some older version of Apache
Flex on a computer. Many Flex shops are stuck on older versions because it
takes a while to approve new versions for use. So they have to
make sure the
> release wasn't tampered by the dist...
Interesting point. Anybody know wny we don't fetch the MD5 from the
apache.org DIST (sans Mirror as recommended by Apache).
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
eople at Spoon have offered to host them. Want me to ping
> them if it becomes a problem?
>
I would like to see Spoon decide whether they want to be this external
entity that fills the gaps with Apache. One concern I have is that the name
Spoon isn't all that meaningful anymore.
-
o execute a distributor's agreement since Adobe
licensing is not Apache compatible.
If I were to start my own "company" I would seek such a distributors
agreement.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
HI,
> I don't see why our binary distributions would be a problem to host
> anywhere... The added stuff the installer downloads -- we can't host
> those, but the binary stuff should be ok.
The binary kit as produced by Apache is fine and could be hosted anywhere,
what I meant was a complete zi
I don't see why our binary distributions would be a problem to host
anywhere... The added stuff the installer downloads -- we can't host
those, but the binary stuff should be ok.
I know that the people at Spoon have offered to host them. Want me to ping
them if it becomes a problem?
-Nick
On T
Hi,
Also keep in mind is that the installer is provided as a convenience for SDK
users to download the binary kit and all 3rd party required pieces and get it
working in there IDE with a mimimum of trouble. While supporting multiple
versions to download etc would be a nice to have feature it's
[
https://issues.apache.org/jira/browse/FLEX-33308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541930#comment-13541930
]
Cyrill Zadra commented on FLEX-33308:
-
hey chema
I just tried to run the SDKSWC
Hi,
I'm not sure there's a reason to set the Flash Player version for the SDK other
than the mimimum version.
The Flash player version can be set on a project by project basis when using an
IDE, an SDK compiled for 11.1 can be compiled into a project that uses 11.1 -
11.6.
I'm not tested a S
Wouldn't we want to keep the config file on our website / SVN? It seems to
me that placing the config file on any of the DISTS would be disasterious,
as this contains the MD5 checksum that the app verifies to make sure the
release wasn't tampered by the dist...
What are the thoughts on doing vers
Perhaps another useful addition would be to offer a UI similar to what the
AIR Launchpad does, where the user selects the APIs they want to take
advantage of ( workers, Stage3D, etc.) and the application indicates to
them what Flex SDK / AIR SDK / PlayerGlobals are the minimum required, and
will
Hi,
> 2) Is this a correct implementation? I'm wondering how would we test the
> next release. As soon as you replace/update that .xml file so we can test
> the next installer we are forcing everyone to suddenly start taking the next
> version. I understand you are saying we don't need to "test
Hi,
> How does the UI handle choosing which version to download?
Currently it downloads the latest Flex version. If it was to download previous
version it would need to get them fro the archive and need to be configured
with multiple URLs.
I think it was decided not to do this as having
Hi,
> Is there a specific reason why we are targeting FP 11.1 as opposed to 11.4 or
> 11.5?
To not force people to update Flash Player and change the minimum player level
the Flex confg file.
The SDK will work with 11.4 and 11.5 but currently uses no 11.4 or 11.5
features so there n
Hi,
>> Would you consider the disclaimer page to be part of the source?
> The DISCLAIMER file is in the source kit for incubating releases.
I was referring to the disclaimer link in the application not the DISCLAIMER
file.
> Source kits are (potentially filtered) dumps of what is in SVN.
And th
1 - 100 of 7529 matches
Mail list logo
