[svn:fx-trunk] 11027: Changes to enable using multiple style managers.

Revision: 11027
Author:   [email protected]
Date:     2009-10-20 08:50:09 -0700 (Tue, 20 Oct 2009)
Log Message:
Changes to enable using multiple style managers.
Multiple style managers are not the default yet. Can be enabled by compiling with -create-style-manager.
QE notes: None.
Doc notes: None.
Bugs:
Reviewer: Alex, Paul
Tests run: checkintests, all mustella
Is noteworthy for integration: Yes.
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/FormItem.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/DateField.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/dataGridClasses/DataGridColu mn.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/dataGridClasses/DataGridItem Renderer.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/Application.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/events/FlexChangeEvent.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/CursorManagerImpl.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/DragManagerImpl.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/dragClasses/DragProxy.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/skins/halo/BusyCursor.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/CSSStyleDeclaration.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleManagerImpl.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleProtoChain.as
    flex/sdk/trunk/frameworks/projects/halo/src/mx/skins/halo/BusyCursor.as
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension. java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/CompilerConfiguration.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleDef.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleDef.vm
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleModule.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StylesContainer.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceGenerator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/MxmlConfiguration.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/gen/ClassDefLib.vm
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java
    flex/sdk/trunk/tools/dependencychecker/flex/tools/dependencychecker/FrameworkSwcDependenc yRules.java
Added Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/CSSMergedStyleDeclaration.as

add type: 'random', to the script below and see what, IF anything happens. I've added after fit: and height: (see below)
<script type="text/javascript">
// BeginOAWidget_Instance_2559022: #slideshow         slideshowAddCaption=false;
$(document).ready(function() {
$('#slideshow').cycle({
  after:   slideshowOnCycleAfter, //the function that is triggered after each transition
  autostop:   false,     // true to end slideshow after X transitions (where X == slide count)
  fx:    'fade,',// name of transition effect
  pause:   true,     // true to enable pause on hover
  randomizeEffects: false,  // valid when multiple effects are used; true to make the effect sequence random
  speed:   2000,  // speed of the transition (any valid fx speed value)
  sync:   false,     // true if in/out transitions should occur simultaneously
  timeout:  5000,  // milliseconds between slide transitions (0 to disable auto advance)
  fit:   false,
type: 'random',
  height:     '600px',
  width:         '0px'   // container width (if the 'fit' option is true, the slides will be set to this width as well)
function slideshowOnCycleAfter() {
if (slideshowAddCaption==true){
   $('#slideshow-caption').html(this.title);
// EndOAWidget_Instance_2559022
  </script>

Similar Messages

  • [svn:bz-trunk] 14749: Change tests to use fully qualified hostname of flexteam.corp.adobe. com as flexteam was not resolving on all regression boxes.

    Revision: 14749
    Revision: 14749
    Author:   [email protected]
    Date:     2010-03-14 05:43:14 -0700 (Sun, 14 Mar 2010)
    Log Message:
    Change tests to use fully qualified hostname of flexteam.corp.adobe.com as flexteam was not resolving on all regression boxes.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/202863/bug202863Doc Lit.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/202863/bug202863Rpc Enc.mxml

  • [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] 10216: Change Label verticalAlign to use "top" if there is too much text.

    Revision: 10216
    Author:   [email protected]
    Date:     2009-09-13 08:20:06 -0700 (Sun, 13 Sep 2009)
    Log Message:
    Change Label verticalAlign to use "top" if there is too much text.  RichText already works this way.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-20589
    Reviewer: Gordon
    API Change: No
    Is noteworthy for integration: No
    tests: checkintests mustella/GraphicsTags
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-20589
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Label.as

    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] 10144: Change Label verticalAlign to use "top" if there is too much text.

    Revision: 10144
    Author:   [email protected]
    Date:     2009-09-10 18:46:11 -0700 (Thu, 10 Sep 2009)
    Log Message:
    Change Label verticalAlign to use "top" if there is too much text.  RichText already works this way.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-20589
    Reviewer: Gordon
    API Change: No
    Is noteworthy for integration: No
    tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-20589
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Label.as

    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:bz-trunk] 14804: Changed securityConstraint samples to use a channel that has login-after-disconnect =true.

    Revision: 14804
    Revision: 14804
    Author:   [email protected]
    Date:     2010-03-17 01:45:39 -0700 (Wed, 17 Mar 2010)
    Log Message:
    Changed securityConstraint samples to use a channel that has login-after-disconnect=true. Login after disconnect does not seem to work right now but at least there's a sample for it now for when it works.
    Modified Paths:
        blazeds/trunk/apps/team/WEB-INF/flex/remoting-config.xml
        blazeds/trunk/apps/team/WEB-INF/flex/services-config.xml
        blazeds/trunk/apps/team/features/security-constraints/securityConstraint_Custom.mxml

    Have you solved your problem? I think I have the same issue.

  • [svn:fx-trunk] 5061: Changed the skin to use hostComponent rather than fxComponent so that binding happens on a strongly typed instance .

    Revision: 5061
    Author: [email protected]
    Date: 2009-02-24 14:18:51 -0800 (Tue, 24 Feb 2009)
    Log Message:
    Changed the skin to use hostComponent rather than fxComponent so that binding happens on a strongly typed instance. By doing this we save the overhead of calling describeType() and doing RTTI. Also updated the backgroundColor to be cast to uint until the getter/setter is updated to return that (currently it is object)
    QE: No
    Doc: No
    Checkintests: Pass
    Reviewer: Ryan F & Glenn
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/skins/spark/FxApplicationSkin.mxml

    Revision: 5061
    Author: [email protected]
    Date: 2009-02-24 14:18:51 -0800 (Tue, 24 Feb 2009)
    Log Message:
    Changed the skin to use hostComponent rather than fxComponent so that binding happens on a strongly typed instance. By doing this we save the overhead of calling describeType() and doing RTTI. Also updated the backgroundColor to be cast to uint until the getter/setter is updated to return that (currently it is object)
    QE: No
    Doc: No
    Checkintests: Pass
    Reviewer: Ryan F & Glenn
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/skins/spark/FxApplicationSkin.mxml

  • [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:bz-trunk] 17010: Bug: Watson #2652870 - use a property file to drive the custom configuration tokens as opposed to setting it in the command line

    Revision: 17010
    Revision: 17010
    Author:   [email protected]
    Date:     2010-07-22 02:52:41 -0700 (Thu, 22 Jul 2010)
    Log Message:
    Bug: Watson #2652870 - use a property file to drive the custom configuration tokens as opposed to setting it in the command line
    QA: Yes
    Doc: Yes - in custom tokens section, talk about the new token.file option
    Checkintests: Pass
    Details: Changed TokenReplacer to look for a token.file JVM option. If it's specified (eg. -Dtoken.file=/User/matamel/Desktop/token.properties), then TokenReplacer looks for a properties file where token name and values are specified. This allows someone to specify a file for custom tokens. Custom tokens can still be specified as straight JVM option and in case where a token is defined both as a JVM option and in a token properties file, JVM option takes precedence.
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/config/TokenReplacer.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] 10358: Change Application. application so it can return spark Applications and spark WindowedApplications .

    Revision: 10358
    Author:   [email protected]
    Date:     2009-09-17 14:18:43 -0700 (Thu, 17 Sep 2009)
    Log Message:
    Change Application.application so it can return spark Applications and spark WindowedApplications.
    Application.application is still deprecated but this change makes the transition to using Spark Applications easier.
    QE notes: None.
    Doc notes: None.
    Bugs: SDK-21898
    Reviewer: Gordon
    Tests run: checkintests, Application
    Is noteworthy for integration: no.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21898
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/Application.as

    Try setting the stepSize on the slider to 4. That should reduce the jiggle effect.
    Not sure if it helps, but the following way of placing the graphic in the skin means you don't need to use those binding tags. The group within the graphic will automatically scale. (I use 48 as an arbitrary size for the group. But it will always display relative to the size of the button. You may need to adjust the 30 and 8 values to match your original.)
    <s:Graphic left="1" right="1" top="1" bottom="1"  >
    <s:Group width="48" height="48" >
    <s:Rect  horizontalCenter="0" verticalCenter="0" height="30" width="8">
    <s:stroke>
    <s:SolidColorStroke color="0x000000"/>
    </s:stroke>
    <s:fill>
    <s:SolidColor color="0xff0000"/>
    </s:fill>
    </s:Rect>
    <s:Rect  horizontalCenter="0" verticalCenter="0" height="8" width="30">
    <s:stroke>
    <s:SolidColorStroke color="0x000000"/>
    </s:stroke>
    <s:fill>
    <s:SolidColor color="0xff0000"/>
    </s:fill>
    </s:Rect>
    </s:Group>
    </s:Graphic>

  • [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] 9349: * Added support for using getStyle() in Mxml data binding expressions.

    Revision: 9349
    Author:   [email protected]
    Date:     2009-08-17 11:32:37 -0700 (Mon, 17 Aug 2009)
    Log Message:
    Added support for using getStyle() in Mxml data binding expressions.
      In addition to the existing "function return watcher" data binding
      functionality, we register to listen for style related change events
      when we see a function marked with [Bindable(style="true")].
      UIComponent's and TextGraphicElement's styleChanged() will now
      dispatch events for "getStyle()" FunctionReturnWatchers to handle.
      When null or "styleName" is passed into styleChanged(), we dispatch
      an "allStylesChanged" event.
    QE notes: mxunit test to follow
    Doc notes:
    Bugs: SDK-20394
    Reviewer: Glenn, Pete F, Peter D
    Tests run: checkintests, mxunit databinding
    Is noteworthy for integration: only if you want to start using it.
    Code-level description of changes:
      modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension.java
        Modified generateWatcher() to do the AST equivalent of the
        WatcherSetupUtil.vm change.
      modules/compiler/src/java/flex2/compiler/as3/binding/FunctionReturnWatcher.java
        Removed unused isNew variable and added isStyleWatcher variable.
        Modified shouldWriteSelf() to return true if isStyleWatcher is true.
      modules/compiler/src/java/flex2/compiler/as3/binding/WatcherSetupUtil.vm
        Modified writeFunctionReturnWatcher macro to add a true arg to the
        FunctionReturnWatcher constructor call when isStyleWatcher() is
        true.
      modules/compiler/src/java/flex2/compiler/as3/binding/BindableFirstPassEvaluator.java
        Modified evaluate(Context, MetaDataNode) to skip reporting an
        error for no events when style is true.
      modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingFirstPassEvaluator.java
        Replaced insideCallExpression boolean with callExpressionStack
        Stack.  The "!insideCallExpression" checks were replaced with
        callExpressionStack.isEmpty().
        Modified addBindables() to handle [Bindable(style="true")].
        Made argumentListStack and resetSet more strongly typed.
      frameworks/projects/framework/src/mx/core/UIComponent.as
        Modified styleChanged() to dispatch a "Changed" and "allStylesChanged" from the previous
        parent and add listeners to the new parent when isStyle is true.
        Modified eventHandler to notifyListeners() when isStyle is true.
      frameworks/projects/spark/src/spark/primitives/supportClasses/TextGraphicElement.as
        Similar changes to UIComponent.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-20394
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/binding/FunctionReturnWatcher.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/TextGraphicE lement.as
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableFirstPassEval uator.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension. java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingFirstPassE valuator.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/FunctionReturnWatcher .java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/WatcherSetupUtil.vm

  • [svn:fx-trunk] 8399: Update WindowedSystemManager to use ChildManager.

    Revision: 8399
    Author:   [email protected]
    Date:     2009-07-06 14:15:40 -0700 (Mon, 06 Jul 2009)
    Log Message:
    Update WindowedSystemManager to use ChildManager.
    WindowedSystemManager:
    Add new childManager property. Implement rawChildren_* methods using the new childManager.
    ChildManager:
    Change systemManager from type SystemManager to ISystemManager since WindowedSystemManager is not of type SystemManager. Use the array access operator to access the methods/properties that are in SystemManager but not in ISystemManager.
    QE Notes: none.
    Doc Notes: none.
    Bugs: SDK-21673
    Reviewer: Alex
    tests: checkintests, components/Alert
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21673
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/managers/WindowedSystemManager.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/systemClasses/ChildManager.a s

    Gordon, it looks like its been a while since you made this post.  Not sure how valid it is now...   I am particularly interested in the LigatureLevel.NONE value.  It seems that it is no longer supported.
    How do I turn of ligatures in the font rendering?
    My flex project involves trying to match the font rendering of Apache's Batik rendering of SVG and ligatures have been turned off in that codebase.  Is there any way (even roundabout) to turn ligatures off in flash?
    Thanks,
    Om

  • [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

Maybe you are looking for