TIGHAR

Chatterbox => Extraneous exchanges => Topic started by: Martin X. Moleski, SJ on June 15, 2011, 06:18:30 PM

Title: Testing the WYSIWYG editor
Post by: Martin X. Moleski, SJ on June 15, 2011, 06:18:30 PM
There seems to be a new function in the User's Profile to allow the use of a What You See Is What You Get (WYSIWYG) editor when you are posting.

http://tighar.org (http://tighar.org/)

It is very interesting and may be helpful for people who are phobic about using tags to mark up their posts.  Well it's not perfect by any means.  The glow tag doesn't show you a preview.

Superscript does work.  So, apparently, does subscript.

Ahhhhhh.  There is a "toggle view" button that lets you go back and forth between WYSIWYG and tag-markup.

The table is not WYSIWYG.
No amateurs need apply!
And the table lacks lines.  That's no fun.
Title: Re: Testing the WYSIWYG editor
Post by: Erik on June 15, 2011, 06:31:30 PM
Quote from: Martin X. Moleski, SJ on June 15, 2011, 06:18:30 PM
The glow tag doesn't show you a preview.

The preview worked for me.   :o
Title: Re: Testing the WYSIWYG editor
Post by: Martin X. Moleski, SJ on June 15, 2011, 08:23:56 PM
Quote from: Erik on June 15, 2011, 06:31:30 PM
Quote from: Martin X. Moleski, SJ on June 15, 2011, 06:18:30 PM
The glow tag doesn't show you a preview.
The preview worked for me.   :o

What I meant was that it doesn't glow in the WYSIWYG mode.  You are correct that it does show up in the preview and in the finished post.

To see the WYSIWYG mode, click the "A" button under the "Change Color" field.  You can turn it on by default in your User Profile--somewhere or another.

I'm having a little meltdown right now, or else I'd do a tutorial.  I was walking away from the keyboard feeling good about the upgrade two hours ago.  Then I found a bug in JFusion's SMF plugin.  The SMF developers have changed many of their field names.  I think I've patched the plugin--time will tell!--so it's time to try the "walk away feeling good" routine again.
Title: Re: Testing the WYSIWYG editor
Post by: Erik on June 16, 2011, 07:36:37 PM
Ok, I'll check that out. 
 
Is there a way to check out which mode your in?  The A  just toggles but doesn't indicate the mode you are currently operating in. 
 
FYI = the GLOW feature produces errors on RSS feeds regardless of which toggled mode you are in when you created the post.
 
 
Title: Re: Testing the WYSIWYG editor
Post by: Martin X. Moleski, SJ on June 16, 2011, 07:44:56 PM
Quote from: Erik on June 16, 2011, 07:36:37 PM
Is there a way to check out which mode your in?  The A  just toggles but doesn't indicate the mode you are currently operating in. 


A blue background on the button seems to indicate that WYSIWYG mode is on.

A grey background means WYSIWYG is off.

Quote
FYI = the GLOW feature produces errors on RSS feeds regardless of which toggled mode you are in when you created the post.

Bummer.  Does it destroy the whole message?  Show you the tags? 
Title: Re: Testing the WYSIWYG editor
Post by: Erik on June 16, 2011, 09:17:12 PM
Quote from: Martin X. Moleski, SJ on June 16, 2011, 07:44:56 PM

A blue background on the button seems to indicate that WYSIWYG mode is on.

A grey background means WYSIWYG is off.


Gotcha... I see now.
 



 
Title: Re: Testing the WYSIWYG editor
Post by: Erik on June 16, 2011, 09:19:00 PM
Quote from: Martin X. Moleski, SJ on June 16, 2011, 07:44:56 PM

Quote
FYI = the GLOW feature produces errors on RSS feeds regardless of which toggled mode you are in when you created the post.

Bummer.  Does it destroy the whole message?  Show you the tags?

Good news.  It must have fixed itself.  It's not happening anymore...
Title: Re: Testing the WYSIWYG editor
Post by: Martin X. Moleski, SJ on June 16, 2011, 09:39:17 PM
Quote from: Erik on June 16, 2011, 09:19:00 PM
Good news.  It must have fixed itself.  It's not happening anymore...

Ah--I suppose maybe it was related to the problems we had with IE.

One was my fault (some misplaced PHP being sent before headers).

The other was a new meta tag intended for IE8 that I needed to add to the mix.

At any rate, I'm delighted to hear that the bug seems to have gone away.  :)