Jörn Nettingsmeier wrote:
hi everyone!
there's a pile of editor updates in my queue, and i think they are
Cool(tm). they're mainly about getting rid of the zillion different
insertFoo usecase implementations and replacing them with a generic
one in the editors module, with a nice javascript API to handle the
communications between editors and generic usecases (it all happens on
the client, no continuations, so it hopefully won't hog as much server
resources as the old approach...).
with that accomplished, i hope it'll be fun again to work on editors,
fix bugs, polish usability and add new features, because now you'll
have to to it JustOnce(tm).
those changes that do not affect existing functionality have already
been merged, but they cannot be tested that way.
what's left will affect oneform, bxe, tiny and fckeditor.
oneform and tiny ports are already done in my sandbox, no regressions
(oneform even gains insertFoo functionality), bxe is almost done.
but i haven't got much clue about fckeditor unfortunately...
should i create a branch, post patches, or just commit after it works
for me? the changes have the potential to break link, asset and image
insertion for all editors, but they will not touch any core
functionality.
richard, will you have some time this week for porting and testing
fckeditor with the new generic usecases? i'm going to tackle that
tomorrow, but i will certainly need some help.
best regards,
jörn
fck isn't too bad. I've been able to cipher out what needs to be done in
the past based on BXE and TinyMCE. I should be able to look at stuff
tomorrow morning, I'm -5 from GMT at the moment. I should have the time
to take a look at the changes you've made thus far and see what I can do
as well.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
