This would be great! If implemented, I'd be happy to help out with anything I could manage to help take some workload off the devs.
On Thursday, May 1, 2014 6:14:52 AM UTC+9, Tony wrote: > > Ok, just created issue #1834 > https://github.com/quicksilver/Quicksilver/issues/1834 which outlines > this in a bit more detail. > > > Tony > > > From: Lucas Garron [email protected] <javascript:> > Reply: [email protected] <javascript:> > [email protected] <javascript:> > Date: April 29, 2014 at 7:48:15 PM > To: Blacktree Quicksiler Mailing List > [email protected]<javascript:> > Subject: Re: Should we move example AppleScripts to github > > If this happens, we should also consider tackling shell scripts at the > same time. > > I, for one, am using a AppleScript files as simple wrappers for a lot of > shell scripts just so I can use them as QS objects/actions easily. I would > love to maintain them as *what they really are* (shell scripts) instead. > > Part of the pain for that also involves $PATH, and figuring out how to > move around stdin/stdout/stderr. > > »Lucas Garron > > > On Tue, Apr 29, 2014 at 7:29 PM, Patrick Robertson > <[email protected]<javascript:> > > wrote: > >> That sounds like a really good idea, and not too difficult I don’t think. >> Perhaps a v2.0 feature. >> >> Could you please create an issue on GH referencing this topic, and >> including the major points? We’d still need someone to review and manage >> any AS plugins that are sent, but my idea is that any submissions could >> just be sent straight to the QS Dev group for review/discussion. >> >> >> On 29 Ebrill 2014, at 02:43, Tony Papale >> <[email protected]<javascript:>> >> wrote: >> >> What about making scripts first class citizens like plugins? I think >> as is scripts are very under utilized because as everyone is saying they >> aren’t centralized so its difficult to find them, install them, and update >> them. >> >> QS already has an *awesome* plugin system that handles updates, version >> dependency, etc. so if we can just bundle scripts into pseudo plugins or >> perhaps create their own format that would significantly increase their >> adoption and creation. Long term it would also be cool to add a simple >> script creator right into the pref pane which would just take a name, >> description, and code. >> >> Thoughts? >> >> Tony >> >> From: philostein [email protected] <javascript:> >> Reply: [email protected] <javascript:> >> [email protected] <javascript:> >> Date: April 28, 2014 at 4:09:14 AM >> To: [email protected] <javascript:> >> [email protected] <javascript:> >> Subject: Re: Should we move example AppleScripts to github >> >> Yes, good idea. >> >> I'd like to volunteer for this, either managing it or helping out with >> it. I'd probably need a bit of advice about GitHub from time to time, and I >> tend to contribute in spurts. :) >> >> It'd also be a good way to host AppleScripts in blog posts and tweets. >> >> On Monday, April 28, 2014 9:44:27 AM UTC+9, Patrick wrote: >>> >>> I was thinking about this the other day, the current wiki solution is >>> not very user-friendly, and does not really promote sharing of >>> AppleScripts. GitHub might still be a little too ‘advanced’ for your >>> layman, but it’s probably a good place to start for storing them all in one >>> place. >>> Perhaps ideally we could have an email address for submitting >>> Applescript Actions, and then have one person manage a dedicated portion of >>> the website, similar to what say… Alfred have. >>> >>> On 28 Ebrill 2014, at 06:42, Lucas Garron <[email protected]> wrote: >>> >>> I've been meaning to collect them and start a pull request to add >>> Applescript actions into the Extra Scripts plugin. Since a lot of them are >>> of interest to many people without modification, it makes sense to share >>> them. >>> >>> »Lucas Garron >>> >>> >>> On Sun, Apr 27, 2014 at 12:01 PM, David Rees <[email protected]> wrote: >>> >>>> It occurs to me it might be better if the example AppleScripts were in >>>> github rather than the wiki. That way folks can submit tweaks easily (and >>>> they are easy to sync). And we would just have links in the wiki. >>>> >>>> I've thought about just putting mine in my own repository, but a shared >>>> one would probably be better. >>>> >>>> -- >>>> 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/d/optout. >>>> >>> >>> >>> -- >>> 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/d/optout. >>> >>> >>> -- >> 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/d/optout. >> >> >> -- >> 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/d/optout. >> >> >> -- >> 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/d/optout. >> > > -- > 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/d/optout. > > -- 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/d/optout.
