Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editor: Mobile editor redesign (phase 2) #4686

Conversation

DanReyLop
Copy link
Contributor

This PR includes the following changes on the mobile editor:

  • Move the action bar to the metadata tab
  • Move the Site information to the main editor tab, plus the status and the date when the post was published
  • Make the Noticebar appear on both tabs, and make it disappear when the user changes the tab

Note that this PR follows #4456. The code on this branch (update/4266-mobile-editor-redesign-2) is the complete redesign, but the diff between update/4266-mobile-editor-redesign-2 and update/4266-mobile-editor-redesign is only the changes I've listed above. Please tell me if there is a less confusing approach to managing this :)

cc / @aduth @alisterscott @folletto

@lancewillett lancewillett added [Feature] Post/Page Editor The editor for editing posts and pages. [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Apr 12, 2016
@alisterscott
Copy link
Contributor

I had a quick look as is and I'm seeing a console error: Uncaught TypeError: this.props.onTabChange is not a function Are you aware of this?

@@ -73,7 +81,10 @@ export default React.createClass( {
aria-label={ this.translate( 'Show advanced status details' ) }
aria-pressed={ !! this.props.advancedStatus }
>
<Gridicon icon="cog" size={ 16 } />
{ this.props.advancedStatus
? <Gridicon icon="chevron-up" size={ 18 } />
Copy link
Member

Choose a reason for hiding this comment

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

This is a regression, should be cog icon.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's an downward / upward arrow in the redesign mock-ups. @folletto was this an intended change, or just a copy&paste error or something?

We are talking about this icon:
sin titulo

Copy link
Contributor

Choose a reason for hiding this comment

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

The design was done before that change went in production. So it's misaligned, and it should be a cog. Sorry about that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No problem, that's what happens when stuff changes, fixed :)

@mtias
Copy link
Member

mtias commented Apr 13, 2016

@DanReyLop hey, do you mind including a screenshot on the description showing where this is at for easy reference?

@folletto
Copy link
Contributor

Quick screenshots:

screen shot 2016-04-13 at 11 14 01

With author:

screen shot 2016-04-13 at 11 16 09

@@ -343,11 +323,26 @@ const PostEditor = React.createClass( {
site={ site }
type={ this.props.type }
/>
<div className="editor__site">
Copy link
Member

Choose a reason for hiding this comment

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

This class would be a bit misleading given that it also includes the status. I'd look for a better name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The main component in that bar is the site, the status is like an small add-on. Also, I'm trying to rationalize my decision because I can't come up with a better name, if you do I'll search&replace it :)

@mtias
Copy link
Member

mtias commented Apr 13, 2016

I think we should only have one notice and change focus to content. Alternatively, we may want to switch to global-notices for this.

@DanReyLop
Copy link
Contributor Author

@folletto Thanks for the screenshots.

@alisterscott I'm not having that console error. Did you try running make run again?

@mtias I think presenting the notice in the tab where the user is would be less confusing. About the other comments, I'll wait to fix them until we decide if we change the approach to this redesign.

@alisterscott
Copy link
Contributor

@alisterscott I'm not having that console error. Did you try running make run again?

All good now thanks! I ran make distclean

@DanReyLop DanReyLop force-pushed the update/4266-mobile-editor-redesign branch 2 times, most recently from 4c73528 to 19ab894 Compare April 20, 2016 22:32
@DanReyLop DanReyLop force-pushed the update/4266-mobile-editor-redesign-2 branch from 390b54b to bdf6ed2 Compare April 20, 2016 22:34
@folletto
Copy link
Contributor

I left a few comments trying to solve some of the questions. I hope that's enough. :)

Once these are sorted, would be possible to have a list of what's still pending (if anything) in order to get this merged? This is a big change so I feel would be useful to have a "We're here" overview. :)

@DanReyLop
Copy link
Contributor Author

Well, if you agree with the latest changes, there should be nothing pending. I would need to:

  • Rebase mobile-editor-redesign and mobile-editor-redesign-2 (this one) to be updated with master. Since this one is a superset of the original PR, it would be easier to just use this and discard the other branch.
  • Change the target of this PR so if goes from mobile-editor-redesign-2 -> mobile-editor-redesign to mobile-editor-redesign-2 -> master. I prefer to do it after it's ready to ship because the resulting PR would be really hard to review.

@DanReyLop DanReyLop force-pushed the update/4266-mobile-editor-redesign branch from 19ab894 to ea7ba8d Compare May 23, 2016 11:27
@DanReyLop DanReyLop force-pushed the update/4266-mobile-editor-redesign-2 branch from ad42159 to 0973d8e Compare May 23, 2016 11:47
@DanReyLop
Copy link
Contributor Author

I've updated this PR and #4456 with master. It was not an easy merge, but it appears that everything is working fine. Please don't let this PR rot :)

As I said, this PR and #4456 have a different set of commits to make them easier to review, but they need to be deployed at the same time (or better yet, just deploy this one and close the other).

The tip of this branch has all the code of the mobile editor redesign, so if you're testing locally, it's enough to test this branch.

@alisterscott
Copy link
Contributor

You can test this live on real devices using: https://calypso.live/?branch=update/4266-mobile-editor-redesign-2

@alisterscott
Copy link
Contributor

alisterscott commented May 24, 2016

I've tested this today:

  1. What determines which 'view' is shown upon loading the editor? When adding a new post, sometimes I saw the edit view, and sometimes the actions view. I would prefer to start on the edit view.
  2. Bug: Featured image cuts across the site title on the edit view, see screenshot below
  3. Bug: Editing the featured image above the editor in the edit view means it doesn't then show in the actions view. See screenshot below
  4. Bug(s): the cursor from the editor shows on the actions screen, and as a result of this, when returning to editor the text is sometimes under the toolbar and can't be accessed - see screenshots below
  5. Bug: in desktop view, when expanding a couple of the sidebar areas if there's not enough vertical room, the back button/drafts loses it's padding - see screenshot below

Featured Image Over Site Title

editor mobile - 1

Featured Image that was edited above editor

featured image empty - 1

Cursor on actions screen

cursor on actions screen - 1

Switching back to edit screen when cursor shown

editor under toolbar

Desktop back/drafts loses spacing when expanding side areas

screen shot 2016-05-24 at 11 40 12 am

@mtias mtias added [Status] Needs Author Reply and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels May 30, 2016
jonathansadowski and others added 2 commits June 6, 2016 17:00
DanReyLop added 22 commits June 13, 2016 09:52
…itor view and it appears in the metadata view
@DanReyLop DanReyLop force-pushed the update/4266-mobile-editor-redesign-2 branch from 0973d8e to d013221 Compare June 13, 2016 11:29
@DanReyLop DanReyLop self-assigned this Jun 13, 2016
@DanReyLop DanReyLop added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. and removed [Status] Needs Author Reply labels Jun 13, 2016
@DanReyLop
Copy link
Contributor Author

Looks like it's not possible to change the target branch of a PR after it's created. I've created a new PR with the @alisterscott comments fixed: #5987

@DanReyLop DanReyLop closed this Jun 13, 2016
@matticbot matticbot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Jun 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Post/Page Editor The editor for editing posts and pages.
Projects
None yet
Development

Successfully merging this pull request may close these issues.