Re: [Radiant] trouble packaging extension as gem

2010-01-29 Thread Josh French
thanks to some off-list help from Josh French the extension now works as either a gem or traditional vendored extension. the key change was just to add `unloadable` to the KramdownFilter class. John, I just pushed a change which should make that unnecessary. Gem extensions are now

[Radiant] trouble packaging extension as gem

2010-01-26 Thread Josh French
i'm at loss now for why it's not appearing in the drop down when loaded as a gem. no errors or anything unusual just a missing filter. I'm actually at a loss as to why it would appear when vendored if you're not explicitly loading that subclass. Radiant doesn't do any pre-loading of filter

Re: [Radiant] trouble packaging extension as gem

2010-01-26 Thread john muhl
On Tue, Jan 26, 2010 at 8:32 AM, Josh French j...@digitalpulp.com wrote: i'm at loss now for why it's not appearing in the drop down when loaded as a gem. no errors or anything unusual just a missing filter. I'm actually at a loss as to why it would appear when vendored if you're not

Re: [Radiant] trouble packaging extension as gem

2010-01-26 Thread john muhl
just noticed that extracting the textile_filter extension out into a gem also fails in the exact same ways that i've run into... On Tue, Jan 26, 2010 at 9:13 AM, john muhl johnm...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:32 AM, Josh French j...@digitalpulp.com wrote: i'm at loss now for why

[Radiant] trouble packaging extension as gem

2010-01-26 Thread Josh French
def activate KramdownFilter end is not explicitly enough? Sorry, misread your post. Yes, this is correct, and you shouldn't need to do anything else. just noticed that extracting the textile_filter extension out into a gem also fails in the exact same ways that i've run into...

[Radiant] trouble packaging extension as gem

2010-01-25 Thread john muhl
i hope someone can point out what stupid thing i've done in my first attempt to package an extension as a gem. http://gist.github.com/286072 the extension works fine as a regular extension. i'm trying this on the edge (current as of about an hour ago).

Re: [Radiant] trouble packaging extension as gem

2010-01-25 Thread Jim Gay
On Jan 25, 2010, at 1:08 PM, john muhl wrote: i hope someone can point out what stupid thing i've done in my first attempt to package an extension as a gem. http://gist.github.com/286072 the extension works fine as a regular extension. i'm trying this on the edge (current as of about an

Re: [Radiant] trouble packaging extension as gem

2010-01-25 Thread Sean Cribbs
Actually, I imagine :lib = false would do the trick -- gem requirements are loaded before extensions. As long as your extension file explicitly loads that text filter, you should be fine. Sean On 1/25/10 1:51 PM, Jim Gay wrote: On Jan 25, 2010, at 1:08 PM, john muhl wrote: i hope

Re: [Radiant] trouble packaging extension as gem

2010-01-25 Thread john muhl
both suggestions seem to fix the boot problem but now i don't see the new filter in the drop down. although i do see the extension listed on the extensions page. On Mon, Jan 25, 2010 at 1:05 PM, Sean Cribbs seancri...@gmail.com wrote: Actually, I imagine :lib = false would do the trick -- gem

Re: [Radiant] trouble packaging extension as gem

2010-01-25 Thread john muhl
by explicitly loads that text filter you just mean having: def activate KramdownFilter end right? i'm at loss now for why it's not appearing in the drop down when loaded as a gem. no errors or anything unusual just a missing filter. On Mon, Jan 25, 2010 at 1:05 PM, Sean Cribbs