I'm curious what the licensing terms of the javascript that creates the RSVP buttons is (http://www.meetup.com/meetup_api/buttons/), and if it could be put out under an open source license?
I'd like to integrate that function into the drupal meetup_events module which is GPL. It also requires some changes to function in that environment. The first is to switch everything to JQuery.noConflict() so that I can use it with the existing jquery in Drupal (1.2 in D6, and the meetup code needs the JSON functions in 1.4).
Additionally, because I will not be fetching the JS from the meetup site, I'm going to have to launch it a bit differently. The oauth id is going to be coming from the Drupal preferences. And, lastly, I'm adding a setting (either automatically or manually, not sure yet) that makes the YES rsvp actually just go to the site, as integrating questions into that popup isn't going to be UI sane.
Anyway, the short of it is: can the licensing terms on that JS file be made open source so that I can take a fork into drupal meetup_events? Would love to have the dynamic RSVP instead of going with just a static link.
> I'd like to integrate that function into the drupal meetup_events module
> which is GPL. It also requires some changes to function in that
> environment. The first is to switch everything to JQuery.noConflict() so
> that I can use it with the existing jquery in Drupal (1.2 in D6, and the
> meetup code needs the JSON functions in 1.4).
> Additionally, because I will not be fetching the JS from the meetup site,
> I'm going to have to launch it a bit differently. The oauth id is going to
> be coming from the Drupal preferences. And, lastly, I'm adding a setting
> (either automatically or manually, not sure yet) that makes the YES rsvp
> actually just go to the site, as integrating questions into that popup
> isn't going to be UI sane.
> Anyway, the short of it is: can the licensing terms on that JS file be
> made open source so that I can take a fork into drupal meetup_events? Would
> love to have the dynamic RSVP instead of going with just a static link.
On 05/21/2012 11:29 AM, Doug Tangren wrote:
<snip>
> Hi Sean. That sounds great. We'd be happy to release it's source under
> the MIT, http://www.opensource.org/licenses/mit-license.php, license.
> We'd be happy to hear about your progress along with way.
Cool. Another way to do that is to reference $ as your own named parameter
in the outer self-executing anonymous function by passing jQuery in as a
param
> Cool. Another way to do that is to reference $ as your own named
> parameter in the outer self-executing anonymous function by passing
> jQuery in as a param
> (function($){
> // $ is safe to use in here.
> })(jQuery);
Is that going to work is this case? given that the jquery library is being dynamically pulled and loaded within the function?
On Mon, May 21, 2012 at 5:17 PM, Sean Dague <s...@dague.net> wrote:
> On 05/21/2012 05:03 PM, Doug Tangren wrote:
>> Cool. Another way to do that is to reference $ as your own named
>> parameter in the outer self-executing anonymous function by passing
>> jQuery in as a param
>> (function($){
>> // $ is safe to use in here.
>> })(jQuery);
> Is that going to work is this case? given that the jquery library is being
> dynamically pulled and loaded within the function?
> Hi Sean. That sounds great. We'd be happy to release it's source under
> the MIT, http://www.opensource.org/licenses/mit-license.php, license.
> We'd be happy to hear about your progress along with way.
