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

Conversation

@RaymondLim
Copy link
Contributor

No description provided.

@ghost ghost assigned peterflynn Oct 31, 2012
@peterflynn
Copy link
Member

"tinycolor-min.js" is a third-party library. I wonder if we should move this into the core src/thirdparty folder, or leave it under the extensions/default subfolder? @njx, @gruehle, @pthiess, any thoughts on that?

@peterflynn
Copy link
Member

We should add TinyColor to the NOTICE file in the root of the repo either way, though.

@peterflynn
Copy link
Member

Related note: all the .js and .css files need to have our standard MIT license header added.

@GarthDB
Copy link
Member

GarthDB commented Nov 1, 2012

Super stoked for this.

Thanks Raymond.

Copy link
Member

Choose a reason for hiding this comment

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

Should align the "=" signs, like in our other modules

@peterflynn
Copy link
Member

I'm seeing a bug where hitting Esc to close the color picker doesn't restore keyboard focus to the host editor. I'm not entirely sure how that works for regular inline editors, so I'd suggest filing a bug to tackle after this is merged (but before the user story is DoD'ed). @RaymondLim, can you do that?

Copy link
Member

Choose a reason for hiding this comment

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

Remove the return keyword (this seems to be a functional-programming CoffeeScript-ism)

…erwise, we won't be able to remove the current color picker with the already deleted bookmark.
… not use a variable to hold the colorPicker that we want to delete. Instead, we can just delete it first and then clear bookmarks.
@peterflynn
Copy link
Member

Just reviewed all the updates -- I'll post all my comments in one batch now.

Copy link
Member

Choose a reason for hiding this comment

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

We might not want to make this an official public API yet -- not sure we have time to think through exactly what the right API is that will serve all the various use cases (e.g. warning markers, etc.). For now it seems ok to have the color editor code just reference _codeMirror directly.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK, I removed it and just directly call _codeMirror in color editor code.

@peterflynn
Copy link
Member

One other comment: can we rename the "helper" folder to "thirdparty"?

@peterflynn
Copy link
Member

Done re-reviewing

@RaymondLim
Copy link
Contributor Author

For consistency I go ahead and update "helper" to "thirdparty".

-Removed _colorPickers map and the corresponding code.
-Added color swatches to tab loop.
-Renamed some handlers xxxFocus() -> xxxKeyDown().
-Removed some redundent "return" keyword.
@peterflynn
Copy link
Member

Alright, I think we're in a good enough state to merge!

peterflynn added a commit that referenced this pull request Nov 15, 2012
Adding inline color editor to core
@peterflynn peterflynn merged commit b2e1dc7 into master Nov 15, 2012
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.

5 participants