He replaces the icons with the popular Famfam silkicons library, you can download his creation on his website.

Check out the article.

If you have any insteresting articles about our products, lets us know and we will feature you here on our blog.

Also done some minor updates to the website, nothing major just some fixes and tweaks.

We have been working on getting TinyMCE to run on the iPad, most things seem to actually work, except that the browser crashes a bit and the UI isn’t really a perfect fit for that type of interaction, but it is getting there.

For more details and signing up, check out the Meetup page!

http://www.meetup.com/tinymcemeetup/

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.

Issue tracker

We have now moved away from the SourceForge issue tracker and built our own custom one. This gives us the ability to add exactly the features we want such as bug voting and tie it to GitHub. It should now be a lot faster to work with since SourceForge was a pretty slow service. We will also be more responsive when it comes to resolving bugs now when we have a more easy to use tool.

Wiki

The Wiki was moved from MediaWiki into a custom Wiki that uses HTML and TinyMCE for it’s editor interface. The wiki lets you structure pages into a page tree and supports syntax validation for source code samples.

Translation Service

A popular feature of the old site was the translation service that enabled uses to translate TinyMCE to it’s native language. We have improved this feature for the new site and it’s now possible to both translate and preview the results on the site. It makes it a lot faster and easier to contribute language packs to the project and those contributions are always welcome.

API Documentation

The documentation has been improved and one of these improvements is the API documentation. This one is now inline inside the wiki, it’s exported out of the source code of TinyMCE using our Moxiedoc tool and users can comment on the different parts of it. It’s very similar to how www.php.net has it’s documentation.

Examples

The example section has been improved by moving all examples into categories. We will continue to add more examples here and any feedback on what to add here is always welcome.

Custom download packages

A common complaint we see regarding TinyMCE is that people say it has to many files. So we wanted to change that, the site now includes a tool for only selecting the components you need and save this as a preset on your account. Then each release you can simply just download the preset package.

On another note, we have a new employee, Davit Barbakadze has been helping us out for a bit the last couple of weeks and he is now a part of Moxiecode Systems AB. His main focus right now will be to incorporate some fixes and enhancements into Plupload and then move over to help out on TinyMCE development as well as other development.

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!

• 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.

So, 500 million ppl just got access to TinyMCE, sweet

And as you might have noticed (we tweeted about it) Facebook is now using TinyMCE in their “Notes” section as well as “Facebook Questions”.

We are now back from vacation since the start of this week, getting back into things again and we got a lot of nice stuff for the community comming up.

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.