Since most of the users use only one theme in one SPAW installation and themes take the most time to upload to the deployment server (because they consist of hundreds of small images), we decided to extract SPAW1 theme from core SPAW Editor v.2 distribution and provide it as a separate download from our Extend page instead.

We have plans to release final version of SPAW Editor v.2.0.0 next week (probably in the first half). Among exciting news it also means that only a couple of days are left for the discounted prices on commercial licenses and upgrades. When v.2.0.0 is released the prices will be back to normal. So, if you were planning on purchasing a commercial license or upgrading your v.1 license, don’t miss your chance to save. Purchase links are available here.

We have just added a documentation section to our website. Currently it contains Integrator’s Guide (available with v.2.0.0RC distribution) and newly added Plugin Developer’s Guide. So, you can start developing your own plugins right away.

We have also created a new forum dedicated to plugin development.

We have just released the first SPAW Editor v.2 Plugin - Zoom. This plugin adds zoom dropdown to plugins toolbar allowing users to zoom in and out on editing area.

It can be downloaded via our new “Extend” page here.

Unfortunately the way it’s done is only supported in MSIE. In case you know how to achieve the same effect in other browsers (Opera has zoom in menu so it could have a way to do the same via code) drop a comment to this post. Thanks!

We’ve found a small bug in release candidate (it could be not that small for some users): all the attributes except style and class were stripped from span, div and font tags. While fixing this bug we’ve also added code to replace those deprecated font tags with their span equivalents.

Updated js/common/editor.js file could be downloaded from sourceforge.net SVN repository. Just overwrite the old file with this one.

We have just released SPAW Editor PHP Edition v.2.0.0 Release Candidate!

Thanks to everyone who downloaded and tried our first v.2 beta! Your feedback was extremely helpful to bring SPAW Editor v.2 closer to the stable release.

Thanks to you we have fixed quite some bugs, added a couple of small features like links to files, keyboard navigation in file manage, etc. (see changelog for details). We believe that in current state it is already mature enough to be used in production environment (we use it to edit our own site) so we encourage you to download, try it and let us know if you find something not working as it should and help us make it as solid as possible by the time of the final v.2.0.0 release in early January.

In the meantime we will concentrate on creating documentation for plugin developers, theme designers, etc., writing some plugins ourselves, fixing some small quirks that are not yet fixed and migrating language files.

Here’s a complete list of changes in this release:

• FEATURE ADDED: config variable ‘base_href’ added to specify protocol and domain part to be added to URLs returned from file manager (use in conjunction with strip_absolute_urls = false)
• FEATURE ADDED: SpawFm plugin returns full file URL if config variable
    ‘base_href’ is specified and is not empty
• FEATURE ADDED: browse button in hyperlink dialog to insert links to files
• FEATURE ADDED: SpawFm plugin keyboard navigation
• FEATURE ADDED: added setStaticConfigValueElement, getStaticConfigValueElement,  getConfigValueElement, setConfigValueElement methods to config and editor classes
• FEATURE ADDED/BUGFIX: editor/page names now can contain square brackets ([ and ])
• OPTIMIZATION: updateToolbar now only checks toolbar item status/value if it’s enabled
• CHANGE: changed default resizing direction in config file to “vertical”
• CHANGE: disabled file upload button is shown in SpawFm plugin if upload is not allowed
• BUGFIX: if submit() method was used on a submit type control (input type=submit or type=image) this often resulted in lost content
• BUGFIX: form onsubmit event handler was added multiple times if there were more than 1 editor instance resulting in unexpected HTML rendering results
• BUGFIX: editor was unusable in Internet Explorer when inserted into page with XHTML doctype declaration
• BUGFIX: editing area wasn’t editable in Mozilla (and probably older versions of Firefox)
• BUGFIX: custom_tbi_css_events used where custom_tbi_events was assumed
• BUGFIX: SpawLang->getLang was just a copy of setLang
• BUGFIX: when moving focus to other editor in Gecko active editor wasn’t set
• BUGFIX: javascript error was generated in Opera when inserting at the end of document
• BUGFIX: in xhtml beautification process br tag wasn’t generating new line and indentation
• BUGFIX: extra quote in one tag in SPAW2 theme templates
• BUGFIX: flash wasn’t properly rendered in html under IE
• BUGFIX: flash wasn’t replaced with placeholder images on initialization
• BUGFIX: in Gecko based browsers disabled buttons were still clickable
• BUGFIX: Javascript error on iframe focus in SpawFm Plugin
• BUGFIX: content wasn’t always correctly inserted under Gecko and Opera
• BUGFIX: php notice in SpawFm plugin
• BUGFIX: text wasn’t properly html encoded when rendered to HTML
• BUGFIX: updated xhtml rendering engine: empty paragraphs were rendered without   under IE, useless empty elements removed (b, i, etc.)
• BUGFIX: added indentation for ul, ol, li, thead, tfoot tags
• BUGFIX: added default_output_charset config variable, dialogs now use user specified output charset, modified setLanguage method to accept output charset as a second parameter
• BUGFIX: ‘.’ and ‘..’ directories were shown in SpawFm plugin
• BUGFIX: some execCommand related calls were throwing exceptions under Gecko
• LANGUAGE FILE ADDED: Hungarian (Szentgyörgyi Janos, www.dynamicart.hu)

SPAW Editor finally got a dedicated domain name spaweditor.com It points to the same SPAW’s page on Solmetra.com but could be easier to remember.

We have just released first beta of SPAW Editor v.2!

Check it out

I’m a little afraid to claim this cause I didn’t do extensive research but I think this is quite a unique feature in browser based WYSIWYG editor world. Correct me if I’m wrong.

If the picture doesn’t tell the whole story here it is. You can have several editing fields combined into one editor as tabs. Much like in tabbed browsing. This way, if you had like 20 WYSIWYG editors on a page occupying quite some “pagedowns”, now you can combine all of them into a single instance of SPAW Editor and get away with no scrollbars at all!

You can have a single toolbar controlling several SPAW instances. This toolbar could either be docked to one of the editors or floating around the screen. You can also have additional “standalone” SPAW instances on the same page or additional instances with separate “floating toolbars”.

Click on the image to enlarge (since new buttons are still in development SPAW 1.x theme was used for this demo).