-
Notifications
You must be signed in to change notification settings - Fork 6
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
Annotations redesign #27
Conversation
…ns in mobile layout
…an set annotations height to 100%
…g on desired browser support
… option until library is fixed
…if its in editor mode or pres mmode, changed some node status styles
ok great i'll take a look at this tomorrow or the day after. On Tue, May 24, 2016 at 3:51 PM, Jess Peter [email protected]
|
Closing as reworking some of same functionality/restyling in other branches to different ends. |
@skomputer Was hoping to get your feedback on this in terms of appearance/functionality in addition to elegance of code. I haven't written any unit tests yet as I don't know how substantial the changes I'll have to make will be.
A simple description of this fork would be that it moves the capabilities of GraphEditForm into the annotation list directly, and changes the editing of annotation text/node selection into a triggerable event.
This would close #16, #9, and #11.
My concerns expressed in #16 were echoed by a user I interviewed who expressed his frustration as forgetting if he was in "green or yellow" edit mode, so I was also trying to make changes based on that perspective as well.
An additional change might be to make it so it's always node edit(/"green") mode unless it's in annotation-edit mode, but I haven't gone there yet.
I did run "npm update" as there were a couple changes to medium-react-editor in the past couple weeks to fix bugs in features I didn't end up using (but still...).
There is no rush on this, I just thought it would be a good idea to get your feedback before moving forward with unit tests etc..