Really nice. Great to see someone putting attention into WYSIWYG rather than yet _another_ Markdown editor. And it supports keyboard shortcuts too (cmd-B, cmd-I etc.)!
Only suggestion I'd make is to speed up the transition when the palette moves around, or maybe replace it with a fast fade in/out - the animation gets in the way.
I would say that is the animation itself, intead following me around from the previous point, i would like that just appear below me with a shorter duration, also the style seems a little bit dated.
The main issue is that the bar moves location. It's really jarring. It would be better if it just sprouted above the text I was editing, instead of flying in to position.
Yeah, I think the animation as "move-from-previous-place" is a mistake, in that I don't think it matches our mental model (or my mental model) - I don't think of the toolbar as something that remains tied to the place I was previously editing after I stop editing there.
The transparency is fine maybe a 0.8 in the alpha channel would do the job, the color is there but the gradient is too harsh, the border line is just there with not purpose and lastly the bubble take so long to hide after i am finish with it that annoys me. Other than that is a great project, i will give a shot to the source code later. Cheers
For your projects, do you consider the fact that this component does not depend on a specific framework to be a positive thing? I ask because when I started writing my editor, I considered to go jQuery free, but then I decided to stick with jQuery and create it as a jQuery plugin since people are used to components wrapped this way.
Stay with jQuery but focus on building an awesome media handler.
The other medium-editor repo isnt focusing at all on handling user-uploaded media and that really sucks.
I would switch immediately if you had baked-in integration for
-Youtube inline upload
-Images upload
But again, thats just my opinion. The other repo is pretty significant and gaining a lot of traction but I think they will end up relying completely on 3rd parties to handle assets. I think if you focused on media, you could compete and be a more beginner-friendly editor.
Best of luck to you, I love the Medium editor and may end up sending you some pull requests if you keep this thing going.
Video and image are definitely on the roadmap. As soon as I get the issues related to the standard editor features out of the way I'll begin to implement image and video.
If I were building a project that used jquery, then this would be a good thing.
But these days I prefer things to be as vanilla as possible. jquery is becoming more of a burden than help given how much better modern browsers are becoming.
In the not-too-distant future I picture myself stripping jQuery from my projects, so the less tie-in the better.
How jQuery is a burden beyond the extra 32kb gziped file that the browser have to load? Please don't try the " i am cool because i hate jQuery" mantra. Cheers
Now it's a race, if jQuery Notebook gets up to snuff by the time I need it, I'll use it, if not, Medium Editor it is (personally, I don't care if I have jQuery or not, I'm a pragmatist).
This is something I hadn't tested. I'll take a good look on this issue. This execCommand thing is new to me. I had never used it before I decided to create this editor.
Interesting piece of work - 2 related scroll problems.
When you paste a long piece of text in your editor:
- the palette doesn't position near the text where you double click (it remains at the top of the document)
- any undo action, which change text below the fold doesn't scroll the editor where the change occurs.
Good luck with that promising project. Most people who took the contenteditable route to build an editor (ace and codemirror for instance), eventually decided to fully implement the editor themselves...
But, you need lists. In fact, I'd either document the exact commands you have implemented, or implement all the commands Medium offers, since you're inspired by Medium:
I get why someone might dislike jQuery plugins, but to think that something is "completely useless" by being wrapped in a jQuery plugin is, IMO, a little extreme.
I'm ambivalent to jQuery plugins themselves, as I simply don't use jQuery. Therefore, any code 'wrapped in a jQuery plugin' (as opposed to, for example, writing well-designed, generic JavaScript objects and providing a jQuery plugin wrapper) is useless to me.
As it is to anyone who's not living in the past, where jQuery's presence in an app was an article of blind faith.
It's cool to hate on jQuery right now (for some odd reason), but don't let that get you down. This is an awesome start and I'll definitely be keeping an eye on it.
We do a lot of front-end editing on WordPress and this might make a handy replacement for the bulky tinyMCE that gets used.
If there is any behaviour that you consider weird, or any feature that you think is missing just create an issue on Github. Also, pull requests are more then welcome ;)
This is cool. Is there anyway you could get markdown (or some similar format) to work with it. Essentially this (http://mangomarkdown.com/) but open source. That would be awesome!
It's certainly an interesting challenge to make the plugin output markdown and I have also considered it. I think that if there are people willing to contribute to this feature we could do it.
I think it may well be worthwhile to do so... In the past, I used pandoc to go from html segments to markdown in order to scrub/cleanup imported input... the eventual goal was to support markdown as a base input in the editor, with a side-by-side view.
I like markdown a lot, but I think the point is to "learn" markdown, and maybe an editor with a side-by-side preview is better if that's your target? The point of markdown is to be a slightly enhanced text input.
Cool! Ya, I have a project that is on the back burner I am planning to work on at some point in the near future that I would like to use. I have started playing around with Codemirror and the newish texteditable HTML tag to see what could be done!
I like githubs flavor of markdown, because I would like the ability to perhaps make todo lists (and maybe other things that may be useful).
Markdown is still a simpler, more lightweight markup than HTML. Storing text in Markdown is good when conversion is not just to HTML but other formats (e.g. EPUB). Even if the text is always going to be converted to HTML, it would make changing the HTML output more straightforward.
I definitely like Markdown's simplicity, but sometimes it feels limiting because the content I am creating includes block elements and special styles that are not in markdown's vocabulary (like a block for a warning).
I took a look at this project when deciding if I should implement my own. I think both my project and pen editor are going to make each other better with a little competition ;)
Love it, very nicely done. The only issue I have is with the animation (movie the popup from the previous position to the current one). It looks nice but it's off-putting. A fade-in/out would work fine.
Short answer: No it is not but it's already fixed ;)
Long answer: The editor mode in the default options was mistakenly set to 'inline' and as the demo does not set this option the editor had the new paragraph feature locked.
Only suggestion I'd make is to speed up the transition when the palette moves around, or maybe replace it with a fast fade in/out - the animation gets in the way.