Re: Flash Player 11.5 - Debug trace in release player

[Justin Mclean]

Hi,

> Is it not working for FB4?? I have upgrade the SDK.
If you using the 4.5+ SDK it may work in FB4. You may have some luck using the 
-targetplayer compiler option rather than the -swf-version compiler option in 
FB4 using an SDK earlier than 4.5. I've not tried either so if someone does 
feedback here would be good.

Thanks,
Justin

AW: Splitting up Flex and Air?

[christofer.d...@c-ware.de]

Hi Om,

Well I think this would definitely be a cool thing. Then the user will have 
several ways of getting a mavenized FDK (Intaller, Manually Mavenizing, 
Mavenizer integrated into the maven-flex-plugin and by using the 
auto-download-feature of the maven-flex-plugin (the one I was talking to Alex 
about)).

But before officially adding this, I'd like to modify the mavenizer to 
correctly mavenize the Air compiler artifacts (adt.jar, smaili.jar and 
baksmali.jar)
 
Chris


-Ursprüngliche Nachricht-
Von: omup...@gmail.com [mailto:omup...@gmail.com] Im Auftrag von Om
Gesendet: Donnerstag, 31. Januar 2013 02:35
An: dev@flex.apache.org
Betreff: Re: Splitting up Flex and Air?

Chris, I meant to reply earlier, but forgot.

The installer already downloads everything while displaying the required 
licenses along the way.  Do you think having a "Mavenize" button at the end 
would be a good idea?  We could just call your mavenize ant script from the AIR 
app.  Please let me know if this is something you would be interested.
 I would be glad to help you out with this.

Thanks,
Om

On Mon, Jan 28, 2013 at 9:20 AM, christofer.d...@c-ware.de < 
christofer.d...@c-ware.de> wrote:

> Hey ... I was never talking about distributing them ... The mavenizer 
> is all about you downloading (after Accepting whatever license Adobe 
> wants you to accept). And then simply to transform this download on 
> your local machine. So every user that wants to use it has to mavenize 
> a FDK before using it.
>
> The tool I promised to create (as soon as I have the time to do so) 
> will take care of the downloading but at this point the Mavenizer 
> expects you to download the stuff manually and this code will be the 
> base for the tool I am intending on building ... but I don't want to 
> go into a discussion about this again.
>
> Currently I'll simply stick to mavenizing every jar in the Air SDK 
> into the groupId "com.adobe.air.compiler" and hard-code an exception 
> to omit the
> 3 files from "com.adobe.flex.compiler" or "org.apache.flex.compiler". 
> I think this should do the trick.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Alex Harui [mailto:aha...@adobe.com]
> Gesendet: Montag, 28. Januar 2013 18:02
> An: dev@flex.apache.org
> Betreff: Re: Splitting up Flex and Air?
>
>
>
>
> On 1/28/13 12:25 AM, "christofer.d...@c-ware.de" < 
> christofer.d...@c-ware.de>
> wrote:
>
> > Hi,
> >
> > a while ago a user complained that in my Mavenizer I was deploying 
> > the Air jars in {fdk-root}/lib to the group 
> > org.apache.flex.compiler/com.adobe.flex.compiler ... ths is indeed 
> > not quite correct and I would like to fix this.
> >
> > All Air sdks except 2.6 contain only adt.jar so I think I'm on the 
> > safe side, but 2.6 has more libs "baksmali.jar", "smali.jar". So 
> > would it be safe to hard-code these three jars and to place them in 
> > "com.adobe.air.compiler", or would this have negative side-effects?
> >
> I don't know what those jars do.  If they come from the Adobe AIR SDK 
> download then unless you have a redistribution agreement with Adobe, 
> it is technically not allowed for these jars to be in FlexMojos distribution.
>
> That's why in the Apache Flex Maven utilities you promised to write 
> that download utility that requires the user accept the license and 
> then get the stuff from Adobe.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

Re: Flash Player 11.5 - Debug trace in release player

[manish sharma]

Hi,

Is it not working for FB4?? I have upgrade the SDK.


Regards,

Manish


On Thu, Jan 31, 2013 at 5:11 AM, Justin Mclean wrote:

> Hi,
>
> > Is there anything I'm missing ?
> You're actually compiling with the compiler that come with 4.1 SDK  and it
> doesn't support that option. Try -target-player option instead that may
> work (I've not tried it), otherwise you'll need to to use 4.5.
>
> Justin
>
>

[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying

[Alex Harui (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567388#comment-13567388
 ] 

Alex Harui commented on FLEX-33372:
---

One more question: Are you creating a Flex Mobile application?  Mobile apps do 
not use RichEditableText and use TextField like mx:TextInput.

In this issue: https://issues.apache.org/jira/browse/FLEX-33366 I describe how 
to swap in a mobile TextInput skin for a non-mobile app and get the Spark 
TextInput to use TextField.  Of course, you have to give up right-to-left text 
support if you use TextField instead of TLF.



> Windows 8 on-screen touch keyboard not displaying
> -
>
> Key: FLEX-33372
> URL: https://issues.apache.org/jira/browse/FLEX-33372
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: RichEditableText, Spark: TextArea, Spark: 
> TextInput
>Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0
> Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark RichEditableText 
> based text input components. It does get displayed when displayAsPassword 
> property is set to true. It does get displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput, s:TextInput with 
> displayAsPassword="true" and mx:TextInput
> 
> 
> 
> 2. Open this application in the Metro Internet Explorer on a touch-enabled 
> Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see 
> http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard 
> shows
> 5. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: 
> http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying

[Stepan Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567383#comment-13567383
 ] 

Stepan Hilbert commented on FLEX-33372:
---

> ...setting focus to a TextInput with displayAsPassword that is actually 
> hidden behind...
That might work, not exactly pretty though :-). But yes, either that or we 
might end up rebuilding what we have on top of mx:TextInput

> ...make a copy of RichEditableText
I tried making a copy of RichEditableText (& RichEditableTextManager). I had to 
do only very minor changes to make those compile- so the copied component was 
near identical with RichEditableText. Somehow though, even if the copied 
component had displayAsPassword="true" it wouldn't trigger the keyboard.
 



> Windows 8 on-screen touch keyboard not displaying
> -
>
> Key: FLEX-33372
> URL: https://issues.apache.org/jira/browse/FLEX-33372
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: RichEditableText, Spark: TextArea, Spark: 
> TextInput
>Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0
> Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark RichEditableText 
> based text input components. It does get displayed when displayAsPassword 
> property is set to true. It does get displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput, s:TextInput with 
> displayAsPassword="true" and mx:TextInput
> 
> 
> 
> 2. Open this application in the Metro Internet Explorer on a touch-enabled 
> Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see 
> http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard 
> shows
> 5. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: 
> http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: FlashBuilder

[Alex Harui]

Scott Castle was going to look into it.  I'll try to follow up.


On 1/30/13 6:44 PM, "Michael A. Labriola" 
wrote:

> Any chance the Flash Builder news could be updated to reflect our release as a
> project instead of an incubator?
> 
> Mike

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying

[Alex Harui (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567370#comment-13567370
 ] 

Alex Harui commented on FLEX-33372:
---

I'm just thinking that a workaround would consist of setting focus to a 
TextInput with displayAsPassword that is actually hidden behind a TextInput 
without displayAsPassword.  If that allows the keyboard to show up, then you 
can reflect what is typed into the hidden TextInput into the one on top.

Another experiment, if you have time to play around, is to make a copy of 
RichEditableText and fool around with the code paths that are affected by 
displayAsPassword until you find out which code path it is that allows the 
keyboard to come up.  That might provide a clue to other workarounds.

> Windows 8 on-screen touch keyboard not displaying
> -
>
> Key: FLEX-33372
> URL: https://issues.apache.org/jira/browse/FLEX-33372
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: RichEditableText, Spark: TextArea, Spark: 
> TextInput
>Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0
> Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark RichEditableText 
> based text input components. It does get displayed when displayAsPassword 
> property is set to true. It does get displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput, s:TextInput with 
> displayAsPassword="true" and mx:TextInput
> 
> 
> 
> 2. Open this application in the Metro Internet Explorer on a touch-enabled 
> Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see 
> http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard 
> shows
> 5. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: 
> http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Stage3D accelerated Flex components

[Daniel Freeman]

Sorry, yes.  I was referring to the new roadmap.
http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html

I've blogged about the news here:
http://madskool.wordpress.com/2013/01/30/adobes-cut-price-roadmap-and-mc3dnext

@Kevin, I can accomplish miraculous graphics performance when I code
natively in: Android Java / Objective-C / MarmaladeSDK,  just using
canvas-style graphics: SurfaceView / Core Graphics / Iw2D - and I STILL get
better graphics performance than I can get fiddling around with Stage3D at
a low level, juggling with vertices, and indices, and AGAL shaders.

I'm pretty attached to freely styling component appearances, and freely
styled text labels.  I don't want to build a framework where developers
need to make new SpriteSheets and Bitmap Font sheets - to change styling.

Right now I'm stuck with drawing to the display-list first, and then
converting DisplayObject surfaces to Stage3D textures.  That's a
bottleneck.  DisplayObject -> Texture.

I don't want to use the old legacy display list.  So I've put in a feature
request for a better way to draw vector graphics and freely-styled text to
textures (or BitmapData, or some other data type that uploads quickly as a
texture).

For example:

texture.graphics.beginFill(0x00);
texture.graphics.drawRoundRect(10.0, 10.0, 100.0, 50.0, 20.0);

texture.graphics.drawText("Hello", 30.0, 40.0, textFormat);

[jira] [Resolved] (FLEX-33361) [WEBSITE] Enable link tracking analysis for flex.apache.org

[Nick Kwiatkowski (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Kwiatkowski resolved FLEX-33361.
-

Resolution: Implemented

Added tracking code for UA-37926454-1 to website and added privacy policy to 
footer of each tracked page.

> [WEBSITE] Enable link tracking analysis for flex.apache.org
> ---
>
> Key: FLEX-33361
> URL: https://issues.apache.org/jira/browse/FLEX-33361
> Project: Apache Flex
>  Issue Type: Improvement
>Reporter: OmPrakash Muppirala
>Assignee: Nick Kwiatkowski
>
> Discussion here: http://markmail.org/message/dpmcb5hi5y7olwu2
> One of the easiest ways to enable tracking statistics on our website would be 
> to use Google Analytics.  If the Flex PMC agrees, this would be the steps.  
> Things to do:
> 1.  Enable GA on flex.apache.org
> 2.  Make stats available to Flex PMC
> 3.  Share GA credentials to Flex PMC
> 4.  Add a privacy-policy page to flex.apache.org a la 
> http://jackrabbit.apache.org/privacy-policy.html
> 5.  Include a link to the opt out plug in: 
> https://tools.google.com/dlpage/gaoptout

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Flash Platform Whitepaper

[Nicholas Kwiatkowski]

Yeah... They tried that once already.  They submitted to have a large
portion of AS3 become the next ECMAScript -- and after a bit of a tizzy,
they were rejected.

-Nick

On Wed, Jan 30, 2013 at 1:46 AM, Avi Kessner  wrote:

> Read to me like they are working on making AS3 the new Javascript.  Just
> saying. :)
>
> brought to you by the letters A, V, and I
> and the number 47
>
>
> On Wed, Jan 30, 2013 at 7:56 AM, Kevin Newman 
> wrote:
>
> > I read the whole thing as Flash entering sunset mode. Basically, Adobe
> > doesn't want to make their AIR package competitive, so they are throwing
> in
> > the towel, while allowing Flash Player in the browser to coast to it's
> > inevitable demise. That's my read anyway.
> >
> > Kevin N.
> >
> >
>

FlashBuilder

[Michael A. Labriola]

Any chance the Flash Builder news could be updated to reflect our release as a 
project instead of an incubator?

Mike

Re: A code name for Apache Flex 5?

[Carol Frampton]

On 1/29/13 5:59 AM, "Sebastian Mohr"  wrote:

>Hi there,
>
>Since using code names for Adobe Flex seemed to be a
>good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we
>should find a code name for Apache Flex 5? Thoughts?
>

I see no reason for a code name.  I think it will only confuse things.

Carol



>
>-- 
>Sebastian (PPMC)
>Interaction Designer
>
>Looking for a Login Example with Apache Flex? Please check out this code:
>http://code.google.com/p/masuland/wiki/LoginExample

Re: Editing the new site

[Nicholas Kwiatkowski]

It's on my to-do list to document the process a lot more on the Wiki.  Hope
to have some time to work on it this weekend.

-Nick

On Wed, Jan 30, 2013 at 5:58 PM, Frédéric THOMAS wrote:

> And to use the CMS feature, I created a favorite with this URL:
> javascript:void(location.href=**'https://cms.apache.org/**
> redirect?uri='+escape(**location.href) Sent: Wednesday, January 30, 2013 11:56 PM
> To: dev@flex.apache.org
> Subject: Re: Editing the new site
>
>
> try http://flex.staging.apache.**org/ 
>
> -Fred
>
> -Message d'origine- From: Gordon Smith
> Sent: Wednesday, January 30, 2013 11:50 PM
> To: dev@flex.apache.org
> Subject: Editing the new site
>
> Now that the new site is live, what URLs do we use to preview staged
> changes
> and push them live? The URLs were documented on the old site, but I can't
> find them any more.
>
> - Gordon
>
>

Re: [Website] New website going live

[Nicholas Kwiatkowski]

Thanks for catching that, it lead me to the answer.  That wasn't in the
source, but the CMS decided to interpret 4 extra spaces at the end of the
div tag as a paragraph.  It is fixed now.

Did I mention how much I <3 mdtext.  I really do.

-Nick

On Wed, Jan 30, 2013 at 6:08 PM, Harbs  wrote:

> I figured out the problem.
>
> There's an extra  tag before the first sub-div in that row:
>
> 
> --->  <---
> 
> 
> 
> 
> 
> 
>
> Harbs
>
> On Jan 30, 2013, at 10:37 PM, Nicholas Kwiatkowski wrote:
>
> > Yeah, I'm still trying to figure that one out.  The div tags are even
> > between everybody, and there is nothing really in there to make him
> appear
> > on another line.  It is still on the hit-list ;)
> >
> > -Nick
> >
> > On Wed, Jan 30, 2013 at 3:13 PM, Harbs  wrote:
> >
> >> Sure. I probably should have posted in a separate thread. The two
> efforts
> >> are not directly connected. Looking at the page source on the blog,
> >> everything seems to be pretty neat in terms of divs, etc. but yes. Let's
> >> definitely get the main site out first! Great job! :-)
> >>
> >> BTW, Sebastian Mohr is still kind of lonely there in the second to last
> >> row of the team page… ;-)
> >>
> >> Harbs
> >>
> >> On Jan 30, 2013, at 8:43 PM, Nicholas Kwiatkowski wrote:
> >>
> >>> I'll take a look at it.  I'm not sure /how/ much we can do with the
> blog
> >> (I
> >>> don't know if they use DIVs, etc., as I've only briefly played with
> their
> >>> setup).
> >>>
> >>> For right now, it is functional so I'm not going to hold up switching
> the
> >>> main site over.  We can play with that in a bit.
> >>>
> >>> -Nick
> >>>
> >>> On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:
> >>>
>  Okay. So I guess I'll wait and see if anyone else thinks styling the
> >> blog
>  is a good idea… ;-)
> 
>  Harbs
> 
>  On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
> 
> > On Wed, Jan 30, 2013 at 2:34 PM, Harbs 
> wrote:
> >> ...Flex seems to have a css file specific to the Flex blog here:
>  http://blogs.apache.org/flex/page/asf-custom.css
> >>
> >> It seems to me a question as to whether there's a policy against
>  customizing the blog more than anything else…
> >
> > I don't think there's an ASF policy, you'll need to find out if
> > infrastructure@ agrees with giving someone from the Flex PMC access
> to
> > that styling configuration. If it's just CSS, it shouldn't be too
> > hard.
> >
> > -Bertrand
> 
> 
> >>
> >>
>
>

[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying

[Stepan Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567252#comment-13567252
 ] 

Stepan Hilbert commented on FLEX-33372:
---

I've added a Flash-only test case to the Flash Player bug. The issue can be 
replicated using TLFTextField - so it seems to be a Player issue.

Paste won't be a workaround as there's nothing to paste (users have no keyboard 
to write on). Toggling displayAsPassword doesn't seem to be useful for a 
workaround either.

> Windows 8 on-screen touch keyboard not displaying
> -
>
> Key: FLEX-33372
> URL: https://issues.apache.org/jira/browse/FLEX-33372
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: RichEditableText, Spark: TextArea, Spark: 
> TextInput
>Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0
> Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark RichEditableText 
> based text input components. It does get displayed when displayAsPassword 
> property is set to true. It does get displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput, s:TextInput with 
> displayAsPassword="true" and mx:TextInput
> 
> 
> 
> 2. Open this application in the Metro Internet Explorer on a touch-enabled 
> Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see 
> http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard 
> shows
> 5. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: 
> http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Release target and Batik

[Frédéric THOMAS]

In my case I didn't want to do a full release with build number and others, 
I needed it only to mavenized it as a snapshot but I read the wiki link and 
found it very well done, thanks.


Fred.

-Message d'origine- 
From: Justin Mclean

Sent: Thursday, January 31, 2013 3:03 AM
To: dev@flex.apache.org
Subject: Re: Release target and Batik

Hi,

Justin, btw, when the build_release script is supposed to called ? do I 
have to call it by manualy ?

You can make a release by hand but the script helps speed up the process.

There information on making a release here that is reasonably up to date:
https://cwiki.apache.org/FLEX/release-guide-for-the-sdk.html

I think it's only missing that a release (once checked voted on) is now 
committed to SVN rather than scped.


Justin 

Re: Release target and Batik

[Justin Mclean]

Hi,

> Justin, btw, when the build_release script is supposed to called ? do I have 
> to call it by manualy ?
You can make a release by hand but the script helps speed up the process.

There information on making a release here that is reasonably up to date:
https://cwiki.apache.org/FLEX/release-guide-for-the-sdk.html

I think it's only missing that a release (once checked voted on) is now 
committed to SVN rather than scped.

Justin

Re: Release target and Batik

[Frédéric THOMAS]

Justin, btw, when the build_release script is supposed to called ? do I have 
to call it by manualy ? (I only ran an ant release)


-Fred


-Message d'origine- 
From: Justin Mclean

Sent: Thursday, January 31, 2013 2:37 AM
To: dev@flex.apache.org
Subject: Re: Release target and Batik

Hi,

If you don't have the lib directory then perhaps you don't have a full SVN 
checkout? Try a full checkout.


Also I think that in order to do a ant release you need to do an ordinary 
ant main first. Take a look at the build_release script in the release_build 
directory.


Hope that helps,
Justin 

Re: Release target and Batik

[Frédéric THOMAS]

Hi Justin,

I did a full checkout and had the lib dir and did a first build before I 
tryied a release from a copy of this built develop branch, the problem id 
that the lib dir is deleted at some point during the release and before the 
init of the batik build which except it to be present.


-Fred

-Message d'origine- 
From: Justin Mclean

Sent: Thursday, January 31, 2013 2:37 AM
To: dev@flex.apache.org
Subject: Re: Release target and Batik

Hi,

If you don't have the lib directory then perhaps you don't have a full SVN 
checkout? Try a full checkout.


Also I think that in order to do a ant release you need to do an ordinary 
ant main first. Take a look at the build_release script in the release_build 
directory.


Hope that helps,
Justin 

Re: Release target and Batik

[Justin Mclean]

Hi,

If you don't have the lib directory then perhaps you don't have a full SVN 
checkout? Try a full checkout.

Also I think that in order to do a ant release you need to do an ordinary ant 
main first. Take a look at the build_release script in the release_build 
directory.

Hope that helps,
Justin

Re: Splitting up Flex and Air?

[Om]

Chris, I meant to reply earlier, but forgot.

The installer already downloads everything while displaying the required
licenses along the way.  Do you think having a "Mavenize" button at the end
would be a good idea?  We could just call your mavenize ant script from the
AIR app.  Please let me know if this is something you would be interested.
 I would be glad to help you out with this.

Thanks,
Om

On Mon, Jan 28, 2013 at 9:20 AM, christofer.d...@c-ware.de <
christofer.d...@c-ware.de> wrote:

> Hey ... I was never talking about distributing them ... The mavenizer is
> all about you downloading (after Accepting whatever license Adobe wants you
> to accept). And then simply to transform this download on your local
> machine. So every user that wants to use it has to mavenize a FDK before
> using it.
>
> The tool I promised to create (as soon as I have the time to do so) will
> take care of the downloading but at this point the Mavenizer expects you to
> download the stuff manually and this code will be the base for the tool I
> am intending on building ... but I don't want to go into a discussion about
> this again.
>
> Currently I'll simply stick to mavenizing every jar in the Air SDK into
> the groupId "com.adobe.air.compiler" and hard-code an exception to omit the
> 3 files from "com.adobe.flex.compiler" or "org.apache.flex.compiler". I
> think this should do the trick.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Alex Harui [mailto:aha...@adobe.com]
> Gesendet: Montag, 28. Januar 2013 18:02
> An: dev@flex.apache.org
> Betreff: Re: Splitting up Flex and Air?
>
>
>
>
> On 1/28/13 12:25 AM, "christofer.d...@c-ware.de" <
> christofer.d...@c-ware.de>
> wrote:
>
> > Hi,
> >
> > a while ago a user complained that in my Mavenizer I was deploying the
> > Air jars in {fdk-root}/lib to the group
> > org.apache.flex.compiler/com.adobe.flex.compiler ... ths is indeed not
> > quite correct and I would like to fix this.
> >
> > All Air sdks except 2.6 contain only adt.jar so I think I'm on the
> > safe side, but 2.6 has more libs "baksmali.jar", "smali.jar". So would
> > it be safe to hard-code these three jars and to place them in
> > "com.adobe.air.compiler", or would this have negative side-effects?
> >
> I don't know what those jars do.  If they come from the Adobe AIR SDK
> download then unless you have a redistribution agreement with Adobe, it is
> technically not allowed for these jars to be in FlexMojos distribution.
>
> That's why in the Apache Flex Maven utilities you promised to write that
> download utility that requires the user accept the license and then get the
> stuff from Adobe.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

Re: Release target and Batik

[Frédéric THOMAS]

Yes, sounds logical, I checked the Ant files to see where it could happen 
without success.


-Fred

-Message d'origine- 
From: Carol Frampton

Sent: Thursday, January 31, 2013 2:17 AM
To: dev@flex.apache.org
Cc: dev@flex.apache.org
Subject: Re: Release target and Batik

The lib dir should not have to be created. It exists in svn. If it doesn't 
exist then something is incorrectly deleting it.


Sent from my iPhone

On Jan 30, 2013, at 8:16 PM, "Frédéric THOMAS"  
wrote:



The modules thirdparty-clean didn't work, it didn't create the lib dir, I
put it in the init of the batik build, that's fine for you ?

-Fred

-Message d'origine- 
From: Carol Frampton

Sent: Thursday, January 31, 2013 1:59 AM
To: dev@flex.apache.org
Cc: dev@flex.apache.org
Subject: Re: Release target and Batik

It builds on both windows and Mac so I think it is something machine
specific. Do a modules thirdparty-clean and then rebuild.

Sent from my iPhone

On Jan 30, 2013, at 7:57 PM, "Alex Harui"  wrote:


It looks like batik/lib is in SVN.  Maybe the fix is to remove it from
SVN,
and add a mkdir for it in the init section of batik's build.xml.  Fred,
can
you try that out?


On 1/30/13 4:50 PM, "Carol Frampton"  wrote:


I don't quite remember. I think the lib dir used to be in svn and now it
is
not. It is created and deleted as part of the build process.

You could do a svn status on this directory. If it has a ? delete it.

Carol



Sent from my iPhone

On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
wrote:


Hi Carel,

Then, Could the problem come from the re-sync ?

-Fred

-Message d'origine-
From: Carol Frampton
Sent: Thursday, January 31, 2013 1:44 AM
To: dev@flex.apache.org
Cc: dev@flex.apache.org
Subject: Re: Release target and Batik

There were some changes in this directory for 4.9.  I saw this error
during
the transition.  I'd delete the batik dir and resync  it and then try 
to

build again.

Carol

Sent from my iPhone

On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:


Might just be a bug that needs fixing so it ignores a missing folder.
I've
found that Windows ANT is more sensitive to missing folders.  Most of
us
use
Macs which seems to ignore missing folders.


On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:


Hi,

I was trying to play with the release target but I encountered a
problem
[1],
before the release target start, I¹ve got lib folder under batik but
it
looks
like it removed it during the release, which cause that error.

Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
 [echo] PLAYERGLOBAL_HOME is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player
 [echo] playerglobal.version is 11.1
 [echo] playerglobal.swc is

U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw
c


check-air-home:
 [echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
 [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
Utilities -
CS5\Pixel Bender Toolkit 2

check-compile-env:
 [echo] OS: Windows 7 / 6.1 / x86
 [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
 [echo] Java: 1.6.0_33
 [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20
2010
Ant
Java Version: 1.6

check-runtime-env:

check-adobe-extension-manager-env:
 [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
Extension Manager CS5\Adobe Extension Manager
CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
[delete] Deleting directory
U:\sources\asf\flex\sdk\developRC1\lib\external\optional

modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
occurred
while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The
following
error
occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
U:\sources\asf\flex\sdk\developRC1\modules\th
irdparty\batik\lib does not exist.

Total time: 1 second


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Release target and Batik

[Alex Harui]

Yeah, but why not delete it from SVN?  There are no files in it.


On 1/30/13 5:17 PM, "Carol Frampton"  wrote:

> The lib dir should not have to be created. It exists in svn. If it doesn't
> exist then something is incorrectly deleting it.
> 
> Sent from my iPhone
> 
> On Jan 30, 2013, at 8:16 PM, "Frédéric THOMAS" 
> wrote:
> 
>> The modules thirdparty-clean didn't work, it didn't create the lib dir, I
>> put it in the init of the batik build, that's fine for you ?
>> 
>> -Fred
>> 
>> -Message d'origine-
>> From: Carol Frampton
>> Sent: Thursday, January 31, 2013 1:59 AM
>> To: dev@flex.apache.org
>> Cc: dev@flex.apache.org
>> Subject: Re: Release target and Batik
>> 
>> It builds on both windows and Mac so I think it is something machine
>> specific. Do a modules thirdparty-clean and then rebuild.
>> 
>> Sent from my iPhone
>> 
>> On Jan 30, 2013, at 7:57 PM, "Alex Harui"  wrote:
>> 
>>> It looks like batik/lib is in SVN.  Maybe the fix is to remove it from
>>> SVN,
>>> and add a mkdir for it in the init section of batik's build.xml.  Fred,
>>> can
>>> you try that out?
>>> 
>>> 
>>> On 1/30/13 4:50 PM, "Carol Frampton"  wrote:
>>> 
 I don't quite remember. I think the lib dir used to be in svn and now it
 is
 not. It is created and deleted as part of the build process.
 
 You could do a svn status on this directory. If it has a ? delete it.
 
 Carol
 
 
 
 Sent from my iPhone
 
 On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
 wrote:
 
> Hi Carel,
> 
> Then, Could the problem come from the re-sync ?
> 
> -Fred
> 
> -Message d'origine-
> From: Carol Frampton
> Sent: Thursday, January 31, 2013 1:44 AM
> To: dev@flex.apache.org
> Cc: dev@flex.apache.org
> Subject: Re: Release target and Batik
> 
> There were some changes in this directory for 4.9.  I saw this error
> during
> the transition.  I'd delete the batik dir and resync  it and then try to
> build again.
> 
> Carol
> 
> Sent from my iPhone
> 
> On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:
> 
>> Might just be a bug that needs fixing so it ignores a missing folder.
>> I've
>> found that Windows ANT is more sensitive to missing folders.  Most of
>> us
>> use
>> Macs which seems to ignore missing folders.
>> 
>> 
>> On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:
>> 
>>> Hi,
>>> 
>>> I was trying to play with the release target but I encountered a
>>> problem
>>> [1],
>>> before the release target start, I¹ve got lib folder under batik but
>>> it
>>> looks
>>> like it removed it during the release, which cause that error.
>>> 
>>> Can someone help ?
>>> 
>>> -Fred
>>> 
>>> [1]
>>> $ ant release
>>> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
>>> 
>>> check-playerglobal-home:
>>>  [echo] PLAYERGLOBAL_HOME is
>>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>>>  [echo] playerglobal.version is 11.1
>>>  [echo] playerglobal.swc is
>>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw>
>>> >>>
>>> c
>>> 
>>> check-air-home:
>>>  [echo] AIR_HOME is U:\sources\adobe\air\3.4
>>> 
>>> check-pixelbender-home:
>>>  [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
>>> Utilities -
>>> CS5\Pixel Bender Toolkit 2
>>> 
>>> check-compile-env:
>>>  [echo] OS: Windows 7 / 6.1 / x86
>>>  [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>>>  [echo] Java: 1.6.0_33
>>>  [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20
>>> 2010
>>> Ant
>>> Java Version: 1.6
>>> 
>>> check-runtime-env:
>>> 
>>> check-adobe-extension-manager-env:
>>>  [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
>>> Extension Manager CS5\Adobe Extension Manager
>>> CS5.exe
>>> 
>>> thirdparty-clean:
>>> 
>>> thirdparty-clean:
>>> 
>>> batik-jars-clean:
>>> 
>>> velocity-jars-clean:
>>> 
>>> clean:
>>> 
>>> thirdparty-clean:
>>> 
>>> swfobject-clean:
>>> 
>>> swfobject-fabridge-clean:
>>> 
>>> clean-adobe-flex-sdk:
>>> 
>>> clean:
>>> [delete] Deleting directory
>>> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
>>> 
>>> modules-clean:
>>> 
>>> batik-clean:
>>> 
>>> init:
>>> 
>>> BUILD FAILED
>>> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
>>> occurred
>>> while executing this line:
>>> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The
>>> following
>>> error
>>> occurred while executing this line:
>>> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:16
>>> 1:
>>> U:\sources\asf\flex\sdk\dev

Re: Release target and Batik

[Carol Frampton]

The lib dir should not have to be created. It exists in svn. If it doesn't 
exist then something is incorrectly deleting it.

Sent from my iPhone

On Jan 30, 2013, at 8:16 PM, "Frédéric THOMAS"  wrote:

> The modules thirdparty-clean didn't work, it didn't create the lib dir, I 
> put it in the init of the batik build, that's fine for you ?
> 
> -Fred
> 
> -Message d'origine- 
> From: Carol Frampton
> Sent: Thursday, January 31, 2013 1:59 AM
> To: dev@flex.apache.org
> Cc: dev@flex.apache.org
> Subject: Re: Release target and Batik
> 
> It builds on both windows and Mac so I think it is something machine 
> specific. Do a modules thirdparty-clean and then rebuild.
> 
> Sent from my iPhone
> 
> On Jan 30, 2013, at 7:57 PM, "Alex Harui"  wrote:
> 
>> It looks like batik/lib is in SVN.  Maybe the fix is to remove it from 
>> SVN,
>> and add a mkdir for it in the init section of batik's build.xml.  Fred, 
>> can
>> you try that out?
>> 
>> 
>> On 1/30/13 4:50 PM, "Carol Frampton"  wrote:
>> 
>>> I don't quite remember. I think the lib dir used to be in svn and now it 
>>> is
>>> not. It is created and deleted as part of the build process.
>>> 
>>> You could do a svn status on this directory. If it has a ? delete it.
>>> 
>>> Carol
>>> 
>>> 
>>> 
>>> Sent from my iPhone
>>> 
>>> On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
>>> wrote:
>>> 
 Hi Carel,
 
 Then, Could the problem come from the re-sync ?
 
 -Fred
 
 -Message d'origine-
 From: Carol Frampton
 Sent: Thursday, January 31, 2013 1:44 AM
 To: dev@flex.apache.org
 Cc: dev@flex.apache.org
 Subject: Re: Release target and Batik
 
 There were some changes in this directory for 4.9.  I saw this error 
 during
 the transition.  I'd delete the batik dir and resync  it and then try to
 build again.
 
 Carol
 
 Sent from my iPhone
 
 On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:
 
> Might just be a bug that needs fixing so it ignores a missing folder.
> I've
> found that Windows ANT is more sensitive to missing folders.  Most of 
> us
> use
> Macs which seems to ignore missing folders.
> 
> 
> On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:
> 
>> Hi,
>> 
>> I was trying to play with the release target but I encountered a 
>> problem
>> [1],
>> before the release target start, I¹ve got lib folder under batik but 
>> it
>> looks
>> like it removed it during the release, which cause that error.
>> 
>> Can someone help ?
>> 
>> -Fred
>> 
>> [1]
>> $ ant release
>> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
>> 
>> check-playerglobal-home:
>>  [echo] PLAYERGLOBAL_HOME is
>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>>  [echo] playerglobal.version is 11.1
>>  [echo] playerglobal.swc is
>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw
>> c
>> 
>> check-air-home:
>>  [echo] AIR_HOME is U:\sources\adobe\air\3.4
>> 
>> check-pixelbender-home:
>>  [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
>> Utilities -
>> CS5\Pixel Bender Toolkit 2
>> 
>> check-compile-env:
>>  [echo] OS: Windows 7 / 6.1 / x86
>>  [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>>  [echo] Java: 1.6.0_33
>>  [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 
>> 2010
>> Ant
>> Java Version: 1.6
>> 
>> check-runtime-env:
>> 
>> check-adobe-extension-manager-env:
>>  [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
>> Extension Manager CS5\Adobe Extension Manager
>> CS5.exe
>> 
>> thirdparty-clean:
>> 
>> thirdparty-clean:
>> 
>> batik-jars-clean:
>> 
>> velocity-jars-clean:
>> 
>> clean:
>> 
>> thirdparty-clean:
>> 
>> swfobject-clean:
>> 
>> swfobject-fabridge-clean:
>> 
>> clean-adobe-flex-sdk:
>> 
>> clean:
>> [delete] Deleting directory
>> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
>> 
>> modules-clean:
>> 
>> batik-clean:
>> 
>> init:
>> 
>> BUILD FAILED
>> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
>> occurred
>> while executing this line:
>> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The 
>> following
>> error
>> occurred while executing this line:
>> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
>> U:\sources\asf\flex\sdk\developRC1\modules\th
>> irdparty\batik\lib does not exist.
>> 
>> Total time: 1 second
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>> 
>> -- 
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.a

Re: Release target and Batik

[Frédéric THOMAS]

The modules thirdparty-clean didn't work, it didn't create the lib dir, I 
put it in the init of the batik build, that's fine for you ?


-Fred

-Message d'origine- 
From: Carol Frampton

Sent: Thursday, January 31, 2013 1:59 AM
To: dev@flex.apache.org
Cc: dev@flex.apache.org
Subject: Re: Release target and Batik

It builds on both windows and Mac so I think it is something machine 
specific. Do a modules thirdparty-clean and then rebuild.


Sent from my iPhone

On Jan 30, 2013, at 7:57 PM, "Alex Harui"  wrote:

It looks like batik/lib is in SVN.  Maybe the fix is to remove it from 
SVN,
and add a mkdir for it in the init section of batik's build.xml.  Fred, 
can

you try that out?


On 1/30/13 4:50 PM, "Carol Frampton"  wrote:

I don't quite remember. I think the lib dir used to be in svn and now it 
is

not. It is created and deleted as part of the build process.

You could do a svn status on this directory. If it has a ? delete it.

Carol



Sent from my iPhone

On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
wrote:


Hi Carel,

Then, Could the problem come from the re-sync ?

-Fred

-Message d'origine-
From: Carol Frampton
Sent: Thursday, January 31, 2013 1:44 AM
To: dev@flex.apache.org
Cc: dev@flex.apache.org
Subject: Re: Release target and Batik

There were some changes in this directory for 4.9.  I saw this error 
during

the transition.  I'd delete the batik dir and resync  it and then try to
build again.

Carol

Sent from my iPhone

On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:


Might just be a bug that needs fixing so it ignores a missing folder.
I've
found that Windows ANT is more sensitive to missing folders.  Most of 
us

use
Macs which seems to ignore missing folders.


On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:


Hi,

I was trying to play with the release target but I encountered a 
problem

[1],
before the release target start, I¹ve got lib folder under batik but 
it

looks
like it removed it during the release, which cause that error.

Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
  [echo] PLAYERGLOBAL_HOME is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player
  [echo] playerglobal.version is 11.1
  [echo] playerglobal.swc is

U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw
c


check-air-home:
  [echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
  [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
Utilities -
CS5\Pixel Bender Toolkit 2

check-compile-env:
  [echo] OS: Windows 7 / 6.1 / x86
  [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
  [echo] Java: 1.6.0_33
  [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 
2010

Ant
Java Version: 1.6

check-runtime-env:

check-adobe-extension-manager-env:
  [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
Extension Manager CS5\Adobe Extension Manager
CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
[delete] Deleting directory
U:\sources\asf\flex\sdk\developRC1\lib\external\optional

modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
occurred
while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The 
following

error
occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
U:\sources\asf\flex\sdk\developRC1\modules\th
irdparty\batik\lib does not exist.

Total time: 1 second


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Release target and Batik

[Carol Frampton]

That isn't the right fix since it is in svn.  Something must be cleaning 
/deleting it when it shouldn't be.

Sent from my iPhone

On Jan 30, 2013, at 8:10 PM, "Frédéric THOMAS"  wrote:

> Adding  a  works, it's running, thanks guys :-)
> 
> -Fred
> 
> -Message d'origine- 
> From: Alex Harui
> Sent: Thursday, January 31, 2013 1:56 AM
> To: dev@flex.apache.org
> Subject: Re: Release target and Batik
> 
> It looks like batik/lib is in SVN.  Maybe the fix is to remove it from SVN,
> and add a mkdir for it in the init section of batik's build.xml.  Fred, can
> you try that out?
> 
> 
> On 1/30/13 4:50 PM, "Carol Frampton"  wrote:
> 
>> I don't quite remember. I think the lib dir used to be in svn and now it 
>> is
>> not. It is created and deleted as part of the build process.
>> 
>> You could do a svn status on this directory. If it has a ? delete it.
>> 
>> Carol
>> 
>> 
>> 
>> Sent from my iPhone
>> 
>> On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
>> wrote:
>> 
>>> Hi Carel,
>>> 
>>> Then, Could the problem come from the re-sync ?
>>> 
>>> -Fred
>>> 
>>> -Message d'origine-
>>> From: Carol Frampton
>>> Sent: Thursday, January 31, 2013 1:44 AM
>>> To: dev@flex.apache.org
>>> Cc: dev@flex.apache.org
>>> Subject: Re: Release target and Batik
>>> 
>>> There were some changes in this directory for 4.9.  I saw this error 
>>> during
>>> the transition.  I'd delete the batik dir and resync  it and then try to
>>> build again.
>>> 
>>> Carol
>>> 
>>> Sent from my iPhone
>>> 
>>> On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:
>>> 
 Might just be a bug that needs fixing so it ignores a missing folder.
 I've
 found that Windows ANT is more sensitive to missing folders.  Most of us
 use
 Macs which seems to ignore missing folders.
 
 
 On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:
 
> Hi,
> 
> I was trying to play with the release target but I encountered a 
> problem
> [1],
> before the release target start, I¹ve got lib folder under batik but it
> looks
> like it removed it during the release, which cause that error.
> 
> Can someone help ?
> 
> -Fred
> 
> [1]
> $ ant release
> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
> 
> check-playerglobal-home:
>   [echo] PLAYERGLOBAL_HOME is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>   [echo] playerglobal.version is 11.1
>   [echo] playerglobal.swc is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw
> c
> 
> check-air-home:
>   [echo] AIR_HOME is U:\sources\adobe\air\3.4
> 
> check-pixelbender-home:
>   [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
> Utilities -
> CS5\Pixel Bender Toolkit 2
> 
> check-compile-env:
>   [echo] OS: Windows 7 / 6.1 / x86
>   [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>   [echo] Java: 1.6.0_33
>   [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 
> 2010
> Ant
> Java Version: 1.6
> 
> check-runtime-env:
> 
> check-adobe-extension-manager-env:
>   [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
> Extension Manager CS5\Adobe Extension Manager
> CS5.exe
> 
> thirdparty-clean:
> 
> thirdparty-clean:
> 
> batik-jars-clean:
> 
> velocity-jars-clean:
> 
> clean:
> 
> thirdparty-clean:
> 
> swfobject-clean:
> 
> swfobject-fabridge-clean:
> 
> clean-adobe-flex-sdk:
> 
> clean:
> [delete] Deleting directory
> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
> 
> modules-clean:
> 
> batik-clean:
> 
> init:
> 
> BUILD FAILED
> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
> occurred
> while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following
> error
> occurred while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
> U:\sources\asf\flex\sdk\developRC1\modules\th
> irdparty\batik\lib does not exist.
> 
> Total time: 1 second
 
 -- 
 Alex Harui
 Flex SDK Team
 Adobe Systems, Inc.
 http://blogs.adobe.com/aharui
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
> 

Re: Release target and Batik

[Frédéric THOMAS]

Adding  a  works, it's running, thanks guys :-)

-Fred

-Message d'origine- 
From: Alex Harui

Sent: Thursday, January 31, 2013 1:56 AM
To: dev@flex.apache.org
Subject: Re: Release target and Batik

It looks like batik/lib is in SVN.  Maybe the fix is to remove it from SVN,
and add a mkdir for it in the init section of batik's build.xml.  Fred, can
you try that out?


On 1/30/13 4:50 PM, "Carol Frampton"  wrote:

I don't quite remember. I think the lib dir used to be in svn and now it 
is

not. It is created and deleted as part of the build process.

You could do a svn status on this directory. If it has a ? delete it.

Carol



Sent from my iPhone

On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
wrote:


Hi Carel,

Then, Could the problem come from the re-sync ?

-Fred

-Message d'origine-
From: Carol Frampton
Sent: Thursday, January 31, 2013 1:44 AM
To: dev@flex.apache.org
Cc: dev@flex.apache.org
Subject: Re: Release target and Batik

There were some changes in this directory for 4.9.  I saw this error 
during

the transition.  I'd delete the batik dir and resync  it and then try to
build again.

Carol

Sent from my iPhone

On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:


Might just be a bug that needs fixing so it ignores a missing folder.
I've
found that Windows ANT is more sensitive to missing folders.  Most of us
use
Macs which seems to ignore missing folders.


On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:


Hi,

I was trying to play with the release target but I encountered a 
problem

[1],
before the release target start, I¹ve got lib folder under batik but it
looks
like it removed it during the release, which cause that error.

Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
   [echo] PLAYERGLOBAL_HOME is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player
   [echo] playerglobal.version is 11.1
   [echo] playerglobal.swc is


U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw
c


check-air-home:
   [echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
   [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
Utilities -
CS5\Pixel Bender Toolkit 2

check-compile-env:
   [echo] OS: Windows 7 / 6.1 / x86
   [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
   [echo] Java: 1.6.0_33
   [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 
2010

Ant
Java Version: 1.6

check-runtime-env:

check-adobe-extension-manager-env:
   [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
Extension Manager CS5\Adobe Extension Manager
CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
 [delete] Deleting directory
U:\sources\asf\flex\sdk\developRC1\lib\external\optional

modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
occurred
while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following
error
occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
U:\sources\asf\flex\sdk\developRC1\modules\th
irdparty\batik\lib does not exist.

Total time: 1 second


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui



--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Release target and Batik

[Carol Frampton]

It builds on both windows and Mac so I think it is something machine specific. 
Do a modules thirdparty-clean and then rebuild. 

Sent from my iPhone

On Jan 30, 2013, at 7:57 PM, "Alex Harui"  wrote:

> It looks like batik/lib is in SVN.  Maybe the fix is to remove it from SVN,
> and add a mkdir for it in the init section of batik's build.xml.  Fred, can
> you try that out?
> 
> 
> On 1/30/13 4:50 PM, "Carol Frampton"  wrote:
> 
>> I don't quite remember. I think the lib dir used to be in svn and now it is
>> not. It is created and deleted as part of the build process.
>> 
>> You could do a svn status on this directory. If it has a ? delete it.
>> 
>> Carol
>> 
>> 
>> 
>> Sent from my iPhone
>> 
>> On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
>> wrote:
>> 
>>> Hi Carel,
>>> 
>>> Then, Could the problem come from the re-sync ?
>>> 
>>> -Fred
>>> 
>>> -Message d'origine-
>>> From: Carol Frampton
>>> Sent: Thursday, January 31, 2013 1:44 AM
>>> To: dev@flex.apache.org
>>> Cc: dev@flex.apache.org
>>> Subject: Re: Release target and Batik
>>> 
>>> There were some changes in this directory for 4.9.  I saw this error during
>>> the transition.  I'd delete the batik dir and resync  it and then try to
>>> build again.
>>> 
>>> Carol
>>> 
>>> Sent from my iPhone
>>> 
>>> On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:
>>> 
 Might just be a bug that needs fixing so it ignores a missing folder.
 I've
 found that Windows ANT is more sensitive to missing folders.  Most of us
 use
 Macs which seems to ignore missing folders.
 
 
 On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:
 
> Hi,
> 
> I was trying to play with the release target but I encountered a problem
> [1],
> before the release target start, I¹ve got lib folder under batik but it
> looks
> like it removed it during the release, which cause that error.
> 
> Can someone help ?
> 
> -Fred
> 
> [1]
> $ ant release
> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
> 
> check-playerglobal-home:
>   [echo] PLAYERGLOBAL_HOME is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>   [echo] playerglobal.version is 11.1
>   [echo] playerglobal.swc is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw
> c
> 
> check-air-home:
>   [echo] AIR_HOME is U:\sources\adobe\air\3.4
> 
> check-pixelbender-home:
>   [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
> Utilities -
> CS5\Pixel Bender Toolkit 2
> 
> check-compile-env:
>   [echo] OS: Windows 7 / 6.1 / x86
>   [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>   [echo] Java: 1.6.0_33
>   [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
> Ant
> Java Version: 1.6
> 
> check-runtime-env:
> 
> check-adobe-extension-manager-env:
>   [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
> Extension Manager CS5\Adobe Extension Manager
> CS5.exe
> 
> thirdparty-clean:
> 
> thirdparty-clean:
> 
> batik-jars-clean:
> 
> velocity-jars-clean:
> 
> clean:
> 
> thirdparty-clean:
> 
> swfobject-clean:
> 
> swfobject-fabridge-clean:
> 
> clean-adobe-flex-sdk:
> 
> clean:
> [delete] Deleting directory
> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
> 
> modules-clean:
> 
> batik-clean:
> 
> init:
> 
> BUILD FAILED
> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
> occurred
> while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following
> error
> occurred while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
> U:\sources\asf\flex\sdk\developRC1\modules\th
> irdparty\batik\lib does not exist.
> 
> Total time: 1 second
 
 -- 
 Alex Harui
 Flex SDK Team
 Adobe Systems, Inc.
 http://blogs.adobe.com/aharui
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
> 

Re: Release target and Batik

[Alex Harui]

It looks like batik/lib is in SVN.  Maybe the fix is to remove it from SVN,
and add a mkdir for it in the init section of batik's build.xml.  Fred, can
you try that out?


On 1/30/13 4:50 PM, "Carol Frampton"  wrote:

> I don't quite remember. I think the lib dir used to be in svn and now it is
> not. It is created and deleted as part of the build process.
> 
> You could do a svn status on this directory. If it has a ? delete it.
> 
> Carol
> 
> 
> 
> Sent from my iPhone
> 
> On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS" 
> wrote:
> 
>> Hi Carel,
>> 
>> Then, Could the problem come from the re-sync ?
>> 
>> -Fred
>> 
>> -Message d'origine-
>> From: Carol Frampton
>> Sent: Thursday, January 31, 2013 1:44 AM
>> To: dev@flex.apache.org
>> Cc: dev@flex.apache.org
>> Subject: Re: Release target and Batik
>> 
>> There were some changes in this directory for 4.9.  I saw this error during
>> the transition.  I'd delete the batik dir and resync  it and then try to
>> build again.
>> 
>> Carol
>> 
>> Sent from my iPhone
>> 
>> On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:
>> 
>>> Might just be a bug that needs fixing so it ignores a missing folder.
>>> I've
>>> found that Windows ANT is more sensitive to missing folders.  Most of us
>>> use
>>> Macs which seems to ignore missing folders.
>>> 
>>> 
>>> On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:
>>> 
 Hi,
 
 I was trying to play with the release target but I encountered a problem
 [1],
 before the release target start, I¹ve got lib folder under batik but it
 looks
 like it removed it during the release, which cause that error.
 
 Can someone help ?
 
 -Fred
 
 [1]
 $ ant release
 Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
 
 check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is
 U:\sources\asf\flex\sdk\develop\frameworks\libs\player
[echo] playerglobal.version is 11.1
[echo] playerglobal.swc is
 
U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.sw
c
 
 check-air-home:
[echo] AIR_HOME is U:\sources\adobe\air\3.4
 
 check-pixelbender-home:
[echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
 Utilities -
 CS5\Pixel Bender Toolkit 2
 
 check-compile-env:
[echo] OS: Windows 7 / 6.1 / x86
[echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
[echo] Java: 1.6.0_33
[echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
 Ant
 Java Version: 1.6
 
 check-runtime-env:
 
 check-adobe-extension-manager-env:
[echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
 Extension Manager CS5\Adobe Extension Manager
 CS5.exe
 
 thirdparty-clean:
 
 thirdparty-clean:
 
 batik-jars-clean:
 
 velocity-jars-clean:
 
 clean:
 
 thirdparty-clean:
 
 swfobject-clean:
 
 swfobject-fabridge-clean:
 
 clean-adobe-flex-sdk:
 
 clean:
  [delete] Deleting directory
 U:\sources\asf\flex\sdk\developRC1\lib\external\optional
 
 modules-clean:
 
 batik-clean:
 
 init:
 
 BUILD FAILED
 U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
 occurred
 while executing this line:
 U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following
 error
 occurred while executing this line:
 U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
 U:\sources\asf\flex\sdk\developRC1\modules\th
 irdparty\batik\lib does not exist.
 
 Total time: 1 second
>>> 
>>> -- 
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Release target and Batik

[Carol Frampton]

I don't quite remember. I think the lib dir used to be in svn and now it is 
not. It is created and deleted as part of the build process. 

You could do a svn status on this directory. If it has a ? delete it. 

Carol



Sent from my iPhone

On Jan 30, 2013, at 7:46 PM, "Frédéric THOMAS"  wrote:

> Hi Carel,
> 
> Then, Could the problem come from the re-sync ?
> 
> -Fred
> 
> -Message d'origine- 
> From: Carol Frampton
> Sent: Thursday, January 31, 2013 1:44 AM
> To: dev@flex.apache.org
> Cc: dev@flex.apache.org
> Subject: Re: Release target and Batik
> 
> There were some changes in this directory for 4.9.  I saw this error during 
> the transition.  I'd delete the batik dir and resync  it and then try to 
> build again.
> 
> Carol
> 
> Sent from my iPhone
> 
> On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:
> 
>> Might just be a bug that needs fixing so it ignores a missing folder. 
>> I've
>> found that Windows ANT is more sensitive to missing folders.  Most of us 
>> use
>> Macs which seems to ignore missing folders.
>> 
>> 
>> On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:
>> 
>>> Hi,
>>> 
>>> I was trying to play with the release target but I encountered a problem 
>>> [1],
>>> before the release target start, I¹ve got lib folder under batik but it 
>>> looks
>>> like it removed it during the release, which cause that error.
>>> 
>>> Can someone help ?
>>> 
>>> -Fred
>>> 
>>> [1]
>>> $ ant release
>>> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
>>> 
>>> check-playerglobal-home:
>>>[echo] PLAYERGLOBAL_HOME is
>>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>>>[echo] playerglobal.version is 11.1
>>>[echo] playerglobal.swc is
>>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc
>>> 
>>> check-air-home:
>>>[echo] AIR_HOME is U:\sources\adobe\air\3.4
>>> 
>>> check-pixelbender-home:
>>>[echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe 
>>> Utilities -
>>> CS5\Pixel Bender Toolkit 2
>>> 
>>> check-compile-env:
>>>[echo] OS: Windows 7 / 6.1 / x86
>>>[echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>>>[echo] Java: 1.6.0_33
>>>[echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 
>>> Ant
>>> Java Version: 1.6
>>> 
>>> check-runtime-env:
>>> 
>>> check-adobe-extension-manager-env:
>>>[echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
>>> Extension Manager CS5\Adobe Extension Manager
>>> CS5.exe
>>> 
>>> thirdparty-clean:
>>> 
>>> thirdparty-clean:
>>> 
>>> batik-jars-clean:
>>> 
>>> velocity-jars-clean:
>>> 
>>> clean:
>>> 
>>> thirdparty-clean:
>>> 
>>> swfobject-clean:
>>> 
>>> swfobject-fabridge-clean:
>>> 
>>> clean-adobe-flex-sdk:
>>> 
>>> clean:
>>>  [delete] Deleting directory
>>> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
>>> 
>>> modules-clean:
>>> 
>>> batik-clean:
>>> 
>>> init:
>>> 
>>> BUILD FAILED
>>> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error 
>>> occurred
>>> while executing this line:
>>> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following 
>>> error
>>> occurred while executing this line:
>>> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
>>> U:\sources\asf\flex\sdk\developRC1\modules\th
>>> irdparty\batik\lib does not exist.
>>> 
>>> Total time: 1 second
>> 
>> -- 
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 

Re: Release target and Batik

[Frédéric THOMAS]

Hi Carel,

Then, Could the problem come from the re-sync ?

-Fred

-Message d'origine- 
From: Carol Frampton

Sent: Thursday, January 31, 2013 1:44 AM
To: dev@flex.apache.org
Cc: dev@flex.apache.org
Subject: Re: Release target and Batik

There were some changes in this directory for 4.9.  I saw this error during 
the transition.  I'd delete the batik dir and resync  it and then try to 
build again.


Carol

Sent from my iPhone

On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:

Might just be a bug that needs fixing so it ignores a missing folder. 
I've
found that Windows ANT is more sensitive to missing folders.  Most of us 
use

Macs which seems to ignore missing folders.


On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:


Hi,

I was trying to play with the release target but I encountered a problem 
[1],
before the release target start, I¹ve got lib folder under batik but it 
looks

like it removed it during the release, which cause that error.

Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player
[echo] playerglobal.version is 11.1
[echo] playerglobal.swc is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc

check-air-home:
[echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
[echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe 
Utilities -

CS5\Pixel Bender Toolkit 2

check-compile-env:
[echo] OS: Windows 7 / 6.1 / x86
[echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
[echo] Java: 1.6.0_33
[echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 
Ant

Java Version: 1.6

check-runtime-env:

check-adobe-extension-manager-env:
[echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
Extension Manager CS5\Adobe Extension Manager
CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
  [delete] Deleting directory
U:\sources\asf\flex\sdk\developRC1\lib\external\optional

modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error 
occurred

while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following 
error

occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
U:\sources\asf\flex\sdk\developRC1\modules\th
irdparty\batik\lib does not exist.

Total time: 1 second


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Release target and Batik

[Carol Frampton]

There were some changes in this directory for 4.9.  I saw this error during the 
transition.  I'd delete the batik dir and resync  it and then try to build 
again.

Carol

Sent from my iPhone

On Jan 30, 2013, at 7:17 PM, "Alex Harui"  wrote:

> Might just be a bug that needs fixing so it ignores a missing folder.  I've
> found that Windows ANT is more sensitive to missing folders.  Most of us use
> Macs which seems to ignore missing folders.
> 
> 
> On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:
> 
>> Hi,
>> 
>> I was trying to play with the release target but I encountered a problem [1],
>> before the release target start, I¹ve got lib folder under batik but it looks
>> like it removed it during the release, which cause that error.
>> 
>> Can someone help ?
>> 
>> -Fred
>> 
>> [1]
>> $ ant release
>> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
>> 
>> check-playerglobal-home:
>> [echo] PLAYERGLOBAL_HOME is
>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>> [echo] playerglobal.version is 11.1
>> [echo] playerglobal.swc is
>> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc
>> 
>> check-air-home:
>> [echo] AIR_HOME is U:\sources\adobe\air\3.4
>> 
>> check-pixelbender-home:
>> [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
>> CS5\Pixel Bender Toolkit 2
>> 
>> check-compile-env:
>> [echo] OS: Windows 7 / 6.1 / x86
>> [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>> [echo] Java: 1.6.0_33
>> [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 Ant
>> Java Version: 1.6
>> 
>> check-runtime-env:
>> 
>> check-adobe-extension-manager-env:
>> [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
>> Extension Manager CS5\Adobe Extension Manager
>> CS5.exe
>> 
>> thirdparty-clean:
>> 
>> thirdparty-clean:
>> 
>> batik-jars-clean:
>> 
>> velocity-jars-clean:
>> 
>> clean:
>> 
>> thirdparty-clean:
>> 
>> swfobject-clean:
>> 
>> swfobject-fabridge-clean:
>> 
>> clean-adobe-flex-sdk:
>> 
>> clean:
>>   [delete] Deleting directory
>> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
>> 
>> modules-clean:
>> 
>> batik-clean:
>> 
>> init:
>> 
>> BUILD FAILED
>> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error 
>> occurred
>> while executing this line:
>> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following error
>> occurred while executing this line:
>> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
>> U:\sources\asf\flex\sdk\developRC1\modules\th
>> irdparty\batik\lib does not exist.
>> 
>> Total time: 1 second
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
> 

Re: Release target and Batik

[Frédéric THOMAS]

yeah, from the develop branch.

Develop/build :
description="Cleans everything including thirdparty downloads."/>


   

   
   
   


modules/build:

   dir="${basedir}"/>

   


downloads.xml:

   

   
   
   
   
   
   
   
   
   
   
   


in batik build:

 
   
 
 
   
   
   
   
 
   

   classname="org.mozilla.javascript.Context">

 
   

-Fred

-Message d'origine- 
From: Alex Harui

Sent: Thursday, January 31, 2013 1:36 AM
To: dev@flex.apache.org
Subject: Re: Release target and Batik

Is this from the develop branch?  Line numbers are not matching up for me.


On 1/30/13 4:18 PM, "Frédéric THOMAS"  wrote:


Actually, in the modules/download.xml, there's  which occure
before the init target in the batik build, which check for classnames in a
jar from this folder, I don't what to do to solve that at this point.

-Fred

-Message d'origine-
From: Frédéric THOMAS
Sent: Thursday, January 31, 2013 1:07 AM
To: dev@flex.apache.org
Subject: Release target and Batik

Hi,

I was trying to play with the release target but I encountered a problem
[1], before the release target start, I¹ve got lib folder under batik but 
it

looks like it removed it during the release, which cause that error.

Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
 [echo] PLAYERGLOBAL_HOME is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player
 [echo] playerglobal.version is 11.1
 [echo] playerglobal.swc is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc

check-air-home:
 [echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
 [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
Utilities - CS5\Pixel Bender Toolkit 2

check-compile-env:
 [echo] OS: Windows 7 / 6.1 / x86
 [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
 [echo] Java: 1.6.0_33
 [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
Ant Java Version: 1.6

check-runtime-env:

check-adobe-extension-manager-env:
 [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
Extension Manager CS5\Adobe Extension Manager
CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
   [delete] Deleting directory
U:\sources\asf\flex\sdk\developRC1\lib\external\optional

modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following
error occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
U:\sources\asf\flex\sdk\developRC1\modules\th
irdparty\batik\lib does not exist.

Total time: 1 second



--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Release target and Batik

[Alex Harui]

Is this from the develop branch?  Line numbers are not matching up for me.


On 1/30/13 4:18 PM, "Frédéric THOMAS"  wrote:

> Actually, in the modules/download.xml, there's  dir="${basedir}/${batik.dir}/lib/**" failonerror="false"/> which occure
> before the init target in the batik build, which check for classnames in a
> jar from this folder, I don't what to do to solve that at this point.
> 
> -Fred
> 
> -Message d'origine-
> From: Frédéric THOMAS
> Sent: Thursday, January 31, 2013 1:07 AM
> To: dev@flex.apache.org
> Subject: Release target and Batik
> 
> Hi,
> 
> I was trying to play with the release target but I encountered a problem
> [1], before the release target start, I¹ve got lib folder under batik but it
> looks like it removed it during the release, which cause that error.
> 
> Can someone help ?
> 
> -Fred
> 
> [1]
> $ ant release
> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
> 
> check-playerglobal-home:
>  [echo] PLAYERGLOBAL_HOME is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>  [echo] playerglobal.version is 11.1
>  [echo] playerglobal.swc is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc
> 
> check-air-home:
>  [echo] AIR_HOME is U:\sources\adobe\air\3.4
> 
> check-pixelbender-home:
>  [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
> Utilities - CS5\Pixel Bender Toolkit 2
> 
> check-compile-env:
>  [echo] OS: Windows 7 / 6.1 / x86
>  [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>  [echo] Java: 1.6.0_33
>  [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
> Ant Java Version: 1.6
> 
> check-runtime-env:
> 
> check-adobe-extension-manager-env:
>  [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
> Extension Manager CS5\Adobe Extension Manager
> CS5.exe
> 
> thirdparty-clean:
> 
> thirdparty-clean:
> 
> batik-jars-clean:
> 
> velocity-jars-clean:
> 
> clean:
> 
> thirdparty-clean:
> 
> swfobject-clean:
> 
> swfobject-fabridge-clean:
> 
> clean-adobe-flex-sdk:
> 
> clean:
>[delete] Deleting directory
> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
> 
> modules-clean:
> 
> batik-clean:
> 
> init:
> 
> BUILD FAILED
> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error
> occurred while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following
> error occurred while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
> U:\sources\asf\flex\sdk\developRC1\modules\th
> irdparty\batik\lib does not exist.
> 
> Total time: 1 second
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Stage3D accelerated Flex components

[Kevin Newman]

I believe he was referring to the cancelation of AVMNext (and AS4) and 
FlashNext.


Kevin N.


On 1/30/13 4:08 AM, Frank Martin wrote:

Daniel, what current announcement are you referring to?

Re: Release target and Batik

[Frédéric THOMAS]

Hi Alex,

Well, I'm not sure that's because Windows ANT is more sensitive to missing 
folders because except if I understand wrong, the release target trigger the 
super-clean, which trigger the module/download.xml clean which clean the 
batik/lib and then try to build batik from batik/lib/build, that's what I 
can't understand.


Am I right reading the Ant scripts or I missed something ?

-Fred

-Message d'origine- 
From: Alex Harui

Sent: Thursday, January 31, 2013 1:16 AM
To: dev@flex.apache.org
Subject: Re: Release target and Batik

Might just be a bug that needs fixing so it ignores a missing folder.  I've
found that Windows ANT is more sensitive to missing folders.  Most of us use
Macs which seems to ignore missing folders.


On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:


Hi,

I was trying to play with the release target but I encountered a problem 
[1],
before the release target start, I¹ve got lib folder under batik but it 
looks

like it removed it during the release, which cause that error.

Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
 [echo] PLAYERGLOBAL_HOME is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player
 [echo] playerglobal.version is 11.1
 [echo] playerglobal.swc is
U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc

check-air-home:
 [echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
 [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe 
Utilities -

CS5\Pixel Bender Toolkit 2

check-compile-env:
 [echo] OS: Windows 7 / 6.1 / x86
 [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
 [echo] Java: 1.6.0_33
 [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 
Ant

Java Version: 1.6

check-runtime-env:

check-adobe-extension-manager-env:
 [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
Extension Manager CS5\Adobe Extension Manager
CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
   [delete] Deleting directory
U:\sources\asf\flex\sdk\developRC1\lib\external\optional

modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error 
occurred

while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following 
error

occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
U:\sources\asf\flex\sdk\developRC1\modules\th
irdparty\batik\lib does not exist.

Total time: 1 second


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Release target and Batik

[Frédéric THOMAS]

Actually, in the modules/download.xml, there's dir="${basedir}/${batik.dir}/lib/**" failonerror="false"/> which occure 
before the init target in the batik build, which check for classnames in a 
jar from this folder, I don't what to do to solve that at this point.


-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Thursday, January 31, 2013 1:07 AM
To: dev@flex.apache.org
Subject: Release target and Batik

Hi,

I was trying to play with the release target but I encountered a problem 
[1], before the release target start, I’ve got lib folder under batik but it 
looks like it removed it during the release, which cause that error.


Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is 
U:\sources\asf\flex\sdk\develop\frameworks\libs\player

[echo] playerglobal.version is 11.1
[echo] playerglobal.swc is 
U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc


check-air-home:
[echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
[echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe 
Utilities - CS5\Pixel Bender Toolkit 2


check-compile-env:
[echo] OS: Windows 7 / 6.1 / x86
[echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
[echo] Java: 1.6.0_33
[echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 
Ant Java Version: 1.6


check-runtime-env:

check-adobe-extension-manager-env:
[echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe 
Extension Manager CS5\Adobe Extension Manager

CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
  [delete] Deleting directory 
U:\sources\asf\flex\sdk\developRC1\lib\external\optional


modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error 
occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following 
error occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161: 
U:\sources\asf\flex\sdk\developRC1\modules\th

irdparty\batik\lib does not exist.

Total time: 1 second 

Re: Release target and Batik

[Alex Harui]

Might just be a bug that needs fixing so it ignores a missing folder.  I've
found that Windows ANT is more sensitive to missing folders.  Most of us use
Macs which seems to ignore missing folders.


On 1/30/13 4:07 PM, "Frédéric THOMAS"  wrote:

> Hi,
> 
> I was trying to play with the release target but I encountered a problem [1],
> before the release target start, I¹ve got lib folder under batik but it looks
> like it removed it during the release, which cause that error.
> 
> Can someone help ?
> 
> -Fred
> 
> [1]
> $ ant release
> Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml
> 
> check-playerglobal-home:
>  [echo] PLAYERGLOBAL_HOME is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player
>  [echo] playerglobal.version is 11.1
>  [echo] playerglobal.swc is
> U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc
> 
> check-air-home:
>  [echo] AIR_HOME is U:\sources\adobe\air\3.4
> 
> check-pixelbender-home:
>  [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
> CS5\Pixel Bender Toolkit 2
> 
> check-compile-env:
>  [echo] OS: Windows 7 / 6.1 / x86
>  [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
>  [echo] Java: 1.6.0_33
>  [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 Ant
> Java Version: 1.6
> 
> check-runtime-env:
> 
> check-adobe-extension-manager-env:
>  [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe
> Extension Manager CS5\Adobe Extension Manager
> CS5.exe
> 
> thirdparty-clean:
> 
> thirdparty-clean:
> 
> batik-jars-clean:
> 
> velocity-jars-clean:
> 
> clean:
> 
> thirdparty-clean:
> 
> swfobject-clean:
> 
> swfobject-fabridge-clean:
> 
> clean-adobe-flex-sdk:
> 
> clean:
>[delete] Deleting directory
> U:\sources\asf\flex\sdk\developRC1\lib\external\optional
> 
> modules-clean:
> 
> batik-clean:
> 
> init:
> 
> BUILD FAILED
> U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error occurred
> while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following error
> occurred while executing this line:
> U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161:
> U:\sources\asf\flex\sdk\developRC1\modules\th
> irdparty\batik\lib does not exist.
> 
> Total time: 1 second

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying

[Alex Harui (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567129#comment-13567129
 ] 

Alex Harui commented on FLEX-33372:
---

My source thinks it is a player bug, otherwise they would have passed the issue 
on to Flex.  If you have time, you can help out by creating a non-Flex version 
of the test case.  Take a TextField and a Sprite.  Try giving them focus and 
see if the keyboard shows up.  If it works for Sprite, there might be other 
code you need to borrow from RichEditableText and TLF until it fails.  When RET 
has displayAsPassword=true it looks like it causes TLF to think someone pasted 
in the '" which might take TLF down some code path that allows the keyboard 
to show up.

I don't have a device to test it on so I can't help much at this time.

It occurs to me that a possible workaround might be to always force that paste 
operation after each keystroke.

> Windows 8 on-screen touch keyboard not displaying
> -
>
> Key: FLEX-33372
> URL: https://issues.apache.org/jira/browse/FLEX-33372
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: RichEditableText, Spark: TextArea, Spark: 
> TextInput
>Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0
> Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark RichEditableText 
> based text input components. It does get displayed when displayAsPassword 
> property is set to true. It does get displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput, s:TextInput with 
> displayAsPassword="true" and mx:TextInput
> 
> 
> 
> 2. Open this application in the Metro Internet Explorer on a touch-enabled 
> Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see 
> http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard 
> shows
> 5. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: 
> http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Release target and Batik

[Frédéric THOMAS]

Hi,

I was trying to play with the release target but I encountered a problem [1], 
before the release target start, I’ve got lib folder under batik but it looks 
like it removed it during the release, which cause that error.

Can someone help ?

-Fred

[1]
$ ant release
Buildfile: U:\sources\asf\flex\sdk\developRC1\build.xml

check-playerglobal-home:
 [echo] PLAYERGLOBAL_HOME is 
U:\sources\asf\flex\sdk\develop\frameworks\libs\player
 [echo] playerglobal.version is 11.1
 [echo] playerglobal.swc is 
U:\sources\asf\flex\sdk\develop\frameworks\libs\player/11.1/playerglobal.swc

check-air-home:
 [echo] AIR_HOME is U:\sources\adobe\air\3.4

check-pixelbender-home:
 [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - 
CS5\Pixel Bender Toolkit 2

check-compile-env:
 [echo] OS: Windows 7 / 6.1 / x86
 [echo] VM: Java HotSpot(TM) Client VM / 20.8-b03
 [echo] Java: 1.6.0_33
 [echo] Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 Ant 
Java Version: 1.6

check-runtime-env:

check-adobe-extension-manager-env:
 [echo] ADOBE_EXTENSION_MANAGER is C:\Program Files (x86)\Adobe\Adobe 
Extension Manager CS5\Adobe Extension Manager
CS5.exe

thirdparty-clean:

thirdparty-clean:

batik-jars-clean:

velocity-jars-clean:

clean:

thirdparty-clean:

swfobject-clean:

swfobject-fabridge-clean:

clean-adobe-flex-sdk:

clean:
   [delete] Deleting directory 
U:\sources\asf\flex\sdk\developRC1\lib\external\optional

modules-clean:

batik-clean:

init:

BUILD FAILED
U:\sources\asf\flex\sdk\developRC1\build.xml:298: The following error occurred 
while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\build.xml:170: The following error 
occurred while executing this line:
U:\sources\asf\flex\sdk\developRC1\modules\thirdparty\batik\build.xml:161: 
U:\sources\asf\flex\sdk\developRC1\modules\th
irdparty\batik\lib does not exist.

Total time: 1 second

Re: Stage3D accelerated Flex components

[Kevin Newman]

What are the bottlenecks, and how might they alleviate them? As far as I 
know, there isn't really any overhead when you upload a ByteArray or 
BitmapData, it's about as fast as you can get, as far as textures go. 
With vector data, they could reduce the type marshaling, but that seems 
like less of a problem than raw texture throughput. But texture 
throughput is limited in native apps too.


Am I missing another bottleneck?

Kevin N.


On 1/30/13 2:31 AM, Daniel Freeman wrote:

there are Stage3D
bottlenecks that will impair performance for anything beyond games
use-cases.  If Adobe solve these technical obstructions

Re: Flash Player 11.5 - Debug trace in release player

[Justin Mclean]

Hi,

> Is there anything I'm missing ?
You're actually compiling with the compiler that come with 4.1 SDK  and it 
doesn't support that option. Try -target-player option instead that may work 
(I've not tried it), otherwise you'll need to to use 4.5.

Justin

Re: Flash Player 11.5 - Debug trace in release player

[Justin Mclean]

Hi,

> Just tried this in FB4.0 and it doesn't compile

Look like the "-swf-version" option was added in FB 4.5 (or rather to the 
compiler for the Flex SDK that come with FB 4.5). You might be able to get it 
to work with the "-target-player" option?

Justin

RE: Flash Player 11.5 - Debug trace in release player

[Cooper, Andrew]

I've upgraded to 4.7

Installed the 4.1 SDK (this is what I need to target for now - I had
issues with the 4.5 and 4.6 SDK's that I haven't had time to sort out)

I've installed the playerglobal.swc, modified flex-config.xml 

But I still get 
Description ResourcePathLocationType
unknown configuration variable 'swf-version'Liteline 19
Flex Problem

even though I'm compiling with FB4.7

Is there anything I'm missing ?

Andy

-Original Message-
From: Cooper, Andrew 
Sent: 30 January 2013 23:04
To: 'dev@flex.apache.org'
Subject: RE: Flash Player 11.5 - Debug trace in release player

Thanks for all the help...

Just tried this in FB4.0 and it doesn't compile

Description ResourcePathLocationType
unknown configuration variable 'swf-version'Liteline 19
Flex Problem

Looks like I'll be upgrading to FB4.7 soon

Andy

-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com] 
Sent: 30 January 2013 21:07
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

Hi,

> Do you need Flash Builder 4.7 for this or will Flash Builder 4.0 be
sufficient
Not tried but see no reason why it shouldn't work on 4.0 if you have the
playerglobal.swc and flash player version and swf version numbers set
correctly in the flex config file.

Thanks,
Justin

[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying

[Stepan Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567077#comment-13567077
 ] 

Stepan Hilbert commented on FLEX-33372:
---

Thanks, the bug has been re-submitted as advised:
https://bugbase.adobe.com/index.cfm?event=bug&id=3493295

I'm really curious if this turns out to be a Player issue or SDK issue. 
Everything points to the Player but then why displayAsPassword="true" works?

> Windows 8 on-screen touch keyboard not displaying
> -
>
> Key: FLEX-33372
> URL: https://issues.apache.org/jira/browse/FLEX-33372
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: RichEditableText, Spark: TextArea, Spark: 
> TextInput
>Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0
> Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark RichEditableText 
> based text input components. It does get displayed when displayAsPassword 
> property is set to true. It does get displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput, s:TextInput with 
> displayAsPassword="true" and mx:TextInput
> 
> 
> 
> 2. Open this application in the Metro Internet Explorer on a touch-enabled 
> Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see 
> http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard 
> shows
> 5. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: 
> http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [Website] New website going live

[Harbs]

I figured out the problem.

There's an extra  tag before the first sub-div in that row:


--->  <---







Harbs

On Jan 30, 2013, at 10:37 PM, Nicholas Kwiatkowski wrote:

> Yeah, I'm still trying to figure that one out.  The div tags are even
> between everybody, and there is nothing really in there to make him appear
> on another line.  It is still on the hit-list ;)
> 
> -Nick
> 
> On Wed, Jan 30, 2013 at 3:13 PM, Harbs  wrote:
> 
>> Sure. I probably should have posted in a separate thread. The two efforts
>> are not directly connected. Looking at the page source on the blog,
>> everything seems to be pretty neat in terms of divs, etc. but yes. Let's
>> definitely get the main site out first! Great job! :-)
>> 
>> BTW, Sebastian Mohr is still kind of lonely there in the second to last
>> row of the team page… ;-)
>> 
>> Harbs
>> 
>> On Jan 30, 2013, at 8:43 PM, Nicholas Kwiatkowski wrote:
>> 
>>> I'll take a look at it.  I'm not sure /how/ much we can do with the blog
>> (I
>>> don't know if they use DIVs, etc., as I've only briefly played with their
>>> setup).
>>> 
>>> For right now, it is functional so I'm not going to hold up switching the
>>> main site over.  We can play with that in a bit.
>>> 
>>> -Nick
>>> 
>>> On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:
>>> 
 Okay. So I guess I'll wait and see if anyone else thinks styling the
>> blog
 is a good idea… ;-)
 
 Harbs
 
 On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
 
> On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
>> ...Flex seems to have a css file specific to the Flex blog here:
 http://blogs.apache.org/flex/page/asf-custom.css
>> 
>> It seems to me a question as to whether there's a policy against
 customizing the blog more than anything else…
> 
> I don't think there's an ASF policy, you'll need to find out if
> infrastructure@ agrees with giving someone from the Flex PMC access to
> that styling configuration. If it's just CSS, it shouldn't be too
> hard.
> 
> -Bertrand
 
 
>> 
>> 

RE: Flash Player 11.5 - Debug trace in release player

[Cooper, Andrew]

Thanks for all the help...

Just tried this in FB4.0 and it doesn't compile

Description ResourcePathLocationType
unknown configuration variable 'swf-version'Liteline 19
Flex Problem

Looks like I'll be upgrading to FB4.7 soon

Andy

-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com] 
Sent: 30 January 2013 21:07
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

Hi,

> Do you need Flash Builder 4.7 for this or will Flash Builder 4.0 be
sufficient
Not tried but see no reason why it shouldn't work on 4.0 if you have the
playerglobal.swc and flash player version and swf version numbers set
correctly in the flex config file.

Thanks,
Justin

Re: Editing the new site

[Frédéric THOMAS]

And to use the CMS feature, I created a favorite with this URL: 
javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))


-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Wednesday, January 30, 2013 11:56 PM
To: dev@flex.apache.org
Subject: Re: Editing the new site

try http://flex.staging.apache.org/

-Fred

-Message d'origine- 
From: Gordon Smith

Sent: Wednesday, January 30, 2013 11:50 PM
To: dev@flex.apache.org
Subject: Editing the new site

Now that the new site is live, what URLs do we use to preview staged changes
and push them live? The URLs were documented on the old site, but I can't
find them any more.

- Gordon

Re: A code name for Apache Flex 5?

[Justin Mclean]

HI,

> The problem with a code name is that any member of the PPMC (And possibly 
> committers?) can decide to release at any time, for pretty much any reason.
Actually it possible for anyone to make a release, but practicalities usually 
mean it limited to commiters. The PMC votes on accepting the release but there 
only has to be three +1 votes and more + 1 votes than -1 votes. No vetos are 
allowed. The release does have to comply with ASF policy on licensing etc

Thanks,
Justin

Re: Editing the new site

[Frédéric THOMAS]

try http://flex.staging.apache.org/

-Fred

-Message d'origine- 
From: Gordon Smith

Sent: Wednesday, January 30, 2013 11:50 PM
To: dev@flex.apache.org
Subject: Editing the new site

Now that the new site is live, what URLs do we use to preview staged changes 
and push them live? The URLs were documented on the old site, but I can't 
find them any more.


- Gordon

Editing the new site

[Gordon Smith]

Now that the new site is live, what URLs do we use to preview staged changes 
and push them live? The URLs were documented on the old site, but I can't find 
them any more.

- Gordon

Re: [Website] New website going live

[Harbs]

Another couple of small things:

1) The Favicon is the Apache feather. Is it supposed to be the Apache feather 
or the Flex logo?
2) The Apache feather in the header remains faded even when I mouse over 
(Firefox Mac 10.7.5.)

On Jan 30, 2013, at 10:37 PM, Nicholas Kwiatkowski wrote:

> Yeah, I'm still trying to figure that one out.  The div tags are even
> between everybody, and there is nothing really in there to make him appear
> on another line.  It is still on the hit-list ;)
> 
> -Nick
> 
> On Wed, Jan 30, 2013 at 3:13 PM, Harbs  wrote:
> 
>> Sure. I probably should have posted in a separate thread. The two efforts
>> are not directly connected. Looking at the page source on the blog,
>> everything seems to be pretty neat in terms of divs, etc. but yes. Let's
>> definitely get the main site out first! Great job! :-)
>> 
>> BTW, Sebastian Mohr is still kind of lonely there in the second to last
>> row of the team page… ;-)
>> 
>> Harbs
>> 
>> On Jan 30, 2013, at 8:43 PM, Nicholas Kwiatkowski wrote:
>> 
>>> I'll take a look at it.  I'm not sure /how/ much we can do with the blog
>> (I
>>> don't know if they use DIVs, etc., as I've only briefly played with their
>>> setup).
>>> 
>>> For right now, it is functional so I'm not going to hold up switching the
>>> main site over.  We can play with that in a bit.
>>> 
>>> -Nick
>>> 
>>> On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:
>>> 
 Okay. So I guess I'll wait and see if anyone else thinks styling the
>> blog
 is a good idea… ;-)
 
 Harbs
 
 On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
 
> On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
>> ...Flex seems to have a css file specific to the Flex blog here:
 http://blogs.apache.org/flex/page/asf-custom.css
>> 
>> It seems to me a question as to whether there's a policy against
 customizing the blog more than anything else…
> 
> I don't think there's an ASF policy, you'll need to find out if
> infrastructure@ agrees with giving someone from the Flex PMC access to
> that styling configuration. If it's just CSS, it shouldn't be too
> hard.
> 
> -Bertrand
 
 
>> 
>> 

Re: A code name for Apache Flex 5?

[Jeffry Houser]

On 1/30/2013 1:57 PM, Phillip wrote:

I personally think there should be a codename.


 The problem with a code name is that any member of the PPMC (And 
possibly committers?) can decide to release at any time, for pretty much 
any reason.  And that may not include stuff that some people are working 
on.  So, I don't see a code name for the next release as being 
beneficial in any way.


 If anyone wants to develop code names for specific features they are 
working on; they are more than welcome to.


--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust

[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying

[Alex Harui (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566945#comment-13566945
 ] 

Alex Harui commented on FLEX-33372:
---

My sources say this is a known issue all the way through 11.6.  Please file a 
bug at bugbase.adobe.com against the Flash Player.

> Windows 8 on-screen touch keyboard not displaying
> -
>
> Key: FLEX-33372
> URL: https://issues.apache.org/jira/browse/FLEX-33372
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: RichEditableText, Spark: TextArea, Spark: 
> TextInput
>Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0
> Environment: Windows 8 Metro
> Internet Explorer (IE) 10.0.1
> Flash Player 11,3,378,5
>Reporter: Stepan Hilbert
>
> On-screen touch keyboard is not being displayed for spark RichEditableText 
> based text input components. It does get displayed when displayAsPassword 
> property is set to true. It does get displayed for TextField based components.
> Additionally, it would be desirable to control the keyboard using:
> - needsSoftKeyboard property
> - requestSoftKeyboard() function
> These currently have no effect.
> Steps to reproduce:
> 1. Create a Flex application that features s:TextInput, s:TextInput with 
> displayAsPassword="true" and mx:TextInput
> 
> 
> 
> 2. Open this application in the Metro Internet Explorer on a touch-enabled 
> Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see 
> http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx)
> 3. Tap the mx:TextInput - on-screen keyboard shows
> 4. Tap the s:TextInput with displayAsPassword="true" - on-screen keyboard 
> shows
> 5. Tap the s:TextInput - on-screen keyboard doesn't show
> Note:
> This bug has been discussed on the web
> (i.e. here: 
> http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html)
> but no resolution has been reached, so that is why I'm logging this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Flash Player 11.5 - Debug trace in release player

[Justin Mclean]

Hi,

> Do you need Flash Builder 4.7 for this or will Flash Builder 4.0 be sufficient
Not tried but see no reason why it shouldn't work on 4.0 if you have the 
playerglobal.swc and flash player version and swf version numbers set correctly 
in the flex config file.

Thanks,
Justin

Re: Flash Player 11.5 - Debug trace in release player

[Justin Mclean]

Hi,

Also in the SVN develop branch of the ide directory there's several scripts 
that can download the swcs and make the changes for you.

Thanks,
Justin

Re: Flash Player 11.5 - Debug trace in release player

[Justin Mclean]

Hi,

> Does this mean that an app that I compile with the default settings for 
> 4.5.1A will not benefit from this stacktrace availability, even if the user 
> has 11.5 installed?  

From my testing that's sadly the case. You could detect the version of the 
flash player and then load a swf compiled with 11.5 if they are using 11.5. 
(Assuming your app is in the browser).

Justin

Re: [Website] New website going live

[Nicholas Kwiatkowski]

yeah.  He gave me a really cropped photo. I didn't get a chance to play
with it yet.

Bertrand,  do you have any photos that are square?

-Nick

On Wed, Jan 30, 2013 at 3:45 PM, Frédéric THOMAS wrote:

> Good Job Nick :-)
>
> What do you think about the Bertrand Delacretaz's photo, wouldn't it be
> better in 200x200px as it would fit in the circle ?
>
> -Fred
>
> -Message d'origine- From: Nicholas Kwiatkowski
> Sent: Wednesday, January 30, 2013 9:37 PM
> To: dev@flex.apache.org
> Subject: Re: [Website] New website going live
>
>
> Yeah, I'm still trying to figure that one out.  The div tags are even
> between everybody, and there is nothing really in there to make him appear
> on another line.  It is still on the hit-list ;)
>
> -Nick
>
> On Wed, Jan 30, 2013 at 3:13 PM, Harbs  wrote:
>
>  Sure. I probably should have posted in a separate thread. The two efforts
>> are not directly connected. Looking at the page source on the blog,
>> everything seems to be pretty neat in terms of divs, etc. but yes. Let's
>> definitely get the main site out first! Great job! :-)
>>
>> BTW, Sebastian Mohr is still kind of lonely there in the second to last
>> row of the team page… ;-)
>>
>> Harbs
>>
>> On Jan 30, 2013, at 8:43 PM, Nicholas Kwiatkowski wrote:
>>
>> > I'll take a look at it.  I'm not sure /how/ much we can do with the blog
>> (I
>> > don't know if they use DIVs, etc., as I've only briefly played with >
>> their
>> > setup).
>> >
>> > For right now, it is functional so I'm not going to hold up switching >
>> the
>> > main site over.  We can play with that in a bit.
>> >
>> > -Nick
>> >
>> > On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:
>> >
>> >> Okay. So I guess I'll wait and see if anyone else thinks styling the
>> blog
>> >> is a good idea… ;-)
>> >>
>> >> Harbs
>> >>
>> >> On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
>> >>
>> >>> On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
>>  ...Flex seems to have a css file specific to the Flex blog here:
>> >> http://blogs.apache.org/flex/**page/asf-custom.css
>> 
>>  It seems to me a question as to whether there's a policy against
>> >> customizing the blog more than anything else…
>> >>>
>> >>> I don't think there's an ASF policy, you'll need to find out if
>> >>> infrastructure@ agrees with giving someone from the Flex PMC access
>> to
>> >>> that styling configuration. If it's just CSS, it shouldn't be too
>> >>> hard.
>> >>>
>> >>> -Bertrand
>> >>
>> >>
>>
>>
>>
>

Re: [Website] New website going live

[Carol Frampton]

Now that the website is live, I just updated the instructions on how to
update your profile

https://cwiki.apache.org/confluence/display/FLEX/Updating+your+profile+on+T
eam+page

to remove the /v2 from all the URLs.

Committers - if you haven't updated your bio yet now would be a great time
to do it.

Carol

Re: [Website] New website going live

[Frédéric THOMAS]

Good Job Nick :-)

What do you think about the Bertrand Delacretaz's photo, wouldn't it be 
better in 200x200px as it would fit in the circle ?


-Fred

-Message d'origine- 
From: Nicholas Kwiatkowski

Sent: Wednesday, January 30, 2013 9:37 PM
To: dev@flex.apache.org
Subject: Re: [Website] New website going live

Yeah, I'm still trying to figure that one out.  The div tags are even
between everybody, and there is nothing really in there to make him appear
on another line.  It is still on the hit-list ;)

-Nick

On Wed, Jan 30, 2013 at 3:13 PM, Harbs  wrote:


Sure. I probably should have posted in a separate thread. The two efforts
are not directly connected. Looking at the page source on the blog,
everything seems to be pretty neat in terms of divs, etc. but yes. Let's
definitely get the main site out first! Great job! :-)

BTW, Sebastian Mohr is still kind of lonely there in the second to last
row of the team page… ;-)

Harbs

On Jan 30, 2013, at 8:43 PM, Nicholas Kwiatkowski wrote:

> I'll take a look at it.  I'm not sure /how/ much we can do with the blog
(I
> don't know if they use DIVs, etc., as I've only briefly played with 
> their

> setup).
>
> For right now, it is functional so I'm not going to hold up switching 
> the

> main site over.  We can play with that in a bit.
>
> -Nick
>
> On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:
>
>> Okay. So I guess I'll wait and see if anyone else thinks styling the
blog
>> is a good idea… ;-)
>>
>> Harbs
>>
>> On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
>>
>>> On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
 ...Flex seems to have a css file specific to the Flex blog here:
>> http://blogs.apache.org/flex/page/asf-custom.css

 It seems to me a question as to whether there's a policy against
>> customizing the blog more than anything else…
>>>
>>> I don't think there's an ASF policy, you'll need to find out if
>>> infrastructure@ agrees with giving someone from the Flex PMC access to
>>> that styling configuration. If it's just CSS, it shouldn't be too
>>> hard.
>>>
>>> -Bertrand
>>
>>

Re: [Website] New website going live

[Nicholas Kwiatkowski]

Yeah, I'm still trying to figure that one out.  The div tags are even
between everybody, and there is nothing really in there to make him appear
on another line.  It is still on the hit-list ;)

-Nick

On Wed, Jan 30, 2013 at 3:13 PM, Harbs  wrote:

> Sure. I probably should have posted in a separate thread. The two efforts
> are not directly connected. Looking at the page source on the blog,
> everything seems to be pretty neat in terms of divs, etc. but yes. Let's
> definitely get the main site out first! Great job! :-)
>
> BTW, Sebastian Mohr is still kind of lonely there in the second to last
> row of the team page… ;-)
>
> Harbs
>
> On Jan 30, 2013, at 8:43 PM, Nicholas Kwiatkowski wrote:
>
> > I'll take a look at it.  I'm not sure /how/ much we can do with the blog
> (I
> > don't know if they use DIVs, etc., as I've only briefly played with their
> > setup).
> >
> > For right now, it is functional so I'm not going to hold up switching the
> > main site over.  We can play with that in a bit.
> >
> > -Nick
> >
> > On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:
> >
> >> Okay. So I guess I'll wait and see if anyone else thinks styling the
> blog
> >> is a good idea… ;-)
> >>
> >> Harbs
> >>
> >> On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
> >>
> >>> On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
>  ...Flex seems to have a css file specific to the Flex blog here:
> >> http://blogs.apache.org/flex/page/asf-custom.css
> 
>  It seems to me a question as to whether there's a policy against
> >> customizing the blog more than anything else…
> >>>
> >>> I don't think there's an ASF policy, you'll need to find out if
> >>> infrastructure@ agrees with giving someone from the Flex PMC access to
> >>> that styling configuration. If it's just CSS, it shouldn't be too
> >>> hard.
> >>>
> >>> -Bertrand
> >>
> >>
>
>

Re: [Website] New website going live

[Harbs]

Sure. I probably should have posted in a separate thread. The two efforts are 
not directly connected. Looking at the page source on the blog, everything 
seems to be pretty neat in terms of divs, etc. but yes. Let's definitely get 
the main site out first! Great job! :-)

BTW, Sebastian Mohr is still kind of lonely there in the second to last row of 
the team page… ;-)

Harbs

On Jan 30, 2013, at 8:43 PM, Nicholas Kwiatkowski wrote:

> I'll take a look at it.  I'm not sure /how/ much we can do with the blog (I
> don't know if they use DIVs, etc., as I've only briefly played with their
> setup).
> 
> For right now, it is functional so I'm not going to hold up switching the
> main site over.  We can play with that in a bit.
> 
> -Nick
> 
> On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:
> 
>> Okay. So I guess I'll wait and see if anyone else thinks styling the blog
>> is a good idea… ;-)
>> 
>> Harbs
>> 
>> On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
>> 
>>> On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
 ...Flex seems to have a css file specific to the Flex blog here:
>> http://blogs.apache.org/flex/page/asf-custom.css
 
 It seems to me a question as to whether there's a policy against
>> customizing the blog more than anything else…
>>> 
>>> I don't think there's an ASF policy, you'll need to find out if
>>> infrastructure@ agrees with giving someone from the Flex PMC access to
>>> that styling configuration. If it's just CSS, it shouldn't be too
>>> hard.
>>> 
>>> -Bertrand
>> 
>> 

Re: [Website] New website going live

[Nicholas Kwiatkowski]

Yeah, I didn't want to touch that until I was sure I wasn't going to break
anything else.  Re-naming the disclaimer.mdtext to disclaimer.cmsPage
should do the trick.

I'm on it now.

-Nick

On Wed, Jan 30, 2013 at 1:54 PM, Om  wrote:

> Thanks!
>
> Also, this disclaimer page has the old template.  It looks quite out of
> place.
>
> http://flex.staging.apache.org/installerbadge/disclaimer.html
>
> Om
>
> On Wed, Jan 30, 2013 at 4:30 AM, Nicholas Kwiatkowski  >wrote:
>
> > Om,
> >
> > This is a crossdomain.xml issue.  It is the 2nd thing I will check once
> the
> > site is moved over (the first being if the page loads)  ;)
> >
> > -Nick
> >
> > On Wed, Jan 30, 2013 at 2:27 AM, Om  wrote:
> >
> > > On Tue, Jan 29, 2013 at 8:29 PM, Nicholas Kwiatkowski <
> nicho...@spoon.as
> > > >wrote:
> > >
> > > > The new website is sitting on staging now.  I'm going to push it to
> > > > production at Noon EDT tomorrow (~12 hours from now) unless somebody
> > > finds
> > > > a compelling reason why we shouldn't.
> > > >
> > > > http://flex.staging.apache.org/
> > > >
> > > > -Nick
> > > >
> > > >
> > > The installer badge on this page [1] is broken.  I guess it is because
> > of a
> > > crossdomain issue and we dont have a policy file.  I wouldnt worry
> about
> > it
> > > because it seems to be working fine here [2]
> > >
> > > When you make it go live, please sure you test this page first, though!
> > >
> > > Thanks,
> > > Om
> > >
> > > [1] http://flex.staging.apache.org/installer.html
> > > [2] http://flex.apache.org/v2/installer.html
> > >
> > >
> > > > On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski <
> > nicho...@spoon.as
> > > > >wrote:
> > > >
> > > > > Hey everybody!
> > > > >
> > > > > We got final permission from a few different groups at Apache to
> make
> > > the
> > > > > website live.  If you have any pending commits to the site/
> directory
> > > in
> > > > > SVN, please make sure those go in soon as things are about to be
> all
> > > > moved
> > > > > around there.
> > > > >
> > > > > After the website goes live, I'll put in the download tracking
> code.
> > > > >
> > > > > -Nick
> > > > >
> > > >
> > >
> >
>

Re: [Website] New website going live

[Jun Heider]

On 1/29/13 7:22 PM, "Nicholas Kwiatkowski"  wrote:


>Hey everybody!
>
>We got final permission from a few different groups at Apache to make the
>website live.  If you have any pending commits to the site/ directory in
>SVN, please make sure those go in soon as things are about to be all moved
>around there.
>
>After the website goes live, I'll put in the download tracking code.
>
>-Nick


Awesome news, thanks everyone involved for the hard work. I think the v2
site looks outstanding!

Re: A code name for Apache Flex 5?

[Phillip]

I personally think there should be a codename. We are all "brain-artists" and 
prove me wrong, but sometimes this work is dry and odd. All committers and 
people working here, their brains need a star shining at the horizon, to be 
motivated to reach our goals. A codename represents an image and gives this 
whole thing a personality, besides moving packages, breaking 42 major tests, 
compiling modules, run for the 100th time in a day etc.
Just my opinion.

So +1 for a codename

Excalibur is great, (Doug | King) Arthur and 5th (century | flex version) suits 
perfectly well for me.
What about just the word
"grale" addressing the same King Arthur story, but standing for his search for 
it.. the wholy grale.

Its short and meaningless to those having concerns of a codename, but shiny to 
those who know the true meaning.

Ps:
said to introdruce myself asap a while ago.
hope a link to xing is ok ;)
http://www.xing.com/profile/Phillip_Luedeling
Excuse its all german!

mobile mail

Am 30.01.2013 um 18:22 schrieb David Coleman :

> from the outside, looking in, I'll throw my hat in the ring for "Excalibur".  
> It just sounds like a fitting successor to "Hero"...
> 
> just my 2 cents, for whatever it's worth.  :-)
> 
>> From: jonbcam...@gmail.com
>> Date: Wed, 30 Jan 2013 10:25:51 -0600
>> Subject: Re: A code name for Apache Flex 5?
>> To: dev@flex.apache.org
>> 
>> On Wed, Jan 30, 2013 at 6:19 AM, Kessler CTR Mark J <
>> mark.kessler@usmc.mil> wrote:
>> 
>>> If we did use code names could be have a running alphabet one?  Like your
>>> android ones work...
>> 
>> 
>> I'm not sure we need to worry about coming to a consensus on a name.
>> Probably just wasted effort. I'd say develop in your whiteboard and name
>> your code whatever cool name you like. If it gets picked up as the
>> next iteration then the name is stuck.
>> 
>> Example: Alex had already been working on an idea with parts that he called
>> "Beads". If he decides to name his branch "Beads" and people get behind it
>> then the next version will most likely be known as "Beads".
>> 
>> 
>> -- 
>> Jonathan Campos
> 

Re: [Website] New website going live

[Om]

Thanks!

Also, this disclaimer page has the old template.  It looks quite out of
place.

http://flex.staging.apache.org/installerbadge/disclaimer.html

Om

On Wed, Jan 30, 2013 at 4:30 AM, Nicholas Kwiatkowski wrote:

> Om,
>
> This is a crossdomain.xml issue.  It is the 2nd thing I will check once the
> site is moved over (the first being if the page loads)  ;)
>
> -Nick
>
> On Wed, Jan 30, 2013 at 2:27 AM, Om  wrote:
>
> > On Tue, Jan 29, 2013 at 8:29 PM, Nicholas Kwiatkowski  > >wrote:
> >
> > > The new website is sitting on staging now.  I'm going to push it to
> > > production at Noon EDT tomorrow (~12 hours from now) unless somebody
> > finds
> > > a compelling reason why we shouldn't.
> > >
> > > http://flex.staging.apache.org/
> > >
> > > -Nick
> > >
> > >
> > The installer badge on this page [1] is broken.  I guess it is because
> of a
> > crossdomain issue and we dont have a policy file.  I wouldnt worry about
> it
> > because it seems to be working fine here [2]
> >
> > When you make it go live, please sure you test this page first, though!
> >
> > Thanks,
> > Om
> >
> > [1] http://flex.staging.apache.org/installer.html
> > [2] http://flex.apache.org/v2/installer.html
> >
> >
> > > On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski <
> nicho...@spoon.as
> > > >wrote:
> > >
> > > > Hey everybody!
> > > >
> > > > We got final permission from a few different groups at Apache to make
> > the
> > > > website live.  If you have any pending commits to the site/ directory
> > in
> > > > SVN, please make sure those go in soon as things are about to be all
> > > moved
> > > > around there.
> > > >
> > > > After the website goes live, I'll put in the download tracking code.
> > > >
> > > > -Nick
> > > >
> > >
> >
>

Re: [Website] New website going live

[Paul Hastings]

On 1/30/2013 7:50 PM, Nicholas Kwiatkowski wrote:

I agree with you, but I've had issues with getting that to render properly
on all browsers.  Both IE and FF have real issues when you explicitly set


that's the funniest thing i've heard all day & it's been a very long day. oh the 
irony ;-) thanks.

Re: [Website] New website going live

[Nicholas Kwiatkowski]

It wasn't my intent, but I think I can make it go to those sections
directly.  My ultimate goal is to have the "What is Flex" page much more
fleshed out with more content talking about those bullet points.

-Nick

On Wed, Jan 30, 2013 at 8:12 AM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:

> One more detail:
> The read more buttons all lead to the top of the "features" page, and not
> to  the corresponding sections inside this page ( Desktop Applications =>
> In the browser, Mobile =>  Mobile and Tablets, Tooling => Choose your
> tools).
> Is that the intended behavior ?
>
> Maurice
>
> -Message d'origine-
> De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as]
> Envoyé : mercredi 30 janvier 2013 13:50
> À : dev@flex.apache.org
> Objet : Re: [Website] New website going live
>
> I agree with you, but I've had issues with getting that to render properly
> on all browsers.  Both IE and FF have real issues when you explicitly set
> height on DIV tags.  Bootstrap didn't really have any hints on how to do it
> either.  If you can get me the CSS code that you think will fix it, I'll
> put it in.
>
> In regards to the video page, I know it looks a bit awkward, but I'm
> really hoping I can have other contributes help out with adding and
> maintaining the content on that page.  I don't really want to set any
> arbitrary limits on the amount of text because that will bite somebody in
> the rear down the road..
>
> -Nick
>
> On Wed, Jan 30, 2013 at 4:53 AM, Hans Van den Keybus <
> h...@dotdotcommadot.com> wrote:
>
> > Looks great!!
> > Minor detail: Wouldn't it be a little tighter if the borders around
> > "licensing", "desktop Applications" etc on the index page all had the
> > same height?
> >
> > Align the content top-down as it is, but put the "read me" button on
> > the bottom, so all read-me buttons are visually next to each other.
> > No?
> >
> >
> >
> >
> > On 30 Jan 2013, at 09:40, Tomislav Pokrajcic 
> wrote:
> >
> > > Looks awesome.
> > > Btw, text on Gordon Smith profile is duplicated.
> > > Cheers,
> > >
> > > Tomislav
> > >
> > > On 30.1.2013. 8:26, Harbs wrote:
> > >> Looks great!
> > >>
> > >> Small thing: On the team page
> > http://flex.staging.apache.org/about-people.html, the last three rows
> > are
> > 3/1/1 rather than two rows of 4/3.
> > >>
> > >> On Jan 30, 2013, at 4:22 AM, Nicholas Kwiatkowski wrote:
> > >>
> > >>> Hey everybody!
> > >>>
> > >>> We got final permission from a few different groups at Apache to
> > >>> make
> > the
> > >>> website live.  If you have any pending commits to the site/
> > >>> directory
> > in
> > >>> SVN, please make sure those go in soon as things are about to be
> > >>> all
> > moved
> > >>> around there.
> > >>>
> > >>> After the website goes live, I'll put in the download tracking code.
> > >>>
> > >>> -Nick
> > >
> >
>

Re: [Website] New website going live

[Nicholas Kwiatkowski]

I'll take a look at it.  I'm not sure /how/ much we can do with the blog (I
don't know if they use DIVs, etc., as I've only briefly played with their
setup).

For right now, it is functional so I'm not going to hold up switching the
main site over.  We can play with that in a bit.

-Nick

On Wed, Jan 30, 2013 at 8:55 AM, Harbs  wrote:

> Okay. So I guess I'll wait and see if anyone else thinks styling the blog
> is a good idea… ;-)
>
> Harbs
>
> On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:
>
> > On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
> >> ...Flex seems to have a css file specific to the Flex blog here:
> http://blogs.apache.org/flex/page/asf-custom.css
> >>
> >> It seems to me a question as to whether there's a policy against
> customizing the blog more than anything else…
> >
> > I don't think there's an ASF policy, you'll need to find out if
> > infrastructure@ agrees with giving someone from the Flex PMC access to
> > that styling configuration. If it's just CSS, it shouldn't be too
> > hard.
> >
> > -Bertrand
>
>

Re: [Website] New website going live

[Nicholas Kwiatkowski]

Fixed.  Thanks for catching that one ;)

-Nick

On Wed, Jan 30, 2013 at 9:42 AM, JP Bader  wrote:

> Very super small detail (pedantic, really), in the footer, under Subscribe,
> the first paragraph, last few words.  please fix to 'and one for SDK users.
>
> and one SDK users.
>
> Otherwise, looks great!
>
> On Tue, Jan 29, 2013 at 10:29 PM, Nicholas Kwiatkowski  >wrote:
>
> > The new website is sitting on staging now.  I'm going to push it to
> > production at Noon EDT tomorrow (~12 hours from now) unless somebody
> finds
> > a compelling reason why we shouldn't.
> >
> > http://flex.staging.apache.org/
> >
> > -Nick
> >
> > On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski  > >wrote:
> >
> > > Hey everybody!
> > >
> > > We got final permission from a few different groups at Apache to make
> the
> > > website live.  If you have any pending commits to the site/ directory
> in
> > > SVN, please make sure those go in soon as things are about to be all
> > moved
> > > around there.
> > >
> > > After the website goes live, I'll put in the download tracking code.
> > >
> > > -Nick
> > >
> >
>
>
>
> --
> JP Bader
> Principal
> Zavteq, Inc.
> @lordB8r | j...@zavteq.com
> 608.692.2468
>

RE: Flash Player 11.5 - Debug trace in release player

[Cooper, Andrew]

One final question on this

Do you need Flash Builder 4.7 for this or will Flash Builder 4.0 be
sufficient

Thanks for all your help with this

Andy

-Original Message-
From: Marcus Fritze [mailto:marcus.fri...@googlemail.com] 
Sent: 30 January 2013 16:03
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

Download the current SDK.

 Just edit the framework/flex-config.xml file and change this lines:
   
  11.1

   
  14

To:
   
  11.5

   
  18

You also need to download the the 11.5 playerglobal.swc from here:
http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playergloba
l11_5.swc

And copy it to:
/frameworks/libs/player/11.5/playerglobal.swc

(Thanks again Justin McLean for this explanation.)

Marcus Fritze

Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :

> Can you target 11.5 in Flash Builder(4.7) Does this automatically set 
> the swf version to 18 or is that something else ?
> 
> Andy
> 
> -Original Message-
> From: Justin Mclean [mailto:jus...@classsoftware.com]
> Sent: 30 January 2013 00:38
> To: dev@flex.apache.org
> Subject: Re: Flash Player 11.5 - Debug trace in release player
> 
> HI,
> 
> Just be aware that you need to compile your application with 11.5 (and

> swf version set to 18) for this to take effect.
> 
> Thanks,
> Justin

Re: Flash Player 11.5 - Debug trace in release player

[Frédéric THOMAS]

Just about every new feature is gated by SWF version


So true, just did a test and wasn't able to make it work without compiling 
with 11.5 :P


-Fred

-Message d'origine- 
From: Alex Harui

Sent: Wednesday, January 30, 2013 5:49 PM
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

Just about every new feature is gated by SWF version.  Some legacy code may
have been relying on the lack of debug information in the
Error.getStackTrace() in a release build.  In fact, I haven't tried it, but
it could break my hacks described here:
http://blogs.adobe.com/aharui/2007/10/debugging_tricks.html


On 1/30/13 8:40 AM, "Marcus Fritze"  wrote:


@Frédéric

Yes, you are right, it's not an API "function". It's more an "internal
functionality" of the Flash Player. But I am not sure if you are right. I 
have
tested this for my own and the debug with release player only worked when 
I

compiled against 11.5.

Maybe someone else can confirm.

Marcus

Am 30.01.2013 um 17:28 schrieb Frédéric THOMAS :

AFAIK, this feature is only about the stack trace of errors in the 
"release
Flash Player >= 11.5", nothing is relative to any API to use, so, the SDK 
is
not implied and you app can be compile with any version, having 11.5 
release

player installed is sufficient.

Tell me if I missed something.

-Fred

-Message d'origine- From: Marcus Fritze
Sent: Wednesday, January 30, 2013 5:16 PM
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

AFAIK, the 4.5.1A targets Flash Player 10.2

So the minimum required FP version of your customers is 10.2 and you can 
use
only the API of 10.2 (no debug trace for release versions). If the user 
has

11.5 installed it will only use 10.2 API because you compiled your app in
this version.


Am 30.01.2013 um 17:08 schrieb David Coleman 
:



Does this mean that an app that I compile with the default settings for
4.5.1A will not benefit from this stacktrace availability, even if the 
user
has 11.5 installed?  Or is having 11.5 release player installed, 
sufficient?
We have an extensive error reporting system in our app that would 
benefit
greatly from this... however forcing users to upgrade their flash player 
is
not an option as our user base contains many people with legacy 
browsers.



From: marcus.fri...@googlemail.com
Subject: Re: Flash Player 11.5 - Debug trace in release player
Date: Wed, 30 Jan 2013 17:02:55 +0100
To: dev@flex.apache.org

Download the current SDK.

Just edit the framework/flex-config.xml file and change this lines:
 
11.1

 
14

To:
 
11.5

 
18

You also need to download the the 11.5 playerglobal.swc from here:
http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11
_5.swc

And copy it to:
/frameworks/libs/player/11.5/playerglobal.swc

(Thanks again Justin McLean for this explanation.)

Marcus Fritze

Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :


Can you target 11.5 in Flash Builder(4.7)
Does this automatically set the swf version to 18 or is that something
else ?

Andy

-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: 30 January 2013 00:38
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

HI,

Just be aware that you need to compile your application with 11.5 (and
swf version set to 18) for this to take effect.

Thanks,
Justin










--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

RE: A code name for Apache Flex 5?

[David Coleman]

from the outside, looking in, I'll throw my hat in the ring for "Excalibur".  
It just sounds like a fitting successor to "Hero"...

just my 2 cents, for whatever it's worth.  :-)

> From: jonbcam...@gmail.com
> Date: Wed, 30 Jan 2013 10:25:51 -0600
> Subject: Re: A code name for Apache Flex 5?
> To: dev@flex.apache.org
> 
> On Wed, Jan 30, 2013 at 6:19 AM, Kessler CTR Mark J <
> mark.kessler@usmc.mil> wrote:
> 
> > If we did use code names could be have a running alphabet one?  Like your
> > android ones work...
> 
> 
> I'm not sure we need to worry about coming to a consensus on a name.
> Probably just wasted effort. I'd say develop in your whiteboard and name
> your code whatever cool name you like. If it gets picked up as the
> next iteration then the name is stuck.
> 
> Example: Alex had already been working on an idea with parts that he called
> "Beads". If he decides to name his branch "Beads" and people get behind it
> then the next version will most likely be known as "Beads".
> 
> 
> -- 
> Jonathan Campos
  

Re: [ASJS] VanillaSDK as part of the SDK

[Erik de Bruin]

Alex,

> So yes, while I still have reservations about your approach and wish I could
> convince you to join me on my re-write, I think you are making a good
> proposal for helping folks know the boundaries on what components you are
> supporting.

I will join you with your work on FlexJS, don't worry. I think I can
be helpful with your transition to FalconJx and in emitting a more
'goog' oriented output. That way FlexJS and the VanillaSDK can share
the 'goog' emitter in FalconJx, one less thing to worry about for you.
That way you (and Om?) can focus on the frameworks.

But first I'm putting the finishing touches on the inclusion of the
Closure Compiler into FalconJx, loosing the Python dependency along
the way, which is a (very) good thing -- that dependency was kinda
ruining the prospects for the VanillaSDK approach ;-)

Then I'm off skiing next week!

Have fun,

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Flash Player 11.5 - Debug trace in release player

[Alex Harui]

Just about every new feature is gated by SWF version.  Some legacy code may
have been relying on the lack of debug information in the
Error.getStackTrace() in a release build.  In fact, I haven't tried it, but
it could break my hacks described here:
http://blogs.adobe.com/aharui/2007/10/debugging_tricks.html


On 1/30/13 8:40 AM, "Marcus Fritze"  wrote:

> @Frédéric
> 
> Yes, you are right, it's not an API "function". It's more an "internal
> functionality" of the Flash Player. But I am not sure if you are right. I have
> tested this for my own and the debug with release player only worked when I
> compiled against 11.5.
> 
> Maybe someone else can confirm.
> 
> Marcus
> 
> Am 30.01.2013 um 17:28 schrieb Frédéric THOMAS :
> 
>> AFAIK, this feature is only about the stack trace of errors in the "release
>> Flash Player >= 11.5", nothing is relative to any API to use, so, the SDK is
>> not implied and you app can be compile with any version, having 11.5 release
>> player installed is sufficient.
>> 
>> Tell me if I missed something.
>> 
>> -Fred
>> 
>> -Message d'origine- From: Marcus Fritze
>> Sent: Wednesday, January 30, 2013 5:16 PM
>> To: dev@flex.apache.org
>> Subject: Re: Flash Player 11.5 - Debug trace in release player
>> 
>> AFAIK, the 4.5.1A targets Flash Player 10.2
>> 
>> So the minimum required FP version of your customers is 10.2 and you can use
>> only the API of 10.2 (no debug trace for release versions). If the user has
>> 11.5 installed it will only use 10.2 API because you compiled your app in
>> this version.
>> 
>> 
>> Am 30.01.2013 um 17:08 schrieb David Coleman :
>> 
>>> Does this mean that an app that I compile with the default settings for
>>> 4.5.1A will not benefit from this stacktrace availability, even if the user
>>> has 11.5 installed?  Or is having 11.5 release player installed, sufficient?
>>> We have an extensive error reporting system in our app that would benefit
>>> greatly from this... however forcing users to upgrade their flash player is
>>> not an option as our user base contains many people with legacy browsers.
>>> 
 From: marcus.fri...@googlemail.com
 Subject: Re: Flash Player 11.5 - Debug trace in release player
 Date: Wed, 30 Jan 2013 17:02:55 +0100
 To: dev@flex.apache.org
 
 Download the current SDK.
 
 Just edit the framework/flex-config.xml file and change this lines:
  
 11.1
 
  
 14
 
 To:
  
 11.5
 
  
 18
 
 You also need to download the the 11.5 playerglobal.swc from here:
 http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11
 _5.swc
 
 And copy it to:
 /frameworks/libs/player/11.5/playerglobal.swc
 
 (Thanks again Justin McLean for this explanation.)
 
 Marcus Fritze
 
 Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :
 
> Can you target 11.5 in Flash Builder(4.7)
> Does this automatically set the swf version to 18 or is that something
> else ?
> 
> Andy
> 
> -Original Message-
> From: Justin Mclean [mailto:jus...@classsoftware.com]
> Sent: 30 January 2013 00:38
> To: dev@flex.apache.org
> Subject: Re: Flash Player 11.5 - Debug trace in release player
> 
> HI,
> 
> Just be aware that you need to compile your application with 11.5 (and
> swf version set to 18) for this to take effect.
> 
> Thanks,
> Justin
 
>>> 
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Flash Player 11.5 - Debug trace in release player

[Marcus Fritze]

@Frédéric

Yes, you are right, it's not an API "function". It's more an "internal 
functionality" of the Flash Player. But I am not sure if you are right. I have 
tested this for my own and the debug with release player only worked when I 
compiled against 11.5.

Maybe someone else can confirm.

Marcus

Am 30.01.2013 um 17:28 schrieb Frédéric THOMAS :

> AFAIK, this feature is only about the stack trace of errors in the "release 
> Flash Player >= 11.5", nothing is relative to any API to use, so, the SDK is 
> not implied and you app can be compile with any version, having 11.5 release 
> player installed is sufficient.
> 
> Tell me if I missed something.
> 
> -Fred
> 
> -Message d'origine- From: Marcus Fritze
> Sent: Wednesday, January 30, 2013 5:16 PM
> To: dev@flex.apache.org
> Subject: Re: Flash Player 11.5 - Debug trace in release player
> 
> AFAIK, the 4.5.1A targets Flash Player 10.2
> 
> So the minimum required FP version of your customers is 10.2 and you can use 
> only the API of 10.2 (no debug trace for release versions). If the user has 
> 11.5 installed it will only use 10.2 API because you compiled your app in 
> this version.
> 
> 
> Am 30.01.2013 um 17:08 schrieb David Coleman :
> 
>> Does this mean that an app that I compile with the default settings for 
>> 4.5.1A will not benefit from this stacktrace availability, even if the user 
>> has 11.5 installed?  Or is having 11.5 release player installed, sufficient? 
>>  We have an extensive error reporting system in our app that would benefit 
>> greatly from this... however forcing users to upgrade their flash player is 
>> not an option as our user base contains many people with legacy browsers.
>> 
>>> From: marcus.fri...@googlemail.com
>>> Subject: Re: Flash Player 11.5 - Debug trace in release player
>>> Date: Wed, 30 Jan 2013 17:02:55 +0100
>>> To: dev@flex.apache.org
>>> 
>>> Download the current SDK.
>>> 
>>> Just edit the framework/flex-config.xml file and change this lines:
>>>  
>>> 11.1
>>> 
>>>  
>>> 14
>>> 
>>> To:
>>>  
>>> 11.5
>>> 
>>>  
>>> 18
>>> 
>>> You also need to download the the 11.5 playerglobal.swc from here:
>>> http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11_5.swc
>>> 
>>> And copy it to:
>>> /frameworks/libs/player/11.5/playerglobal.swc
>>> 
>>> (Thanks again Justin McLean for this explanation.)
>>> 
>>> Marcus Fritze
>>> 
>>> Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :
>>> 
 Can you target 11.5 in Flash Builder(4.7)
 Does this automatically set the swf version to 18 or is that something
 else ?
 
 Andy
 
 -Original Message-
 From: Justin Mclean [mailto:jus...@classsoftware.com]
 Sent: 30 January 2013 00:38
 To: dev@flex.apache.org
 Subject: Re: Flash Player 11.5 - Debug trace in release player
 
 HI,
 
 Just be aware that you need to compile your application with 11.5 (and
 swf version set to 18) for this to take effect.
 
 Thanks,
 Justin
>>> 
>> 
> 

Re: Performance expectations for Flex JS

[Alex Harui]

On 1/30/13 1:12 AM, "Roland Zwaga"  wrote:

> I'm pretty sure that the snappiness of HTML5 applications has little to do
> with the execution speed of JS.
> In most modern browser VM's JS actually is faster than AS3, the trouble
> starts when dealing with UI stuff,
> which is more DOM or Canvas related.

I've seen some information that implies that execution speed of AS and JS
depends a lot on how strongly typed it is (for JS, I think that includes
both type hints and type inference) and how often that code runs.  In AS,
just about everything gets JIT'd, and for Flex, we have lots of code that
runs once (or relatively few times) and despite the fact we use strict-mode
compilation, is not nearly as strongly typed as as it could be.

One of the things I'm trying to do in my rewrite is create more re-usable
chunks of code and allow for more strong typing.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Flash Player 11.5 - Debug trace in release player

[Frédéric THOMAS]

AFAIK, this feature is only about the stack trace of errors in the "release 
Flash Player >= 11.5", nothing is relative to any API to use, so, the SDK is 
not implied and you app can be compile with any version, having 11.5 release 
player installed is sufficient.


Tell me if I missed something.

-Fred

-Message d'origine- 
From: Marcus Fritze

Sent: Wednesday, January 30, 2013 5:16 PM
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

AFAIK, the 4.5.1A targets Flash Player 10.2

So the minimum required FP version of your customers is 10.2 and you can use 
only the API of 10.2 (no debug trace for release versions). If the user has 
11.5 installed it will only use 10.2 API because you compiled your app in 
this version.



Am 30.01.2013 um 17:08 schrieb David Coleman 
:


Does this mean that an app that I compile with the default settings for 
4.5.1A will not benefit from this stacktrace availability, even if the 
user has 11.5 installed?  Or is having 11.5 release player installed, 
sufficient?  We have an extensive error reporting system in our app that 
would benefit greatly from this... however forcing users to upgrade their 
flash player is not an option as our user base contains many people with 
legacy browsers.



From: marcus.fri...@googlemail.com
Subject: Re: Flash Player 11.5 - Debug trace in release player
Date: Wed, 30 Jan 2013 17:02:55 +0100
To: dev@flex.apache.org

Download the current SDK.

Just edit the framework/flex-config.xml file and change this lines:
  

 11.1

  
 14

To:
  

 11.5

  
 18

You also need to download the the 11.5 playerglobal.swc from here:
http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11_5.swc

And copy it to:
/frameworks/libs/player/11.5/playerglobal.swc

(Thanks again Justin McLean for this explanation.)

Marcus Fritze

Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :


Can you target 11.5 in Flash Builder(4.7)
Does this automatically set the swf version to 18 or is that something
else ?

Andy

-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: 30 January 2013 00:38
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

HI,

Just be aware that you need to compile your application with 11.5 (and
swf version set to 18) for this to take effect.

Thanks,
Justin

Re: A code name for Apache Flex 5?

[Jonathan Campos]

On Wed, Jan 30, 2013 at 6:19 AM, Kessler CTR Mark J <
mark.kessler@usmc.mil> wrote:

> If we did use code names could be have a running alphabet one?  Like your
> android ones work...


I'm not sure we need to worry about coming to a consensus on a name.
Probably just wasted effort. I'd say develop in your whiteboard and name
your code whatever cool name you like. If it gets picked up as the
next iteration then the name is stuck.

Example: Alex had already been working on an idea with parts that he called
"Beads". If he decides to name his branch "Beads" and people get behind it
then the next version will most likely be known as "Beads".


-- 
Jonathan Campos

Re: [ASJS] VanillaSDK as part of the SDK

[Alex Harui]

There is already precedence for mapping existing components to a new
namespace.  Some spark components are just MX components also referenced
from the spark manifest (SWFLoader, ArrayCollection).

So yes, while I still have reservations about your approach and wish I could
convince you to join me on my re-write, I think you are making a good
proposal for helping folks know the boundaries on what components you are
supporting.

-Alex


On 1/30/13 12:05 AM, "Erik de Bruin"  wrote:

> I'm proposing to use what the SDK has to offer, mx and spark, and add
> a thin wrapper class around each of those: goog. However, the goog
> components don't add any functionality, they only provide support for
> the JS workflow. From a developer point of view they'll look and act
> just like their mx and spark counterparts.
> 
> EdB
> 
> 
> 
> On Wed, Jan 30, 2013 at 6:08 AM, Avi Kessner  wrote:
>> Something isn't clear to me.
>> 
>> Are you proposing that the AS3 code for Flex contains 3 groups of
>> components?  (mx or it's equivilent, spark, and goog)
>> Or are you proposing that there are 2 groups of AS3 components, mx and
>> spark, and one set of JS components (goog) which have different levels
>> of compatibility with the first 2 groups?
>> 
>> brought to you by the letters A, V, and I
>> and the number 47
>> 
>> 
>> On Tue, Jan 29, 2013 at 9:30 PM, Erik de Bruin  wrote:
>> 
>>> Hi,
>>> 
>>> One of the goals behind the vanilla SDK is to create a JS compatible
>>> framework that closely resembles the Flex SDK. The idea is that the
>>> coding and workflow in the AS IDE (likely Flash Builder) closely
>>> matches working with Flex as we know it. This way ASJS has no learning
>>> curve at all: it's just another release build option. JS output that
>>> "just works" :-)
>>> 
>>> In order to do accomplish this, I'm working on integrating the
>>> VanillaSDK into the SDK proper. Don't worry, it's all happening in my
>>> whiteboard for now.
>>> 
>>> But I'd like your feedback on some of my ideas, while the
>>> implementation is still in it's early stages:
>>> 
>>> 1) create a new namespace in the SDK: http://flex.apache.org/js/goog
>>> 2) add only the components to this namespace that are compatible with JS
>>> output
>>> 3) create JS compatible versions of spark (and other?) components,
>>> using composition
>>> 4) create JS versions of these components: the VanillaSDK
>>> 
>>> This way hope to achieve the following:
>>> 1) isolate the new components from the rest of the SDK, to avoid
>>> "confusion" for developers
>>> 2) allow for incremental development, since only properly prepared
>>> components will be available
>>> 3) by using composition instead of inheritance we keep control over
>>> what we expose to the developer, allowing for API compatibility on the
>>> JS and AS side, while still use Flex components on the AS side
>>> 
>>> There's (much) more to it, but for now I'd like to ask: does this make
>>> any sense, and if it does, how might we improve on this idea to make
>>> it work better?
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> --
>>> Ix Multimedia Software
>>> 
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>> 
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>> 
> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Flash Player 11.5 - Debug trace in release player

[Marcus Fritze]

AFAIK, the 4.5.1A targets Flash Player 10.2

So the minimum required FP version of your customers is 10.2 and you can use 
only the API of 10.2 (no debug trace for release versions). If the user has 
11.5 installed it will only use 10.2 API because you compiled your app in this 
version.


Am 30.01.2013 um 17:08 schrieb David Coleman :

> Does this mean that an app that I compile with the default settings for 
> 4.5.1A will not benefit from this stacktrace availability, even if the user 
> has 11.5 installed?  Or is having 11.5 release player installed, sufficient?  
> We have an extensive error reporting system in our app that would benefit 
> greatly from this... however forcing users to upgrade their flash player is 
> not an option as our user base contains many people with legacy browsers. 
> 
>> From: marcus.fri...@googlemail.com
>> Subject: Re: Flash Player 11.5 - Debug trace in release player
>> Date: Wed, 30 Jan 2013 17:02:55 +0100
>> To: dev@flex.apache.org
>> 
>> Download the current SDK.
>> 
>> Just edit the framework/flex-config.xml file and change this lines:
>>   
>>  11.1
>> 
>>   
>>  14
>> 
>> To:
>>   
>>  11.5
>> 
>>   
>>  18
>> 
>> You also need to download the the 11.5 playerglobal.swc from here:
>> http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11_5.swc
>> 
>> And copy it to:
>> /frameworks/libs/player/11.5/playerglobal.swc
>> 
>> (Thanks again Justin McLean for this explanation.)
>> 
>> Marcus Fritze
>> 
>> Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :
>> 
>>> Can you target 11.5 in Flash Builder(4.7)
>>> Does this automatically set the swf version to 18 or is that something
>>> else ?
>>> 
>>> Andy
>>> 
>>> -Original Message-
>>> From: Justin Mclean [mailto:jus...@classsoftware.com] 
>>> Sent: 30 January 2013 00:38
>>> To: dev@flex.apache.org
>>> Subject: Re: Flash Player 11.5 - Debug trace in release player
>>> 
>>> HI,
>>> 
>>> Just be aware that you need to compile your application with 11.5 (and
>>> swf version set to 18) for this to take effect.
>>> 
>>> Thanks,
>>> Justin
>> 
> 

Re: URGENT: ASNext and FlashPlayer Next are DEAD!

[Avi Kessner]

Or we will see the death of Javascript and the rise of Actionscript native
in the browser :D

brought to you by the letters A, V, and I
and the number 47


On Wed, Jan 30, 2013 at 5:54 PM, Michael A. Labriola <
labri...@digitalprimates.net> wrote:

> "At the same time, Adobe plans to continue its next-generation virtual
> machine and language work as part of the larger web community doing such
> work on web-based virtual machines."
>
> To me this means the fulfillment of something we mostly predicted a while
> ago. Adobe will begin playing even more with others and will contribute
> more to things like web kit. We will see some tooling and Flash Player play
> a less important role over the coming years. It's not a big surprise, I
> could never figure out how they were justifying the investment in their new
> virtual machine anyways, and I really don't see it impact Apache Flex in
> the least for years to come.
>
> Mike
>
>

RE: Flash Player 11.5 - Debug trace in release player

[David Coleman]

Does this mean that an app that I compile with the default settings for 4.5.1A 
will not benefit from this stacktrace availability, even if the user has 11.5 
installed?  Or is having 11.5 release player installed, sufficient?  We have an 
extensive error reporting system in our app that would benefit greatly from 
this... however forcing users to upgrade their flash player is not an option as 
our user base contains many people with legacy browsers. 

> From: marcus.fri...@googlemail.com
> Subject: Re: Flash Player 11.5 - Debug trace in release player
> Date: Wed, 30 Jan 2013 17:02:55 +0100
> To: dev@flex.apache.org
> 
> Download the current SDK.
> 
>  Just edit the framework/flex-config.xml file and change this lines:
>
>   11.1
> 
>
>   14
> 
> To:
>
>   11.5
> 
>
>   18
> 
> You also need to download the the 11.5 playerglobal.swc from here:
> http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11_5.swc
> 
> And copy it to:
> /frameworks/libs/player/11.5/playerglobal.swc
> 
> (Thanks again Justin McLean for this explanation.)
> 
> Marcus Fritze
> 
> Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :
> 
> > Can you target 11.5 in Flash Builder(4.7)
> > Does this automatically set the swf version to 18 or is that something
> > else ?
> > 
> > Andy
> > 
> > -Original Message-
> > From: Justin Mclean [mailto:jus...@classsoftware.com] 
> > Sent: 30 January 2013 00:38
> > To: dev@flex.apache.org
> > Subject: Re: Flash Player 11.5 - Debug trace in release player
> > 
> > HI,
> > 
> > Just be aware that you need to compile your application with 11.5 (and
> > swf version set to 18) for this to take effect.
> > 
> > Thanks,
> > Justin
> 
  

Re: Flash Player 11.5 - Debug trace in release player

[Marcus Fritze]

Download the current SDK.

 Just edit the framework/flex-config.xml file and change this lines:
   
  11.1

   
  14

To:
   
  11.5

   
  18

You also need to download the the 11.5 playerglobal.swc from here:
http://fpdownload.macromedia.com/get/flashplayer/updaters/11/playerglobal11_5.swc

And copy it to:
/frameworks/libs/player/11.5/playerglobal.swc

(Thanks again Justin McLean for this explanation.)

Marcus Fritze

Am 30.01.2013 um 16:44 schrieb "Cooper, Andrew" :

> Can you target 11.5 in Flash Builder(4.7)
> Does this automatically set the swf version to 18 or is that something
> else ?
> 
> Andy
> 
> -Original Message-
> From: Justin Mclean [mailto:jus...@classsoftware.com] 
> Sent: 30 January 2013 00:38
> To: dev@flex.apache.org
> Subject: Re: Flash Player 11.5 - Debug trace in release player
> 
> HI,
> 
> Just be aware that you need to compile your application with 11.5 (and
> swf version set to 18) for this to take effect.
> 
> Thanks,
> Justin

RE: URGENT: ASNext and FlashPlayer Next are DEAD!

[Michael A. Labriola]

"At the same time, Adobe plans to continue its next-generation virtual machine 
and language work as part of the larger web community doing such work on 
web-based virtual machines."

To me this means the fulfillment of something we mostly predicted a while ago. 
Adobe will begin playing even more with others and will contribute more to 
things like web kit. We will see some tooling and Flash Player play a less 
important role over the coming years. It's not a big surprise, I could never 
figure out how they were justifying the investment in their new virtual machine 
anyways, and I really don't see it impact Apache Flex in the least for years to 
come.

Mike

RE: Flash Player 11.5 - Debug trace in release player

[Cooper, Andrew]

Can you target 11.5 in Flash Builder(4.7)
Does this automatically set the swf version to 18 or is that something
else ?

Andy

-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com] 
Sent: 30 January 2013 00:38
To: dev@flex.apache.org
Subject: Re: Flash Player 11.5 - Debug trace in release player

HI,

Just be aware that you need to compile your application with 11.5 (and
swf version set to 18) for this to take effect.

Thanks,
Justin

RE: URGENT: ASNext and FlashPlayer Next are DEAD!

[Kessler CTR Mark J]

Well it's not dead per se.  It looks to be adding them into the "web based 
virtual machines".   I am hoping they will just make a new namespace inside AS 
so you can keep your old components while having the ability to transition in 
some new features.  Such as moving from MX to Spark.  Then we could keep our 
idea of compiling for X.

"At the same time, Adobe plans to continue its next-generation virtual machine 
and language work as part of the larger web community doing such work on 
web-based virtual machines."

-Mark

-Original Message-
From: Lists [mailto:li...@psycholutions.com] 
Sent: Wednesday, January 30, 2013 9:55 AM
To: dev@flex.apache.org
Subject: URGENT: ASNext and FlashPlayer Next are DEAD!

Read it on:

http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.edu.html

c u stevie

RE: [Website] New website going live

[Skogen, Espen]

Looks great! Glad to see it materialize!!

E:)

-Original Message-
From: JP Bader [mailto:j...@zavteq.com] 
Sent: 30 January 2013 14:42
To: dev@flex.apache.org
Subject: Re: [Website] New website going live

Very super small detail (pedantic, really), in the footer, under Subscribe,
the first paragraph, last few words.  please fix to 'and one for SDK users.

and one SDK users.

Otherwise, looks great!

On Tue, Jan 29, 2013 at 10:29 PM, Nicholas Kwiatkowski wrote:

> The new website is sitting on staging now.  I'm going to push it to
> production at Noon EDT tomorrow (~12 hours from now) unless somebody finds
> a compelling reason why we shouldn't.
>
> http://flex.staging.apache.org/
>
> -Nick
>
> On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski  >wrote:
>
> > Hey everybody!
> >
> > We got final permission from a few different groups at Apache to make the
> > website live.  If you have any pending commits to the site/ directory in
> > SVN, please make sure those go in soon as things are about to be all
> moved
> > around there.
> >
> > After the website goes live, I'll put in the download tracking code.
> >
> > -Nick
> >
>



-- 
JP Bader
Principal
Zavteq, Inc.
@lordB8r | j...@zavteq.com
608.692.2468
This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of
securities, accuracy and completeness of information, viruses,
confidentiality, legal privilege, and legal entity disclaimers,
available at http://www.jpmorgan.com/pages/disclosures/email.

RE: URGENT: ASNext and FlashPlayer Next are DEAD!

[Antonio Ortiz]

That Alex Hauri already says when published...

> From: li...@psycholutions.com
> To: dev@flex.apache.org
> Subject: URGENT: ASNext and FlashPlayer Next are DEAD!
> Date: Wed, 30 Jan 2013 15:55:00 +0100
> 
> Read it on:
> 
> http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.edu.html
> 
> c u stevie
> 
  

[jira] [Updated] (FLEX-33373) bindable styles in ColorTransform

[mike (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mike updated FLEX-33373:


Description: 

http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]



















current code working, but for default state 
color="{getStyle('myColor')}"
it show black color

  was:
{code:mxml}

http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]


















{code}

current code working, but for default state 
{code}color="{getStyle('myColor')}"{code} it show black color


> bindable styles in ColorTransform
> -
>
> Key: FLEX-33373
> URL: https://issues.apache.org/jira/browse/FLEX-33373
> Project: Apache Flex
>  Issue Type: Wish
>  Components: Skinning
>Reporter: mike
>Priority: Minor
>  Labels: colortransform,, skinning
>
> 
> http://ns.adobe.com/mxml/2009"; 
> xmlns:s="library://ns.adobe.com/flex/spark">
> 
> 
> [HostComponent("spark.components.Button")]
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  source="@Embed('icon.png')"
> >
> 
> 
>  color="{getStyle('myColor')}"
> color.over="{getStyle('myColorOver)}"
> />
> 
> 
> 
> 
> 
> current code working, but for default state 
> color="{getStyle('myColor')}"
> it show black color

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33373) bindable styles in ColorTransform

[mike (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mike updated FLEX-33373:


Description: 
{code:mxml}

http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]


















{code}

current code working, but for default state 
{code}color="{getStyle('myColor')}"{code} it show black color

  was:
{code:mxml}

http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]


















{code}

current code working, but for default state 
{code}color="{getStyle('myColor')}"{code} it show black color


> bindable styles in ColorTransform
> -
>
> Key: FLEX-33373
> URL: https://issues.apache.org/jira/browse/FLEX-33373
> Project: Apache Flex
>  Issue Type: Wish
>  Components: Skinning
>Reporter: mike
>Priority: Minor
>  Labels: colortransform,, skinning
>
> {code:mxml}
> 
> http://ns.adobe.com/mxml/2009"; 
> xmlns:s="library://ns.adobe.com/flex/spark">
>   
> 
>   [HostComponent("spark.components.Button")]
>   
>   
>   
>   
>   
>   
>   
>   
>   
>  source="@Embed('icon.png')"
>   >
>   
>   
>  color="{getStyle('myColor')}"
>   color.over="{getStyle('myColorOver)}"
>   />
>   
>   
>   
>   
> 
> {code}
> current code working, but for default state 
> {code}color="{getStyle('myColor')}"{code} it show black color

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [Website] New website going live

[JP Bader]

Very super small detail (pedantic, really), in the footer, under Subscribe,
the first paragraph, last few words.  please fix to 'and one for SDK users.

and one SDK users.

Otherwise, looks great!

On Tue, Jan 29, 2013 at 10:29 PM, Nicholas Kwiatkowski wrote:

> The new website is sitting on staging now.  I'm going to push it to
> production at Noon EDT tomorrow (~12 hours from now) unless somebody finds
> a compelling reason why we shouldn't.
>
> http://flex.staging.apache.org/
>
> -Nick
>
> On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski  >wrote:
>
> > Hey everybody!
> >
> > We got final permission from a few different groups at Apache to make the
> > website live.  If you have any pending commits to the site/ directory in
> > SVN, please make sure those go in soon as things are about to be all
> moved
> > around there.
> >
> > After the website goes live, I'll put in the download tracking code.
> >
> > -Nick
> >
>



-- 
JP Bader
Principal
Zavteq, Inc.
@lordB8r | j...@zavteq.com
608.692.2468

[jira] [Updated] (FLEX-33373) bindable styles in ColorTransform

[mike (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mike updated FLEX-33373:


Description: 
{code:mxml}

http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]


















{code}

current code working, but for default state 
{code}color="{getStyle('myColor')}"{code} it show black color

  was:


http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]




















current code working, but for default state `color="{getStyle('myColor')}"` it 
show black color


> bindable styles in ColorTransform
> -
>
> Key: FLEX-33373
> URL: https://issues.apache.org/jira/browse/FLEX-33373
> Project: Apache Flex
>  Issue Type: Wish
>  Components: Skinning
>Reporter: mike
>Priority: Minor
>  Labels: colortransform,, skinning
>
> {code:mxml}
> 
> http://ns.adobe.com/mxml/2009"; 
> xmlns:s="library://ns.adobe.com/flex/spark">
>   
>   
>   [HostComponent("spark.components.Button")]
>   
>   
>   
>   
>   
>   
>   
>   
>   
>  source="@Embed('icon.png')"
>   >
>   
>   
>  color="{getStyle('myColor')}"
>   color.over="{getStyle('myColorOver)}"
>   />
>   
>   
>   
>   
> 
> {code}
> current code working, but for default state 
> {code}color="{getStyle('myColor')}"{code} it show black color

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLEX-33373) bindable styles in ColorTransform

[mike (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FLEX-33373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mike updated FLEX-33373:


Description: 


http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]




















current code working, but for default state `color="{getStyle('myColor')}"` it 
show black color

  was:


http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]




















current code working, but for default state 
color="{getStyle('myColor')}" it show black color


> bindable styles in ColorTransform
> -
>
> Key: FLEX-33373
> URL: https://issues.apache.org/jira/browse/FLEX-33373
> Project: Apache Flex
>  Issue Type: Wish
>  Components: Skinning
>Reporter: mike
>Priority: Minor
>  Labels: colortransform,, skinning
>
> 
> 
> http://ns.adobe.com/mxml/2009"; 
> xmlns:s="library://ns.adobe.com/flex/spark">
>   
>   
>   [HostComponent("spark.components.Button")]
>   
>   
>   
>   
>   
>   
>   
>   
>   
>  source="@Embed('icon.png')"
>   >
>   
>   
>  color="{getStyle('myColor')}"
>   color.over="{getStyle('myColorOver)}"
>   />
>   
>   
>   
>   
> 
> 
> current code working, but for default state `color="{getStyle('myColor')}"` 
> it show black color

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FLEX-33373) bindable styles in ColorTransform

[mike (JIRA)]

mike created FLEX-33373:
---

 Summary: bindable styles in ColorTransform
 Key: FLEX-33373
 URL: https://issues.apache.org/jira/browse/FLEX-33373
 Project: Apache Flex
  Issue Type: Wish
  Components: Skinning
Reporter: mike
Priority: Minor




http://ns.adobe.com/mxml/2009"; 
xmlns:s="library://ns.adobe.com/flex/spark">


[HostComponent("spark.components.Button")]




















current code working, but for default state 
color="{getStyle('myColor')}" it show black color

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [Website] New website going live

[Nils Dupont]

Hi Nick,

Very good job! Very nice looking :)

Just a small detail: it seems that a thin left margin (around 20-30 pixels
wide) appears with media queries when window's width is smaller than 767
px. I could reproduce this with firefox 18 and IE 8 on Windows and with any
browser on Android (including Chrome and Firefox).

Cheers,
Nils



2013/1/30 Nicholas Kwiatkowski 

> The new website is sitting on staging now.  I'm going to push it to
> production at Noon EDT tomorrow (~12 hours from now) unless somebody finds
> a compelling reason why we shouldn't.
>
> http://flex.staging.apache.org/
>
> -Nick
>
> On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski  >wrote:
>
> > Hey everybody!
> >
> > We got final permission from a few different groups at Apache to make the
> > website live.  If you have any pending commits to the site/ directory in
> > SVN, please make sure those go in soon as things are about to be all
> moved
> > around there.
> >
> > After the website goes live, I'll put in the download tracking code.
> >
> > -Nick
> >
>

Re: [Website] New website going live

[Harbs]

Okay. So I guess I'll wait and see if anyone else thinks styling the blog is a 
good idea… ;-)

Harbs

On Jan 30, 2013, at 3:38 PM, Bertrand Delacretaz wrote:

> On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
>> ...Flex seems to have a css file specific to the Flex blog here: 
>> http://blogs.apache.org/flex/page/asf-custom.css
>> 
>> It seems to me a question as to whether there's a policy against customizing 
>> the blog more than anything else…
> 
> I don't think there's an ASF policy, you'll need to find out if
> infrastructure@ agrees with giving someone from the Flex PMC access to
> that styling configuration. If it's just CSS, it shouldn't be too
> hard.
> 
> -Bertrand

Re: [Website] New website going live

[Bertrand Delacretaz]

On Wed, Jan 30, 2013 at 2:34 PM, Harbs  wrote:
> ...Flex seems to have a css file specific to the Flex blog here: 
> http://blogs.apache.org/flex/page/asf-custom.css
>
> It seems to me a question as to whether there's a policy against customizing 
> the blog more than anything else…

I don't think there's an ASF policy, you'll need to find out if
infrastructure@ agrees with giving someone from the Flex PMC access to
that styling configuration. If it's just CSS, it shouldn't be too
hard.

-Bertrand

Re: [Website] New website going live

[Harbs]

Technically, I don't see any reason why it can't be customized. It's supposed 
to be customizable via css.

Flex seems to have a css file specific to the Flex blog here: 
http://blogs.apache.org/flex/page/asf-custom.css

It seems to me a question as to whether there's a policy against customizing 
the blog more than anything else…

Harbs

On Jan 30, 2013, at 3:22 PM, Bertrand Delacretaz wrote:

> Hi,
> 
> On Wed, Jan 30, 2013 at 2:19 PM, Harbs  wrote:
>> ...Is there any chance of getting the blog [1] skinned to match the website, 
>> or does it have to match the rest of Apache blogs?...
> 
> That runs on http://roller.apache.org/ - you could have a look in
> there to see if blogs can have individual skins, and if yes talk to
> infra to see if that's supported on our setup.
> 
> -Bertrand
> 
>> [1] http://blogs.apache.org/flex/

Re: [Website] New website going live

[Bertrand Delacretaz]

Hi,

On Wed, Jan 30, 2013 at 2:19 PM, Harbs  wrote:
> ...Is there any chance of getting the blog [1] skinned to match the website, 
> or does it have to match the rest of Apache blogs?...

That runs on http://roller.apache.org/ - you could have a look in
there to see if blogs can have individual skins, and if yes talk to
infra to see if that's supported on our setup.

-Bertrand

> [1] http://blogs.apache.org/flex/