Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
Inventsable
Enthusiast
Inventsable
Enthusiast
Activity
‎Dec 25, 2019
12:36 PM
I think it would depend on the construction of the objects and where the effects exist in their Appearance. Are the effects within the Layer Appearance, a Group Appearance, or etc? I'd think an easier workaround would be to group the entirety of your selection, scale this new group up, then ungroup, but that relies on Effects not being on the Layer. You'd probably want to loop through the selection, save a reference to the original layer the item belongs to, then do the above and place the items back in their original layers (since grouping them will force them to the active layer only).
... View more
‎Dec 20, 2019
08:34 PM
1 Upvote
You make CEP panels, right? If you're trying to process multiple files you could have a CEP panel send an evalScript call to open some file, then using the documentAfterActivate event trigger your script on launch and have the document close itself afterward if needed, looping through a list of files for all of the above
... View more
‎Dec 15, 2019
07:47 PM
Great job! Thanks so much for doing the digging, will test on my side too
... View more
‎Dec 05, 2019
10:20 AM
1 Upvote
Hello all, I made a quick CLI generator to set up Typescript if you're interested: It does all the heavy lifting for you, and is very quick when the types are already installed at some folder in the parent. If you're unsure of what the advantage to Typescript is, notice that I can see the App DOM as I type below, a .jsx file is compiled every time I save, and I could even use more modern Javascript than scripting would typically allow: To install, you'll need NodeJS: npm install -g scriptopia Usage can be any of the following: // We need a package.json somewhere in our project, even if a few folders above. If you haven't made one already, you'll need to generate a package.json beforehand:
npm init -y
// With CLI prompts:
scriptopia
// With shorthands, no prompt:
scriptopia id test.jsx
scriptopia idsn helloworld.ts
scriptopia indesign myScript.js
// Detailed help message:
scriptopia help
... View more
‎Dec 05, 2019
10:18 AM
Hello all, I made a quick CLI generator to set up Typescript if you're interested: It does all the heavy lifting for you, and is very quick when the types are already installed at some folder in the parent. If you're unsure of what the advantage to Typescript is, notice that I can see the App DOM as I type below, a .jsx file is compiled every time I save, and I could even use more modern Javascript than scripting would typically allow: To install, you'll need NodeJS: npm install -g scriptopia Usage can be any of the following: // We need a package.json somewhere in our project, even if a few folders above. If you haven't made one already, you'll need to generate a package.json beforehand:
npm init -y
// With CLI prompts:
scriptopia
// With shorthands, no prompt:
scriptopia ae test.jsx
scriptopia aeft helloworld.ts
scriptopia aftereffects myScript.js
scriptopia afterfx
// Detailed help message:
scriptopia help
... View more
‎Dec 05, 2019
10:16 AM
Thanks Carlos! Let me know if you need any help, I understand that it's confusing to try after being so used to doing things a certain way. But essentially, this lets you see the DOM as you type (exactly like the online editor I made) along with parameters of app methods -- can definitely be useful instead of constantly needing to stop and doublecheck the documentation.
... View more
‎Dec 04, 2019
09:50 PM
1 Upvote
Hello all, I made a quick CLI generator to set up Typescript if you're interested: It does all the heavy lifting for you, and is very quick when the types are already installed at some folder in the parent. If you're unsure of what the advantage to Typescript is, notice that I can see the App DOM as I type below, a .jsx file is compiled every time I save, and I could even use more modern Javascript than scripting would typically allow: To install, you'll need NodeJS: npm install -g scriptopia Usage can be any of the following: // We need a package.json somewhere in our project, even if a few folders above. If you haven't made one already, you'll need to generate a package.json beforehand:
npm init -y
// With CLI prompts:
scriptopia
// With shorthands, no prompt:
scriptopia ai test.jsx
scriptopia ilst helloworld.ts
scriptopia illustrator myScript.js
// Detailed help message:
scriptopia help
... View more
‎Dec 04, 2019
09:42 PM
Hello again Liam, I made a quick CLI generator to set up Typescript if you're interested: It does all the heavy lifting for you, and is very quick when the types are already installed at some point in the parent: To install: npm install -g scriptopia Then to use, any of the following: // With CLI prompts:
scriptopia
// With shorthands, no prompt:
scriptopia ai test.jsx
scriptopia ilst helloworld.ts
scriptopia illustrator myScript.js
... View more
‎Dec 03, 2019
08:11 PM
Hi Liam, Here's the typescript setup that I use along with my tsconfig file. I generally write all my code in a "host.ts" file, then have my setup compile to host.jsx on every save. For this to work, you'll need to run "npm install types-for-adobe", and then press Control + Shift + B to run "tsc: watch - [path to tsconfig]" in VSCode. I also have a dedicated sandbox for Typescript here, though the repo is old and I think pravdomil's original repo is deprecated (which is why I use @Ten-A's fork). If you have trouble setting it up feel free to post here. I took a codecademy class for HTML/CSS, then went on to their Javascript class but fell out of it because it was overwhelming and, in retrospect, really poorly designed since they try teaching you JQuery and React just a lesson or two after you learn what a function is. I don't remember the exact path after this beyond trying scripts out here in the forum, asking a lot of questions, taking a couple cheap Udemy classes, and Silly-V turning me onto Vue, the Javascript framework, which is fantastic and very beginner friendly -- it really abstracted a lot of the tedium from Javascript away and let me produce things quicker which let me practice more often, and then I became comfortable enough to branch into pure vanilla DOM manipulation and ES6+ methods like arrow functions. I understand the value of books but feel that my learning style isn't always compatible with the heavy literary one -- sometimes it feels like the burden to entry is very high and the abstraction needed to understand all the between-the-lines implications of taking text from the page to it working on screen isn't straightforward, so I've always opted for browser-based code editor resources, like codecademy, the Odin Project, and Scrimba, and take a bunch of Udemy classes for anything that interests me (like Vue). If it helps I have a panel version of that code editor which lets you write, run, save and open scripts while still inside Illustrator. The ZXP to install is located in the ./archive folder. It's based on Monaco so it shares the same foundation as VSCode itself does, though it was a quick project and there are graphical errors with the console drawer that I never addressed (plus syntax highlighting -- I couldn't get it to work alongside typescript definitions, so I chose typescript over syntax highlighting).
... View more
‎Dec 01, 2019
11:19 AM
1 Upvote
True! The editor is completely lacking there, though it'd make finding possibilities a lot easier rather than digging through documentation. The aenhancers site does have a few beginner-friendly sections and examples, though to be honest I had a hard time learning scripting until I just spent a few months in general web dev and Javascript. Once you get the basics of Javascript all together (where there's no shortage of beginner friendly material) it isn't hard to jump into Adobe scripting, but it's understandable if curious artists aren't willing to make that big of a leap. I've kept this in mind and would like to start doing beginner friendly tutorials eventually
... View more
‎Dec 01, 2019
11:16 AM
I actually wouldn't mind that if it opens up a lot of new possibilities. I keep asking about Illustrator and After Effects for UXP but never get a very clear answer of when to expect it. Sidenote though, I noticed there actually is a UXP extension in AI 2020. In Program Files > Adobe > Adobe Illustrator 2020 > Support Files > Required, there's a UXP and UxpResources folder. When you open it up and look around, it looks like it's the Photoshop Welcome screen, but it's interesting nonetheless because that means they might be opening it up in prerelease soon(ish)
... View more
‎Dec 01, 2019
09:43 AM
1 Upvote
Hey Carlos, there is ai.aenhancers, which is online Read-The-Docs format for Illustrator's DOM with a bunch of examples. I prefer this to PDFs and books because it's so easily searchable
... View more
‎Dec 01, 2019
09:41 AM
1 Upvote
Hello, I made an online code editor with typescript support for all Adobe apps (shows the app DOM as you type): Also has a curated list of resources per app in the drawer, though there's a lot more for AE than AI: My personal favorite for both AE and AI scripting is aeenhancers, here's the Illustrator version with a lot of examples per method/property.
... View more
‎Dec 01, 2019
09:35 AM
Cool! I didn't know if there were going to be new methods/properties added until maybe when UXP officially hits (do we know if there will be any rework with the scripting engine due to this btw?) Is there a canonical list for the tool name strings for application.selectTool? Or possibly an app.activeTool to see these?
... View more
‎Nov 29, 2019
02:39 PM
1 Upvote
What I'm trying to do is manually recreate the bezier handles of any given pathPoint. This does work inside a Shape Layer's Path as an expression to generate a line between the tangentIn and it's target anchor: const parentLayer = thisComp.layer("line");
const parentPath = parentLayer.content("line").content("Path 1").path;
let vertices = [0,1]
const data = {
position: parentLayer.transform.position,
anchor: parentLayer.transform.anchorPoint,
vertex: parentPath.points()[1],
tangent: parentPath.inTangents()[1],
};
createPath(
vertices.map((index, i) => {
let offsetX = 0;
let offsetY = 0;
Object.keys(data).forEach((val, e) => {
if (i < 1 || val !== "tangent") {
offsetX = offsetX + data[val][0];
offsetY = offsetY + data[val][1];
}
});
return [offsetX, offsetY];
}),
[],
[],
false
); Which is awesome. ES6 Array methods
... View more
‎Nov 29, 2019
01:56 PM
1 Upvote
Hi all. I know that for scripting .jsx files, it's ECMA 262, but after taking a long break from animating to learn all about coding and scripting, I've recently come back and was shocked to see that I can use this in an expression: Object.keys(data).forEach(key => {
console.log(key)
}) And this throws no errors. Obviously this has no effect because AE doesn't have a console (...right? I wish it did. Can I print data from expressions anywhere, to see coordinate data, etc?) but the implication of Object.keys, Array.prototype.forEach, and arrow functions leads me to think this is at least ECMA2015/ES6? Is it fair to assume these actually work, or is this just some bug where the expression validation doesn't catch them as errors?
... View more
‎Nov 29, 2019
12:03 PM
1 Upvote
I'd never needed to do this before, and I'm surprised it doesn't show as a PathItem property like all the other stroke options too. One way to get around this, though it may be complete overkill and someone might come in and give a much better solution, is to dynamically create an Action which you load, execute, then unload when needed: // Thanks Qwertyfly
// https://community.adobe.com/t5/illustrator/js-cs6-executemenucommand/m-p/5904772#M19673
function setStrokeAlignToInside() {
if ((app.documents.length = 0)) {
return;
}
var ActionString = [
"/version 3",
"/name [ 4",
" 74657374",
"]",
"/isOpen 1",
"/actionCount 1",
"/action-1 {",
" /name [ 9",
" 5365745374726f6b65",
" ]",
" /keyIndex 0",
" /colorIndex 0",
" /isOpen 0",
" /eventCount 1",
" /event-1 {",
" /useRulersIn1stQuadrant 0",
" /internalName (ai_plugin_setStroke)",
" /localizedName [ 10",
" 536574205374726f6b65",
" ]",
" /isOpen 0",
" /isOn 1",
" /hasDialog 0",
" /parameterCount 7",
" /parameter-1 {",
" /key 2003072104",
" /showInPalette -1",
" /type (unit real)",
" /value 1.0",
" /unit 592476268",
" }",
" /parameter-2 {",
" /key 1667330094",
" /showInPalette -1",
" /type (enumerated)",
" /name [ 8",
" 4275747420436170",
" ]",
" /value 0",
" }",
" /parameter-3 {",
" /key 1836344690",
" /showInPalette -1",
" /type (real)",
" /value 10.0",
" }",
" /parameter-4 {",
" /key 1785686382",
" /showInPalette -1",
" /type (enumerated)",
" /name [ 10",
" 4d69746572204a6f696e",
" ]",
" /value 0",
" }",
" /parameter-5 {",
" /key 1684825454",
" /showInPalette -1",
" /type (integer)",
" /value 0",
" }",
" /parameter-6 {",
" /key 1684104298",
" /showInPalette -1",
" /type (boolean)",
" /value 0",
" }",
" /parameter-7 {",
" /key 1634494318",
" /showInPalette -1",
" /type (enumerated)",
" /name [ 6",
" 496e73696465",
" ]",
" /value 1",
" }",
" }",
"}"
].join("\n");
createAction(ActionString);
var ActionString = null;
app.doScript("SetStroke", "test", false);
app.unloadAction("test", "");
function createAction(str) {
var f = new File("~/ScriptAction.aia");
f.open("w");
f.write(str);
f.close();
app.loadAction(f);
f.remove();
}
} We can set the Stroke alignment within an Action, but one problem is that we don't set only the alignment -- we also set the width, dashes, etc. You can record any Action, save it, open the .aia file in a text editor, and replace the ActionString variable above with it's contents to dynamically run it within a script without needing the user to have this action. For the above to work, you'd likely want to clear you app.selection at the beginning of the loop, then set each PathItem.selected to true, run this action just after the stroked = true, then do the styling, and PathItem.selected = false to remove it from the selection so future actions don't affect it.
... View more
‎Nov 28, 2019
01:34 PM
1 Upvote
Updated this quite a bit, source code on GitHub: Handles are only drawn when needed (needed to wrap Number() around them while comparing) Refactored basic recursion Merges all Clipping Masks for visible results only Places anchors/handles in same layer as target Optionally reconstructs every PathItem from scratch to override complex appearances (stacked fills/strokes) Optionally inherits layer label color to paint anchors/handles Optionally nests grouped handles within collection group for entire anchor Smart sorting of Layer contents after render places outlines just above their target Smart renaming appends Layer index, pathPoint index, and variable suffix per item entry for After Effects expression compatibility Before: Before, with clipping masks and unnamed paths After: Merge all masks, inherit layer label color, rename all targets, deeply organize them by handle and anchor and more
... View more
‎Nov 25, 2019
10:21 PM
Thanks Carlos! Could always be better though 😋 It probably makes more sense to use PathItems instead of PageItems, since then I wouldn't have to compare for groups/compounds, and right now the script still produces handles even when they aren't extended since leftDirection and rightDirection never seem to be null. Initially I tried comparing the anchor position to the handle data directly and only drawing if they aren't equal -- this didn't work (at least in comparing both array entries directly) so I dropped it but didn't look too far into why. Might do a bit of sprucing up and fixes regardless. Someone had asked if this was possible on reddit and I recommended scripting, but they didn't think that could draw the handles/anchors. But we all know better than that
... View more
‎Nov 23, 2019
08:05 PM
3 Upvotes
Figured it out: I had a few problems: I thought that decrementing from app.activeDocument.pageItems would mean I'd only draw anchors for items existing at the beginning of the loop because I assumed that pageItems was a chronological list. Turns out the bundled drawn anchors were a result of anchors drawing on anchors and recursing themselves, and I fixed this by saving all pageItems to an array at the beginning, then looping through this array to convert. Though the above technically solved all issues in this test file, I might have run into issues with CompoundPathItems, since I'd used /path/i.test(item.typename) and this would pass true for both PathItem (intended) and CompoundPathItem (unintented). The function which iterates through items for conversion itself shouldn't have a hardcoded list, like prior with app.activeDocuments.pageItems. Instead, it's better to pass an array as a parameter to this, and iterate through this array -- reason being that #2 can be solved for instantly by the function calling itself like "convertListToOutlines(items.pageItems)" if it comes across something that isn't a pathItem. For posterity I'm including the final script below. I'd still be interested in hearing any ways that it could be made better! // https://github.com/Inventsable
// contact: tom@inventsable.cc
//
// Barebones script to convert all paths in current document to permanent Outlines, including handles and anchors.
// This action can be undone with a single Edit > Undo command.
//
// You can edit the below settings:
var anchorWidth = 1; // number in pixels, width of stroke
var anchorSize = 5; // number in pixels, height/width of rectangle
var handleSize = 4; // number in pixels, size of ellipse/orb where handle is grabbed
var anchorColor = newRGB(50, 50, 200); // RGB values, currently blue
var anchorIsFilled = true; // Boolean (true or false) if true, anchors are filled, otherwise have only stroke
//
var outlineWidth = 1; // number in pixels, width of stroke
var outlineColor = newRGB(0, 0, 0); // The RGB value of color ([0,0,0] = black)
//
var forceOpacity = true; // Boolean (true or false) if true, force all paths to have full opacity
// --------------------------------------------------- //
//
// Do not edit below unless you know what you're doing!
//
convertAllToOutlines();
function convertAllToOutlines() {
// Need to collect all current pageItems otherwise recurses into it's own drawn anchors
// app.activeDocument.pageItems is not chronological! Adding to it, even if decrementing, causes recursion
var targets = scanCurrentPageItems();
convertListToOutlines(targets);
}
function scanCurrentPageItems() {
var list = [];
for (var i = app.activeDocument.pageItems.length - 1; i >= 0; i--) {
list.push(app.activeDocument.pageItems[i]);
}
return list;
}
function convertListToOutlines(list) {
for (var i = list.length - 1; i >= 0; i--) {
var item = list[i];
if (/compound|group/i.test(item.typename)) {
if (item.pageItems && item.pageItems.length) {
convertListToOutlines(item.pageItems);
}
} else if (/path/i.test(item.typename)) {
if (item.stroked || item.filled) {
replaceAppearance(item);
if (item.pathPoints && item.pathPoints.length) {
for (var p = 0; p < item.pathPoints.length; p++) {
var point = item.pathPoints[p];
drawAnchor(point);
if (point.leftDirection) drawHandle(point, "left");
if (point.rightDirection) drawHandle(point, "right");
}
item.opacity = forceOpacity ? 100.0 : item.opacity;
} else {
alert("Problem with " + item.name + ": " + item.typename);
}
}
} else {
alert(item.name + " " + item.typename);
}
}
}
function drawAnchor(point) {
var anchor = app.activeDocument.pathItems.rectangle(
point.anchor[1] + anchorSize / 2,
point.anchor[0] - anchorSize / 2,
anchorSize,
anchorSize
);
setAnchorAppearance(anchor, false);
}
function drawHandle(point, direction) {
var handle = app.activeDocument.pathItems.add();
handle.setEntirePath([point.anchor, point[direction + "Direction"]]);
setAnchorAppearance(handle, true);
var handleBar = app.activeDocument.pathItems.ellipse(
point[direction + "Direction"][1] + handleSize / 2,
point[direction + "Direction"][0] - handleSize / 2,
handleSize,
handleSize
);
handleBar.stroked = false;
handleBar.filled = true;
handleBar.fillColor = anchorColor;
}
function setAnchorAppearance(item, isHandle) {
if (!isHandle) {
item.filled = anchorIsFilled;
item.stroked = !anchorIsFilled;
if (!anchorIsFilled) {
item.strokeWidth = anchorWidth;
item.strokeColor = anchorColor;
} else {
item.fillColor = anchorColor;
}
} else {
item.filled = false;
item.stroked = true;
item.strokeWidth = anchorWidth;
item.strokeColor = anchorColor;
}
}
function replaceAppearance(item) {
item.filled = false;
item.stroked = true;
item.strokeWidth = outlineWidth;
item.strokeColor = outlineColor;
}
function newRGB(r, g, b) {
var color = new RGBColor();
color.red = r;
color.green = g;
color.blue = b;
return color;
}
... View more
‎Nov 23, 2019
07:05 PM
I'm including the file (couldn't attach it, said the contents didn't match the file type?) in case any one willing to help wants to verify or test against it. Thanks guys! Mango
... View more
‎Nov 23, 2019
06:53 PM
Just for practice I wrote a basic script that would loop through all document.pageItems then replace it's appearance with a stroke while attempting to draw each of it's pathPoint anchors/handles manually. I'm getting unexpected results, though. On a simple shape, there are no problems. Left is the script result, right is the actual path: Looks great. But once I try a more complex file like a character, I get strange results: The left script results produces a bundled group of anchors where there should be none (between the pencil and the clipboard, beneath the left eye). It looks as though it stops executing at this point, because it doesn't continue to the leaf, shadow, eyes, mouth, etc. When I comment out the section that draws handles, all is fine, it strips the appearance just as expected: Can I get some help here? What am I doing wrong? How can this be done better overall? //
// Barebones script to convert all paths in current document to permanent Outlines, including handles and anchors.
// This action can be undone with a single Edit > Undo command.
//
var anchorWidth = 1; // number in pixels, width of stroke
var anchorSize = 5; // number in pixels, height/width of rectangle
var handleSize = 4; // number in pixels, size of ellipse/orb where handle is grabbed
var anchorColor = newRGB(50, 50, 200); // RGB values, currently blue
//
var outlineWidth = 1; // number in pixels, width of stroke
var outlineColor = newRGB(0, 0, 0); // The RGB value of color ([0,0,0] = black)
//
var forceOpacity = true; // Boolean (false or true) if true, force all paths to have full opacity
function convertToOutlines() {
for (var i = app.activeDocument.pageItems.length - 1; i >= 0; i--) {
var item = app.activeDocument.pageItems[i];
if (/path/i.test(item.typename)) {
if (item.stroked || item.filled) {
replaceAppearance(item);
// If I comment out the code below, all objects convert appearance exactly as expected.
// But certain parts (leaf, shadow, eyes/mouth) aren't affected by this?
if (item.pathPoints.length)
for (var p = 0; p < item.pathPoints.length; p++) {
var point = item.pathPoints[p];
drawAnchor(point);
if (point.leftDirection) drawHandle(point, "left");
if (point.rightDirection) drawHandle(point, "right");
}
// ---------------
item.opacity = forceOpacity ? 100.0 : item.opacity;
}
}
}
}
convertToOutlines();
function drawAnchor(point) {
var childpos = point.anchor;
var anchor = app.activeDocument.pathItems.rectangle(
point.anchor[1] + anchorSize / 2,
point.anchor[0] - anchorSize / 2,
anchorSize,
anchorSize
);
setAnchorAppearance(anchor);
}
function drawHandle(point, direction) {
var handle = app.activeDocument.pathItems.add();
handle.setEntirePath([point.anchor, point[direction + "Direction"]]);
setAnchorAppearance(handle);
var handleBar = app.activeDocument.pathItems.ellipse(
point[direction + "Direction"][1] + handleSize / 2,
point[direction + "Direction"][0] - handleSize / 2,
handleSize,
handleSize
);
handleBar.stroked = false;
handleBar.filled = true;
handleBar.fillColor = anchorColor;
}
function setAnchorAppearance(item) {
item.filled = false;
item.stroked = true;
item.strokeWidth = anchorWidth;
item.strokeColor = anchorColor;
}
function replaceAppearance(item) {
item.filled = false;
item.stroked = true;
item.strokeWidth = outlineWidth;
item.strokeColor = outlineColor;
}
function newRGB(r, g, b) {
var color = new RGBColor();
color.red = r;
color.green = g;
color.blue = b;
return color;
}
... View more
‎Nov 14, 2019
10:04 PM
1 Upvote
Hi, what version of Illustrator are you running? I don't get this behavior: function exportFileToSVG(path) {
// Replace current file extension with .svg
var name = app.activeDocument.name.replace(/\.[\w]*/, ".svg");
// Then export file without modifying the activeDocument (desired behavior)
app.activeDocument.exportFile(
new File(path + name),
ExportType.WOSVG,
new ExportOptionsWebOptimizedSVG()
);
} I personally really dislike the Javascript PDF guide you're quoting, and tend to use ai.aenhancers as my go to reference and guide because it's far more convenient, easily searchable, has better examples, and is a lot more beginner friendly.
... View more
‎Nov 12, 2019
02:08 PM
Hi is this from the r/Illustrator thread? I use AHK successfully in AI including modifier keys, with a Logitech G602 (13 buttons). Do you have a script to show?
... View more
‎Oct 15, 2019
11:21 AM
1 Upvote
You can create a File object from the window.__adobe__.cep.fs.writeFile() method if you can successfully stream the data from some other means like a Node API or npm package with unpkg. Since you have I/O and file system access on the CEP side of Javascript and not strictly scripting/Extendscript, you should be able to retrieve the data (many npm modules and libraries for this depending on where that file is), write to the local file system via the method above, then on successful write (believe the function is synchronous) prompt the host app to open that above file in whatever location you placed it.
... View more
‎Oct 14, 2019
05:11 PM
Using a CEP panel and not strictly a .jsx file, sure, since you're able to access Node APIs and use anything ~V8 at your disposal. Do you use any JS frameworks, or are you only writing .jsx files? There are some simple templating systems for CEP panels. You could retrieve content from the web via the panel JS, then likely pass it through CSInterface.evalScript() for whatever your personal needs would be, if not save the file to your local disk under a certain path then have the application open it.
... View more
‎Oct 03, 2019
06:54 PM
Plugin or extension? Many people use the terms interchangeably but technically a plugin is a C++ SDK snippet that extends Illustrator's own functionality, and an extension is a script or HTML panel which has access to the scripting environment exposed by Illustrator. If a CEP HTML extension, you can manually check the current security status assuming that it was created with NodeJS and you have NodeJS installed on your computer. You can travel to the extension's root path in your command line/terminal then use npm audit And see a detailed list of current security problems, their implications and how to fix them, like this.
... View more
‎Aug 06, 2019
09:57 AM
Oh wow, that's never happened to me before. Sent a link in the site instead, email is also on my github profile. Thanks again Trevor!
... View more
‎Aug 06, 2019
09:00 AM
Hey Dave, I'd be very interested in this. I have over 70 open source panels on my github here: Inventsable (Tom Scharstein) · GitHub I even have a Yeoman generator for my personal setup that allows me to generate, stage, and sign new extensions in less than a minute (very rapid prototyping): GitHub - Inventsable/generator-cep-vue-cli: Yeoman generator for Adobe CEP extensions with Vue-CLI-3 Let me know! Email is ??????? Edited, send a Private Message or use a contact page
... View more
‎Jul 23, 2019
11:44 PM
1 Upvote
Thanks! I get that, which is why I really like those docs linked here in particular. For the compiling I'm using @babel/standalone and targeting certain plugins to get results for what I need: Before this web app, I had a similar setup inside a panel to run, edit and write scripts directly in the host app with some of the same features like Typescript, but additional I/O controls and a console.log alias (via CSEvent on the panel's JS): I mostly just want Array methods, arrow functions and template literals, which I get now via this panel (which runs/saves compiled verisons via @babel/standalone). I'd bet there's a way to use Babel within your tsconfig directly to produce a compiled .jsx from your .ts directly every save and when your compileOnSave event is triggered, but I haven't dug into how to make it work just yet. I did come across an es6 shim repository from ExtendScript ​​after that Array discussion a few weeks back ​​which seems to have the same goal and might be worth looking into as another option though.
... View more
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more
Copyright © 2025 Adobe. All rights reserved.
AdChoices