Yes, that is really what I would like to do. Better script support could 
open up QS to a much wider range of developers. While optimally I would 
like to have ruby/python/bash, really just better AppleScript would be a 
great step since developers can then use it as a bridge to other languages.

The other thing I would like is the ability to add an object tree to QS 
from a script. For example, I can easily write a script to walk headers in 
google docs, word, orgmode, etc. What I am missing is an easy way to add 
these object/links into the QS catalog. Essentially I'm talking about a 
catalog entry type that allows you to bulk add objects. The most flexible 
would be an applescript that has a "get catalog" action that just returns 
them. That would allow bunding the catalog and "open" handlers in the same 
script file which would be very useful for sharing. 

You could then combine that with the existing Pane 2 scripts functionality 
to do all kinds of things. Even without having to introduce a new object 
type. For example, in a single script file using the "get catalog" action 
and an "open" action I could add the ability to navigate through all my 
orgmode headers and do refile/move/print/delete actions on them.

If you go one step further and say that the "get catalog" action or the 
catalog file can indicate what types the objects it returns are, then you 
can narrow the "open"  actions to only show up for those object types using 
"get direct/indirect types" action. Still all within a single script file.

A less flexible, but perhaps simpler approach to get custom objects into 
the catalog would be a catalog source that points to a file of 
objects/links (perhaps with object types as well). It sounds like Defaults 
Reader may be a specialized example of this, but I can't find any doc on 
how to use it.

d

On Wednesday, June 26, 2013 8:49:41 PM UTC-7, lgarron wrote:
>
> This is moving further in the direction of "Applescipt files as 
> quick/dirty/simple/easy/custom/hackable plugins". I seem to remember some 
> issues about this, but I can't find a general one right now -- does anyone 
> know of one?
>
> »Lucas Garron
>
>
> On Wed, Jun 26, 2013 at 6:09 PM, Jon Stovell <[email protected]<javascript:>
> > wrote:
>
>> That's a good idea. One might need to play with the syntax a little, but 
>> the ability to define a list of choices in the third pane would be great.
>>
>>
>> On Wednesday, June 26, 2013 7:56:57 PM UTC-4, David Rees wrote:
>>>
>>> I had an applescript idea that I think could be very useful. What if 
>>> applescripts could provide their own third pane items items?
>>>
>>> Right now an applescript can indicate a subset of the global catalog by 
>>> indicating the indirect types. But that is filtering against the global 
>>> catalog without any awareness of the first pane object.
>>>
>>> Instead, what if we added a "indirect choices" handler that allowed the 
>>> applescript to indicate a list of third pane choices for the user. The 
>>> script could build and return the third pane choices based on the first 
>>> pane object. QS would show them in the third pane, allow the user to pick, 
>>> then call the open handler normally with the items and selected indirect 
>>> items.
>>>
>>> For example, a script could allow copying text to a particular header 
>>> inside a word document:
>>>
>>> get indirect choices _items_
>>>   -- cool applescript here that looks at _items_ to build a text list of 
>>> choices
>>>   return { "text list of headers in document" }
>>> end get indirect choices
>>>
>>>
>>> Or it could be used to handle variations on the action, for example for 
>>> a "copy to server" script:
>>>
>>> get indirect choices _items_
>>>   return { "normal", "force" }
>>> end get indirect choices
>>>
>>> Or the script could filter the third/indirect items to the ones that 
>>> mattered for the first pane object.
>>>
>>> get indirect choices _items_
>>>   return { "only folders/servers/URLs than make sense for _items_" }
>>> end get indirect choices
>>>
>>>
>>> d
>>>  
>>>  
>>>
>>  -- 
>> 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] <javascript:>
>> .
>> To post to this group, send email to 
>> [email protected]<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/blacktree-quicksilver.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
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.

Reply via email to