How to use editor in plugins?

[Holger]

Hi folks,

the problem at the end seems to be the different ways how to include the different editors. For me it's much easier with (F)CK than with Tiny...

But that:

Code: Select all


    function editor_test_2()
    {
           $html = '<form>
            <textarea id="my_teaser" name="my_teaser" class="my_teaser_class">Guten Tag!</textarea>
            <textarea id="my_content" name="my_content" class="my_content_class">I need a fullblown editor</textarea>
         </form>';

        init_editor(array('my_teaser_class'), 'minimal');
        init_editor(array('my_content_class'), 'full');
      
      return $html;
    }  
 

is exactly what I meant (of course with full paths to config-files).

And that's why I thought that editor_replace() is complete useless, because everything is (or can be) done with a config(.js) - with CK.

The only thing is that CK needs IDs and Tiny needs classes. But if the plugin provides both, it should not be a problem.

But I have to think about how to provide a useful function editor_replace() for CK. At the end it'll be the same as init_editor()...

KR
Holger

[Holger]

BTW: is it ok to use 1.5.1 for development, or are there some planned changes / bugfixes available?
(I can't find some new code on SF ).

Holger

[cmb]

Hi Martin, hi Holger,

That's a good idea!

Shall we add it to the roadmap?

The only thing is that CK needs IDs and Tiny needs classes.

No! To allow differently configured editor instances on the same page, even tinyMCE needs IDs. And Whizzywig too, BTW. But as I've written, it's not hard to map that either way.

But I have to think about how to provide a useful function editor_replace() for CK. At the end it'll be the same as init_editor()...

Have a look as it's currently implemented for tinyMCE. tinymce_replace() doesn't do anything besides passing the $config to the instantiation of the editor. init_tinymce() does a lot more (reading the config file, calling tinymce_filebrowser() and replacing the %PLACEHOLDER%s).

BTW: is it ok to use 1.5.1 for development, or are there some planned changes / bugfixes available?

There were some changes (minor improvements) suggested (see the Roadmap), but not finally discussed or decided upon.

The most important changes would be changes to the editor interface IMO, as they have to be made, before it's reasonable to procede with the editor integration or updating plugins that need an editor.

Christoph

[Martin]

Hallo Holger,

tinymce_replace($elementID, $config = '') inserts a small javascript snippet. This snippet will convert the textarea (or div) with the given id to an editor. The second parameter can be used to configure it the way you need it. If you do not use $config, a most basic instance of TinyMCE editor will be produced. (Not even the "init_minimal.js", just a TinyMCE out of the box). The only thing the plugin author really has to care about is to insert this snippet to the output after the targeted textarea/div has been written.

CKEditor offers the same possibility. Just have a look at http://nightly.ckeditor.com/7350/_samples/replacebycode.html

Martin

[Holger]

Hi Christoph & Martin

@Christoph: ok, I got it now...

@Martin:
I know about CKEDITOR.replace( 'textarea_id' ); - but I can't imagine when this blank editor might be useful.
And when I give some some minimal configuration (basePath etc.) to function editor_replace(), there might be only a small difference to init_editor().

Anyway, I'll stop to discuss that at this point and use the time to build some compatible code for CK now .
About FCK: IMO it's a waste of time. My quick&dirty installation is running and that might be enough.

KR
Holger

[cmb]

Hello Holger,

it was not my intention to suppress the discussion about improving the editor interface. But if we discuss that, a decision should be made quickly.

there might be only a small difference to init_editor().

Yes, you're right. But it doesn't hurt to implement the EDITOR_replace(), and perhaps some plugin authors prefer to use it this way.

Christoph

[Holger]

Hi Christoph,

no problem. I wont suppress that discussion too. I meant what I wrote: I have now understand why things were made this way.
So IMO it's the best now to finish a barebone of a CKeditor - plugin with all the same functions like tinymce.
I'll drop FCK, because that is not really possible with the old one (from my knowledge).

So if my barebone is available, we can discuss if there are things to change at the interface.

Ok?

Holger

[cmb]

Hi Holger,

So if my barebone is available, we can discuss if there are things to change at the interface.

Ok?

Yes -- that might be the best thing to do. IMO the two most important editors are tinyMCE and CKeditor, and so the interface should mainly be useful for this editors. Other editor integrators will probably manage to find a way to conform to the specification somehow.

So I'm looking forward to the CKeditor barebone.

Christoph

[svasti]

Hi folks,
today I tried to put tiny into calendar and half way succeeded and now going to the forum and I see the big discussion here. Difficult to follow.

Fckeditor works calendar and has got textfields with IDs, but having 50 events with lots of text the page build up is slooow. So I made the user click a buttom to activate the editor in specific text areas. With Tiny + classes there is no problem with page build up.

However the configuration init_calendar.js is now in the plugin/editor/inits folder as I haven't understood how to call the editor with config, css etc. in the calendar folder.
svasti

[Holger]

Hi Frank,

Fckeditor works calendar and has got textfields with IDs

Don't waste time for FCK at the moment.
If you really want to build a calendar version for the older XH, we can look for a solution later. It's possible to create editors on the fly with FCK too.
But now we should first concentrate on the interface with new editors.

So I made the user click a buttom to activate the editor in specific text areas. With Tiny + classes there is no problem with page build up.

Good to hear! Than it should work with CK too - hope so .

KR
Holger