Jake Goldman, chief engineer and CEO of 10up LLC posted a slide of his talk at 2011 Wordcamp earlier.

Showing some advanced work on how to customize and form the editor to fit your website better, using custom styles, adding custom buttons and styling the interface, a very good slide, wish I had heard the talk.

Check out the article and slides here.

Today we released a new service, to allow you to try different configurations and setups with TinyMCE, as well as aid in examples for our bugtracking system, we introduce TinyMCE Fiddle (fiddle.tinymce.com). Service is still in beta stage, feel free to comment and provide feedback in the forums at tinymce.com.

This service is heavily inspired by jsfiddle.net

The buzz around Plupload is huge right now, much more than we anticipated, and we are putting more resources into the continued development of Plupload and starting to create a community around it similar to TinyMCE. Over the next couple of weeks/months you will see a rebuild of the website so contain a wiki for the documentation as well as its own bug/feature tracker system (like the new one we are using for TinyMCE). The current website wasn’t built to contain so much content, but as the project grows, so must the website.

The new TinyMCE website is a huge success, ppl are getting engaged with the bug/feature tracker and submitting good quality reports, something we appreciate a lot and we no longer have to put up with the incredibly turtle-slow Sourceforge tracker system.

Just as a side note, many seems very interested in exactly when the new TinyMCE version will be out of Beta, can’t give you any exact date, but we expect this to be the last beta unless something unexpected shows up.

Been a while since we gave some form of update, if its quiet it is cause we are working very hard. We are working in parallel on a big update on TinyMCE and the major 4.0 TinyMCE release as well as our MCFileManager and MCImageManager that is way overdue for a major update.

On another note, Drupalcamp Atlanta happend a few weeks ago and one of the topics there was a shootout between different editors, the result was posted a few days after collecting what criterias was most important from the attendees of the camp. TinyMCE came out on top in this little shootout.

You can read the result here.

These kind of comparisons are good for all parties involved, its good for us to see what features are valued the most, it gives us a direction of focus when we do updates. We think the upcoming TinyMCE versions will be even  better than the current, improved performance, more power in configurating output, changes to the graphical interface, and a lot of other things, some we like to keep a secret! Stay tuned!

We have had many questions about how paragraphs are handled in TinyMCE and users wanting to have <BR> elements instead of <P>. Adrian Sutton at our partner Ephox has written a few blog posts about various issues and misconceptions on this topic. And we also explained many issues in our FAQ.

• Why P Tags are Your Friends
• P Tags in Word
• P Tags and Single Line Fields
• P tags and Flash
• The Email and P Myth

So to sum things up, paragraphs are here to stay and TinyMCE will continue to produce them on enter by default.

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.

Moxiecode and TinyMCE is doing well, and we are looking for more ppl to join our team of developers. You can be located almost anywhere in the world.

These are the job openings right now:

Backend Developer

We need help working on the MCFileManager and MCImageManager products, an experienced developer could really help us develop some new thoughts we have regarding our products as well as develop new products and ideas.

Primary skills: C#, PHP

Secondary skills: JavaScript, HTML, CSS

Frontend Developer

Would you like to work on the most popular Open Source WYSIWYG editor in the world? We need someone who knows JavaScript like the back of his hand.

Primary skills: JavaScript, HTML, CSS

Secondary skills: PHP, C#

How to apply!

If you feel like you have the skills needed, send your application to info at moxiecode dot com with your name, address, current work situation and CV. If you are apart of some Open Source project or have code located in some public repository, send some info on how/where we can look at it and describe how you where involved in that project.

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.

Social coding is the new thing, since our move to GitHub the community activity on all our project have increased, users find it easier to clone, fix, extend, patch and contribute to the software through GitHub.

The learning curve for Git is kind of steep, and we hope that more ppl will be able to help out when the tools (such as TortoiseGit etc) becomes better and more understandable. It can only get better from here.

We recently released a new version of TinyMCE (3.3.2), and we continue to review patches and contributions made by others.

Also, through a recent partnership we can offer better support and custom license options for TinyMCE, but more on that later.

If you wish to follow any of our products on GitHub, here is a link list of our current project.

• TinyMCE
• PunyMCE
• Plupload
• js-build-tools
• TinyMCE Compressor
• TinyMCE Spellchecker

Thank you everyone for all your contributions!

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.