Live data from Hacker News

Aloha Editor: an awesome HTML5 browser based editor

aloha-editor.com

11–20 of 24 posts

Re: Aloha Editor: an awesome HTML5 browser based editor

#13
post #5

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 --…

CKEditor and TinyMCE have solved a very difficult problem in extremely elegant ways; their developers deserve more respect than wishing their projects death.

Re: Aloha Editor: an awesome HTML5 browser based editor

#14
post #4

Very slow for me in Chrome 5 on OS X. Seems like it needs some major polishing before it's ready.

It's causing Safari 5 to hang and pop 'slow script' warnings.

The demo is actually pretty fast http://aloha-editor.com/demos/960-fluid-demo/

I think it's a front page script that's causing the slowness.

Re: Aloha Editor: an awesome HTML5 browser based editor

#15

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.

I'd also like clarification on this. I think I remember the AGPL pissing off the ExtJS community quite a bit. From the discussion though, all it meant is that the javascript code you write to extend the library has to also be AGPL'ed. But if you bundle it with an open source app, it can be MIT, and you can still use it on top of a closed source web site.

Just like if one library cross references another GPL library, it doesnt automatically make that library GPL also. No code sharing is happening, just runtime dependencies.

But please let me know if I'm way off base here...

Re: Aloha Editor: an awesome HTML5 browser based editor

#16
post #5

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 --…

CKEditor and TinyMCE have solved a very difficult problem in extremely elegant ways; their developers deserve more respect than wishing their projects death.

Both of those editors rely on the contentEditable support of the browser to power the actual editing, and browsers have traditionally done a very poor job at producing valid HTML. They make attempts at "post-validation" and "attribute scrubbing", but these are at best makeup on a gorilla. I certainly wouldn't call their solutions elegant.

Having worked on numerous content management systems in the past, one of our biggest issues was trying to "lock down" the WYSIWYG editor so as to minimize the chances that clients could inadvertently break the layout when editing. It was a huge pain point for us, and I lost count of the number of times I had to go in and fix broken pages.

I'm very glad to see that the state of the art in HTML editing is moving forward, and it's well past time for CKEditor and TinyMCE to be put to pasture, IMHO.

Re: Aloha Editor: an awesome HTML5 browser based editor

#17
Hmm. Not particularly impressive thus far. Here were my first two impressions:

- Tried the link last night several times, and the server never responded.

- Tried again today, it came up, I selected some text and clicked "Heading". The whole document turned bold. Hit Ctrl+Z and nothing happened.

Left.

Stuff like this is all about first impressions. These guys managed to screw that up for me twice. It's like Joel Spolsky said about premature exposure: "Now you've got two problems: your thing sucks, and everybody knows it."

Re: Aloha Editor: an awesome HTML5 browser based editor

#18

Earlier quoted context omitted.

CKEditor and TinyMCE have solved a very difficult problem in extremely elegant ways; their developers deserve more respect than wishing their projects death.

Both of those editors rely on the contentEditable support of the browser to power the actual editing, and browsers have traditionally done a very poor job at producing valid HTML. They make attempts at "post-validation" and "attribute scrubbing", but these are at best makeup on a gorilla. I certainly wouldn't call their solutions elegant. Having worked on numerous content management systems in the past, one of our bi…

Same problem here: the one feature that all these editors lack is the ability to restrict what kind of formatting that the users can create.

In a system I've created for a client, some users are allowed to use e.g. bold and italic, but most users aren't (because they would go overboard and make every other word bold). Post-scrubbing the edited html often breaks the editing experience, and browsers have lot's of bugs in contenteditable.

Re: Aloha Editor: an awesome HTML5 browser based editor

#19
post #7

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 i…

Hi asnyder, the difference between Aloha Editor and others is, that you can make any element in the HTML DOM like H1-H6, DIVs, P, SPAN, etc. directly editable.

Re: Aloha Editor: an awesome HTML5 browser based editor

#20

Earlier quoted context omitted.

Both of those editors rely on the contentEditable support of the browser to power the actual editing, and browsers have traditionally done a very poor job at producing valid HTML. They make attempts at "post-validation" and "attribute scrubbing", but these are at best makeup on a gorilla. I certainly wouldn't call their solutions elegant. Having worked on numerous content management systems in the past, one of our bi…

Same problem here: the one feature that all these editors lack is the ability to restrict what kind of formatting that the users can create. In a system I've created for a client, some users are allowed to use e.g. bold and italic, but most users aren't (because they would go overboard and make every other word bold). Post-scrubbing the edited html often breaks the editing experience, and browsers have lot's of bugs…

Hi all, we try to address this issues (bugs of the browsers and functionally to restrict to defined formatting) with Aloha Editor. For ex. we have more than 80 unit tests for the ENTER button. One of those is hitting the ENTER in a H1 Tag. The current is a release in an early development state and we want to focus on reliability and basic functionality (be able to write without errors) in first step.
Post reply on HN