<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Support for both WYSIWYG and WikiStyle editors</title>
	<atom:link href="http://blog.pbwiki.com/2006/12/17/support-for-both-wyswyg-and-wikistyle-editors/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pbwiki.com/2006/12/17/support-for-both-wyswyg-and-wikistyle-editors/</link>
	<description>The official blog of PBwiki</description>
	<pubDate>Fri, 16 May 2008 04:52:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: michael callen</title>
		<link>http://blog.pbwiki.com/2006/12/17/support-for-both-wyswyg-and-wikistyle-editors/#comment-1136</link>
		<dc:creator>michael callen</dc:creator>
		<pubDate>Fri, 19 Jan 2007 17:44:02 +0000</pubDate>
		<guid isPermaLink="false">http://pbwiki.com/blog/?p=21#comment-1136</guid>
		<description>I have seen another Wiki website provider use a drop down choice for selecting between editors.  

It can be changed in the "configure" settings when desired.</description>
		<content:encoded><![CDATA[<p>I have seen another Wiki website provider use a drop down choice for selecting between editors.  </p>
<p>It can be changed in the &#8220;configure&#8221; settings when desired.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anemone</title>
		<link>http://blog.pbwiki.com/2006/12/17/support-for-both-wyswyg-and-wikistyle-editors/#comment-662</link>
		<dc:creator>Anemone</dc:creator>
		<pubDate>Thu, 21 Dec 2006 18:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://pbwiki.com/blog/?p=21#comment-662</guid>
		<description>That's great news.  There are too many tools that are not available on the WYSIWIG interface (e.g., buttons for "Paste without formatting", "Anchor", etc.) so that I constantly have to revert to HTML anyway, negating some of the benefits of using a wiki versus a classic Website.  If I'm going to markup by hand and on the fly, I might as well do it in wiki style.</description>
		<content:encoded><![CDATA[<p>That&#8217;s great news.  There are too many tools that are not available on the WYSIWIG interface (e.g., buttons for &#8220;Paste without formatting&#8221;, &#8220;Anchor&#8221;, etc.) so that I constantly have to revert to HTML anyway, negating some of the benefits of using a wiki versus a classic Website.  If I&#8217;m going to markup by hand and on the fly, I might as well do it in wiki style.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MattGriffin</title>
		<link>http://blog.pbwiki.com/2006/12/17/support-for-both-wyswyg-and-wikistyle-editors/#comment-628</link>
		<dc:creator>MattGriffin</dc:creator>
		<pubDate>Tue, 19 Dec 2006 14:59:17 +0000</pubDate>
		<guid isPermaLink="false">http://pbwiki.com/blog/?p=21#comment-628</guid>
		<description>THANK YOU. 

Let me second the bump for having both wikitext and wysiwyg interfaces for editing content. This would be perfect for a mix of wiki-savvy and word processor only collaborators where there is an active moderator (like me) who can always come in and fiddle with what other people did to make things cleaner, clearer, and populate links in all of the pertinent places.

 I FAR prefer wikiformat (and html) to WYSIWYG (at least at this point when the latter is a bit slower to load, slower to physically select, and lacks certain features like tricky tables and scripts stuff) because I can just stream out a page on the keyboard and save it. Most of my fellow collaborators will prefer the other version and aren't not quite sure that programs exist beyond MS Office!

I will say that the real worry I had with the WYSIWYG editor is how it handles spacing and the logic of switching between styles. I should probably read and memorize the CSS associated with the template or something to really grok this, but I was never quite sure what was going on with the WYSIWYG editor. I often retyping material when I got trapped in a heading or similar. These are natural kinks expected for bringing in a new tool, so I figure you'll iron these things out in the next month or so!

Maybe I've just been a wiki-geek in hiding all of these years, but I'd rather build a loose structure in wikitext, set the look of things, and then approach everything as WYSIWYG for content as a way to STOP thinking about formating. 

My real dream? Probably a pain in the tail. A WYSIWYG editor that has a toggle to reveal or conceal code/script stuff. If I could do my part to make a page beautiful and then know that my users won't flip out when they see HTML or complicated wikitext, then I would...I dunno....giggle? 

Matt

Matt</description>
		<content:encoded><![CDATA[<p>THANK YOU. </p>
<p>Let me second the bump for having both wikitext and wysiwyg interfaces for editing content. This would be perfect for a mix of wiki-savvy and word processor only collaborators where there is an active moderator (like me) who can always come in and fiddle with what other people did to make things cleaner, clearer, and populate links in all of the pertinent places.</p>
<p> I FAR prefer wikiformat (and html) to WYSIWYG (at least at this point when the latter is a bit slower to load, slower to physically select, and lacks certain features like tricky tables and scripts stuff) because I can just stream out a page on the keyboard and save it. Most of my fellow collaborators will prefer the other version and aren&#8217;t not quite sure that programs exist beyond MS Office!</p>
<p>I will say that the real worry I had with the WYSIWYG editor is how it handles spacing and the logic of switching between styles. I should probably read and memorize the CSS associated with the template or something to really grok this, but I was never quite sure what was going on with the WYSIWYG editor. I often retyping material when I got trapped in a heading or similar. These are natural kinks expected for bringing in a new tool, so I figure you&#8217;ll iron these things out in the next month or so!</p>
<p>Maybe I&#8217;ve just been a wiki-geek in hiding all of these years, but I&#8217;d rather build a loose structure in wikitext, set the look of things, and then approach everything as WYSIWYG for content as a way to STOP thinking about formating. </p>
<p>My real dream? Probably a pain in the tail. A WYSIWYG editor that has a toggle to reveal or conceal code/script stuff. If I could do my part to make a page beautiful and then know that my users won&#8217;t flip out when they see HTML or complicated wikitext, then I would&#8230;I dunno&#8230;.giggle? </p>
<p>Matt</p>
<p>Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clif Notes</title>
		<link>http://blog.pbwiki.com/2006/12/17/support-for-both-wyswyg-and-wikistyle-editors/#comment-610</link>
		<dc:creator>Clif Notes</dc:creator>
		<pubDate>Sun, 17 Dec 2006 23:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://pbwiki.com/blog/?p=21#comment-610</guid>
		<description>Thank you, thank you, and thanks again.

I'll be going out today to try out our new WYSIWYG wikis so I can learn more about the features.

I was thinking it would be really cool to have the ability to edit any wiki page in either format. Perhaps a checkbox at the top and bottom of the edit window would allow WYSIWYG or WikiStyle.

Best wishes and Merry Christmas

Clif</description>
		<content:encoded><![CDATA[<p>Thank you, thank you, and thanks again.</p>
<p>I&#8217;ll be going out today to try out our new WYSIWYG wikis so I can learn more about the features.</p>
<p>I was thinking it would be really cool to have the ability to edit any wiki page in either format. Perhaps a checkbox at the top and bottom of the edit window would allow WYSIWYG or WikiStyle.</p>
<p>Best wishes and Merry Christmas</p>
<p>Clif</p>
]]></content:encoded>
	</item>
</channel>
</rss>
