[WYSIWYG] [Beta 2] Feedback Thread

[Kier]

Let's continue the discussion here.

[Grover]

The new editor is a lot more efficient - it runs faster due to more streamlined code, it loads faster due to quite a few fundamental changes to the initialization systems, it's easier to put into systems (we'll be putting it into the bug tracker shortly) and the code is put together in such a way that it will do the best job it can with the browser running it. (ie: as soon as Safari matures, it will automatically get all the features of the rest of the modern browsers, without us having to alter the code)

This is very good to hear. Feedback like this from the developers team makes it better to understand why some decisions have been made and what we can (or may) expect in the future. Communication like this to the customerbase is very much appreciated.

Hopefully with the new improved and easy to implement editor, our wishes posted in : Announcement manager redesign or upgrade is needed
can be fullfilled for 3.5.0 Gold.

[Mainer82]

Can we have some news on the new polling system? I'm anxious to here what's planned.

[Kier]

The new editor automatically sizes the attachments and sizes popups.

[buro9]

Does the font Size selector allow us to easily remove some of the sizes?

I don't allow my members to use size 6 and 7, as I just see no need for those sizes on my site.

When I stripped them out of my site, I noticed that I had to manually resize the dimensions of the popout layer after I had changed the font size options.

Will this still be the case?

[polat_alemdar]

[WYSIWYG] [Beta 2] veryyyy good

[Erwin]

Wow... very nice!

[Mac Write]

Thanks Kier.

How about the Styles manager? Does it work like IE now? How about background/foreground color in form elements (or why not just use button instead of the input form button)?

Also how soon after the WYSIWYG editor works in Safari will it be updated to work in VB (or is it there already and it will just work once it is fixed in Safari).

Lastly now that when you click on the font color a proper drop down works, will that be changed in the adminCP for color section for Safari? (Don't have the money to renew at present).

Thanks Kier.

[welo]

But ultimately, a spell checker should be a client side thing, IMHO. So I hope the ieSpell folks manage to make it work for Mac and Linux, and the various browsers.

I disagree (spellchecker should be an indigenous part of any BB software), although if Firefox folks want a browser spellchecker there's always the SpellBound plugin. Works really well long as you remember to install the dictionary for it .

[tamarian]

I wish there was a better dictionary than IEspell...especially since it doesn't work for our mozilla/firefox users

I've released this hack for 3.5 beta:

http://www.vbulletin.org/forum/showt...threadid=83258

Some of my users (on 3.0.7) still prefer it over ieSpell.

But ultimately, a spell checker should be a client side thing, IMHO. So I hope the ieSpell folks manage to make it work for Mac and Linux, and the various browsers.

[Grover]

Did you guys try the attachment manager drop down yet?
[ATTACH]14695[/ATTACH]
How is THAT for a unique feature


The video: http://www.vBulletin-Fans.com/attachdropdown.htm

Brilliant! Much, much better (more logical) then before. Things seem to be improving constantly during this beta-process. Good to see!

[welo]

Something I don't really understand is why the BB code for font formatting is inserting quotes for the parameters, e.g.:

[FONT="Arial Black"]This is a font[/FONT]
[SIZE="4"]Here is another font[/SIZE]
[COLOR="Olive"]Woohoo, the last font[/COLOR]

If you look at the source of the page for the following two examples:

Without quotes:

This is a font
Here is another font
Woohoo, the last font

With quotes:

This is a font
Here is another font
Woohoo, the last font

...it is rendering the code correctly whether you use quotes or not. Since it works either way no big deal, really. Just seems to me like it has the potential to confuse non-HTML-savvy users by unnecessarily cluttering up the BB code. Even switching to WYSIWYG mode the version w/o quotes still works.

(Incidentally, if you switch from standard to WYSIWYG mode on the fly then switch it back again, the quotes are magically removed from the BB code.)

[Kier]

In Opera I don't see the quick switch from WYSIWYG to simple editor.

When Opera has the capability to use contentEditable or designMode, we will include support for it in vBulletin.

[Kier]

Safari 1.3 and 2.0 already support Inline WYSIWYG editing. So what's stopping vb working with it? Kier do you test code on a Mac personally? Does Safari 1.3/2 now work properly with the IE version of the template editor?

Safari's impementation of contentEditable/designMode is laughably bad right now (even the Safari developers admit this).

I even bought a Mac to see if anything could be salvaged and made workable as a WYSIWYG editor for Safari but unfortunately it was just not meant to be.

Let me give you a few examples:

The following commands work as expected:

• Bold
• Italic
• Underline
• Align Left
• Align Center
• Align Right
• Font Color
• Font Name
• Undo
• Redo
• Cut
• Copy

The following commands have problems:

• Font Size
  This only works with if CSS size values are passed to it, making it incompatible with BBcode
• Insert Image
  Does not insert an image at all
• Create Link
  Does not create a link at all
• Remove Link
  Does not remove a link, and hyperlinks within the WYSIWYG editor actually act as links, so if you accidentally click one, you visit that page (oh dear)
• Insert List (ordered or unonrdered)
  Fails to do anything
• Indent
  Fails to do anything
• Outdent
  Fails to do anything
• Paste
  I find this rather amusing - Cut and Paste work as expected, but paste does nothing (oh dear again)

Additionally, if anything triggers an onclick event the selection within the editor window is lost. There is a workaround for this but it's ugly and kinda unintuitive for the user.

Another 'special' feature is that if you select all the text in the edit window, Safari decides that you actually want to select the window itself, and none of the formatting controls will work at that point. This is particularly annoying if you have just typed a single word into the editor and want to apply formatting to it - it's just not possible.

With all these problems it just doesn't seem worth hacking together something that will work around the issues with Safari. That said, as soon as the Safari developers give us something decent to work with the new vBulletin editor will be updated.

[Sephiroth]

In Opera I don't see the quick switch from WYSIWYG to simple editor.