Advanced version

[ryan]

Hello

I've chatted a little to Chee Aun about where he sees MooEditable
developing in the future, and he's keen on keeping it as a simple
editor, which is totally his decision and probably a good thing.

However, I've been using the app for quite some time now in our CMS
system, and have developed it with additional plugins and so on, so
I'm keen to push development in that direction, and develop its
feature set to work in that environment. Currently I keep having to
port plugins and so on over every time something considerable changes
in the core code.

So with Chee Aun's agreement, I think its best at this stage to fork
the project and pursue the goal of making a complete, full featured
WYSIWYG editor based on MooTools.

Obviously there will be a code base shared between the two projects,
and I'm sure aspects of development will overlap, but there will end
up being quite a difference between the two.

I'm letting you all know this as I'm very keen for others to get
involved with this aim and help make the development fast-paced. My
plan would be to use the base of existing plugins and develop them
further to achieve parity with systems like TinyMCE and so on - which
is obviously a considerable task. I'm sure there is already a pool of
plugins that we have all developed and not pushed to the main
codebase.

Over the next few days I'm going to start pushing the code to
http://github.com/ryanmitchell/mooeditr.

If you're interested at all let me know - I won't be able to take this
project on without the help of others.

Thanks,
Ryan

[Kenton Gray]

Very excited to see what happens!

Kenton

> --
> You received this message because you are subscribed to the Google Groups "MooEditable" group.
> To post to this group, send email to mooed...@googlegroups.com.
> To unsubscribe from this group, send email to mooeditable...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mooeditable?hl=en.
>

[Vic]

Great idea Ryan!

I would love this version to include an 'inline' option for the editor
to use with existing div content on a page instead of a textarea
element. The browser support is increasingly getting better at
contenteditable with html5. The main advantages obviously being to be
able to drop the whole iframe and the automatic cascaded styles from
the page. This would therefore increase the usability manyfold. (In my
opinion the iframe solution has many disadvantages in a real world
wysiwyg cms editor, for example: noticeable loading and styling delays
when activated, the need for extra stylesheets which mimic the page
styles but need to work without the page context in the cascading, the
limits when scripting elements in an iframe for advanced extra ui
elements (like an extra context sensitive image menu when an image is
selected) etc etc...)

I think a modern 'html5' wysiwyg cms editor would be using inline
editing in combination with the group functionality to have 1 toolbar
for many editable div elements on a page. I hope you will therefore
consider this functionality in the roadmap of mooeditr. I will watch
the github fork and if I think I can be of help (i'm no ninja/guru,
just regular) i will try.

good luck !!

VIc

On Jun 25, 3:50 pm, Kenton Gray <kentong...@gmail.com> wrote:
> Very excited to see what happens!
>
> Kenton
>

[ryan]

Hello

Thanks for the feedback.

This is definitely something I'm keen to add - I have need of it
myself. I had a basic version working a few months ago on the
MooEditable codebase, however it was a little buggy so theres a good
bit of work involved in it.

I think the plan of action at this stage is get the iframe version up
to a good standard with all the required features, then start adding
the inline functionality. That way it gets the focus it deserves.

Keep the ideas coming...

Thanks,
Ryan