forked from Adobe-CEP/Samples
-
Notifications
You must be signed in to change notification settings - Fork 0
Title #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tawanjairew
wants to merge
56
commits into
tawanjairew:master
Choose a base branch
from
Adobe-CEP:AfterEffects
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Title #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed 'undefined is not an object' on startup
Fixed 'undefined is not an object' on startup
This is the first submition of Audition CEP samples to the git repository. There're four samples: - ApplicationCommands: Demonstrate the usage of application commands (aka menu commands) - PlayheadPanel: Demonstrate how to get/set the playhead position in a wave document as well as start/end/current time - TransportEvents: Demonstrates how to process transport events, how to process ExtendScript events in general, how to post data from an ExtendScript script to a CEP panel - ScriptDictionary: - Displays reference documentation of the ExtendScript scripting DOM
Initially add Audition CEP samples
Fix manifest, in preparation for node.js usage.
Numerous additions and edits for 11.0: * Encoder API can now transcode files, and projectItems. * Panels can now walk across all clips in sequences, manipulate standard effect parameter types (but not Lumetri .look file paths, sorry), and replace the projectItems behind clips, to enable "render and replace" functionality.
Updated readme.
Added links to source code in "What's Possible" section.
Fixed incorrect documentation, touched manifest and .debug files
Also, fixed line endings in PProPanel.
Fixed broken render call, minor updates.
Fixed some function calls that worked in ESTK, but not when executed from within a panel. Also, I added numerous alerts, so that instead of failing silently, PProPanel tries to explain what happened.
Re-enabled stylesheet.
Touching the file with ExtendScript Toolkit messed up the line endings. Fixed.
These were switched to Macintosh line endings, by ESTK.
More line ending issues.
Replaced by updated image.
* Now listens for 'workspace changed' events * Disables the importing of workspaces with projects * Demonstrates Insert and Overwrite edits * Expanded XMP handling * Other things I've probably forgotten. :)
Minor edits. Reinstalled MarkDown formatting.
(Line numbers had moved since creation.)
Added usage of new onEncoderJobCanceled messaging.
Updated for 11.1; added onEncoderCanceled messaging, new insert and overwrite edits, abilty to control whether workspaces are opened with projects.
(corrected line numbers in docs)
(For some reason, GitHub hates Markdown...)
# Conflicts: # PProPanel/ReadMe.md
(Markdown fight continues)
Some users encountered an expression syntax error.
Typo in ext.js
Update ext.js
Lots of whitespace improvements, too.
Sorry for all the churn. I'm testing a new Git client. Until I've ruled out pilot error on my part, I won't rat them out, but for now, I've gone back to the previous client.
setEnableProxies is done using the app object now. Old reference to do this via a sequence object has been replaced to use app instead.
Fix a problem with enable proxies
Initial commit of the ExtendScript and Premiere Pro type declaration files. They exist in the raw state that they were initially developed in. Much work is needed.
This is the PProPanel sample, adjusted to take advantage of TypeScript-based type declaration files to build an environment that enables modern tooling around Adobe CEP.
JavaScript syntax highlighting doesn't work in HTML in VSCode. This enables syntax highlighting for the scripts in question.
The "shared" folder is mostly interesting for TypeScript. This repository does not contain any actual TypeScript files yet - it merely has JavaScript and ExtendScript content. It _is_ setup for TypeScript, yes, but nothing makes use of this "feature". For now, leave it out to keep things as simple as possible.
The ExtendScript declaration files got a comment cleanup pass and a few more classes supported. The big win here is the inclusion of Object and ObjectConstructor which somewhat links it to the ECMAScript base.
The massive block of comments at the top was moved out into a ReadMe.md for easier viewing. What's more, the intermediary `PremiereObject1 class was re-implemented so as to provide full type support.
Declaration file authoring is somewhat of a black magic. Hopefully, these comments will help make some of the black magic a little more clear.
Add a ReadMe to the sample that provides some information as to the structure and content of the "project".
The `with` statement was deprecated and should not be used.
Add TypeScript-enabled Sample Environment and First-Pass Type Declarations
This property was explained in the forums. See: https://forums.adobe.com/message/9677988#9677988
Copy the updated documentation to the sample to keep things in sync.
Expand nodeid documentation
Implement a multi-app approach to JSX-loading
Lots of little improvements.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
*#