Wysiwyg 2.1

Yes we really should make a 2.1 release soon. Still have a few more issues which need to get in before I'm satisfied though, and I'll have to discuss it with Sun of course.

Any updates on this?

Here's my personal todo list with some notes on what I think 2.1 should have.
A ton of fixes have already been made to 2.x-dev since 2.0 but I think it would be nice to have as many of these in as well. That way we should have a more solid base to work on for when 3.x development really gets going.

Please note that the issues are only loosely grouped and not sorted by anything specific. I haven't shown this to sun yet so I have a hunch he'll have a thing or two to say about it. ;)

Easy to fix, just needs a review or proper patch. "Must have"s:
#667848: FCKeditor is not properly detached in IE Data loss in IE!
#659200: Using YUI Rich Text Editor with 2.8.0r4 version of the YUI library causes page content to be lost Data loss in at least IE!
#557100: Finnish translation for Wysiwyg (Don't know if this is still accurate, but shold be no problem to commit.)
#620176: No Ukrainian options in Language list
#597852: There is no turkish lang selection
#659194: YUI Editor should check the version in build/editor/editor-min.js Revert.
#660080: Notice: Undefined offset A warning on profiles overview, no serious problems.
#631494: Multi-site Libraries Directory Failure WYMEditor
#689218: Improved support for CKEditor At least parts of this could go in 2.1

Not difficult to fix but needs attention. "Should have"s:
#659680: WhizzywigToolbar.png not found Fixed merged into patch for issue below.
#557090: Old Whizzywig instance not removed on detach(). Patch creates a new .js implementation due to API changes in the library.
#594928: The 'Attribs' button is missing in TinyMCE
#613480: PHP 5.3 Support
#613922: "Warning Invalid Argument" when you click Save on admin/settings/wysiwyg but haven't made any changes

Would be nice to have fixed in 2.1. "Want to have"s:
#550428: Tags like "&nbsp;" or "<p>&nbsp;</p>" or "<br />" added to empty textareas. Makes "empty" fields show up in Views etc.
#510552: Invalid XHTML: missing trailing slashes, absolute urls and uppercase tags
#497654: Drupal plugin buttons disabled in WebKit based browsers
#594322: Add nicEdit insert method. NicEdit
#613944: data.node object not present in FCKeditor/CKEditor
#671528: Support custom css styles FCKeditor, might be tricky to get user friendly names.

Others which need discussions:
#627180: TinyMCE: Firefox's build-in spelling checker is disabled Always enable it? (We can't have a GUI option for it until the issue about advanced settings is fixed for 3.x)
#678580: Drupal.wysiwygAttachToggleLink hijacks my click event :( "Let's play nice with other scripts"-thing.
#628110: Allow to alter profile and editor settings GUI support for advanced settings won't be in until 3.x and the workarounds to inject settings aren't working that well. This would be very helpful.

subscribing

Yes it's a long list and I'm certainly not counting on getting all that into 2.1 as it is more a list of "candidates" for inclusion. I would however insist that we wait with 2.1 until at least the top group and some of the second group are committed, either because they are really simple or cause big problems/annoyances.
All that's left for most of them is just a second opinion either from sun or the community.

Also, I had nowhere else to keep a todo with auto-updating statuses which just needs a quick look to get an overview, the issue queue re-orders itself too much, so I hijacked this issue. ;)

I took a first stab today and will continue with the first two sections this tomorrow or at least this weekend.

I'd like to move improved CKEditor support into the must have issues. I think that would be great to do.

Awesome work sun!

Moved the issue up like you suggested.

I probably would have another stopper : http://drupal.org/node/693418 (if you guys agree ofc)

subscribing

subscribe

Tackled some more today. While merging and syncing code around branches, I realized that there are a couple of changes that only exist in 2.x or 3.x (i.e. vice-versa), and while some of them may be on purpose, a couple of them looked like they were forgotten. I'll try to figure out the issues/patches and re-open the corresponding issues later on.

sub...

Alrighty. Can we summarize the current status?

Can people report back whether updating to the latest development snapshot of 2.x works without errors?

Any pressing/critical issues left that we absolutely need to tackle for 2.1? (note: there's always a 2 after a 1!)

Otherwise, it's likely that I'll create 2.1 tonight. However, feedback from testing the most recent dev snapshot would really be great to have upfront.

hefox created a demo site for Wysiwyg 2.x-dev and recorded some (minor) bugs in #713942: OpenWYSIWYG broken, jWysiwyg needs jQuery 1.3+

I am using the latest 2.x-dev for a couple of weeks now. It seems to be fine. Anyway, I think this #606952: Inserting content in fullscreen TinyMCE should be committed in the new release.

Thanks for your feedback! However, not sure what "a couple of weeks" means -- plenty of stuff changed just recently, so we need feedback for the dev snapshot from 2010-Feb-14, available on the project page.

Sorry, if I wasn't clear. I am using the actual dev snapshot from 2010-Feb-14 with the patch applied from the issue linked in my previous post above.

Subscribing.

Thanks for reporting back! :)

http://drupal.org/project/wysiwyg