[svn:fx-trunk] 9054: Refactoring DataGroup a bit to allow for more robust delegation of renderer updates to owning components .

Revision: 9054
Author:   [email protected]
Date:     2009-08-04 07:12:22 -0700 (Tue, 04 Aug 2009)
Log Message:
Refactoring DataGroup a bit to allow for more robust delegation of renderer updates to owning components. Found and addressed an issue where we were setting the label for each item renderer upwards of four times each update.
QE notes: None
Doc notes: None
Bugs: SDK-22153, SDK-22226
Reviewer: Ryan
Tests run: Checkin, Mustella Spark (List, ButtonBar, DataGroup)
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22153
    http://bugs.adobe.com/jira/browse/SDK-22226
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/ButtonBar.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DataGroup.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/SkinnableDataContainer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ListBase.as

Similar Messages

[svn:fx-trunk] 12788: By popular demand, we now allow for empty child property tags for Array type properties.

Revision: 12788
Revision: 12788
Author:   [email protected]
Date:     2009-12-10 07:46:54 -0800 (Thu, 10 Dec 2009)
Log Message:
By popular demand, we now allow for empty child property tags for Array type properties. Coerced to empty array '[]'.
QE notes: None
Doc notes: None
Bugs: SDK-24500
Reviewer: Paul
Tests run: Checkin
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24500
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBuilder.jav a

Hi John,
Sorry to tell but tab completion is still failing on my Windows XP/Indesign CS5 (caught by Indesign).
I just saw your remark on coloring text, here is an example pulled out from Peter's book "ScriptUI for dummies":
var w = new Window ("dialog");
var s = w.add ("statictext", undefined, "Static");
var e = w.add ("edittext", undefined, "Edit");
var b = w.add ("button", undefined, "Button");
// The window's backround
w.graphics.backgroundColor = w.graphics.newBrush (w.graphics.BrushType.SOLID_COLOR, [0.5, 0.0, 0.0]);
// Font and its colour for the first item, statictext
s.graphics.font = ScriptUI.newFont ("Helvetica", "Bold", 30);
s.graphics.foregroundColor = s.graphics.newPen (w.graphics.PenType.SOLID_COLOR, [0.7, 0.7, 0.7], 1);
// Font and colours for the second item, edittext
e.graphics.font = ScriptUI.newFont ("Letter Gothic Std", "Bold", 30);
e.graphics.foregroundColor = e.graphics.newPen (e.graphics.PenType.SOLID_COLOR, [1, 0, 0], 1);
e.graphics.backgroundColor = e.graphics.newBrush (e.graphics.BrushType.SOLID_COLOR, [0.5, 0.5, 0.5]);
// Font for the tird control, a button. Can't set colours in buttons
b.graphics.font = ScriptUI.newFont ("Minion Pro", "Italic", 30);
w.show ();
Loic

[svn:fx-trunk] 12025: Switching out the old video component for the new video component that uses OSMF .

Revision: 12025
Revision: 12025
Author:   [email protected]
Date:     2009-11-19 17:48:04 -0800 (Thu, 19 Nov 2009)
Log Message:
Switching out the old video component for the new video component that uses OSMF. Also fixing RSL issue with OSMF because a change in flex-config.xml accidentally got overwritten. Also fixing a bug caught during the last code review where you would set the volume on the VideoPlayer, but the volumeBar wouldn't be made aware of that change.
Switching out the video component results in many API changes. The changes are highlighted below:
Class name changes:
- spark.primitives.VideoElement is being renamed to spark.components.VideoDisplay
- spark.components.mediaClasses.StreamingVideoSource is renamed to park.components.mediaClasses.DynamicStreamingVideoSource
- spark.components.mediaClasses.StreamItem is renamed to park.components.mediaClasses.DynamicStreamingVideoItem
VideoDisplay/VideoPlayer event changes:
The new video component's events are:
- bytesLoadedChange : org.osmf.events.LoadEvent
- currentTimeChange : org.osmf.events.TimeEvent
- durationChange : org.osmf.events.TimeEvent
- mediaPlayerStateChange : org.osmf.events.MediaPlayerStateChangeEvent
The old video component's events were:
- close : spark.events.VideoEvent (removed)
- complete : spark.events.VideoEvent (replaced with mediaPlayerStateChange)
- metaDataReceived : spark.events.VideoEvent (replaced with mediaPlayerStateChange)
- playheadUpdate : spark.events.VideoEvent (replaced with currentTimeChange)
- progress : flash.events.ProgressEvent (replaced with bytesLoadedChange)
- ready : spark.events.VideoEvent (replaced with mediaPlayerStateChange)
VideoDisplay/VideoPlayer property changes:
Renames:
- maintainAspectRatio:Boolean has been renamed to scaleMode:String and rather than true/false, it now access 4 values: none, zoom, letterbox, and stretch. See the enum class org.osmf.display.ScaleMode.
- playheadTime:Number has been renamed to currentTime:Number
- playWhenHidden has been renamed to pauseWhenHidden, and it's "tense" has been reversed. So playWhenHidden = true correlates to pauseWhenHidden = false. Also, before we would only pause when the video component was explcitly set to visible=false, but now we detect if the video components or any of it's ancestors have been hidden.
- totalTime:Number has been renamed to duration:Number
New properties:
- bytesLoaded:Number This is a new property not available on the old video component
- bytesTotal:Number This is a new property not available on the old video component
- loop: Boolean this was a property added a while ago on the old video component but not in the original video player spec
- mediaPlayerState: this is a new property that details the state of the video component. See org.osmf.media.MediaPlayerState for all the possible values.
- seekToFirstFrame:Boolean (pending PARB approval) - This is a new property available on VideoDisplay/VideoPlayer. When autoPlay = false, if seekToFirstFrame is set to true, then we will connect to the server to start downloading the video, figure out the size of the video and resize appropriately, and show the first frame of the video. If seekToFirstFrame is false, then no connection to the server is made, there's no implicit size for this video, and the first frame will not be show automatically. By default the value of this property is true. In the old video component, when autoPlay = false, we always has the same behavior as seekToFirstFrame = true. Now it is controllable through this property. Eventually, (not for Flex 4.0), we will most-likely have support for a thumbnail source or a splash screen so the video's preview will show up without making an unneeded connection to the server. The property name may change depending on PARB.
Other changes:
- autoRewind: The default of autoRewind is now true instead of false
- enabled: before we paused the video when the video component was explicitly set to enabled = false. Now we pause the video when the video component or any of it's ancestors have been disabled.
VideoPlayer-only changes:
- videoObject:flash.media.Video property is now a new property on VideoPlayer. It was previously only on VideoDisplay.
- The skin states for the old VideoPlayer were: connectionError, disabled, disconnected, loading, playing, stopped, connectionErrorAndFullScreen, disabledAndFullScreen, disconnectedAndFullScreen, loadingAndFullScreen, playingAndFullScreen, stoppedAndFullScreen. The new skin states are: uninitialized, loading, ready, playing, paused, buffering, playbackError, disabled, uninitializedAndFullScreen, loadingAndFullScreen, readyAndFullScreen, playingAndFullScreen, pausedAndFullScreen, bufferingAndFullScreen, playbackErrorAndFullScreen, disabledAndFullScreen
DynamicStreamingVideoItem property changes:
- bitRate:Number renamed to bitrate:Number
DynamicStreamingVideoSource property changes:
- initialIndex has been added to DynamicSteramingVideoSource
- live:Boolean has changed to streamType:String which accepts values: live, recorded, any. See the enum class org.osmf.net.StreamType for more info.
- serverURI:String renamed to host:Object
- streamItems:Array has changed types to streamItems:Vector.
ScrubBar property changes (THESE CHANGES ARE NOT DONE YET, BUT SHOULD BE DONE SOON)
- bufferedStart will be removed
- bufferedEnd will be renamed to loadedRangeEnd. This property name still may change depending on PARB.
- bufferedArea skin part needs to be renamed. Probably will be renamed to loadedArea. PARB still deciding.
QE notes: -
Doc notes: -
Bugs: -
Reviewer: Kevin
Tests run: checkintests
Is noteworthy for integration: Yes
Modified Paths:
    flex/sdk/trunk/frameworks/flex-config.xml
    flex/sdk/trunk/frameworks/projects/spark/defaults.css
    flex/sdk/trunk/frameworks/projects/spark/src/SparkClasses.as
    flex/sdk/trunk/frameworks/projects/wireframe/build.xml
    flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/VideoPlayerSkin.mx ml
    flex/sdk/trunk/frameworks/spark-manifest.xml
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/VideoPlayerSkin.mxml
Removed Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer2.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/mediaClasses/StreamItem.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/mediaClasses/StreamingVideo Source.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/VideoElement.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/VideoElement.png
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/VideoPlayerSkin.mxml
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/VideoPlayerSkin2.mxml

I've got that same problem: iPod Touch 2nd Gen, Apple Component Cables, and an HD TV.
The funny thing is, the cable works fine with an iPod Classic (160 GB) but not for the iPod Touch. Can anyone explain why that is?

[svn:fx-trunk] 4982: Moving DataGroup from item based lookup to an index based lookup.

Revision: 4982
Author: [email protected]
Date: 2009-02-16 23:31:05 -0800 (Mon, 16 Feb 2009)
Log Message:
Moving DataGroup from item based lookup to an index based lookup. Also, we now cleanup old item renderers when the dataProvider changes. This solves some memory leak problems.
Because of this, we should now be able to deal with duplicate items again.
We still need to work on data collection changes in the virtual layout case.
QE Notes: Please add the tests for dup items back in
Doc Notes: -
Bugs: SDK-19245, SDK-18043
Reviewer: Hans
tests: checkintests, DataGroup and FxList mustella tests (some new ones failed, but are really due to SDK-19287, and these tests should be excluded to that bug now)
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19245
http://bugs.adobe.com/jira/browse/SDK-18043
http://bugs.adobe.com/jira/browse/SDK-19287
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/DataGroup.as

GREAT info, but it may be helpful to note that when replacing a portion of the variable "Countries" with a whitespace character, you may cause the workflow to fail in a few specific cases (certain lookup fields will not accept this and will automatically
cancel). I only found this out when recreating your workflow on a similar, but much more complex list set.
To resolve this issue, I used another utility action (Extract Substring from Index of List) to clear out the whitespace. I configured it as "Copy from
Variable: Countries, starting at
1 (Output to Variable: Countries), which takes care of this issue in those few cases.
Otherwise, WOW! AWESOME JOB! Thanks! :)

[svn:fx-trunk] 12973: Added DataGroup/getItemIndicesInView() method and fixed a DataGroup virtual ItemRenderer leak.

Revision: 12973
Revision: 12973
Author:   [email protected]
Date:     2009-12-15 15:59:25 -0800 (Tue, 15 Dec 2009)
Log Message:
Added DataGroup/getItemIndicesInView() method and fixed a DataGroup virtual ItemRenderer leak.
Removed an obsolete FIXME from Spinner.
QE notes:
Doc notes:
Bugs: sdk-24702, sdk-24704
Reviewer: Evtim
Tests run: DataGroup
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-24702
    http://bugs.adobe.com/jira/browse/sdk-24704
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DataGroup.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Spinner.as

[svn:fx-trunk] 11530: Fix ASC-3790 ( conditional expression in for loop causes verifier error) r=jodyer

Revision: 11530
Author:   [email protected]
Date:     2009-11-06 13:23:05 -0800 (Fri, 06 Nov 2009)
Log Message:
Fix ASC-3790 (conditional expression in for loop causes verifier error) r=jodyer
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3790
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/ConditionalExpressionNode.java

[svn:fx-trunk] 10866: Fix broken links in ASDoc comments for TLFTextInput. as and TextArea.as, and add OverrideBase.as to ASDoc output

Revision: 10866
Author:   [email protected]
Date:     2009-10-05 08:56:44 -0700 (Mon, 05 Oct 2009)
Log Message:
Fix broken links in ASDoc comments for TLFTextInput.as and TextArea.as, and add OverrideBase.as to ASDoc output
QE notes: -
Doc notes: -
Bugs: -
Reviewer: -
Tests run: - checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/states/OverrideBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/mx/controls/TLFTextInput.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TextArea.as

Sorry about that. I am not exactly sure where the problem is, but I know it takes place after I put the <nav> in (in the html portion). If I understand what I am learning, the CSS at the top will structure my html code so I would have thought the CSS tageting my nav would be the focus. Maybe it is a different section though.
CSS part:
nav p {
font-size: 90%;
color: #FFC;
text-align: right;
font-weight: bold;
background-color: #090;
padding-top: 5px;
padding-right: 20px;
padding-bottom: 5px;
border-top-width: 2px;
border-top-style: solid;
border-top-color: #060;
HTML part: (bold italic is the part I added)
<body>
<div class="container">
<div id="apDiv1"><img src="Lessons/images/butterfly-ovr.png" width="170" height="158" alt="GreenStart Logo"></div>
<header></header>
<nav>
    <p>Home | About Us | Contact Us</p>
</nav>
<div class="sidebar1">
    <ul class="nav">
      <li><a href="#">Green News</a></li>
      <li><a href="#">Green Products</a></li>
      <li><a href="#">Green Events</a></li>
      <li><a href="#">Green Travel</a></li>
      <li><a href="#">Green Tips</a></li>
    </ul>

[svn:bz-trunk] 20004: Remove unneeded cast and instanceof check for FlexConfigurable.

Revision: 20004
Revision: 20004
Author:   [email protected]
Date:     2011-01-28 11:13:07 -0800 (Fri, 28 Jan 2011)
Log Message:
Remove unneeded cast and instanceof check for FlexConfigurable.
No functional change.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/FactoryDestination.java

[svn:fx-trunk] 10209: reverting commit 10198, which affected animation for some halo components like Tree and ComboBox.

Revision: 10209
Author:   [email protected]
Date:     2009-09-12 17:36:41 -0700 (Sat, 12 Sep 2009)
Log Message:
reverting commit 10198, which affected animation for some halo components like Tree and ComboBox. Should wait for either the real fix (involves RPC changes) or at least a fix that limits the scope to only Flex4 effects instead of all uses of UIComponent.suspendBackgroundProcessing.
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/LayoutManager.as

[svn:fx-trunk] 8136: Adjustments to default size and padding for TextInput and TextArea skins.

Revision: 8136
Author:   [email protected]
Date:     2009-06-23 16:16:49 -0700 (Tue, 23 Jun 2009)
Log Message:
Adjustments to default size and padding for TextInput and TextArea skins.
TextInput default with is big enough to hold 10 characters (it will actually hold more than 10 "normal width" characters)
TextArea padding matches TextInput padding
These changes are done to the Spark and Wireframe skins.
Bugs: SDK-16300 & SDK-16294
QE Notes: New baseline bitmaps are needed (sorry Peter!)
Doc Notes: None
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-16300
    http://bugs.adobe.com/jira/browse/SDK-16294
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/TextAreaSkin.mxml
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/TextInputSkin.mxml
    flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/TextAreaSkin.mxml
    flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/TextInputSkin.mxml

[svn:fx-trunk] 7204: Tweaks to appearance of Halo skins for WindowedApplication/ Window to match Spark appearance.

Revision: 7204
Author:   [email protected]
Date:     2009-05-21 16:30:20 -0700 (Thu, 21 May 2009)
Log Message:
Tweaks to appearance of Halo skins for WindowedApplication/Window to match Spark appearance.
Bug: SDK-19653
QA Notes: Baseline images of Halo WindowedApplication/Window need to be updated.
Doc Notes: none
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19653
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/defaults.css

I had downloaded it for test, and requested for evaluation license...
But I haven't got license, and also I am not able to find Flash Builder Plugins from HFCD site....
I think those plugins are removed from site....
Please help me, if anyone have those plugins...

[svn:fx-trunk] 11540: Adding a bunch of ASDoc samples for the following classes:

Revision: 11540
Author:   [email protected]
Date:     2009-11-06 14:27:40 -0800 (Fri, 06 Nov 2009)
Log Message:
Adding a bunch of ASDoc samples for the following classes:
    ColorBurnShader.as
    ColorDodgeShader.as
    ColorShader.as
    ExclusionShader.as
    HueShader.as
    LuminosityMaskShader.as
    LuminosityShader.as
    SaturationShader.as
    SoftLightShader.as
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Colo rBurnShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Colo rDodgeShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Colo rShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Excl usionShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/HueS hader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Lumi nosityMaskShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Lumi nosityShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Satu rationShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/shaders/Soft LightShader.as

[svn:bz-trunk] 10240: Add validateClient API to the MessageBroker for use in subclases

Revision: 10240
Author:   [email protected]
Date:     2009-09-14 11:36:09 -0700 (Mon, 14 Sep 2009)
Log Message:
Add validateClient API to the MessageBroker for use in subclases
to filter clients. Add a noop implementation.
If validateClient throws an exception, return 403 Forbidden to
client for the request.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java

[svn:fx-trunk] 8615: Added in enumerations to Inspectable metadata for a bunch of properties.

Revision: 8615
Author:   [email protected]
Date:     2009-07-15 17:06:27 -0700 (Wed, 15 Jul 2009)
Log Message:
Added in enumerations to Inspectable metadata for a bunch of properties.
Reviewer: Ryan
QA: Yes, regress
Doc: No
Checkintests: Pass
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/HGroup.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/SkinnableContainer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/GroupBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/core/IDeferredContentOwner.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/core/SpriteVisualElement.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform3D.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/HorizontalLayout.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/TileLayout.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/supportClasses/LayoutBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/BitmapImage.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/VideoElement.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/styles/metadata/BasicInheritingTextSty les.as

[svn:bz-trunk] 19782: Add Remoting test application and endpoints for testing login-after-disconnect channel setting .

Revision: 19782
Revision: 19782
Author:   [email protected]
Date:     2011-01-17 11:21:11 -0800 (Mon, 17 Jan 2011)
Log Message:
Add Remoting test application and endpoints for testing login-after-disconnect channel setting.
Modified Paths:
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/remoting-config.mods.xml
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/services-config.mods.xml
Added Paths:
    blazeds/trunk/qa/apps/qa-manual/remoting/
    blazeds/trunk/qa/apps/qa-manual/remoting/RemotingApp.mxml

I appreciate Adobe teams efforts to reproduce the issue and acknowledged it as a Bug in AIR
But now I am waiting on them to come back with an answer - Is it going to be fixed in future versions? Is there a work around?
Is adobe even considering this as an Issue? What are the next steps after acknowleding the issue?
I hope I am not too aggressive but I also want Adobe to understand the urgency of the situation when it comes to a product release.
I have experimented with couple of work arounds but none seem to work.
If anyone has come across this issue please comment.
Thanks,

[svn:fx-trunk] 9054: Refactoring DataGroup a bit to allow for more robust delegation of renderer updates to owning components .

Similar Messages

Maybe you are looking for