On Monday, January 13, 2014 8:29:02 PM UTC+1, Rob McBroom wrote:
> Most of what you see in the interface can be expressed as a property list.
> So there could be some new thing that just needs the path to a command (or
> it could just run every script in a particular directory). You write the
> command and have it spit out a property list.
>
>From Quıcĸsıɩⅴεʀ User’s Guide 0.14, p 33
'The Defaults Reader allows you to index some keys from preferences files
(.plist), though it’s a little flakey (doesn’t deal well with paths), is
difficult to configure (you must manually specify each key) and doesn’t let
you change the plist file, so it doesn’t seem useful.'
I haven't tried it yet and I couldn't find any details nor issues in the
tracker. Does it still work?
Would specifying an AppleScript Object Type be a feasible workaround?
For instance, if I could specify a (custom) 'qs.object' for AppleScript
actions, I could use any form of preset source or run a script with cron to
update a file with something QS can parse.
on get direct types
return {"qs.object_Custom_MyCatalog"}
return {"qs.object_Custom_MyDefaultsReader"}
return {"qs.object_Custom_MyGroup"}
return {"qs.object_Custom_MyCustomCatalog.txt"}
end get direct types
on get indirect types
return {"qs.object_System_Devices"}
end get indirect types
on get argument count
return 2
end get argument count
I think, it'd be just redirecting or making existing objects available for
AppleScript (and everything you could bridge with it).
--
You received this message because you are subscribed to the Google Groups
"Quicksilver" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/blacktree-quicksilver.
For more options, visit https://groups.google.com/groups/opt_out.
