Try this (NOTE, edited existing code without testing, so bugs likely) function cropPercentage(ratio) {   if (app.documents.length > 0 && ratio < 0.5) {   var doc = app.activeDocument   var crop_w = Math.floor(doc.width*ratio + 0.5)   var crop_h = Math.floor(doc.height*ratio + 0.5)   doc.crop(new Array(crop_w, crop_h, doc.width-crop_w, doc.height-crop_h))   } }, ... View more

Btw, Davide how does that work with layer name as param? It's not a unique id across whole doc or even group. A rather simple alternative is to create an empty layer below and use artLayer.merge(). There is also artLayer.rasterize(RasterizeType), but I think it had the issue that even with param RasterizeType.ENTIRELAYER it does not rasterize layer style & smart filter. This limitation might (or might not) apply to Davide's solution also since it uses similar attribute. ... View more

For everyones info, this is based on the node module "tmp". It tries to search environment variables and defaults to "/tmp". At least in the standalone Node.js in Windows it resolves to C:\Users\USERNAME\AppData\Local\Temp _findTemporaryDirectory: function () {   var tmpNames = ['TMPDIR', 'TMP', 'TEMP'];   var dir = null   for (var i = 0, length = tmpNames.length; i < length; i++) {   dir = dir || process.env[tmpNames]   }   _temporaryDirectory =  dir || '/tmp'   console.log("_findTemporaryDirectory: " + _temporaryDirectory) } ... View more

Thanks, I actually just realized the Architecture page in GitHub is not just one page but a full wiki, so that was my "missing docs" and helped me a lot You could consider putting some overview& links in the wiki home page and then linking to that in Read.me so the oblivious ones like me don't miss it.. By "ExtendScript-able preference" do you mean sending e.g. the menu event like here http://https://github.com/adobe-photoshop/generator-core/wiki/Calling-Generator-Plugins-from-ExtendScript‌? Or do you mean you could use ScriptListener to record action to enable generator and call it from panel? Packaging sounds like I could make hybrid ZXP and use either $pluginsfolder/Generator or $photoshopappfolder/Plug-ins/Generator as the destination-parameter. Not really clear what the state would be (some doc mentioned that in "undefined" state it should be enough to copy plugin to folder. But plan is to use websockets for plugin<->panel communications, so if all else fails should be possible to detect state and instruct user what to do. Matias ... View more

Ok, sounds like "just a bug", hopefully just in your machine. I did script performance timing accross versions and they were pretty equal (~CC 2012 10% faster than 2014, Mac 10% faster than Win). Try changing settings in Preferencs -> Performance -> Graphics Processor -> Advanced and/or updating video drivers. CC 2014 could use some feature your video card does not support and gets slow SW emulation. ... View more

Not really, but they have different versions of Chrome which is the likely reason. You could see if there are any known issues related to that, update JS libraries, etc. ... View more

Just want to point out that a background layer is format specific. I.e. if you create a doc with transparent background, it does not have a background. And flattening a doc without background does not create one. Also in case you need to check per-layer, see function below isAreaEmpty: function (left, top, right, bottom) {   var selection_area = new Array(new Array(left, top), new Array(right, top), new Array(right, bottom), new Array(left, bottom))   var selection = app.activeDocument.selection   selection.select(selection_area)   try {   selection.copy()   } catch (e) {   return true   } finally {   selection.deselect()   }   return false }, ... View more

If I understood you correctly you I you could have a company plugin/panel and a bunch of jsx files on server. When panel is opened it would check if any of the jsx has updated (e.g. one service for returning a list of jsx-files and versions) and download changed ones. That said, sounds like an uphill battle trying to force Photoshop into something it's not. One question is how often will those droplets change? If it's like ~monthly, then bundling everything as a zxp (you can include multiple things in one) and distributing those through corporate IT infra (in anycase you need some to maintain network shares & such) might be simpler. ... View more

Can you post a PSD that replicates issue? Like JJ said, bounds is an array of left, top, right, bottom, you have to calculate center (your original script just used [0], [1]). I have not experienced issues with bounds showing wrong values, but that is not to say it could not happen as a per-PSD issue. One thing to try is to create new PSD and copy content and see if that changes result. Another thing you can try is using explicit .value.as("px"), there were some situations where setting .rulerUnits = Units.PIXELS did not fix the default conversion. ... View more

One has to remember that there's quite a few years between PS5.1 and CC (2012) that is still getting updates so it's inherent that there will be differences that you will need to handle. Probably when they discovered the issue, CS5 no longer got updates. And Adobe is maybe a bit erratic here, I've been fighting with paragraph text bounding box extents that has very different behaviour in Win/Mac CS6/CC2012/CC2014 that also changes every so often in updates. My other point was that a layer can lots of things that can be rasterized and just calling .rasterize() will not get rid of all of them. So unless you need tight control (e.g. "rasterize shape, keep layer style") merging to an empty layer is the easiest way to get rid of all non-raster content. ... View more

If you want to rasterize everything in the layer (e.g. shape, smart objects, styles, smart filters), simplest way is to create an empty layer below and merge to it. ... View more

Is there some issue in enabling one layer comp, using doc.saveAs, enabling next comp, etc. in a script? If it's just having in one PDF, you'd probably be better off merging output PDFs manually. ... View more

I would say flattening is more reliable, i.e. then it does a render to specific resolution and should work the same way in any computer with same version of PS. However screenshot depends on monitor resolution, window size, possibly even graphics card drivers (i.e. if Photoshop is compatible with using HW acceleration in your card or not). Try zooming a bigger than screen doc in and out and you'll see pretty big distortions depending on zoom level. I'd try. ... View more

Do you have a reason to take a screenshot, i.e. having Photoshop UI included in the shot? Can you explain what you are trying to achieve more closely. Why do you take a screenshot of a file you load to be saved to a file, what changes? In general I'd recommend to use Photoshop scripting to automate what you would do manually in Photoshop like 1) Open template document 2) Open content document 3) Duplicate content layer in template and position it 4) Duplicate template doc 5) Flatten the duplicate and save to disk 6) Delete content layer from template and close content doc 7) go to 1) ... View more

Thanks on both links! Need to do some more profiling what the actual bottlenecks are and look into optimizing those. ... View more

Started cleaning the relevant code and noticed I had the the layer selection (loop through layerSet.artLayers) in the measurement and turns our that was the culprit and not the artLayer.textItem.contents! Makes more sense (i.e. more layers means slower), but is worrysome as it's really pervasive and hard to get rid of. Also it's a bit alarming that it seems to be based on doc size, not group size. This was group with 6 layers, no children and looping through them like below takes 2700ms for (var i=0; i < group.artLayers.length; i++) {      var layer = group.artLayers      // do stuff with layer Now dug deeper and turns out there are lots of things to improve using artLayer.getByName() is much faster and takes only 90ms. Can't use it for everything, but definitely worth optimization to differentiate the cases! strangely using group.layers and adding "if layer.typename == "ArtLayer" only takes 1300ms so worthy optimization storing artLayers.length in local variable speeds it further to 900ms so worth doing storing group.artLayers as local variable had no major change iterating as "for (var layer in group.artLayers) {}" does not seem to work No difference between 32/64bit CC 2012 in Windows CC2014 seems a bit slower (~20%) Mac seems a bit faster (~20%) than Windows I do a lot of finding layers with certain prefix/regex which looks like a big performance hole. Never thought this would be so big and was wondering if you could do this in AM code? ... View more

File size you can get from File.lenght: var f = new File(path) var l = 0 if (f.exists) l = f.lenght f.close() f = null Dimensions is probably hard ... View more

Not really sure if I get it, but have you tried making the layer a point-text (not paragraph) so it doesn't wrap and then add line changes to the places where it should break? Also there are lots of invisible chars that would not break, but then that is an issue if its code and needs to be parsed. Maybe if you can swap the chars back to spaces before parsing. ... View more

You are right, it's not linked even if you use "File->Open as Smart Object".. Doesn't seem to be a way in API to create linked ones ... View more

Also you should be able to use application.open(file, OpenDocumentType.PHOTOSHOP, true) to open a file as a smart object and the duplicate it to your target doc. If you do the same in UI, it should create a linked smart object. ... View more

One risk is that you'd be violating Photoshop EULA doing that (at least if offering it for other people). Also several such services exists and you might want to look into just building something on top of them. Third point/idea is to take some existing image manipulation library like ImageMagick and mapping that with a web/Javascript API (those probably exist too) so you don't have to do whole stack. ... View more

Taking above even further, you could first add just one characters and establish base line height estimate if you can't have it static. You could even keep adding chars until you get a wrap to estimate both line height and line space. height_after_wrap = 2*original_height+line_space  <=> line_space = height_after_wrap -  2*original_height ... View more

Probably not like you say, but maybe you could achieve it in some other way. So if you mean you have a transparent layer with one just one pixel (or one solid block), you can find out coords by trimming it twice and noting how the dimensions change. So create an empty doc of same size, duplicate your layer there and trim it to find out x and y. Then you can keep running current script with those params or maybe eval a new script. As an example see trimDocument: function (doc) {   if (doc) {   var extents = {}   var orig_w = Photoshop.getDocumentWidth(doc)   var orig_h = Photoshop.getDocumentHeight(doc)   doc.trim(TrimType.TRANSPARENT, false, true, true, false)   var x = orig_w - Photoshop.getDocumentWidth(doc)   var y = orig_h - Photoshop.getDocumentHeight(doc)   doc.trim(TrimType.TRANSPARENT, true, false, false, true)   var h = Photoshop.getDocumentHeight(doc)   var w = Photoshop.getDocumentWidth(doc)   return { x: x, y: y, height: h, width: w }   } }, ... View more

It depends a bit on how you are distributing (Addons/ZXP/JSX) and running (Scripts-menu, Flash/HTML-Panel), but have you considered Put the customizable part to a text file, deliver it with your script and read the settings from your binary. Put the customizable part to web server to be downloaded once (even Dropbox. Split your script in plaintext and binary parts and eval the plaintext ... View more

When working with textItem properties it's good practice to always wrap access and have default value (and maybe user warnings), it can just blow up For example sometimes accessing justification gets in a bad state and only help is resetting the setting in UI. ... View more

What values are you getting and what version are you testing with? Can you post the .psd? Like I said, the size has issues with scaling and it varies from version to version. But in CS6 and CC I've not had issues with position. ... View more