MoxieManager

MoxieManager has been in development for a long time, and was quite frankly very delayed, well we want to release not just a solid product, but a solid platform for future features, updates and improvements, we have now released a product we are very proud of, and the feedback so far has been great. There will probably be a fair amount of support regarding upgrading and integrating MoxieManager, as well as any bugs that might get brought up to the surface when our 18 000 customers starts to implement the software. We have a new website and a new support system, if your a client, you should have recieved email about this.

.NET version is scheduled to be released within 1½ month from the PHP release, so don’t panic you .NET users out there.

Visit moxiemanager.com

TinyMCE 4

And yes, TinyMCE 4, totaly new user interface and tons of changes behind the scenes as well, code quality improvements have been drastic, as well as the improved build process, inline editing and much much more. Those of you who are missing features, do not panic, most of the features are still there, its just that the user interface have been greatly simplified for end users, as time progress we will get back some of the more advanced ui features as well, but our policy on these changes are simplicity, most users do not need the clutter that is advanced image options or detailed style editing.

We really hope you focus more on implementation issues, setting up formats and classes to use, instead of relying on the source code editor or any of the previously tricky advanced options for setting styles and what not.

TinyMCE 4 is beta, if you find any issues, use the bug tracker to submit them, thanks. We are also working on updating the documentation as fast as we can.

Check out the presentation

If you encounter any problems, try again the next day, if you still encounter problems with our website or services after Wednesday, please report it to us.

So grab a copy of MCImageManager / MCFileManager now at a discount while you can! Please note this is for any of the Enterprise licenses ONLY!

Go here for MCImageManager!

Go here for MCFileManager!

Plupload is also gaining a lot of popularity still, with the beta version of a rewrite out about a month ago, stable release and a new website will be out sometime January.

We would like to thank everyone for contributing code, doing translations and helping out in the forums, you are making this community great!

We hope you had a great year, and are looking forward to the next as much as we are!

/Moxiecode Systems AB

Bit of backstory, since it’s quite complicated. First of all I would like to make one thing very clear, until it gets confusing – functionality of Plupload on a big part has stayed the same. Yes – it has gained huge potential for growth, but on the surface it shouldn’t feel to you any different. And this is actually good – ’cause if you feel the difference, then something went not as it was expected to and you should immediately report it to us 

As you might know, so far Plupload consisted of two distinctive parts – the Core (a small framework that made it easy to quickly implement cross-browser file uploader of any kind) and the Widgets – UI Widget and Queue Widget (two visually rich implementations of the Core and basically examples of Plupload’s potential). But while having a core completely separate turned out to be very handy, it still felt a bit constraining. For example it wasn’t possible to easily get the hold of a raw file data – to display thumbnails for example, or access file meta tags. Yes – Plupload was able to extract Exif and GPS info from images, but it was doing this on it’s own, without giving any control to the user. Another problem was that it was nearly impossible to control the flow of the chunks – resend them separately for example, if they failed to reach the server, calculate  checksums for increased reliability, and so on.

So the necessity was obvious – we required to expand the Core farther. But how? Provide more events and methods (much more in fact)? Or separate low-level file manipulation and upload logic into a separate set of libraries? The answer was laying on the surface, but felt so crazy that it took us quite some time to comprehend that it was the only proper way to proceed. So what we did in our major update, is that we’ve extracted all the low-level logic from the Core and wrapped it up in standalone multi-runtime and cross-browser pollyfills, that are closely resembling behavior and functionality of HTML5’s File and XMLHttpRequest Level 2 APIs!…

Now, maybe currently it doesn’t sound as crazy as it did, back in early days when we started, but believe me it still opens up some very interesting opportunities for legacy browsers,  that are still around (and not only). While working on pollyfills, we tried to follow existing W3C specs as close as it was possible in our circumstances, which means that our implementation of FileReader interface, or XMLHttpRequest will act and have all the properties and methods that according to W3C are expected for them to have. And if for some reason they lack some (specs were noticed to mutate quite often), let us know and we will take on them 

Therefore now we have three tier system: very first level – File and XMLHttpRequest API pollyfills, second level – Plupload Core and third level – Core implementations, like our UI and Queue Widgets. Bottom levels can be extended separately – just as easy as anyone can use the Core to build customized file uploader, pollyfills can be used to create all kinds of components and obviously not only file uploaders.

Currently we publish our first beta of Plupload 2. On big part you should be able to simply drop it in instead of the previous one and everything should simply work. But there are some precautions to take into account. First of all, we’ve dropped BrowserPlus and Gears support, mostly because their authors dropped them themselves. Second point to consider is the fact, that we’ve renamed .swf and .xap shims, since they are not strictly Plupload specialized anymore (they are now part of pollyfills and not the Plupload). So in the places where you reference plupload.flash.swf and/or plupload.silverlight.xap, you must now put correspondingly - Moxie.swf and Moxie.xap (as these are the names of updated shims).

That’s it! You can download Plupload 2 here. Together with minified Moxie (combined name for pollyfill code) and Plupload code, we bundle our Widgets. Queue plugin wasn’t touched, but UI got updated to leverage the power of new APIs and now is able to show the client-side thumbs (even in IE6!).

Happy testing. We are ready to accept bug reports and feature requests. Now that we’ve mostly done with the major update, bug hunting will get top priority.

Was a long time ago they showed us the beta of the new iCloud and told us they wanted to use TinyMCE. They are also using it together with Sproutcore, with TinyMCE mostly just used as an engine for the editable field, much like Squarespace and others are doing.

Stay tuned for TinyMCE 4, it will be another excellent major update to TinyMCE!

Tugberk has created Nuget’s for various TinyMCE implementations (MVC, jQuery etc).

Check out this blog post for more information and some help on getting started.

There is a lot of modules, issues and security to keep track of when configuring your editor to Drupal, she goes through configuring and adding some good functionality.

Check out the video on her website.

Of course, we would recommend using MCFileManager and/or MCImageManager with Drupal to make it easier to work with images

Shoutouts to our friends at Ephox, for their great contribution to the TinyMCE code base.

Also shoutouts to the WordPress guys, congratulations on the 3.3 release, we now have 2 of our projects running within WordPress, both TinyMCE and Plupload.

Thanky you all for using our products.

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.