Better documentation of AE API?

hi,
What docs are you guys using when scripting for AE?
I'm using the CS6 pdf here:
http://download.macromedia.com/pub/developer/aftereffects/scripting/After-Effects-CS6-Scri pting-Guide.pdf
And I'm looking at the data browser inside ESTK.
But isn't there a more efficient source to look up what methods and properties certain classes have?
Something like this (outdated I think and no AE, just an example):
API Documentation
Suppose I want to know what I can do with an ItemCollection. Then searching for 'ItemCollection' in the pdf gives me way too many results
to work with in a fast way. Looking up ItemCollection in the data browser doesn't gve me any info either, but
maybe I'm not looking at the right ItemCollection in there? This is just an example of course,
which goes for all Classes.
Thanks,
Jeff.

Hi Jeff,
i'm using the two tools you are mentionning and most of the time it is fine.
Two things:
(1) When browsing ESTK data, you should look at an instance of ItemCollection, not the constructor function itself.
For instance:
     var items = app.project.items;
     put a breakpoint there and look in the browser the properties/methods of the 'items' variable.
(2) And the pdf is well organized, it has bookmarks/table of contents, so you can get to the ItemCollection paragraph pretty fast, without using the search function.
I use the pdf for generic things (for instance, find properties/methods of objects) and the data browser for precise info about a specific object (for instance: get the property's actual value, is this group elided?, is this layer "name set"? etc): not the same usage.
Xavier.

Similar Messages

  • WCF and WP8.1: Can I only use WCF REST services? Then better WCF or Web API?

    I am trying to create a simple application to test WCF with WP8.1. I have created my service. Later I create my WP8.1 silver light application and I try to add a reference to my service Project. The problem is that I get an error that says that I have only
    add reference to projects that are Windows pone 8.
    I have read some solutions, but all of them are creating a WCF REST service, so my doubt if the WP8.1 applications only can connect to WCF REST services.
    In this case, if this is true, it not would be better to use Web API instead of WCF?
    Thanks so much.

    You can use any type of rest service with windows phone 8.1 because rest services can be called via the httpclient class.  You dont need a service reference.  Personally I prefer the web api but there is no reason you can not use a wcf rest service.

  • Better documentation of how LR handles metadata

    I would like the on-line help to accurately describe how LR handles metadata, especially writing them in files like DNG and TIFF, the usage of sidecar files (.XMP), and how all of that interacts with Adobe Photoshop CS and its Browser, and Photoshop CS2 and CS3 and Bridge.

    The short answer is that the IPTC, EXIF and other built-in core metadata is written to DNG and TIFF and JPEG and travels with the file and can be viewed in any application that provides xmp functionality to view it - like a File Info... menu item. Metadata about changes made to the file and how it looks is not carried as embedded metadata when the image is exported. There is no functionality in CS2 or CS3 to view a sort of history file with images alterations.

  • Specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML

    After reading a bit about JavaFX Script (which is actually remarkebly close to ActionScript 3) as a developer I thought the way one can specify the GUI declaratively in JavaFX Script via JSON-like notation for the components is pretty cool. It would be nice to have something like that in Flex/ActionScript too. The advantages I see over MXML are:
    1) a more compact notation than XML which is nice from a developers view point who actually writes this kind of code. Of course the idea would be that designers still design the GUI with graphical tools that generate this code but if you have to dive in and edit the code it's nice not to have to deal with verbose XML and I think even designers can easily understand JSON-like code; don't just assume that designers love XML because HTML was based on SGML! I'm not so sure if today many designers really still know raw HTML that well (like in 1997, the early days...). Server side developers probably know it better because they have to adapt it to jsp or asp or whatever framework.
    2) The fact that it's all ActionScript gives a seamless integration between just composing the components to form the GUI and adding scripts to add additionial behavior instead of mixing XML with actionscript code => no more need for those nasty CDATA blocks! It would also be easy for development tools like Flexbuilder to give a seamsless experience with code completion and zooming in on the code because it's all Actionscript! There's also no need for a separate expression language to tie the MXML to the underlying Actionscript. It would it also make easier to create custom components (not just simple composition components which is really easy in MXML) because you don't have to implement separate XML tags.
    here's a short JavaFX Script example:
    Frame {
    content: GroupPanel {
    var myRow = Row { alignment: BASELINE }
    var label_col = Column { alignment: TRAILING }
    var field_col = Column { alignment: LEADING }
    rows: [myRow]
    columns: [label_col, field_col]
    content:
    [SimpleLabel {
    row: myRow
    column: label_col
    text: "Type your text here:"
    TextField {
    row: myRow
    column: field_col
    columns: 50
    visible: true
    Note that this shouldn't be confused with programmatically specifying the GUI in Actionscript (which is possible today as an alternative to MXML). What I propose is at a (slightly) higher level: you don't give a detailed sequence of methods/functions to call to construct the GUI (i.e. HOW to do it) but just specify WHAT you want.
    Hopefully some Adobe Flex will see this and think about it. Although I think MXML is not too bad and I can live with it if I have to ;)

    I like that idea Sean. A standard and well-supported way to separate MXML and code would be good. I'd love to have builder support a MVC style triad for MXML files, with the
    model.as being simply an all-public-all-bindable class full of VOs and view-specific information, any view-manipulation and view<->app communications in the
    controller.as, and nothing but bindings and layour in the MXML. There's (almost) nothing stopping you doing this by hand at the moment, but it's a pain, and developers wouldn't stick to it for very long, when they need to create and maintain 3 separate files for that simple "error dialog" without a hand from Builder.
    Then again, I'd rather Adobe spent the time that would take on opening and better-documenting builder's APIs, so we can write our own plugins easily, but that's my greedy side- A standard builder-supported MVC pattern for custom MXML components would be aweseome for people that aren't me :)
    -Josh
    As for JavaFX, I don't care for it.
    On Tue, Sep 30, 2008 at 7:56 AM, Sean Christmann
    <
    [email protected]> wrote:
    A new message was posted by Sean Christmann in
    Developers --
      specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML
    Jason you bring up a good point on a concept that I think Adobe should
    poach from a different framework, Silverlight. In Silverlight the
    code-behind pattern is automatic and very nice to work with. Every
    interface can be composed of both a layout file and a script file, and
    they get composited into the SAME class at compile time. So you can
    have both a FileDialog.mxml and FileDialog.as file that know about each
    other automatically, without the need to subclass one from the other.
    Sean
    Jason Stafford wrote:
    A new message was posted by Jason Stafford in
    Developers --
      specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML
    Personally, I like the separation between the MXML and ActionScript.
    We're working on a large project, and so we have all the ActionScript
    separate from the MXML files.  For example we'll have something like
    filedialoglayout.mxml, and then
    filedialog.as that is a subclass of
    filedialoglayout.  All event handlers and the like are setup in the
    filedialog.as file - the mxml file doesn't know about any function names.
    Advantages:
    MXML files become layout only - and are more easily shared and worked on
    with non-technical people
    ActionScript is all in *.as files: no CDATA blocks and no FlexBuilder
    quirks where editing ActionScript inside a CDATA block doesn't work
    quite like in a real AS file.
    For simple experiments, and for learning, it's obviously nice to have
    everything in one mxml file, but in a big project like ours, the
    separation helps keep things clearer and more maintainable.
    Why use the mxml at all?  The MXML files are nice to edit with the
    visual editor in Flex Builder, and it's much easier to apply styles and
    embed assets in MXML than it is in pure ActionScript.
    I think two ways to talk about the same thing (XML and ActionScript) is
    already almost one too many - adding a third (JSON) would really be too
    much.
    Just my thoughts.
    -Jason Stafford
    Sean Christmann wrote:
    A new message was posted by Sean Christmann in
    Developers --
    specify the GUI declaratively in ActionScript like in JavaFX Script
    instead of MXML
    This reminds me of a certain workflow pattern that has emerged for us
    which might help provide some insight on this topic. I'm working on a
    project with a couple other developers which connects to a webservice
    for supplying clientside data. This data is available in both json
    notation and xml notation. The thing is, while the developers have
    overwhelmingly agreed that we should be consuming the json version
    since it can be parsed faster and provide more meaningful context for
    objects (ie strings vs ints vs arrays etc...), all these same
    developers rely exclusively on the xml notation when asking questions
    about the data or passing structures around to discuss.
    I see the same thing when looking at JavaFX and MXML. JavaFX might
    allow for more accurate structures and might be able to be compiled
    faster, but MXML is better for being self documenting even if it
    requires more verbosity.
    Sean
    Matt Chotin wrote:
    A new message was posted by Matt Chotin in
    Developers --
      specify the GUI declaratively in ActionScript like in JavaFX Script
    instead of MXML
    I'd be curious what other people think.  I see MXML as a distinct
    advantage over doing the pseudo-script stuff.  I really don't like
    the JavaFX system actually.
    Matt
    On 9/28/08 10:33 AM, "neo7471"
    <[email protected]> wrote:
    A new discussion was started by neo7471 in
    Developers --
      specify the GUI declaratively in ActionScript like in JavaFX Script
    instead of MXML
    After reading a bit about JavaFX Script (which is actually remarkebly
    close to ActionScript 3) as a developer I thought the way one can
    specify the GUI declaratively in JavaFX Script via JSON-like notation
    for the components is pretty cool. It would be nice to have something
    like that in Flex/ActionScript too. The advantages I see over MXML are:
    1) a more compact notation than XML which is nice from a developers
    view point who actually writes this kind of code. Of course the idea
    would be that designers still design the GUI with graphical tools
    that generate this code but if you have to dive in and edit the code
    it's nice not to have to deal with verbose XML and I think even
    designers can easily understand JSON-like code; don't just assume
    that designers love XML because HTML was based on SGML! I'm not so
    sure if today many designers really still know raw HTML that well
    (like in the 1997, the early days...). Server side developers
    probably know it better because they! have to adapt it to jsp or asp
    or whatever framework.
    2) The fact that it's all ActionScript gives a seamless integration
    between just composing the components to form the GUI and adding
    scripts to add additionial behavior instead of mixing XML with
    actionscript code => no more need for those naster CDATA blocks! It
    would also be easy for development tools like Flexbuilder to give a
    seamsless experience with code completion and zooming in on the code
    because it's all Actionscript! There's also no need for a separate
    expression language to tie the MXML to the underlying Actionscript.
    It would it also make easier to create custom components (not just
    simple composition components which is really easy in MXML) because
    you don't have to implement separate XML tags.
    here's a short JavaFX Script example:
    Frame {
        content: GroupPanel {
        var myRow = Row { alignment: BASELINE }
        var label_col = Column { alignment: TRAILING }
        var field_col = Column { alignment: LEADING  }
        rows: [myRow]
        columns: [label_col, field_col]
        content:
        [SimpleLabel {
        row: myRow
        column: label_col
        text: "Type your text here:"
        TextField {
        row: myRow
        column: field_col
        columns: 50
        visible: true
    Note that this shouldn't be confused with programmatically specifying
    the GUI in Actionscript (which is possible today as an alternative to
    MXML). What I propose is at a (slightly) higher level: you don't give
    a detailed sequence of methods/functions to call to construct the GUI
    (i.e. HOW to do it) but just specify WHAT you want.
    Hopefully some Adobe Flex will see this and think about it. Although
    I think MXML is not too bad and I can live with it if I have to ;)
    View/reply at specify the GUI declaratively in ActionScript like in
    JavaFX Script instead of MXML
    <
    http://www.adobeforums.com/webx?13@@.59b69b42>
    Replies by email are OK.
    Use the unsubscribe
    <
    http://www.adobeforums.com/webx?280@@.59b69b42!folder=.3c060fa3>
    form to cancel your email subscription.
    View/reply at
    <
    http://www.adobeforums.com/webx?13@@.59b69b42/0>
    Replies by email are OK.
    Use the unsubscribe form at
    <
    http://www.adobeforums.com/webx?280@@.59b69b42!folder=.3c060fa3> to
    cancel your email subscription.
    <div><div></div><div>
    Jason Stafford
    Principal Developer
    Inspiration Software, Inc.
    The leader in visual thinking & learning
    Now available - Kidspiration(r) 3, the visual way to explore and understand words, numbers and concepts.
    Learn more at
    www.inspiration.com/kidspiration.
    503-297-3004 Extension 119
    503-297-4676 (Fax)
    9400 SW Beaverton-Hillsdale Highway
    Suite 300
    Beaverton, OR 97005-3300
    View/reply at
    <
    http://www.adobeforums.com/webx?13@@.59b69b42/2>
    Replies by email are OK.
    Use the unsubscribe form at
    <
    http://www.adobeforums.com/webx?280@@.59b69b42!folder=.3c060fa3></div>
    </div> to cancel your email subscription.
    Sean Christmann | Experience Architect | EffectiveUI | 720.937.2696
    View/reply at
    specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML
    Replies by email are OK.
    Use the
    unsubscribe form to cancel your email subscription.
    "Therefore, send not to know For whom the bell tolls. It tolls for thee."
    http://flex.joshmcdonald.info/
    :: Josh 'G-Funk' McDonald
    :: 0437 221 380 ::
    [email protected]

  • Search API Documentation Insufficient

    I'm trying to retrieve information about Movies & TV Shows using the search api.  I can get basic information using:
    https://itunes.apple.com/search?media=tvShow&entity=tvEpisode&term=breaking+bad& country
    But I can't get additional information like the cast, producer, ...  I've tried using the attribute by appending
    &attribute=actorTerm (plus many of the others that say that they are supported for all media types)
    but I get an error.  Is there any better documentation of examples that might help?

    That and this: http://www.apple.com/itunesaffiliates/API/AffiliatesSearch2.1.pdf
    ...are it.
    More than that, Apple intends to keep out of public view, apparently.

  • Cannot view Crystal Reports 2008 API documentation

    I've purchased Crystal Reports 2008 From the On-line Store.
    I found the documentation on the API in the SAP Help Portal
    I downloaded the Crystal Reports 2008 .Net API manual.
    I get this great outline but there is no content with the statement "Navigation to the webpafe was canceled"
    Were can I get a usable manual?

    Hi Edward,
    Try to download product guide  from the following link:
    [https://websmp105.sap-ag.de/bosap-support].
    Have a look to this thread:
    [Read Before Posting - Where to find Crystal Reports .NET SDK resources;
    you will get all the links of SDK Libraries,Business objects notes, Sample code.
    If you have any issue with SDK post your question in
    NET Development - Crystal Reports Forum
    [SAP Crystal Reports, version for Visual Studio;
    Hope this helps!!
    Regards,
    Shweta

  • Crystal Reports XI API documentation

    Hi.  I'm using the activex object for Crystal Reports Viewer (version XI).  Can someone please point me to the unabridged documentation for the API (full class and function syntax/descriptions).  Thanks.

    You can get developer documenation on the [Dev Library|http://www.sdn.sap.com/irj/boc/sdklibrary;jsessionid=(J2EE3417200)ID1988526350DB01651156239711280771End]
    Here is the [XI Documentation|http://devlibrary.businessobjects.com/BusinessObjectsXI/en/devlib.htm]
    Jason

  • Documentation for Service Contract API

    Hi All,
    Sub: Any Documentation For The Public API's OKS_CONTRACTS_PUB,
    OKC_CONTRACTS_PUB.
    Firstly i would like to say Thank You for spending your valuable time for this Query.
    Introduction:
    Currently i am working in Oracle Service Contracts module, which is Oracle
    Application's CRM module.
    Specifications:
    oracle application version: 11.5.10.2
    Data Base version: oracle 9.2.0.6
    Problem:
    We are trying to integrate the Service Contracts through following Public API's
    with web.
    API's are:
    OKS_CONTRACTS_PUB,
    OKC_CONTRACTS_PUB.
    I search so much to the documentation for these API's, but i did not get any thing.
    I search in Oracle Meta Link, Google.
    Could you help If any Documentation If you find (or) you have ?
    Please forward to:
    [email protected]
    [email protected]
    Any help from your side will appreciate.
    Thank you.
    Regards,
    Sai Krishna @cavaya

    Look at this link you will be able to get some information about the Api
    http://mywebpages.comcast.net/muzaffarl/whitepaper/02d.pdf
    If you find any document regarding this Api other than this kindly let me know.

  • Customization, API documentation

    Where does the source code reside for portal components such as forms, reports, charts etc.? Is that possible that I can add my own customized codes in order to fit my needs (such as client side data validation using javaScript, adding a few text line etc)?
    Where does the page source code reside? How can I access it and do some customization?
    Is there any documentation on portal API?
    Thanks for your help.
    null

    You can get documentation on the portal APIs from the Portal Development Kit (PDK). Do a search on technet for 'pdk' and it will come up in the results. There is documentation on the APIs for PL/SQL and Java.

  • Documentation/API details for Policy automation

    Where can we find more details about Oracle Policy automation software documentation, download and API's? Please advise.
    I reviewed the URL below but it primarily had product data sheets and some whitepapers.
    http://www.oracle.com/industries/government/policy-automation/index.html
    Thanks,
    Sudip

    This page has lots of very useful information: http://www.oracle.com/technology/products/applications/policy-automation/index.html
    Cheers,
    Jasmine

  • RMS R10 API Documentation

    Hi,
    I'm experimenting problems with the library MVIEW45 used to build Dynamic MultiView with RMS.
    Example:
    P_MULTIVIEW.INITIALIZE('FM_PROMSUMM_9', 'B_action.PB_ok', 13, 700, 'N', 'N');
    P_MULTIVIEW_DRAW.SET_ENABLE;
    P_MULTIVIEW_DRAW.REDRAW(1, TRUE);
    Do you know where we can find documentation on these API?
    Righ now we have to look at the code of the program to figure out how it works.
    Thanks
    Pierre

    There is no official public documentation on Forms design and Forms architecture - you will have to figure this out for yourself. And of course the integration partners may have done this already and may be able to help

  • EDN Java API documentation

    Hello everybody,
    is there any documentation on the EDN Java API available? I know there is a section in the Soa Suite Developers Guide, and there are a couple of blog postings, but I can't find any documentation of the API.
    Best regards, Chris

    There is sample Java code that shows most of the functions. Take a look in the Samples\japi directory where you installed EDS.Regards,Jade-----------------------------Jade ColeSenior BI ConsultantClarity [email protected]

  • Transactions API in AR

    We are developing a custom application that will integrate with Oracle Receivables in Oracle Applications 11.5.2. We will need to send transactions (i.e. invoices, payments, etc.) to AR. We are considering using either Auto Invoice or Transaction API. The documentation for Transaction API for Applications 11 states it is a 'beta' version. Has Transaction API gone to a full production release? Also, is there any more documentation available on Transaction API other than the Oracle Receivables User Guide?
    null

    Hi Jaya,
    U ought to use Autoinvoice to import Invoices, Credit Memos and
    Debit Memos. There is no other alternative. It's quite strange
    that Oracle hasn't come up with the Transaction API.
    Regards,
    Rajkumar
    [email protected]

  • Is there any way (API ?) to access the UDS repository directly ...?

    This is probably reviving some older thread from way back in 1998 when similar questions where asked ...
    I am working on a program of my own (writing it in Borland Delphi), and I would like to have access to the Repository.
    One way I could think of is through the command line tools (like FScript) that come with UDS . However, I figure that there must e an 'easier' way to access the repository and retrieving/storing information.
    In one of the old threads I saw that an API would become available in v4 ...
    Alas ... no v4 ever saw the light. Instead of v4, the boys and girls of IPlanet/Sun went straight to v5 (and renamed their product from Forte to UDS).
    I can't find the API (documentation) mentioned above ...
    Does any of you guys out there have any information or, even better, examples on how to achieve access to the repository from a non-Forte application.
    If I could get this to work it would mean a huge (and that should be written HUGE) step forward in reaching my goal ...
    Hansz

    Of course there is an API to repository objects, and the SUN/iPlanet people are using it. Also in past times Forte-partners have used it. You can see the classes when you set certain cfg. flags. The problem is, there is no documentation about that API provided by SUN. If you find an expert within the community (who is not bound by a non disclosure ), it will be rather easy to set up C++ wrappers to integrate with an external (non TOOL) application.
    We feel a need for documented access to the repository objects as well, as that would make several tasks of development automatization and integration with other development tools (Forte for JAVA e.g.) more straight forward.

  • CS6 Beta first impressions

    Here is a list of things I noticed during a first test drive of the Photoshop CS6 Beta. This is a mixture of feature requests, bug reports and general observations. I just typed this up as I went along. I'm sorry I don't have enough time to file proper bug reports and feature requests, but I though this might still be useful feedback. These things are in no particular order (well, except in the order I noticed them), and I'm sure there are a quite a few grammar/spelling errors, but right now that's all the time I can invest, sorry.
    And even though this all sounds really negative (I basically just listed the annoying points since a list of good thigs probably isn't very useful), I am quite happy with the new version, congratulations to the team! I love the cat graphic on the splash screen by the way.
    All these things were tested on a MacBook (2008 I think) with OS X Snow Leopard and 8 GB of RAM. So here you go:
    Ctrl+Some Key still not available as shortcuts (e.g. Cmd+H Hide Photoshop, Ctrl+H Hide Extras)
    The aesthetic merit of the font choice in the about box/splash screen is debatable
    Despite all the vector enhancements, Spacebar+drag still doesn't work in the Pen tool like it does in other Adobe applications
    Paragraph and Character style definitions apparently cannot be shared with InDesign or Illustrator so far. There is no way to link to external style definition files, and no way to import or export. Since all these applications use the same text engine, this seems like a missed opportunity, requiring a lot of duplicate work on the user's part (not as much as in previous versions, though)
    The title bar of the document window uses the system title bar and thus does not match the overall interface skin. If that is set to dark (which is the default), it calls attention to itself.
    There is no way to hide the filter bar in the layers panel, making it waste screen space on laptop screens when it is not needed.
    The Warp option in Free Transform was updated to add GPU acceleration, which is great. That would have been a perfect opportunity to make the number of subdivisions user-adjustable.
    There are lots of new vector features. This would have been a perfect opportunity to integrate After Effects' mask and shape system (including effects like repeaters), resulting in increased compatibility for importing Photoshop files into AE. Besides, all enhancements would pay off double since two applications would benefit from them. That would also have added the option to feather vector shapes for use as soft vector masks (Photoshop's mask feather function seems to perform a blur and thus is significantly slower, plus it applies globally to all paths in the mask). Still, the vector features are very well implemented, even though Fireworks still seems to have a slight edge.
    The red "active" indicator on the layers panel filter bar calls attention to itself. The entire application uses grayscale icons. While I can see why this indicator needs to be obvious, I think that is too much.
    The "Scripted Pattern" function is not very intuitive to use without any kind of preview. Also, it is not really clear how to create your own scripts, edit the existing ones or even just adjust parameters.
    The Fill dialog in general takes too many clicks with that popup menu. Using icons or something similar would save a lot of mouse miles/clicks.
    There is still no way to directly load 50% gray as the foreground/background color. In photo retouching etc., this comes up a lot. Adding a little icon to the color picker in the toolbox with the ability to assign a shortcut would help a lot. Waiting for this since version 5 or so...
    Curves still doesn't support editing the layer's alpha channel nor LAB mode (at least not without converting the entire document to LAB mode or a smart object).
    The "File Info" is still the ugly inefficient Flash monster where everything takes ten times as long to do than it did with the old dialog it replaced a few versions back (mouse wheel doesn't work on tabs, text editing shortcuts are different/don't work, tabs instead of the InDesign-like list of categories and many more). Photomerge is still ugly, but at least it doesn't have such major usability issues. The interface is inconsistent enough already, why do these have to be Flash?!
    Shift key during canvas rotation to constrain angles still only works when using the tool but is ignored when using a multitouch pad gesture
    The minimum size on the new "Adjustments" panel is larger than necessary
    There still seems to be no option to not hide all panels when activating another application, causing that visual jump and slight desorientation every time
    That new pen tool cursor is huge
    There are still no Lightroom-like info bubbles or indicator icons (like LR's process version upgrade warning) for entering Quick Mask, toggling Softproofing etc. that would alert the user when accidental keystrokes
    Photoshop doesn't seem to ask the user to automatically migrate settings and presets from any previous version on first launch. The migrate presets function does nothing (don't know if this is an issue related to the computer I am testing this on).
    The "Blend RGB Colors using Gamma" feature in the color management settings still seems to be global and not per document (not 100% sure, though). This results in files being displayed differently on different computers, which is not a good idea.
    The line-based warping in "Adaptive Wide Angle" is only available within that filter as far as I can tell. This is a missed opportunity IMO. Being able to specify arbitrary source and destination paths to that algorithm would make for a very powerful warping tool.
    I'm not exactly sure what caused it, but I managed to accidentally disable path anti-aliasing and I can't seem to find a way to switch it on again. No combinations in the GPU preferences under "Performance", including switching GPU acceleration off completely, restored it. This is either a bug or a usability problem. Personally, I think the option to antialias paths and guides should be located in the View menu, not hidden in the GPU preferences.
    In the settings for a LUT adjustment layer, clicking any of the radio buttons will automatically pop up a file selection dialog, even if my intention was to use one of the presets. That file selection dialog also gives me no clue which file formats are supported (i.e the regular format popup is missing).
    Both Cmd+Space and the zoom tool itself now seem to behave identically. There is no more way to drag a box, except to switch off "Scrubby Zoom" altogether. Using both methods in parallel (as I would prefer) is unfortunately no longer possible as far as I can tell.
    The brush cursor in Liquify is always dark, making it hard to see on black surfaces for instance. "Advanced Mode" is also off by default. Since the entire thing is in a huge dialog box (a solution like Blur Gallery's interface would seem like a better way to do this by the way), there is no real benefit to hiding these controls since there are no UI elements that would benefit from the additional space. It just requires an additional click.
    The Liquify preview flickers as I am typing this in a TextEdit window that is floating above it
    Select > Color Range would benefit from buttons with icons for preview mode instead of a dropdown. Same for Curves (tabs would probably be best in that case, but at least we have the shortcuts for now)
    The "Sample all Layers" option vanishes when switching the Patch tool from "Content Aware" to "Normal"
    That's it for now, thanks for listening.

    @Chris Cox: I didn't mean post professionals who probably answered your surveys, but cinematographers and the like who currently simply deliver JPEGs of their desired look as far as I know, not colorists and effects artists using Photoshop to generate their look. But I'm no expert on those workflows, and I completely agree, a third party solution for LUT export is probably the best way to implement such a workflow.
    @c.pfaffenbichler: Most professionals are still working predominantly in a semi-destructive way (i.e. using layers). Smart objects are too much hassle for most things (especially not being able to see your changes in context when editing them), so keeping an original layer and re-applying a filter is still very common.
    Seeing that Blur Gallery can export a channel, that actually makes it quite useful, contrary to my initial assessment. Even though the interface is currently not optimized for this, it looks like Blur Gallery is a great quick and easy way to generate layer masks for color corrections.
    @TLL..: Professionals will always buy their software. And those people who don't won't make that decision dependent on the licensing model. Very few of those who pirate programs are actually lost customers who don't buy software because they found a way can get it for free. It just doesn't work that way even though many companies would like to think it does. Most people simply wouldn't buy the software if piracy was not an option, with price being the deciding factor. The question is simply how spread-out the transition area inbetween is. I don't have Adobe's research data, though, so I can't comment on their specific case (I'd guess Photoshop is one of the most pirated programs, though), but I don't think threatening them with piracy is going to be that effective, they probably have someone who does nothing else all day than figure out smart ways to optimize these kinds of things for maximum profit
    Just as a side note, in some cases piracy actually works in a company's favor. Microsoft owed much of its market dominance in their early days to the fact that unlike the competition their software was not copy protected and thus became much more widely used than comparable solutions, leading to much higher sales than copy protection could ever have given them.
    Don't get me wrong, I am in no way defending piracy here, of course, I just think it's interesting from a strategic perspective. On the other hand, Photoshop is quite well known and doesn't have any real competition, so that probably defeats my point. Anyway, moving on.
    I had a chance to play with the Beta again today for about an hour, and here are a few more things I found (again, a mixture of bugs, features I had hoped for, quirks etc. that I noticed and jotted down as I went along):
    The new in-place/on-canvas filters like Blur Gallery use an OK/Cancel button combination to exit the semi-modal state, which is inconsistent with all the existing semi-modal tools like Crop and Free Transform (which continue to use the checkmark system).
    Panel groups can no longer be collapsed by double clicking in the free area next to the tabs, only the tabs themselves. Not sure if that is intended behavior or a bug.
    Most panels seem to be docked below the Brushes panel by default for some reason so that showing any of these panels will also automatically bring up the much larger Brushes panel.
    ExtendScript Toolkit always crashes when switching to the "Fonts and Colors" tab in Preferences. This behavior can be reproduced every time. Unless this is related to a specific configuration, I can't imagine how this could have slipped through during QA/internal testing.
    There is currently no documentation for the APIs for the new Deco patterns, at least I was not able to find any, but I guess this is going to change in the release build.
    The Displace filter is still stuck in the early nineties (no preview, not accepting channels but using separate map files etc.). Displace is one of the most used filters in photo post production and image compositing.
    When placing files, it is never made 100% clear to the user which files/file types are linked to and which ones are embedded. An option to choose and possibly even a links panel like in InDesign and Illustrator would be useful.
    For placed videos (which seem to be linked to rather than embedded), the link seems to consist of just an absolute path (heard about this problem somewhere else, didn't have a chance to verify). I'd suggest storing both relative and absolute paths and if one fails to match, try the other before requesting a manual relink.
    The properties panel displays an unnecessary vertical scrollbar for Curves adjustment layers that just scrolls down to some empty space below
    The Timeline panel flyout menu has lost the "Document Settings" command. There now seems to be no reasonably obvious way to set the overall animation duration. There is also no "Trim Animation to Work Area" command. New layers seem to always use some kind of default duration, not the duration of the current timeline sequence.
    The segments in the animation timeline are a very vibrant color (at least on a wide gamut monitor). Ideally, they should at least match the color palette established by the blue selection highlight color, the ok buttons in the options bar and the render progress bar (which I really like). Strongly colored UI elements affect the perception of color in the image. Autodesk Smoke/Flame does a great job of using a non-obtrusive color palette in its interface.
    The "Set Current Time" dialog box that pops up when double-clicking the timecode display in the bottom area of the Timeline panel does not support pressing the escape key to cancel if the text field has the focus. Pressing Tab doesn't seem to change the focus either. Pressing down on the OK button, holding and dragging out of it doesn't hide the selection in the text field, but the escape key now works as expected. The return key works as expected in all situations, no matter which control has the focus.
    The "Split Clip" button doesn't seem to work well with the undo system. The corresponding menu bar item (Edit > Undo Split Clip) is sometimes grayed out. Switching to another application and back to Photoshop seems to re-enable the menu item in some cases. The grayed-out menu item obviously also blocks out the use of the corresponding hotkey (Cmd+Z in the default configuration).
    Dragging transitions to clips sometimes has no effect. I can't give a specific combination of things that cause this behavior, but it seems to be a per-document issue. If it kicks in, transition dragging doesn't work at all, i.e. it is always all segments in a particular timeline that don't accept transitions, not just individual ones. The dragging process happens as expected, but basically, the segments don't highlight under the mouse, nor do they accept the transition.
    Keyframe interpolations are limited to "Linear" and "Hold". A minimalistic "Smooth" option would be really useful, and it wouldn't have a noticeable impact on the complexity of the video timeline feature for novice users. I'm no AE expert, but I believe it has a feature called "Easy easy" keyframes, too, giving you smooth interpolation without manually adjusting the bézier animation curves.
    The horizontal scroll bar on the Timeline panel always shows some extra empty space, like the Properties panel for Curves. There is also no obvious "Zoom Timeline to Fit All" function (a toggle between 100% and the last zoom position would make sense, I think this is also how Avid implemented it in Media Composer).
    3D layer rendering still isn't really a background thread and almost all interactions with the applications cancel the render operation.
    Vector shapes unfortunately only support plain vector outline strokes instead of allowing the user to apply any of the brush presets (or even use any of the settings inside the "Stroke Path" command, which would enable things like smearing using vector shapes). In my opinion, that is really the missed opportunity for additional usefulness that vector support in a pixel-based application can offer. I know the vector shapes feature is aimed at designers who don't want to switch between Photoshop and Illustrator for every single vector task, but that would have been a way to make that feature much more relevant for more than just the screen design demographic.
    The beta doesn't ship with the Pixel Bender filter, which I hope is going to change with the final build. That filter needs some work compared to CS5 (supporting the AE user control fields, supporting high-resolution images at least in CPU mode, channels as input images, color management issues, etc.) The CS5 release still feels very much like Alpha software (Pixel Bender Toolkit is even worse).
    The 3D camera has no on-screen widget to specify depth of field distance settings or even locking them to an object (similar to an aimed camera in compositing programs and 3D software). The sliders are also sometimes quite laggy, ideally all sliders should be completely interactive with only the render lagging behind. A slider that sticks jumps around while the software is rendering can be quite frustrating for a user (Lightroom has had that problem for a long time).
    The "Sketch" render presets seem to give incorrect results (i.e. results that have nothing to do with the 3D object, just a bunch of semi-random shapes and rectangles. The render button is also completely disabled. There also seems to be no way to activate the "Sketch" setting except through the presets.
    The fact that Content Aware Move allows the user to change the Adaptation setting after the fact is not very discoverable and inconsistent with both the other tools and apparently even the behavior of the Mode setting on the same tool. I'd suggest giving the tool a pseudo-modal state like the crop and free transform tools instead.
    The lorem ipsum command is called "Paste Lorem Ipsum". The use of the term "Paste" here is potentially confusing since it has nothing to do with the system clipboard. "Insert" would be a better choice of words in my opinion. Also, the same command inside InDesign is called "Fill with Placeholder Text", so you may want to consider using that for cross-application consistency.
    On the 2008 generation MacBook I was able to test this on, Liquify always launches in CPU mode (1 pixel black border around the preview image). Not sure if the GPU in that system is simply not supported. I suggest showing an unobtrusive information note somewhere (maybe below the settings), like "GPU acceleration for this filter is not supported on this hardware configuration". Like the "Efficiency" setting in the document window status bar, this would help users identify potential performance bottlenecks on their systems. The black border is just not very discoverable.
    The improvements to text (paragraph/character styles etc.) would make a glyphs panel like in InDesign and Illustrator a logical addition (saves unnecessary copy & paste operations).
    It seems that multiple clips in the Animation Timeline cannot be trimmed at the same time, even if they are both selected.
    The "Show Asian Text Options" checkbox seems to have disappeared from Preferences. Things like the Warichu option still seems to be Illustrator-only, even though it is incredibly useful for other things beyond what it was intended for (movie poster-style credits are the most popular example, but there are many more). Also, it seems illogical that you would have to choose between either of the text engines available, but I guess this is required by historical engineering decisions.
    Panels still can only be docked to the edges of the primary monitor. Docking is not available on secondary monitors. On Windows, docking only works inside the main window, no matter on which screen. I know this is standard behavior, but I never really understood the logic behind that.
    Hope this is useful.

Maybe you are looking for