jejacks0n/mercury — comment on commit 4936f9728ab71e111c75dd0f3bae42936ea912cd
File:  line 0
By jejacks0n:

Bleah! That's no good.

I have two potential solutions.. or rather methods to resolution.. I'll be available this weekend, and we could do some Skype screen share/pairing, unless your company would need an NDA agreement (you would have my word, but nothing else), and if that's the case I'd need more info about your setup. I'm guessing that #2 is out of my control.. that seems like it's happening outside of my control, but perhaps pre-compiling them wouldn't be so bad for the gem -- since you'd need to bundle update to get new code anyway. I guess I would've assumed that it keeps them precompiled for things like engines, but I guess not.

For the other issue.. odd.. can you give me more info? eg. browser, etc.

On Oct 7, 2011, at 9:48 PM, Will Clark wrote:

> Glad I could contribute something useful, even if just a partial line change : )
>
> No rush in answering the following, I see you've been busy addressing others lately.
>
> So, when you get a chance in the next few weeks, I'm running into two scenarios using the latest code of Mercury:
>
> 1. I can't load the editor unless I include mercury_loader.js (which then loads the editor by default).
> 2. I keep getting 500s in production mode saying mercury_loader hasn't been precompiled.
>
> I'm sure I'm missing something obvious that will really embarrass me, but for not I'm just not getting anywhere.
>
> Have a good weekend and thanks again.
>
> - Will
>
>
>
>
>
> On Oct 7, 2011, at 6:49 PM, Jeremy Jackson wrote:
>
>> Cheers!
>>
>> --
>> Reply to this email directly or view it on GitHub:
>> https://github.com/jejacks0n/mercury/commit/4936f9728ab71e111c75dd0f3bae42936ea912cd#commitcomment-638578
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/jejacks0n/mercury/commit/4936f9728ab71e111c75dd0f3bae42936ea912cd#commitcomment-638648