So far I'm liking this new message editor.
|
Hi All,
As readers of beta@ may know, there's a test of a new message editor afoot, which users can volunteer to join. So if you're the sort of person who likes to puzzle out a new feature, acid test it, and report your findings, you might want to give it a spin. I did, and am using it now. This editor has many more features, and removes one of my pet peeves with the old one. This editor turns Enter into <br/> rather than </p><p>. That's a good thing when you used one of them and wanted a line break. I'm not so sure if it is a good thing when you used two intending them as a paragraph break. Those with some knowledge of HTML will understand what I'm talking about here. If you don't, that's ok. It is (probably) a small point. It currently suffers one of the problems that (I think) got fixed in the old one: if your group "normalizes" HTML it nevertheless allows you to use and see in WYSIWYG formatting features that get stripped by normalization. I've only used it for a few test messages so far, so I wouldn't say that I've given it anything like a good test. One of the fun things is an insert tool for special characters - ¦¸ is the button icon for it. ¡ú It is a limited set ¡û but has many of the more useful glyphs. Gratuitous font change - the Lucida family is one I like. But this needs to be bumped up a bit to match the weight of the default (Helvetica Neue). Or, just to tweak the haters you can write in Comic Sans. Shal |
|
I wrote:
As readers of beta@ may know, there's a test of a new message editor afoot, which users can volunteer to join. So if you're the sort of person who likes to puzzle out a new feature, acid test it, and report your findings, you might want to give it a spin.Ok, that was unexpectedly awkward. I used the speech bubble button on the left of the formatting bar to insert a quote my prior message, then tried to break it into sections as I normally do to make inline comments like this one. Inserting and removing newlines did not break it. Nor did attempting to Decrease Indent. Then I noticed that the?¡° (Blockquote) button was pushed. So I selected my inline text and un-pushed it. Rather than removing the Blockquote attribute from just my inline text, it removed it from the entire quoted message. Fine. So I re-applied Blockquote on the prior section and moved on. It currently suffers one of the problems that (I think) got fixed in the old one: if your group "normalizes" HTML it nevertheless allows you to use and see in WYSIWYG formatting features that get stripped by normalization.I reported this one and Mark reports it to be fixed. I haven't retested it. One of the fun things is an insert tool for special characters - ¦¸ is the button icon for it. ¡ú It is a limited set ¡û but has many of the more useful glyphs.I noticed in a view source of my message that the special characters are inserted as named . This probably explains how those particular glyphs were chosen. I tried to insert other Unicode glyphs using the < > (Source code) mode to insert them as numeric references, but that failed. They got converted to asterisks by the editor. Some kind of exploit defense perhaps? Shal ? |
|
Hi Ginny,
I've created a Wiki page to start collecting observations on using the TinyMCE editor. I've boldly titled it Message editing tips and tricks, but it isn't in that form yet - just loose observations. Because it is such a rough draft at this point I haven't linked to it from any of the other Wiki pages. I probably won't until TinyMCE goes "live" because otherwise it would be confusing to readers who aren't testing the new editor. But in the mean time, please feel free to add your own observations and comments about using the new editor. Shal |
|
Hi Tony,
I too would like to have a look at and use TinyMCE. Can't figure out[email protected] will work. As will his corporate email, which if you receive individual messages from beta@ you could copy from any recent message of his. Shal |
Shal Farley