Closed EisenbergEffect closed 11 years ago
Mercury1 is deprecated, yes (as the readme on that branch would suggest).. you might want to wait for mercury2 before using it, in which case your timing might be bad. Mercury1 is still very useful -- though it sounds like you didn't bother reading the current docs.
Mercury2 is still under development (as the notice on that branch specifies), and I'm giving my free time for it. It's much nicer, and way easier to add functionality to and extend. No, it doesn't require an iframe, but it allows for one, as well you can use a shadow dom if the client supports it (it makes it invisible to the dom) -- also covered in the documentation.
The documentation does in fact outlines these things. If you're interested in how to use Mercury2 you may want to follow the steps for development outlined in the documentation. Start the server using rackup, and then browse to http://localhost:9292 to see where I'm at with current development -- there's also a place in the documentation where I direct you to the adding_functionality.coffee file in examples that shows how to integrate and extend Mercury2.
Just look into the examples path on mercury2 for how I'm using it while I'm developing it.
Is it possible to use Mercury 1 without an iframe? If so, how can I do that? I didn't find any docs around that.
On Sun, Apr 21, 2013 at 3:52 PM, jejacks0n notifications@github.com wrote:
Mercury1 is deprecated, yes (as the readme on that branch would suggest).. you might want to wait for mercury2 before using it, in which case your timing might be bad. Mercury1 is still very useful -- though it sounds like you didn't bother reading the current docs.
Mercury2 is still under development (as the notice on that branch specifies), and I'm giving my free time for it. It's much nicer, and way easier to add functionality to and extend. No, it doesn't require an iframe, but it allows for one, as well you can use a shadow dom if the client supports it (it makes it invisible to the dom) -- also covered in the documentation.
The documentation does in fact outlines these things. If you're interested in how to use Mercury2 you may want to follow the steps for development outlined in the documentation. Start the server using rackup, and then browse to http://localhost:9292 to see where I'm at with current development -- there's also a place in the documentation where I direct you to the adding_functionality.coffee file in examples that shows how to integrate and extend Mercury2.
Just look into the examples path on mercury2 for how I'm using it while I'm developing it.
— Reply to this email directly or view it on GitHubhttps://github.com/jejacks0n/mercury/issues/369#issuecomment-16743953 .
Rob Eisenberg, President - Blue Spire www.durandaljs.com
No, there's not sadly. Though it can be integrated nicely to not break things. One of the things I'm trying to rectify with this next version.
Ok. I'm trying to get v2 working...I'm not a rails developer and the app isn't even a web app (it's a desktop app built with node-webkit)....I'm just struggling to figure out how to initialize the editor now....and to re-initialize it when the regions change.
On Sun, Apr 21, 2013 at 4:17 PM, jejacks0n notifications@github.com wrote:
No, there's not sadly. Though it can be integrated nicely to not break things. One of the things I'm trying to rectify with this next version.
— Reply to this email directly or view it on GitHubhttps://github.com/jejacks0n/mercury/issues/369#issuecomment-16745134 .
Rob Eisenberg, President - Blue Spire www.durandaljs.com
Yeah, Mercury2 will be better for that for sure. If you're pressed for time, I'd suggest checking out Aloha Editor or something similar -- or wait for Mercury2 to be finished -- probably another month or two. At this point of development a demo would only detract from what I'm focused on, which is to get it working really well.
I have so many questions...What is the state of Mercury? It looks abandoned. I stumbled on Mercury 2...is that ready yet? How do I use it? Where are the docs? Does it have to use an iframe? Can I use it in a single page app? Can I instantiate it on the fly? How do I even initialize it?
I've got some pretty awesome use cases for this editor...but after a lot of time wasted poking around, I can't seem to find answers to even the most basic questions. Here's something that would be very helpful:
Personally, I'm interested in non-iframe scenarios, since iframes don't work well on mobile or tablet and don't fit single page apps very well. So, I would need to know how to make Mercury not shove my whole UI into an iframe (which is what happended when I tried Mercury 1....resulting in breaking my entire application...and it did it just by including the script...without me initializing anything...which was very surprising.)
Please, please, please, just take 15 or 20 minutes to write something as an act of kindness...so that future developers don't waste hours bumbling around...resulting in nothing but confusion and frustration.