[Updated] Ext.ux.TinyMCE - TinyMCE form field (v0.7b1)

[craigharmonic]

Also having another issue with the editor.
I load it using metaForm which all seems to work great except I get 2 errors:

this.getDoc() has no properties
http://127.0.0.1/Conductor/Conductor...ce/tiny_mce.js
Line 1

e has no properties
http://127.0.0.1/Conductor/Conductor...ce/tiny_mce.js
Line 1

I have followed the examples and tried placing the following code before my onReady event:

// Initialise the TinyMCE editor for use by any of the components
Ext.ux.TinyMCE.initTinyMCE();

But this didn't help, possibly because I am using meta form. Any help would be greatly appreciated!

Apart from the 2 errors (and the resize issue above) - which I think has to do with how I am creating the editor, this is a great extension. Thank you!

[Dumbledore]

i have a problem when rendering components in Ext.onReady...

I call Ext.ux.TinyMCE.initTinyMCE() before Ext.onReady. the Editor will be rendered but with the wrong configuration...

With first call of Ext.ux.TinyMCE.initTinyMCE() the editor(s) will be initialized with the standard configuration. After that tmceInitialized will be true.

Then comes the calls of my xtypes... But tmceInitialized is true from the first call an the editors will not be initialized with the right language...

Next Problem:

When use the Spellchecker-Plugin the misspelled word are marked for a second and will be overwrited when call form.isDirty().

Any ideas?

Bye, Dumbledore

[AVerta]

Hi,

I

[Dumbledore]

Hi AVerta,

your must sync the value before submit via syncValue() or tinyMCE.triggerSave();

Bye, Dumbledore

[Dumbledore]

Hi,

after study the source and the documentation of tinyMCE i modified this extension for my personal requirements.

I implement a isDirty() Funtion:

/**
* own isDirty() Function - maps to the TinyMCE-isDirty()
*/
isDirty : function() {
    if(this.disabled) {
        return false;
    }

    return this.ed.isDirty();
}

and i inserted in setValue following to get the isDirty() working:

/** ----------------------------------------------------------
*/        
setValue : function( v ){
	this.value = v;
	if( this.rendered )
		this.withEd( function(){
			this.ed.undoManager.clear();
			this.ed.setContent( v === null || v === undefined ? '' : v );
			
			// rb - patch for handling isDirty()
			this.ed.startContent = this.ed.getContent({format : 'raw'});
			
			this.validate();
		});
},

perhaps someone find it usefull...


Bye, Dumbledore

[xor]

Hi!

Sorry, guys, it was a long time since my last reply.

...
If you do a similar check as the suggestion above all works fine, perhaps this needs adding to the next version?

Current version uses native TinyMCE's resize method so all such issues should be gone automatically.

[xor]

I am having a problem getting the HTML Editor to resize in a split frame. When I drag the split frame left or right I want my editor to resize accordingly.

I have set both the width of the editor and the tinyMCE config to 100% and the initial size works fine. Then when I drag the frame splitter the tinyMCE element does not resize. What's the best solution for this?

Is there a resize event for this UX that I can use? (The idea would be to add a listener on the tinymce object that listens for moving of the split and calls resize).

All resizing is inherited from Ext.BoxComponent, so it should work as other elements. For an instance, standard "resize" event should be fired. I've checked resizing to the "fit" layout (works) and vertical resizing with Ext's resizer. It was working as expected. If this problem still persist, can you provide me with test case on the base of my example files?

Just as a notice, TinyMCE's built-in resizing mechanism is not supported. Use Ext instead.

[xor]

i have a problem when rendering components in Ext.onReady...

I call Ext.ux.TinyMCE.initTinyMCE() before Ext.onReady. the Editor will be rendered but with the wrong configuration...

With first call of Ext.ux.TinyMCE.initTinyMCE() the editor(s) will be initialized with the standard configuration. After that tmceInitialized will be true.

Then comes the calls of my xtypes... But tmceInitialized is true from the first call an the editors will not be initialized with the right language...

Have you tried to pass right configuration to initTinyMCE() function? It accepts the same settings object as TinyMCE itself.

[xor]

after study the source and the documentation of tinyMCE i modified this extension for my personal requirements.
...

I've added it to the trunk.

BTW, have you checked - maybe it's enough to simply set startContent to the value of setValue parameter?

[xor]

Also having another issue with the editor.
I load it using metaForm which all seems to work great except I get 2 errors:...

Can you reproduce it on the base of one of my test files?