[v0.5] MooRTE - Textbox RTE / Inline WYSIWYG Editor

hum, I am actually hammering the developer at http://groups.google.com/group/mooedita ... 690ecc38d6

I have no doubt the 3 of us can do a wonderful job. But frankly I would rather work in a group of 4 developers (or even more).

forking the project? if we have no other choices, then yes. But then let's rename it.
I don't see why MooEditable should get all the credits when it's been so hard getting our stuff in.

I agree - Ideally i want it to be all part of mooeditable, but im running out of time...
The base of mooeditable is almost perfect to me ... throw in the ability for actions to have events for certain things happening, and it would be great.
Its the extending of it that needs done to me...

Ideally I'd like to create an editor that has NO default buttons, but a button builder, much like the MooTools builder - you choose the buttons you want it to have, which are then bundled into your script. So you concentrate on creating an extendable base, then everything else is a "plugin"...

We are on the same page Ryan : no buttons, a plugable theme.
Sam probably has a few more ideas to enhance flexibility.

Let's wait til next week. This should give enough time for the MooEditable author to react to our calls.

Cool - sounds good to me.
I think it would take me half a day to merge the best bits of this and mooeditable to make the flexible core we all want.

ryanmitchell wrote:What do you think sam and orefalo? With 3 of us hammering at something we could get it up and running pretty quick.
I think it would take me half a day to merge the best bits of this and mooeditable to make the flexible core we all want.

orefalo wrote:I have no doubt the 3 of us can do a wonderful job. But frankly I would rather work in a group of 4 developers (or even more).

I am definitely excited at the prospect. Perhaps we can even get the other forks (ggedit) and horseweapon to chip in as well.

ryanmitchell wrote:Ideally I'd like to create an editor that has NO default buttons, but a button builder, much like the MooTools builder - you choose the buttons you want it to have, which are then bundled into your script. So you concentrate on creating an extendable base, then everything else is a "plugin"...

orefalo wrote:We are on the same page Ryan : no buttons, a plugable theme.
Sam probably has a few more ideas to enhance flexibility.

Definitely!!!!
Please look at the code (svn). Notice that this class has NO BUTTONS at all.
It has seven functions: init, setRange/getRange/exec(utilities), insertMI(puts it on page), toolbar(adds toolbars), clean.
Everything else - bar none - is not an integral part of the class - bold, etc are just parts of an extendable "button" hash.

You can initialize the class with as many toolbars and butons as you want/need:
To make two rows, the first with bold & italics:

You can create buttons with a simple extend to the hash. Or you can create popups and submenus with the same ease.

Eventually, as said above, we can put together a php page that will only send those buttons requested:

ryanmitchell wrote:Interesting... very interesting.
I think its worth considering the option of forking it, and making a fully featured editor... using the core cheeaun wants as a base, and extending it ... some of what you've done here is great, but we can get the best of both worlds in a fork...

I agree - Ideally i want it to be all part of mooeditable, but im running out of time...

forking the project? if we have no other choices, then yes. But then let's rename it.
The base of mooeditable is almost perfect to me ... throw in the ability for actions to have events for certain things happening, and it would be great.
Its the extending of it that needs done to me...

MooInline is not a fork of MooEditable. It was written from the ground up to have the extensibility and features that it does.
Among other points, it ability to edit inline is something I cannot discard (for my own use).
Please, help integrate the applicable good ideas that have been suggested for MooEditable.
You could try to squeeze these ideas into ME, but it will much easier to just use MI as a base - again, its a different animal.

[MooInline is easy to read (I think) - but it might be beneficial to chat (gtalk - ssgoodman) and go through the code together - it won't take long.]

For all those watching the project through these forums:

We have renamed from MooInline to MooRTE.

We are even more inline-friendly then before, but liked the new name better.

New Project Page: http://siteroller.net/projects/moorte/
New Github Page: http://github.com/siteroller/moorte/

Mootools community - keep up the great work!!

Looking forward to the Forge!