Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Implement Splitview #8913

Merged
merged 3 commits into from
Sep 4, 2014
Merged

Implement Splitview #8913

merged 3 commits into from
Sep 4, 2014

Conversation

JeffryBooher
Copy link
Contributor

  • This pr creates a split view of either side-by-side or upper-lower views of 2 different files.
  • From the View Menu select "Split Vertically" or "Split Horizontally" to create a second pane.
  • Selecting the menu item again will collapse the panes down to a single pane (merging the two working sets and showing the current view)
  • Selecting the opposing menu item will just reorient the views without disturbing the documents
  • A blue outline currently denotes the active pane. Functions such as opening a document, searching, etc... will target the active pane. Functions like Close All will target both panes and close all documents.
  • Lint will work on the currently focused editor
  • Images are not supported and viewing images has been disabled in this build
  • The UI as it works now is temporary. A UI treatment story will come next with @larz0 UI treatments

Known Issue:
#8513 (comment)
The selection is getting reworked with @larz0 UI treatment and will be addressed at that time

This is a rebased branch and replaces #8522 for merging into master

@le717
Copy link
Contributor

le717 commented Aug 30, 2014

Curiosity, what is the current time frame for Splitview to land in master? I know my extension breaks as part of the ImageViewer refactoring, and I am trying to work out a time frame for making it compatible.

@JeffryBooher
Copy link
Contributor Author

@le717 We're merging it this week.

@le717
Copy link
Contributor

le717 commented Sep 2, 2014

@JeffryBooher Thank you!

@peterflynn
Copy link
Member

Alright, let's get this puppy onto master...

peterflynn added a commit that referenced this pull request Sep 4, 2014
Implement Splitview (with non-final UI)
@peterflynn peterflynn merged commit 82bb3f7 into master Sep 4, 2014
@peterflynn
Copy link
Member

I'll leave it to @larz0 or @ryanstewart to add the appropriate animated GIF now :-)

@@ -155,6 +155,10 @@ define(function HTMLDocumentModule(require, exports, module) {
self._onChange(event, editor, change);
});

$(this.editor).on("beforeDestroy.HTMLDocument", function (event, editor) {
self._onDestroy(event, editor);
});
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JeffryBooher How come this is necessary for HTMLDocument, but not CSSDocument or CSSPreprocessorDocument? All three of them have a detachFromEditor() that needs to get run...

I'm also not clear on why this change is needed, though. It already listens to "activeEditorChange", which should be enough to always clean up when needed. Was this added for a unit test or something maybe, where the EditorManager events weren't firing?

@JeffryBooher
Copy link
Contributor Author

tumblr_m9trl9hppk1rxlmf0o1_250

@larz0
Copy link
Member

larz0 commented Sep 4, 2014

zr1qb5gkjo5_400

@le717
Copy link
Contributor

le717 commented Sep 4, 2014

It's happening

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants