[svn:fx-trunk] 7125: Change default columnGap from 0 to 20 to match Vellum' s default.

Revision: 7125
Author:   [email protected]
Date:     2009-05-20 04:12:27 -0700 (Wed, 20 May 2009)
Log Message:
Change default columnGap from 0 to 20 to match Vellum's default.
QA Notes:
Doc Notes:
Bugs: SDK-18095
Reviewers: Gordon
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18095
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/defaults.css

Similar Messages

[svn:fx-trunk] 10269: Changing default for -enable-runtime-design-layers to true.

Revision: 10269
Author:   [email protected]
Date:     2009-09-15 10:46:10 -0700 (Tue, 15 Sep 2009)
Log Message:
Changing default for -enable-runtime-design-layers to true. The flag may still be used to disable processing of design layer instances if so desired.
QE notes: None
Doc notes: None
Bugs: SDK-23238
Reviewer: Paul
Tests run: Checkin
Is noteworthy for integration: Yes, runtime design layers are now enabled by default.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23238
Modified Paths:
    flex/sdk/trunk/frameworks/tests/basicTests/BasicTests-config.xml
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/CompilerConfiguration.java

APDivs are a thing of the past and is bad practice. You need a working knowledge of CSS to get a modern looking layout and to do justice to your design which looks great btw.
One out-of-the-box solution is to use Bootstrap - http://twitter.github.com/bootstrap/index.html and use the pre-defined classes/ grids to layout your content.

[svn:fx-trunk] 9778: Change default creationPolicy for NavigatorContent to null.

Revision: 9778
Author:   [email protected]
Date:     2009-08-28 17:16:26 -0700 (Fri, 28 Aug 2009)
Log Message:
Change default creationPolicy for NavigatorContent to null. If null, NavigatorContent will check its parent Navigator's creationPolicy. If the parent Navigator's creationPolicy is "all", NavigatorContent will use "all" and create all of its children. Otherwise, NavigatorContent will use "none" as the creationPolicy.
QE Notes: default value for creationPolicy is null
Doc Notes: default value for creationPolicy is null
Bugs: None
Reviewer: Ryan
API Change: No
Is noteworthy for integration: No
tests: checkintests
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/NavigatorContent.as

[svn:osmf:] 14372: PARB changes: Remove metadata from MediaContainer and LayoutTargetSprite constructors.

Revision: 14372
Revision: 14372
Author:   [email protected]
Date:     2010-02-23 15:17:18 -0800 (Tue, 23 Feb 2010)
Log Message:
PARB changes: Remove metadata from MediaContainer and LayoutTargetSprite constructors. Instead, metadata is set on LayoutTargetSprite via a non-public setter used by the framework. Update a bunch of ASDocs, make some enum classes final, remove elementIDs from sample apps (since they rely on metadata, and we want to keep samples focused on the public API).
Modified Paths:
    osmf/trunk/apps/samples/framework/MediaContainerSample/MediaContainerSample.as
    osmf/trunk/apps/samples/framework/NestedMediaContainersSample/NestedMediaContainersSample .as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as
    osmf/trunk/framework/OSMF/org/osmf/containers/IMediaContainer.as
    osmf/trunk/framework/OSMF/org/osmf/containers/MediaContainer.as
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/CompositeDisplayObjectTrait. as
    osmf/trunk/framework/OSMF/org/osmf/layout/HorizontalAlign.as
    osmf/trunk/framework/OSMF/org/osmf/layout/ILayoutTarget.as
    osmf/trunk/framework/OSMF/org/osmf/layout/LayoutMode.as
    osmf/trunk/framework/OSMF/org/osmf/layout/LayoutTargetSprite.as
    osmf/trunk/framework/OSMF/org/osmf/layout/VerticalAlign.as
    osmf/trunk/framework/OSMFTest/org/osmf/containers/TestMediaContainer.as
    osmf/trunk/framework/OSMFTest/org/osmf/layout/TestLayoutRenderer.as
    osmf/trunk/framework/OSMFTest/org/osmf/layout/TestMediaElementLayoutTarget.as

[svn:osmf:] 14235: PARB changes: Remove targetBufferTime from the metrics provider, this value can' t be set in the absence of an understanding of the buffering strategy which is layered on top of NetStreamBufferTrait .

Revision: 14235
Revision: 14235
Author:   [email protected]
Date:     2010-02-17 19:27:33 -0800 (Wed, 17 Feb 2010)
Log Message:
PARB changes: Remove targetBufferTime from the metrics provider, this value can't be set in the absence of an understanding of the buffering strategy which is layered on top of NetStreamBufferTrait. Adjust switching rules to work from the raw buffer data instead of this target. Remove all bufferTime modifications from the MBR code, so that they won't impact any buffering strategies (addresses FM-436).
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-436
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamMetricsBase.as
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamSwitchManager.as
    osmf/trunk/framework/OSMF/org/osmf/net/rtmpstreaming/InsufficientBufferRule.as
    osmf/trunk/framework/OSMF/org/osmf/net/rtmpstreaming/RTMPNetStreamMetrics.as
    osmf/trunk/framework/OSMF/org/osmf/net/rtmpstreaming/SufficientBandwidthRule.as
    osmf/trunk/libs/adobe/NetMocker/org/osmf/netmocker/MockNetStreamMetricsBase.as
    osmf/trunk/libs/adobe/NetMocker/org/osmf/netmocker/MockRTMPNetStreamMetrics.as

Please do not duplicate posts. You have already started a thread on this subject.

[svn:osmf:] 14542: PARB changes: Move mediaElementNotificationFunction from MediaFactoryItem to PluginInfo.

Revision: 14542
Revision: 14542
Author:   [email protected]
Date:     2010-03-02 17:22:20 -0800 (Tue, 02 Mar 2010)
Log Message:
PARB changes: Move mediaElementNotificationFunction from MediaFactoryItem to PluginInfo. Modify MediaFactory (via PluginManager) to invoke the notification function for each MediaElement that the MediaFactory creates, independent of creation order. Update unit tests.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/media/MediaFactory.as
    osmf/trunk/framework/OSMF/org/osmf/media/MediaFactoryItem.as
    osmf/trunk/framework/OSMF/org/osmf/media/PluginInfo.as
    osmf/trunk/framework/OSMF/org/osmf/media/pluginClasses/PluginManager.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/TestMediaFactory.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/TestMediaFactoryItem.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/pluginClasses/CreateOnLoadPluginInfo.as
    osmf/trunk/framework/OSMFTest/org/osmf/media/pluginClasses/TestPluginManager.as

[svn:bz-trunk] 20609: Change the default max object nest level from 1024 to 512.

Revision: 20609
Revision: 20609
Author:   [email protected]
Date:     2011-03-04 10:23:41 -0800 (Fri, 04 Mar 2011)
Log Message:
Change the default max object nest level from 1024 to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Update documentation for the max object nest level setting to reflect the new default.
Add documentation for the new max collection nest level setting.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/trunk/resources/config/services-config.xml

You should be able to get some more precise information from your Xorg logs, but I would bet it is related to the evdev driver. Some of the options in your xorg.conf no longer work with the latest version. For now you should be able to either map your mouse directly to the appropriate /dev/event* entry or change to the standard mouse driver, both of those methods should be in the wiki.
You are supposed to be able to use the evdev driver without the input section of your xorg.conf by using dbus/hal autodetection, but AFAIK at the moment the xorg-server package still isn't compiled with hal support, so you would have to patch and rebuild the package.

[svn:fx-trunk] 7661: Change from charset=iso-8859-1" to charset=utf-8" and save file with utf-8 encoding.

Revision: 7661
Author:   [email protected]
Date:     2009-06-08 17:50:12 -0700 (Mon, 08 Jun 2009)
Log Message:
Change from charset=iso-8859-1" to charset=utf-8" and save file with utf-8 encoding.
QA Notes:
Doc Notes:
Bugs: SDK-21636
Reviewers: Corey
Ticket Links:
    http://bugs.adobe.com/jira/browse/iso-8859
    http://bugs.adobe.com/jira/browse/utf-8
    http://bugs.adobe.com/jira/browse/utf-8
    http://bugs.adobe.com/jira/browse/SDK-21636
Modified Paths:
    flex/sdk/trunk/templates/swfobject/index.template.html

same problem here with wl8.1
have you sold it and if yes, how?
thanks

[svn:fx-trunk] 8530: Change Slider and NumericStepper default value

Revision: 8530
Author:   [email protected]
Date:     2009-07-13 11:17:46 -0700 (Mon, 13 Jul 2009)
Log Message:
Change Slider and NumericStepper default value
http://bugs.adobe.com/jira/browse/SDK-18380 - FxHSlider and FxVSlider have default max of 100, should be 10
Changed the default value for Slider by setting the value to 10 in the constructor. I changed NumericStepper?\226?\128?\153s implementation to match Slider. The problem with NumericStepper?\226?\128?\153s previous implementation was that it wasn?\226?\128?\153t calling Range?\226?\128?\153s maximum setter. Thus there was some important logic in Range.commitProperties that wasn?\226?\128?\153t called.
QE Notes: Update tests with new default
Doc Notes: Update docs with new default
Bugs: SDK-18380
Reviewer: Hans
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18380
    http://bugs.adobe.com/jira/browse/SDK-18380
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/NumericStepper.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

[svn:bz-trunk] 20471: Changed visibility of start/ stopEndpoints methods from private to protected, so subclasses can override them.

Revision: 20471
Revision: 20471
Author:   [email protected]
Date:     2011-02-25 06:54:09 -0800 (Fri, 25 Feb 2011)
Log Message:
Changed visibility of start/stopEndpoints methods from private to protected, so subclasses can override them.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn:fx-trunk] 14377: Merging revision 14376 from 4.x to trunk

Revision: 14377
Revision: 14377
Author:   [email protected]
Date:     2010-02-23 16:35:29 -0800 (Tue, 23 Feb 2010)
Log Message:
Merging revision 14376 from 4.x to trunk
Mirroring bug fixes
http://bugs.adobe.com/jira/browse/SDK-25427 - HTML AIR component should not be mirrored even when layoutDirection=rtl
Set layoutDirection=ltr in defaults.css
http://bugs.adobe.com/jira/browse/SDK-25626 - The Spark VSlider dataTip is not positioned correctly when layoutDirection=rtl. It obscures the thumb.
Translate the position from mirrored local coordinate to global coordinates.
http://bugs.adobe.com/jira/browse/SDK-25584 - MX MenuBar displays menus offscreen when layoutDirection is rtl
Added logic to keep the menus from going off the left side of the screen.
QE notes: none
Doc notes: none
Bugs: SDK-25427, SDK-25626, SDK-25584
Reviewer: Hans
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-25427
    http://bugs.adobe.com/jira/browse/SDK-25626
    http://bugs.adobe.com/jira/browse/SDK-25584
    http://bugs.adobe.com/jira/browse/SDK-25427
    http://bugs.adobe.com/jira/browse/SDK-25626
    http://bugs.adobe.com/jira/browse/SDK-25584
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/defaults.css
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/MenuBar.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VSlider.as
Property Changed:
    flex/sdk/trunk/

[svn:fx-trunk] 8437: Change the TextInput border stroke to a solid opaque color so it matches the TextArea border when baseColor is applied .

Revision: 8437
Author:   [email protected]
Date:     2009-07-07 16:52:58 -0700 (Tue, 07 Jul 2009)
Log Message:
Change the TextInput border stroke to a solid opaque color so it matches the TextArea border when baseColor is applied.
Bugs: SDK-18511, SDK-22097
Doc notes: none
QE notes: none
Reviewer: XD
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18511
    http://bugs.adobe.com/jira/browse/SDK-22097
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/NumericStepperTextInputSki n.mxml
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/TextInputSkin.mxml

That's one of the problems with liquid (%) based layouts. In your default.css file, replace the top 2o selector rules with the following:
body {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 12px;
    color: #333;
    margin:0;
    padding:0;
    background: url(images/main-right.png) repeat-y;
.thrColLiqHdr #container {
    width: 95%;
   min-width: 870px; /**keep page from collapsing**/
    margin:0 auto;
    background: url(/images/halftone1.png);
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com

[svn:fx-trunk] 10459: Change to ensure ScriptNodes are no longer part of the node tree after interface compilation stage in order to avoid the extra code that was necessary to avoid tripping over them during type checking , etc.

Revision: 10459
Author:   [email protected]
Date:     2009-09-21 08:42:44 -0700 (Mon, 21 Sep 2009)
Log Message:
Change to ensure ScriptNodes are no longer part of the node tree after interface compilation stage in order to avoid the extra code that was necessary to avoid tripping over them during type checking, etc.
Improving revision 10199 a bit, to allow for single line comments.
QE notes: None
Doc notes: None
Bugs: SDK-22027
Reviewer: Paul
Tests run: Checking, Compiler cyclones
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22027
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java

In general theory, one now has the Edit button for their posts, until someone/anyone Replies to it. I've had Edit available for weeks, as opposed to the old forum's ~ 30 mins.
That, however, is in theory. I've posted, and immediately seen something that needed editing, only to find NO Replies, yet the Edit button is no longer available, only seconds later. Still, in that same thread, I'd have the Edit button from older posts, to which there had also been no Replies even after several days/weeks. Found one that had to be over a month old, and Edit was still there.
Do not know the why/how of this behavior. At first, I thought that maybe there WAS a Reply, that "ate" my Edit button, but had not Refreshed on my screen. Refresh still showed no Replies, just no Edit either. In those cases, I just Reply and mention the [Edit].
Also, it seems that the buttons get very scrambled at times, and Refresh does not always clear that up. I end up clicking where I "think" the right button should be and hope for the best. Seems that when the buttons do bunch up they can appear at random around the page, often three atop one another, and maybe one way the heck out in left-field.
While I'm on a role, it would be nice to be able to switch between Flattened and Threaded Views on the fly. Each has a use, and having to go to Options and then come back down to the thread is a very slow process. Jive is probably incapable of this, but I can dream.
Hunt

[svn:bz-trunk] 20765: change photo to line art

Revision: 20765
Revision: 20765
Author:   [email protected]
Date:     2011-03-10 10:20:42 -0800 (Thu, 10 Mar 2011)
Log Message:
change photo to line art
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/photo/person0.jpg

If you use Threshold, you can add some gaussian blur to the image to make the edges smoother. You can also add a brightness/contrast adjustment layer between the blurred image and the threshold layer to fine tune the edges.
If you have Windows, you might want to look at Medhi's Fine Threshold filter (freeware) found here:
http://www.mehdiplugins.com/english/finethreshold.htm
Edit: You could also use Find Edges on the image first; desaturate it; then use a threshold adjustment layer. Go back to the Find Edges layer and add gaussian blur to taste. To further fine tune, slip a brightness/contrast layer between the blurred image and the threshold to control line thickness/detail. (FWIW, I would make a copy of the Find Edges layer and blur the duplicate so if you change your mind you don't have to start the project from scratch.)

[svn:fx-trunk] 13741: Changes made by sbannur.

Revision: 13741
Revision: 13741
Author:   [email protected]
Date:     2010-01-24 20:51:01 -0800 (Sun, 24 Jan 2010)
Log Message:
Changes made by sbannur. Removed patent related comments from the files.
Reviewed By: Sameer Bhatt
Modified Paths:
    flex/sdk/trunk/frameworks/projects/datavisualization/src/mx/charts/chartClasses/Cartesian CanvasValue.as
    flex/sdk/trunk/frameworks/projects/datavisualization/src/mx/charts/chartClasses/Cartesian DataCanvas.as
    flex/sdk/trunk/frameworks/projects/datavisualization/src/mx/charts/chartClasses/IDataCanv as.as
    flex/sdk/trunk/frameworks/projects/datavisualization/src/mx/charts/chartClasses/PolarData Canvas.as

[svn:fx-trunk] 7125: Change default columnGap from 0 to 20 to match Vellum' s default.

Similar Messages

Maybe you are looking for