Using File Tools in Stand Alone App

scalf's picture

Hello,

I am using the "open panel" patch from the Kineme File Tools in a test application.

I can get all the other interactions to work - click, osc in/out, syphon in/out - but no open panel.

I though this might be from xcode not letting that action happen but I am not sure. has anyone else encountered this? Of course, the composition behaves as should when tested inside Quartz Composer on 10.8

All I need for it to do is look at a certain image or folder in the end product. Can this be coded via opening up a port for the file location and doing the opening dialogue in xcode? Or is there a way to rearrange the composition so this might work?

Thanks for any suggestions

PreviewAttachmentSize
QuartTest~.qtz14.5 KB

franz's picture
Re: Using File Tools in Stand Alone App

you'd better do this in xcode directly and pass the path to your composition. look for NSOpenPanel

gtoledo3's picture
Re: Using File Tools in Stand Alone App

The patch has a string in it somewhere that tells it what apps it can open in, so that it doesn't randomly spam stuff like Quicklook.

If you get the source, check that out, add your app identifier, recompile.

What franz is saying might not be a bad idea. That said, I've made custom plugins that do other stuff like this, and it seems ok. No reason it shouldn't work.

smokris's picture
Re: Using File Tools in Stand Alone App

Yes, check out https://github.com/kineme/FileTools/blob/master/FTOpenPanelPatch.m#L21 and customize with your app bundle's identifier.

scalf's picture
Re: Using File Tools in Stand Alone App

Very cool.

This should be really sweet, thanks for the pointers!

I'll post what comes up

gtoledo3's picture
Re: Using File Tools in Stand Alone App

scalf wrote:
Very cool.

This should be really sweet, thanks for the pointers!

I'll post what comes up

It's kinda a really cool aspect of QC that people overlook. The "climb window app" plugin has a similar kind of principal (standard API). It's neat to create GUI or windows in code, or Interface Builder and be able to load it via plugin.

scalf's picture
Re: Using File Tools in Stand Alone App

I think it has great potential, yes!

So I got into the xcode plugin, changed the target to my machine correctly, but it gives me a "no such file" in reference to the SkankySDK.

I assume it's because I did not have it included. So I went and got it from the Hub. A.k.a. Xcode Template??

Open it up, and I try to install. This is where I got to this morning. How do I appropriately run the install.sh file? I tried a few commands (sh install.sh) from terminal but it did not copy it correctly as I got these "No such file or directory" for every listing after each command attempt.

Is this because the shell script does not reflect the file hierarchy of 10.8? Or is it because I don't have the right install approach?

Any help would be awesome

scalf's picture
Re: Using File Tools in Stand Alone App

went with the sudo command this time as listed on the back version of Skanky. Still got the same error

First Error: "/Developer/Library/Xcode: no such file exists"

scalf's picture
Re: Using File Tools in Stand Alone App

Figured out how to build correctly.

I had to change the install.sh file to accept the current developer related file hierarchy found in 10.8

I will conclude with more testing in a few

#!/bin/sh
 
cp -R sdk/Project\ Templates /Users/"    "/Library/Developer
cp -R sdk/File\ Templates /Users/"    "/Library/Developer
mkdir -p /Library/Frameworks/SkankySDK.framework
cp -R include /Library/Frameworks/SkankySDK.framework/Headers
cp -R resource /Library/Frameworks/SkankySDK.framework/Resources
<code/>