where is TinyMCE 5.2 version?

Sorry I haven't responded sooner. I think we've finally found a plan to move forward that the Moxie module developers are happy with. We're calling this the "Borris Mann Plan". I was hoping for a fix for TinyMCE (the Moxie Systems toolbar, not the module) that ufku identified. That hasn't happened. I am working on the 5.2 branch now.

There is as yet no release or tag for what is being discussed as '5.2'. Looking at the .module file, the last version I find along the drupal-id/thenicespider approach is this:

// $Id: tinymce.module,v 1.90.4.12 2007/01/30 06:58:37 thenicespider Exp $

The next commit,

// $Id: tinymce.module,v 1.90.4.13 2007/02/07 12:15:19 thenicespider Exp $

overwrote this version with the original module version. This is what is now in the 5.2 branch. So, for now, the only way of getting that drupal-id code would be to do a CVS checkout of the module prior to that commit.

Correct. The 2.1 release from Moxiecode of TinyMCE fixes the IE issue, but there is still a problem with Safari and 5.2. The 5.2 code I'm using is a version of 5.1 that includes the customized role/theme.js hack I wrote to meet my needs, so it isn't suitable for a release.

My top priority has been to fix the issues with official releases of the module. The TinyMCE 2.1 did that for 5.1. I thought putting the broken 5.2 code out there would only confuse things more.

Now right now I'm looking at fixing 5.2's issue with Safari. Then I will look into ways to improve the role/theme/content type features in a way that it would be more flexible than the 5.1 method. Finally, I was going to look at ways to have both the a GUI button picker AND custom .js themes. I was thinking that a GUI .js theme creator would work, but Allie didn't like that approach for multisite installs.

Well it seems to me that 5.1 should be tagged and an official release setup.

Then work can start again DRUPAL-5 to add in these new features & fixes.

Just my $0.02 coming from the guy that largely wrote the 4.7 version of TinyMCE ;-)

Nedjo kindly volunteered to clean up the CVS. We've been exchanging email about whether 5.2 should be based on the current 5.1 OR the old 5.1. Essentially... should the current 5.1 become the Head? This is important for those of use who started using features included in the 5.1 release that required custom .js themes during the first 30 days of Drupal 5.

Since there were issues in both the Moxie module and the 5.1 TinyMCE module codebase until Moxiecode released TinyMCE 2.1, it was hard to tell which direction was going to save time.

I've been trying to clear the issue of queue to figure out what real issues (if any) exist with the 5.1 release so we can address those. AFAICT the only real issue with 5.1 is the vertical resize which is VERY important to users with 3 column sites, but not much of an issue for others.

The only other issues that I'm aware of are the need to support for custom plugins and issues with GZ compressor.

I think we're finally at the point where we have a clear enough idea of where 5.1 is at and where we want to go with 5.2 that we can move forward.

One thing that I would find EXTREMELY helpful is to clear more of the 4.7 issues from the queue. I don't mind dealing with the new 4.7 issues, but I'm not familiar enough with the 4.7 releases to know when/if some of these issues have been fixed.

m3avrck?