In order to provide better TinyMCE support for those who need it, we have started a Partner network, and our first partner signed up is Ephox, they will provide support and commercial licensing for TinyMCE.

In addition, they have also commited resources to help out the community in a more direct way, by helping to fix bugs, answer issues on the forum and various other things. You might have seen Adrian commiting bug fixes on Git and answering some topics on the forums. Ephox has also setup an automated UNIT test bed that checks TinyMCE across browsers on different Operating systems as soon as something is commited to GitHub TinyMCE project. You can check out the Ephox Enterprise TinyMCE offering at their website. Also check out Adrians view on this partnership at his blog.

So why do we need this? Moxiecode Systems is a rather small company, we want to focus on the development of TinyMCE and not get bogged down with to much support and licensing issues (not everyone like/can use LGPL). “Outsourcing” these parts to our partner network and filtering bug reports through them will allow us to focus more on the needs of the community and future development.

Switching to GitHub was a major step in getting more social, getting more developers engaged in TinyMCE and making it simpler to contribute. This Partnership network is another step towards Enterprise customers that want more than just a community supported editor, they need premium support, guaranteed turn around times and many other things.

If you wish to become a partner, contact us and we will fill you in on how this works.

When we switched from Subversion to GitHub, the only negative feedback we got was that it is a lot harder to user SVN External in order to import the TinyMCE SVN tree into your own repository.

Well on the 1st of April, GitHub announced SVN support, most ppl thought it was an April fools joke, but it does actually work.

It is read-only of course.

If you want to check out TinyMCE using SVN you use this url.

svn checkout http://svn.github.com/tinymce/tinymce.git

Check out their blog post on GitHub for more info.

This new release adds better error handling with the new “Error” event. It enables you to handle everything from initialization errors to custom errors depending on server responses. We will add examples of usage of this to the site as soon as possible.

We also introduced a new ChunkUploaded event this is very similar to the FileUploaded event except that it’s fired when a chunk is sent to the server not when all chunks have been uploaded. If you trigger an error inside this event it will cancel the remaining chunks.

A new bytesPerSec property was added to the total progress. This allows you to display the current upload speed.

We also added new support for renaming of files before they get uploaded. This is a feature of the jQuery queue widget and will only be available if you disable the unique_names option and enable the rename option. It will only allow the user to rename the base part of the file not change the extension, how ever extensions should always be verified on the server for security reasons.

The Plupload site finally got a Forum. This has been a popular request by the community. So discussions regarding the product, news about the product etc will now be posted there rather on this blog. You can also follow the news using Twitter on our Plupload twitter account.

The latest move from SVN to GitHub is one step in our effort to reach out more to our community. If you go to our TinyMCE GitHub project, you can get RSS feeds for commits and all kinds of stuff. We now have over 100 followers on GitHub!

Another step is that we have added Twitter links on our TinyMCE website so you can follow this blog and forum news. The TinyMCE twitter (www.twitter.com/tinymce) will also take all TinyMCE related blog posts from this website, and the Moxiecode twitter (www.twitter.com/moxiecode) will only take everything from this blog and not the TinyMCE forum news.

For a while back we have also a Facebook page, sign up to show your support.

We are hard at work tweaking the latest version of TinyMCE, and there hasn’t been any major bugs found in the beta even though this is a big rewrite of certain parts.

From version 4 of Plone, TinyMCE will be the default editor, replacing Kupu.

Rob Geitema has made some excellent work in integrating the editor into Plone.

There was a Plone conference covering (amongst other things) the upcoming TinyMCE integration, check out the recording on Rob Geitema blog.

Very nice integration work!

WPTavern.com posted an interview with our good friend Andrew Ozz, currently working with the WordPress team.

I suggest you checkout the interview here.

http://www.wptavern.com/interview-with-andrew-ozz-mr-visual-editor

We continue to listen to the WordPress community (through our friends working with WordPress) and are very happy about the intergration of our editor in this most excellent blog/site engine.

Need more ppl like Andrew Ozz, for other platforms, we can simple not handle integration with every CMS system out there, if you are working on integration with other CMS, feel free to contact us if you need assistance, we will help you out as much as we can.

EPIServer is a very popular .NET CMS in Sweden, unfortunately the built in WYSIWYG editor in EPIServer is really crappy and only works on Internet Explorer, but some handy ppl have created an adapter that everyone can use in order to get TinyMCE to work with EPIServer.

It integrates with the file and image software built into EPIServer. When we get some time we are going to look into officially supporting the integration of our file and imagemanager with EPIServer.

Check out this blog for more information about the adapter, and where you can download it.

I recently read an interesting blog post at Ajaxian it described that Hedger Wang discovered that some Chinese fellow was able to fix the circular reference memory leak in IE using a finally statement. This got me very exited since it would remove the need to use the unload event to cleanup memory leaks. There are lots of issues using the unload event to cleanup memory leaks I blogged about one of them earlier and using an non unload approach would make things a lot easier and more efficient.

Here is the proof of concept class and you can see it in action at the example page.

(function() {
	window.EventUtils = {
		eventFuncs : [],

		addEvent : function(o, n, f) {
			var el, id;

			// Resolve element by id if needed
			o = typeof(o) == 'string' ? document.getElementById(o) : o;

			if (o.attachEvent) {
				// Since we can't use attachEvent we need to generate an unique id for the object
				// and place functions in an array one for each object
				el = EventUtils.eventFuncs;
				id = o._evtID;

				if (!el[id]) {
					// Generate new unique id
					id = o._evtID = el.length;

					// Add event listener old fashion way instead of attachEvent
					o['on' + n] = function() {
						var i, l, e = window.event, li;

						e.target = e.srcElement; // Force W3C style

						// Execute each event listener in order
						for (i = 0, li = el[e.target._evtID], l = li.length; i < l; i++)
							li[i](e);
					};

					// Create array with first function
					el[id] = [f];
				} else
					el[id].push(f); // Push in more functions

				// Fix the IE leak
				o = null;
			} else if (o.addEventListener)
				o.addEventListener(n, f, false);
			else
				o['on' + n] = f;

			return f;
		},

		removeEvent : function(o, n, f) {
			var i, li;

			// Resolve element by id if needed
			o = typeof(o) == 'string' ? document.getElementById(o) : o;

			if (o.detachEvent) {
				li = EventUtils.eventFuncs[o._evtID];

				if (li) {
					// Detach event listener by looking for it and remove it from the array
					for (i = 0; i < li.length; i++) {
						if (li[i] === f)
							li.splice(i, 1);
					}
				}
			} else if (o.removeEventListener)
				o.removeEventListener(n, f, false);
			else
				o['on' + n] = null;
		}
	};
})();

Here is a simple example on how to use the class it adds two events and removes one of them this sample code can be seen live running the example page:

var f;

EventUtils.addEvent('elm', 'click', function(e) {
	alert('Listener 1: ' + e.target.id);
});

f = EventUtils.addEvent('elm', 'click', function(e) {
	alert('Listener 2: ' + e.target.id);
});

EventUtils.addEvent('elm', 'click', function(e) {
	alert('Listener 3: ' + e.target.id);
});

EventUtils.removeEvent('elm', 'click', f);

We never really thought we would be the type of ppl that uses blogs, we have so many places where we could post news and stuff, but I guess here we can be somewhat less serious and just post some fun and cool stuff related to what we do for a living.

Will try to keep this up to date with a few articles per week.