TinyMCE Forum / TinyMCE 3.0a3 and Spellchecker 2.0a2 released

spocke · 2007-11-13 16:24:47

This release contains some major changes to the event dispatching the editor instance will now be passed as the first argument to all observer functions some functions in the AI has also been renamed or removed to produce a more robust core.

Documentation of all the API functions have now been added to the API section in the Wiki most of the functions and classes have examples on how to use them so it should be a lot easier to create custom plugins now when that is well documented.

The spellchecker has also been updated to use the new API, so if you are using the spellchecker you need to replace the older 2.0a1 version with this one.

A new setup callback function was added this one gives you the ability to add editor event using the new event model. Check the Setup editor events example on how to use that.

A translation example was added to help users to translate TinyMCE into different languages. We will also launch a translation service platform that enables users to contribute translations much more easy using an XML format and then export it into .js files.

Development of experimental adapters for jQuery and Prototype has been started, this will enable you to use TinyMCE with a jQuery or prototype core to reduce script size etc. But TinyMCE will continue to be library independent so using these versions will be optional ones they are finished they are supposed to be used by folks already using them. We will release more info about these when they get more stable and usable the ones in this release if more of a proof of concept than something useful.

Change log:
Added new experimental jQuery and Prototype framework adapters to the development package.
Added new translation.html file for the development package. Helps with the internationalization of TinyMCE.
Added new setup callback option, use this callback to add events to TinyMCE. This method is recommended over the old callbacks.
Added new API documetation to all classes, functions, events, properties to the Wiki with examples etc.
Added new init method to all plugins and themes, since it's shorter to write and it mimics interface capable languages better.
Fixed various CSS issues in the default skin such as alignment of split buttons and separators.
Fixed issues with mod_security. It didn't like that a content type of text/javascript was forced in a XHR.
Fixed all events so that they now pass the sender object as it's first argument.
Fixed some DOM methods so they now can take an array as input.
Fixed so addButton and the methods of the ControlManager uses less arguments and it now uses a settings object instead.
Fixed various issues with the tinymce.util.URI class.
Fixed bug in IE and Safari and the on demand gzip loading feature.
Fixed bug with moving inline windows sometimes failed in IE6.
Fixed bug where save_callback function wasn't executed at all.
Fixed bug where inlinepopups produces scrollbars if windows where moved to the corners of the browser.
Fixed bug where view HTML source failed when inserting a embedded media object.
Fixed bug where the listbox menus didn't display correctly on IE6.
Fixed bug where undo level wasn't added when editor was blurred.
Fixed bug where spellchecker wasn't disabled when fullscreen mode was enabled.
Fixed bug where Firefox could crash some times when the user switched to fullscreen mode.
Fixed bug where tinymce.ui.DropMenu didn't remove all item data when an item was removed from the menu.
Fixed bug where anchor list in advlink dialog wasn't populated correctly in Safari.
Fixed bug where it wasn't possible to edit tables in IE when inlinepopups was enabled.
Fixed bug where it wasn't possible to change the table width of an existing table.
Fixed bug where xhtmlxtras like abbr didn't work correctly on IE.
Fixed bug where IE6 had some graphics rendering issues with the inlinepopups.
Fixed bug where inlinepopup windows where moved incorrectly when they were boundary checked for min width.
Fixed bug where textareas without id or name couldn't be converted into editor instances.
Fixed bug where TinyMCE was stealing element focus on IE.
Fixed bug where the getParam method didn't handle false values correctly.
Fixed bug where inlinepopups was clipped by other TinyMCE instances or relative elements in IE.
Fixed bug where the contextmenu was clipped by other TinyMCE instances or relative elements in IE.
Fixed bug where listbox menus was clipped by other TinyMCE instances or relative elements in IE.
Fixed bug where listboxes wasn't updated correctly when the a value wasn't found by select.
Fixed various CSS issues that produced odd rendering bugs in IE.
Fixed issues with tinymce.ui.DropMenu class, it required some optional settings to be specified.
Fixed so multiple blockquotes can be removed with a easier method than before.
Optimized some of the core API to boost performance.
Removed some functions from the core API that wasn't needed.

raine1988 · 2007-11-13 20:10:00

> Fixed bug where view HTML source failed when inserting a embedded media object.

That has been fixed, but when i try to embed a youtube video and save the document,
this is what tinymce outputs:

<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0" height="350" width="425">
<param name="name" value="youtube" />
<param name="src" value="http://www.youtube.com/v/S7_YFKyhQMI&rel=1" />
<param name="width" value="425" /><param name="height" value="350" />
</object>

Wich only works in IE and Opera,
Firefox and Safari won't render it.. :'(

And the <embed> tag is not XHTML valid...

Last edited by raine1988 (2007-11-13 20:12:03)

spocke · 2007-11-13 21:00:20

I will look over the whole embed support for the next release. There seems to be a few problems with the current implementation.

Alexqw · 2007-11-13 23:13:38

This page has quite the journey on this issue and has one or two solutions.
http://www.adobe.com/devnet/dreamweaver … satay.html
I personally like the solution just before the "Satay Method," but the "Satay Method" works too. Maybe it could be a configurable option. If your site only uses small files then the pre-Satay solution works great. If the user wants to do the slightly additional work to get the Satay Method working then they can turn on that flag and configure things correctly.
Just an idea; hope this helps.

---Alex

Felix Riesterer · 2007-11-13 23:55:32

I'm using SWFObject since it has the best solution there seems to be out there (from my perspective).

Greetings from Germany,

Felix Riesterer.

spocke · 2007-11-14 00:16:29

I've been thinking of integrating with SWFObject from time to time but the problem is how do you parse and edit that kind of script. I mean I then need to convert back javascript code into an image inside the editor and then back again. Tricky stuff. Also I would love to see someone making QuickTime object or WindowsMediaObject so they are all uniformed.

Felix Riesterer · 2007-11-14 01:14:44

Hi spocke!

Why not "misuse" a div element for that kind of purpose? You could give it certain attributes (like a href attribute for the multimedia source) and treat it accordingly. An on_save_cleanup could then convert it back into HTML with a real script element for both the SWFObject and the initialization.

Is this a possible approach?

In my opinion these multimedia plugins are a bit of a philiosophical question, aren't they? When it comes to content management these contents also need to be managed by a CMS. It should be handled by the CMS and not by its WYSIWYG editor how to implement the multimedia contents into pages.

What do you think?

Greetings from Germany,

Felix Riesterer.

happy_noodle_boy · 2007-11-14 07:03:12

What about the TinyMCE embed.js and the script method? Could that not be expanded to sniff the browser and output the 'correct' xhtml code for each? That way you have the option of using it, and the Media plugin already supports the script.

spocke · 2007-11-14 16:24:07

Yes, using those is probably the best thing then you can use SWFObject or what ever for them. By reading the article Alex posted getting Flash to work right with XHTML required a lot of steps and even at the end a wrapper movie. But loading external things like YouTube content trough a wrapper won't work so we are pretty much stuck with JS or invalid HTML elements.

Alexqw · 2007-11-15 14:41:53

As a disclaimer, I have not tested the following code.
Maybe I'm missing something obvious, but why can't something like the last example before the Satay Method be used for all formats and not just Flash?
<object type="application/x-shockwave-flash" data="movie.swf"
width="400" height="300">
<param name="movie" value="movie.swf" />
</object>
Wouldn't TinyMCE just have to detect what the MIME type is for the media type in question and use that value for "type" and then put the pathname for "data?" The only downside (from what I understand in the article) is that IE doesn't stream it properly and waits for the entire file to load first, but other browsers stream just fine. It seems like a small price to to pay for cross browser, easy to read, and valid code in a difficult HTML quandary.
But, again, I havn't tested any of this out since I am in the middle of writing a paper and don't have time at the moment.

---Alex

spocke · 2007-11-15 15:14:28

We can't implement a method that doesn't work properly on IE since it's still the major browser platform out there also I don't know how this would affect other plugins like quicktime or windows media. We might add an option to produce this output later on but the writeFlash function that it currently supports are more flexible then you can use for example SWFObject with it.

higher_one · 2007-11-19 21:19:51

spocke,

great job you guys are doing! Version 3 is the best thing ever.

With respect,

#1 2007-11-13 16:24:47

TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#2 2007-11-13 20:10:00

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#3 2007-11-13 21:00:20

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#4 2007-11-13 23:13:38

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#5 2007-11-13 23:55:32

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#6 2007-11-14 00:16:29

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#7 2007-11-14 01:14:44

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#8 2007-11-14 07:03:12

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#9 2007-11-14 16:24:07

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#10 2007-11-15 14:41:53

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#11 2007-11-15 15:14:28

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

#12 2007-11-19 21:19:51

Re: TinyMCE 3.0a3 and Spellchecker 2.0a2 released

Board footer