On May 7, 2013, at 2:51 AM, Andreas Johansson <[email protected]> wrote:
> That might be possible, but I figured that since I import the Chrome app > specifically I would have to do the same to make it work with Canary. But I > guess the Scripting Bridge interface is more dynamic than I thought. The purpose of importing Chrome is just so you can auto-generate the header file on build. So if that header works for Canary, that should be all you need. (Lately, I’ve taken to just generating the header manually and adding it to the project because having entire applications in there makes “Find in Project” awful. The downside is that you have to manually keep up with changes in the application’s scripting dictionary, but those are pretty rare.) > Anyway, I need to do more changes in the plugin to make it work properly with > Canary. The plugin won't be recommended in QS if only Canary is installed > (can you set that a plugin depends on app A or app B or both?), and I need to > enable right arrow children for Canary. You can have it recommended for either, but if you list both as a requirement, the plug-in won’t load unless both are present. Maybe a separate fork is the way to go after all. :-) -- Rob McBroom <http://www.skurfer.com/> -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
