Does anyone know if we make JSTalk files conform to the
com.netscape.javascript-source uti, will QL automagically pick up on
that?
And along with this, any objections to a UTI like this? What URL
should we use?
<key>UTExportedTypeDeclarations</key>
<array>
<dict>
<key>UTTypeConformsTo</key>
<array>
<string>com.netscape.javascript-source</string>
</array>
<key>UTTypeDescription</key>
<string>JSTalk JavaScript Document</string>
<key>UTTypeIdentifier</key>
<string>com.flyingmeat.jstalk.jstalk</string>
<key>UTTypeReferenceURL</key>
<string>http://github.com/ccgus/jstalk/tree/master</string>
<key>UTTypeTagSpecification</key>
<dict>
<key>public.filename-extension</key>
<array>
<string>jstalk</string>
</array>
<key>public.mime-type</key>
<string>application/x-jstalk</string>
</dict>
</dict>
</array>
--
August 'Gus' Mueller
Flying Meat Inc.
http://flyingmeat.com/
> And along with this, any objections to a UTI like this? What URL
> should we use?
Nevermind, I'm an idiot. I forgot I registered jstalk.org a while
back :)
I just need to point it at my server and set some stuff up.
-gus
> Does anyone know if we make JSTalk files conform to the
> com.netscape.javascript-source uti, will QL automagically pick up on
> that?
And as it turns out, it does. So the next build of JSTalk will work
with QL automagically, and it'll have a new bundle id as well.
thanks,
-gus