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

Research implementing Bootstrap WYSIHTML5 #38

Closed
sirlancelot opened this issue Nov 16, 2012 · 4 comments
Closed

Research implementing Bootstrap WYSIHTML5 #38

sirlancelot opened this issue Nov 16, 2012 · 4 comments

Comments

@sirlancelot
Copy link

http://jhollingworth.github.com/bootstrap-wysihtml5/

Looks like the simplicity would fit very well with Bolt.

P.S. I'm the same guy on Twitter ;-)

@pvankouteren
Copy link
Contributor

Looks nice and clean. How does it compare to CKEditor in terms of features?

@bobdenotter
Copy link
Member

After you've mentioned bootstrap/wysihtml5 on Twitter, i've looked into it. Some of my thoughts:

  • It's definitely lightweight. This is a big plus.
  • Its Look and feel would make it fit in with Bolt smoothly.
  • It has problems when pasting from Word or other sources, because it doesn't strip the HTML. CKeditor strips all unwanted Word-HTML to clean, simple <p>'s and other basic, semantic HTML.
  • It inserts unwanted elements in the HTML it generates: things like <span id="_wysihtml5-undo" class="_wysihtml5-temp"></span> and random <p>&nbsp;</p> blocks between paragraphs or lists.
  • It doesn't have an 'view source' option. Which is problematic, especially considering the points about the odd HTML it inserts. I notice that wysihtml5 itself does support 'view source', so we could probably add that easily.
  • The current version of wysihtml5 is '0.3.0', and was released over half a year ago. I'm worried about whether there will ever be a version that's considered to be stable, and at which timeframe. I wouldn't want to invest in a tool that is not going to be developed further.

All things considered, I think we should stick with CKEditor for the time being. The fact that is has been around for something like 10 years, does show that it's a mature product, and it's not going to be abandoned anytime soon.
The only issue with CKEditor that i currently have is its size: It's big, because it has way more features than we need. I've stripped most of these from the toolbar, but that means it's still in the code. Once CKeditor 4 gets closer to release, i'd like to look into its build scripts, to see if we can use that to compile a slimmer version.

@pvankouteren
Copy link
Contributor

Yes, if there's no progression on the project and versioned < 1, I agree the tool should not be used in this project.

@sirlancelot
Copy link
Author

Good points :)

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

No branches or pull requests

3 participants