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

[ajlaluan]

Hi gurus,

I am implementing my own file browser for tinyMCE. I referenced tiny_mce_popup.js to support some functions in returning values in image dialog window but unfortunately I got tinymce is null error when loading my page.

Does anyone from the community who experienced and solved this problem? Or can anyone from the group helped me out in returning values from a custom file browser to the standard image dialog window of tinyMCE?

This is the link where I based the function:
http://wiki.moxiecode.com/index.php/..._Return_Values

Thanks is advance

[uwolfer]

xor, attached you can find the whole file with all my changes. Thanks for looking into it. Feel free to use any of the changes in your official code.

[lj2008]

it's great,I will use it

[xor]

Ajlaluan, maybe you should also include main tinymce script into your popup? But honestly, I don't know. I believe it will be more productive to ask this question at TinyMCE forum. After all, here we merely binding existing TinyMCE code with Ext JS.

[xor]

uwolfer, can you explain what benefits are you getting by putting WindowManager and ControlManager classes creation into initTinyMCE method? Their code will be anyway executed only after an isntance of a class would be created. I.e. in onRender method.

[uwolfer]

uwolfer, can you explain what benefits are you getting by putting WindowManager and ControlManager classes creation into initTinyMCE method? Their code will be anyway executed only after an isntance of a class would be created. I.e. in onRender method.

Without my change, the plugin overrides the methods / classes at load time of the plugin. That requires loading TinyMCE before loading the plugin. With my changes, the overrides of TinyMCE classes is done of first initialization of a Ext form field (some type of lazy loading). It does also not produce any JS errors if TinyMCE is not included in some pages where it is not required (may be the case in some applications...).

[xor]

OK, I got it. Certainly, I was not thinking of a scenario when TinyMCE could be not loaded at all. In this case I' prefer to lazily load Ext.ux.TinyMCE also. Actually, we use this approach in our applications. If I need Ext.ux.TinyMCE, then it also automatically load all dependencies.

If community doesn't insist, I' prefer not to include this "lazy loading" modification in the trunk. I believe its use case is quite rare.

[kavih7]

I ran into a problem with the zseed windowgroup managing MessageBox dialogs being too low. Its either that or the declared zseed for the tinyMCE windowgroup is too high. In any case, moving the zseed down by a thousand from where the MessageBox starts (9000) seemed to fix it. So, in this bit of code:

// Create a new Windows Group for the dialogs
var windowGroup = new Ext.WindowGroup();
windowGroup.zseed = 12000;//Another version had 20000 here

change to:

// Create a new Windows Group for the dialogs
var windowGroup = new Ext.WindowGroup();
windowGroup.zseed = 8000;

and then MessageBox's will have the highest z-index.

To see the issue, click on the insert image tool, put in a URL to an image and click "Insert." A MessageBox will appear behind that insert image tool window.

I searched this big thread for a possible solution to this issue, but since I didn't find one, above is mine. Let me know if there is a more supported solution or if the issue was already addressed.

[Dumbledore]

hmm... 8000 is to low...

I use the TinyMCE inside an Ext.Editor. The rendering is ok, but when use a plugin the new dialogs are behind the Ext.Editor. Perhaps this should be a config parameter?

Bye, Dumbledore

[kavih7]

Yes, it probably should be a config param. The only app I'm using it in (for now) works with 8000 fortunately.