Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Aloha Editor: an awesome HTML5 browser based editor

aloha-editor.com

Post reply on HN
Print view View original

1–10 of 24 posts

Re: Aloha Editor: an awesome HTML5 browser based editor

#2

Post by timmfin »

I like the idea, but you can't even insert a link with the editor. I assume it is just an oversight because it would make perfect sense to have an insert link button right next to the insert table button. Kind of a large omission though, especially if you are claiming HTML WYSIWYG. (And what about images?)

Re: Aloha Editor: an awesome HTML5 browser based editor

#3

Post by jacksoncarter »

On the insert tab, all I see is Table, but I can't seem to find inserting images, editing hyperlinks, bullet points.

Also, Firefox keeps asking me if I want to kill an unresponsive script, so wondering what that is...

And what is the aGPL? If I include a link to the js file on my webapp, do I have to open source all my code? I really don't get what all these different licenses mean.

Re: Aloha Editor: an awesome HTML5 browser based editor

#5

Post by kiwidrew »

I found a more detailed look at Aloha on Slideshare: http://www.slideshare.net/draftkraft/aloha-editor-contentedi...

In particular, there are some screenshots which show table editing, insertion of images, and what appears to be navigation and forms as well. My favourite, though, is on page 37, where it looks like some user-defined paragraph classes ("info" and "alert") have been included in the formatting toolbar -- it looks _really_ slick!

There's at least one other project which is trying to make editing web content better: http://www.wymeditor.org/

I recall reading that, due to the way that WYMeditor makes the HTML structure explicity (while still keeping it relatively end-user-friendly), it tends to encourage users to produce "nice" HTML -- simply because poorly-structured HTML looks ugly in WYMeditor. :)

But wow, Aloha looks absolutely beautiful! The sooner FCKeditor and tinyMCE die, the better off we'll all be.

Re: Aloha Editor: an awesome HTML5 browser based editor

#7

Post by asnyder »

Much of the functionality they mention can be done with other Editors. We've used edit-in-place for the past several years, even with things like CKEditor. There's nothing that forces you to need to do a page-reload to load CKEditor or other editors, rather you need an omniscient wrapper that can deal with it. For example, we use edit-in-place all the time with CKEditor, but of course we created a NOLOH wrapper for it.

A live example of instantiating and changing CKEditors: http://www.noloh.com/Demos/CKEditor/Example/index.php

Code for example: http://github.com/noloh/CKEditor/blob/master/Example/index.p...

From there, it's easy to create an Edit-In-Place object using CKEditor: http://noloh.diffpaste.com/#/667/, then wherever you would like edit-in-place functionality you simply instantiate an EditRegion.

Re: Aloha Editor: an awesome HTML5 browser based editor

#9

Post by _delirium »

jacksoncarter wrote: post #3

On the insert tab, all I see is Table, but I can't seem to find inserting images, editing hyperlinks, bullet points. Also, Firefox keeps asking me if I want to kill an unresponsive script, so wondering what that is... And what is the aGPL? If I include a link to the js file on my webapp, do I have to open source all my code? I really don't get what all these different licenses mean.

AGPL's a version of the GPL that considers "running a modified version as a webapp" equivalent to what counts as "distribution" with the normal GPL. The goal is that if, say, Amazon AGPL'd their EC2 infrastructure, and you created an improved version that you then put online as your own cloud provider, you'd have to release your improvements. The normal GPL wouldn't require that, because running a service off code isn't considered "distribution" of the code (the code itself never leaves your servers). People who use the AGPL, though, want semantics roughly equivalent to what the GPL got you with fat-client apps: if someone made and sold a modified version of your GPL'd offline word processor, for example, they'd have to GPL the modifications.

Not sure it makes any difference with .js code, though, because in that case the code is being distributed, so the normal GPL would already apply.

Post reply on HN