Capability for more than one Tab in the Ace Pane.
Is there a way to have more than one tab through ember-ace?
I had been changing the value attribute to handle different documents, but this is not ideal. For one, undo functionality gets confused. I think the intended Ace approach for doing this is to use a new Tab for each document.
I haven't seen an in-Ace notion of tabs — is there documentation for that somewhere?
You're definitely right that changing the value attribute can lead to some weird behavior. You can actually see that Ember Twiddle has the same problem with their CodeMirror integration when you switch between documents.
I have a half-baked addon that I've been using to manage tabs external to the editor itself, though there you have essentially the opposite problem: when you switch tabs within a pane and then switch back, the undo history is lost because the component is completely torn down. I could imagine interacting with the editor's UndoManager to persist this as part of document state, but it's not something I've looked into much.
This is the documentation I was looking at for tabs: https://apidoc.c9.io/c9v3/?mobile=/api/tabManager
On May 8, 2017 3:55 PM, "Dan Freeman" [email protected] wrote:
I haven't seen an in-Ace notion of tabs — is there documentation for that somewhere?
You're definitely right that changing the value attribute can lead to some weird behavior. You can actually see that Ember Twiddle has the same problem with their CodeMirror integration when you switch between documents.
I have a half-baked addon https://dfreeman.github.io/ember-leadlight/ that I've been using to manage tabs external to the editor itself, though there you have essentially the opposite problem: when you switch tabs within a pane and then switch back, the undo history is lost because the component is completely torn down. I could imagine interacting with the editor's UndoManager to persist this as part of document state, but it's not something I've looked into much.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dfreeman/ember-ace/issues/9#issuecomment-299988274, or mute the thread https://github.com/notifications/unsubscribe-auth/AA5rOi8tkvPwwLPzVrKCkUvVU8seGZCTks5r34FHgaJpZM4NUVQ3 .
There's a (fuzzy) distinction between Ace itself, which is just the editor, and the Cloud9 platform as a whole, which includes all the rest of the "IDE stuff" like tab/pane management, a debugging framework, and other things outside the core functionality of editing code.
The stuff at apidoc.c9.io is API documentation for the Cloud9 platform as a whole, while ace.c9.io has docs specifically for Ace.
Ah. I see. Thank you.
On Tue, May 9, 2017 at 9:31 AM, Dan Freeman [email protected] wrote:
There's a (fuzzy) distinction between Ace itself, which is just the editor, and the Cloud9 platform as a whole, which includes all the rest of the "IDE stuff" like tab/pane management, a debugging framework, and other things outside the core functionality of editing code.
The stuff at apidoc.c9.io https://apidoc.c9.io/c9v3 is API documentation for the Cloud9 platform as a whole, while ace.c9.io https://ace.c9.io/#nav=api has docs specifically for Ace.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dfreeman/ember-ace/issues/9#issuecomment-300183311, or mute the thread https://github.com/notifications/unsubscribe-auth/AA5rOtP0ne6wAtMWbkkHET9eyG2IF3x9ks5r4HiqgaJpZM4NUVQ3 .
It's entirely possible that there could be value in an addon wrapping up the Cloud9 platform as a whole — I haven't looked into it in much depth because I haven't needed a lot of the other specific aspects of it. The core is also at alpha status right now, so I'd be a little nervous to start building against it, but that doesn't mean it's not worth investigating 🙂
In pure JS, it's much easier in ember ;) https://codepen.io/vincentmolinie/pen/bjBPvg