Re: Documentation query

john beardsworth · ‎Jun 22, 2009

OK, here is how I did it. The key is to set theXML instance so the XML declaration is omitted: local xmlBuilder = LrXml.createXmlBuilder(true) Then you can add the declaration by code, add the XSLT stylesheet link in the same manner, and then the XML blocks. So, assuming FileStr is the name of the XML file and xmlString contains the data you're exporting: Hnd = io.open(FileStr, "w") Hnd:write ( '<?xml version="1.0"?>' ) Hnd:write ( '<?xml-stylesheet type="text/xsl" href="spreadsheet.xsl"?>' ) Hnd:write (xmlString) Hnd:close () John

john beardsworth · ‎Jun 17, 2009

xmlDomInstance:text() appears to work, but isn't documented. I wonder if there's anything else. John

john beardsworth · ‎Jun 17, 2009

And maybe as a feature request, bin the bin default.... John

john beardsworth · ‎Jun 16, 2009

You sure it's not open source? At least the Flash side of it. John

john beardsworth · ‎Jun 16, 2009

Thanks Dave. I'm much more at home on Windows and was wondering if I'd have to go via WSH and VB - the Mac side of it is much less familiar (would have though "du" was a Canadian pronuniciation of "doh"). I guess I've got to decide if I want to return the size of the actual directories, or analyse the target photos by directory. If anything I'm leaning towards the latter, in which case I either battle on building arrays or write and read back some XML . At some point though, I suspect one of us is going to have to give this temporary file approach a go. John

john beardsworth · ‎Jun 16, 2009

Is it possible to specifiy the XSLT file as part of an XML output? I've got XML output working fine, and reading too *, but for this plugin I want all data present in the XML file, and with the XSL summoned in the file's header? Can I do this with the SDK? John * Anyone seen XPATH? Is it missing from the SDK?

john beardsworth · ‎Jun 15, 2009

Thanks both. LrPathUtils was a more direct way of getting what was still the wrong data, as Eric found. As the plug in loops through the target photos, I think I'll just build an array based on the folder paths and pass the images' size to it. Though it'll overlook uncatalogued files in the folders, it should be sufficient for the use I have in mind. John

john beardsworth · ‎Jun 15, 2009

I'm using setRawMetadata in a plugin that allows the user to transfer the value of a chosen field over to another field. Undo appears to work normally, so for example, the user may decide to write the filename to the caption and a subsequent Ctrl/Cmd Z will undo that action and restore the original caption. So I'm pretty sure the plugin is correctly undo mechanism: MyHWLibraryItem.outputToLog("Transfer between fields") catalog:withWriteAccessDo( "Transfer between fields", function() ... However, if the user write the filename to the title field, the undo action "Transfer between fields" appears available, but selecting it fails to restore the previous title. Any thoughts? Bug? John

john beardsworth · ‎Jun 13, 2009

FYI The reason for that Mac/Win code was originally because of these shell differences. On PC, I could use LrShell to launch a PDF directly - just sending its name launched it in Acrobat Reader. That default app approach failed on Mac and I was forced to point LrTasks at Preview. John

john beardsworth · ‎Jun 13, 2009

No offence taken, Dave. I'm now picking up speed with this Lua stuff and am very confident I'm doing some things in a crude and inelegant manner! To get the code looking OK here, I switched to HTML view and then use the pre HTML tag. John

john beardsworth · ‎Jun 13, 2009

Does this snippet from my exiftool plugin help? It's sending mulitple variables to the selected thumbnail (effectively extending Ctrl/Cmd S) . John if WIN_ENV == true then command = '"' .. LrPathUtils.child(LrPathUtils.child( _PLUGIN.path, "win"), "exiftool.exe") .. '" ' .. newUrgency .. ' "' .. phoPath .. '" ' .. newOverwrite quotedCommand = '"' .. command .. '"' else command = '"' .. LrPathUtils.child(LrPathUtils.child(_PLUGIN.path, "mac"), "exiftool") .. '" ' .. newUrgency .. ' "' .. phoPath .. '" ' .. newOverwrite quotedCommand = command end

john beardsworth · ‎Jun 12, 2009

A getRawMetadata approach would work fine here. Life's too short to write that wrapper function! John

john beardsworth · ‎Jun 12, 2009

I'm trying to establish the size of the directory containing a photo, using LrFileUtils.fileAttributes. I can happily return a photo's file size using LrFileUtils.fileAttributes( photo.path) so I suspect the problem is specifying the folder path. According to the manual, LrFileUtils.fileAttributes ( path ) "retrieves the file attributes for the file or directory at a given path." So I'm trying: folderPath = string.gsub( photo.path, photo:getFormattedMetadata('fileName'), '') phoAttributes = LrFileUtils.fileAttributes( folderPath) folderSize = phoAttributes['fileSize'] Any thoughts? John

john beardsworth · ‎May 31, 2009

Thanks Dave - that's good to confirm the approach. It's such a pain to be using Exiftool to do what LR's perfectly-good XMP engine could be made to do! John

john beardsworth · ‎May 30, 2009

OK, let's bounce this one around and see if anyone has an elegant solution! I'd like to read metadata that is in images/sidecars, but which LR doesn't display, and put the information into custom fields. While it would be great to have direct access - ie the SDK should let you read XMP data from files or from the Additional_metadata SQL table - in in its absence I am using Exiftool to extract that information. Where I hit a roadblock is that LRTasks can send the correct command line, but LRTasks.execute only returns a 0 or 1, the OS exit message, and not the Exiftool string. So I'm forced to look at alternatives. One would be to make Exiftool generate a temporary file, and then attempt to read that. Any other ideas - or support for the above feature request ? John

john beardsworth · ‎May 30, 2009

Well, I wouldn't say that's a problem for Adobe to implement - just a quick comparison. The fragility is in the mind of whoever uses the loosely-controlled colour label field for long term metadata! John

john beardsworth · ‎May 30, 2009

Not sure I understand what you are asking, but I think it's that you want to add a section in the Metadata panel that is shown via Window > Metadata Panel. On that assumption, does this help? John

john beardsworth · ‎May 29, 2009

Yes, in one sense I was looking for confirmation, Matt, so thanks. Perhaps getFormattedMetadata really should be able to return the numerical shortcut for the current label? If the label matches a choice in the current Color Label Set, return the number. Otherwise return 0? John

john beardsworth · ‎May 28, 2009

Is it possible to obtain the numerical value of the label? photo:getFormattedMetadata('label') returns the string value, so Red, Yellow etc, or whatever is in the colour label set at the time the value was assigned. I would like to return 6, 7 etc - the goal is to roundtrip the colour to iView/Expression Media. Can this be done? John

john beardsworth · ‎May 24, 2009

Well spotted Eric.I've now isolated the problem to using the most recent version of ExtendScript ToolKit on the Mac and not noticing ESTK3's new preference for the UTF-8 signature. Its default is "Always write signature" which does exactly what it says on the tin - saving the file with the default preference results in the error, switching it to "Never" resolves it. The Mac-PC thing is not a case of LR handling UTF-8 encoded files differently on different OS's. It's simply the result of initially writing the plug-in an earlier version of ETSK which doesn't have this preference. Thanks for your help John

john beardsworth · ‎May 22, 2009

Gene It's the version number of the field - p55 of the PDF. Each time you change the definition of a field, change its version number. John

john beardsworth · ‎May 20, 2009

A plug-in that works correctly on PC is generating an error on the Mac. The plug-in adds a menu command and launches a dialog box, but running it on the Mac produces this error dialog: Internal error has occurred - Invalid parameter not satisfying : aString!-nil . After that error occurs, the PlugIn Manager is unavailable (similar error message) and only becomes accessible after a restart. The plugin is shown to be running, but any subsequent attempt to run the menu item causes the error. To eliminate the menu command's code, I have removed almost all the code, but the same problem happened. I have also replaced its code with code from another plug-in that does work on the Mac. Again no solution. I have also changed the LrToolkitIdentifier and plug-in name. By now, I recognise enough of the messages to suspect that this is an odd one. Any thoughts? John

john beardsworth · ‎May 20, 2009

Thanks Eric, that should help.

john beardsworth · ‎May 19, 2009

On the PC, this launches a file phoPath in that file type's default application - eg a NEF opens directly in Capture NX if it is the Windows default for NEF files: LrTasks.execute('"' .. phoPath .. '"') But it doesn't seem to work on Mac. LrShell.openFilesInApp is no use here because it needs the name of the target application, which I don't want to hard code (because the user may have set some other app as the default). Any thoughts? Can the SDK determine the Mac OS's default application for a file type? Or is there a way to get LrTasks to do the job? John

john beardsworth · ‎May 13, 2009

Your requirement is not at all unusual and I'm actually working on something along those lines. One of the problems is how the list is parsed, and the likelihood of false positives, but it is achievable. As a temporary solution, you can remove the line breaks from your list, so it's "00001.dng 00420.dng 00288.dng 03365.dng" . You then paste this into a smart collection "filename contains ...." John

john beardsworth · ‎May 05, 2009

Lightroom doesn't have a command line interface. What's the bigger picture? Where does Lightroom fit into what you're trying to achieve? John

john beardsworth · ‎May 01, 2009

And the "123, 456 enter"? As soon as you press enter and commit the entry, as it now has keywords, the image should vanish from the smart collection and the next one should be selected. John

john beardsworth · ‎May 01, 2009

Did you set up that smart collection? And instead of "123 enter 456 enter", it should be "123,456 enter". John

john beardsworth · ‎May 01, 2009

Ken, are you keying into the little one line area, not the multiline area? I tested my suggestion before posting. John

john beardsworth · ‎Apr 28, 2009

Set up a smart collection (keywords / is empty) and select the first item. Now Ctrl K (Cmd K if Mac), type your keywords, hit enter. Now type in the keywords for the next one. John

john beardsworth

john beardsworth

Activity

Re: Documentation query

Documentation query

Re: Creating modified default galleries

Re: Creating modified default galleries

Re: Detecting size of a directory

Adding XSLT to XML output

Re: Detecting size of a directory

Undo - does it exclude any fields?

Re: 4000. + a question re external files.

Re: 4000. + a question re external files.

Re: 4000. + a question re external files.

Re: Label value

Detecting size of a directory

Re: Reading metadata with exiftool

Reading metadata with exiftool

Re: Label value

Re: Custom Metadata Panel and Palette

Re: Label value

Label value

Re: Internal error aString!-nil

Re: Schema question

Internal error aString!-nil

Re: Calling default app in Mac

Calling default app in Mac

Re: LRPlugin to mark or filter photos by an extern...

Re: Lightroom Command Line Usage?

Re: Developer needed

Re: Developer needed

Re: Developer needed

Re: Developer needed