[Neos] Why no iframe in the "backend" editing mode?

[Christopher Hlubek]

Hi Stefan,

that looks fantastic!

Just had a brief look at the source code and the approach looks really promising.

About the message passing: I think it might be better for the architecture to decouple the editing view and the surrounding interface more strictly by not binding to the DOM elements (or whatever object) directly.

Are you visiting some TYPO3 event in the near future? We have some more code sprints planned for this year and it would be great to bring this concept into Neos. In the meantime I'll be glad to help you wherever I can to guide you through the Neos backend or frontend.

Greetings,

Christopher

Am 12.05.2014 um 17:09 schrieb Stefan R. <rumzucker at gmail.com>:

> Actually I wanted to try to implement this in Neos but sadly I don't fully understand all parts of the Flow framework and Neos yet. So I couldn't figure out where exactly to hook in. Also I could imagine that this would require a lot of changes in how components are rendered in the backend.
> 
> Anyways in order to show (those who are interested in this approach) how this could look like, I created a simple demo with a few functionalities. The demo can be found here: 
> h t t p://demo.rumzucker.at/neos-edit-demo/
> 
> (Tested with Chrome, Firefox, IE11)
> 
> Please let me know what you think ;)
> 
> So again, in my opinion I really think this could be the ideal solution for now. If some of you are interested in building this, I'd like to help.
> 
> Stefan
> 
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos