<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: My Bad</title>
	<atom:link href="http://bbpress.org/blog/2009/12/my-bad/feed/" rel="self" type="application/rss+xml" />
	<link>http://bbpress.org/blog/2009/12/my-bad/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 05 Feb 2012 20:28:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dantel</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22954</link>
		<dc:creator>Dantel</dc:creator>
		<pubDate>Sat, 11 Dec 2010 20:43:01 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22954</guid>
		<description>Regarding a WYSIWIG editor, I added very stripped down TinyMCE to a bbPress install I run on a site that has a very non-technical audience. It only has minimal buttons for basic features. The users absolutely loved it and are so happy they can do things they didn’t understand before. Even the plugins that gave buttons for inserting HTML or bbcode were too confusing because they inserted code into the text that didn’t mean anything to the audience. They just want to be able to visually make something bold, italic, or add a link. So adding Oembed support would not meet the need in that kind of scenario.</description>
		<content:encoded><![CDATA[<p>Regarding a WYSIWIG editor, I added very stripped down TinyMCE to a bbPress install I run on a site that has a very non-technical audience. It only has minimal buttons for basic features. The users absolutely loved it and are so happy they can do things they didn’t understand before. Even the plugins that gave buttons for inserting HTML or bbcode were too confusing because they inserted code into the text that didn’t mean anything to the audience. They just want to be able to visually make something bold, italic, or add a link. So adding Oembed support would not meet the need in that kind of scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akvaryum</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22953</link>
		<dc:creator>Akvaryum</dc:creator>
		<pubDate>Sat, 11 Dec 2010 20:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22953</guid>
		<description>WordPress strongly suggests that the best way to stay secure is to always have the latest version of WP installed, but when that doesn’t correlate with BBpress, we’re then left a choice we don’t want to make. Given that in the past 2 years we’ve had 5 versions of BBpress and 5 versions of WordPress, and only 2 combinations out of the 25 have integrated at any given time (though there was a hack to make 1 more combination work for a few months), WordPress integration has, whether rightly or wrongly, come to be seen a yardstick to gauge many things by.</description>
		<content:encoded><![CDATA[<p>WordPress strongly suggests that the best way to stay secure is to always have the latest version of WP installed, but when that doesn’t correlate with BBpress, we’re then left a choice we don’t want to make. Given that in the past 2 years we’ve had 5 versions of BBpress and 5 versions of WordPress, and only 2 combinations out of the 25 have integrated at any given time (though there was a hack to make 1 more combination work for a few months), WordPress integration has, whether rightly or wrongly, come to be seen a yardstick to gauge many things by.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Giyim modası</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22949</link>
		<dc:creator>Giyim modası</dc:creator>
		<pubDate>Sat, 11 Dec 2010 20:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22949</guid>
		<description>I think an editor WYSIWYG editor is not very useful. Webmasters away from being original.</description>
		<content:encoded><![CDATA[<p>I think an editor WYSIWYG editor is not very useful. Webmasters away from being original.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ahmetkirik</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22920</link>
		<dc:creator>ahmetkirik</dc:creator>
		<pubDate>Fri, 10 Dec 2010 15:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22920</guid>
		<description>Any chance you might offer the stripped down TinyMCE as a bbpress plugin?

I tried using another TinyMCE plugin someone else made but there was no hyperlink button built in.</description>
		<content:encoded><![CDATA[<p>Any chance you might offer the stripped down TinyMCE as a bbpress plugin?</p>
<p>I tried using another TinyMCE plugin someone else made but there was no hyperlink button built in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22419</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 23 Dec 2009 23:51:02 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22419</guid>
		<description>@ Doug Smith:

Any chance you might offer the stripped down TinyMCE as a bbpress plugin?

I tried using another TinyMCE plugin someone else made but there was no hyperlink button built in.</description>
		<content:encoded><![CDATA[<p>@ Doug Smith:</p>
<p>Any chance you might offer the stripped down TinyMCE as a bbpress plugin?</p>
<p>I tried using another TinyMCE plugin someone else made but there was no hyperlink button built in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22410</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Tue, 22 Dec 2009 18:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22410</guid>
		<description>I&#039;m really in favor of email notification that works - I&#039;ve had no luck with the plugins. Anything to make the bb more sticky for my users.</description>
		<content:encoded><![CDATA[<p>I&#8217;m really in favor of email notification that works &#8211; I&#8217;ve had no luck with the plugins. Anything to make the bb more sticky for my users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Smith</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22407</link>
		<dc:creator>Doug Smith</dc:creator>
		<pubDate>Mon, 21 Dec 2009 03:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22407</guid>
		<description>Like so many others, I voted for more integration with WordPress. It would be a huge advantage to have things like shared search, the ability to display posts from either WordPress or bbPress on each other&#039;s pages, common widgets, and logins always working across the two.

Regarding a WYSIWIG editor, I added very stripped down TinyMCE to a bbPress install I run on a site that has a very non-technical audience. It only has minimal buttons for basic features. The users absolutely loved it and are so happy they can do things they didn&#039;t understand before. Even the plugins that gave buttons for inserting HTML or bbcode were too confusing because they inserted code into the text that didn&#039;t mean anything to the audience. They just want to be able to visually make something bold, italic, or add a link. So adding Oembed support would not meet the need in that kind of scenario.</description>
		<content:encoded><![CDATA[<p>Like so many others, I voted for more integration with WordPress. It would be a huge advantage to have things like shared search, the ability to display posts from either WordPress or bbPress on each other&#8217;s pages, common widgets, and logins always working across the two.</p>
<p>Regarding a WYSIWIG editor, I added very stripped down TinyMCE to a bbPress install I run on a site that has a very non-technical audience. It only has minimal buttons for basic features. The users absolutely loved it and are so happy they can do things they didn&#8217;t understand before. Even the plugins that gave buttons for inserting HTML or bbcode were too confusing because they inserted code into the text that didn&#8217;t mean anything to the audience. They just want to be able to visually make something bold, italic, or add a link. So adding Oembed support would not meet the need in that kind of scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22406</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 21 Dec 2009 02:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22406</guid>
		<description>Steve, no need to be dogmatic, we&#039;re in a brainstorming stage so all ideas are worth entertaining. We want to make bbPress accessible to people who can&#039;t build their own WYSIWYG, like me. :) We&#039;re going to beef up core functionality to not be so reliant on plugins, and that&#039;s not a bad thing.</description>
		<content:encoded><![CDATA[<p>Steve, no need to be dogmatic, we&#8217;re in a brainstorming stage so all ideas are worth entertaining. We want to make bbPress accessible to people who can&#8217;t build their own WYSIWYG, like me. <img src='http://bbpress.org/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  We&#8217;re going to beef up core functionality to not be so reliant on plugins, and that&#8217;s not a bad thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22405</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 20 Dec 2009 20:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22405</guid>
		<description>@ Steve Bank:

&quot;There’s already 2 working WYSIWYG plugins for BBpress&quot;

I currently have BBcode Buttons installed (http://bbpress.org/plugins/topic/bbcode-buttons/).

Tried Tiny MCE (3.2.5) (http://bbpress.org/plugins/topic/tinymce/#post-4021) but there is no way to hyperlink things.

Are these the 2 you mean? Is there another program I&#039;m missing? (I&#039;m not a developer, just a newbie who taught himself how to muddle though WordPress and bbPress...am skeptical about my plugin development skills)

LOL, I certainly understand that bbPress is minimalist and not claiming to have everything but the kitchen sink. &quot;Less (code) is more&quot; &quot;Simplicity is a feature&quot;. But with vBulletin&#039;s updated licensing costs there is going to be an opening for bbPress to be a vBulletin killer a la what WordPress did to MovableType in 2004. Just saying if bbPress got a little more feature-rich it would go a long way toward positioning itself as that alternative ;)</description>
		<content:encoded><![CDATA[<p>@ Steve Bank:</p>
<p>&#8220;There’s already 2 working WYSIWYG plugins for BBpress&#8221;</p>
<p>I currently have BBcode Buttons installed (<a href="http://bbpress.org/plugins/topic/bbcode-buttons/" rel="nofollow">http://bbpress.org/plugins/topic/bbcode-buttons/</a>).</p>
<p>Tried Tiny MCE (3.2.5) (<a href="http://bbpress.org/plugins/topic/tinymce/#post-4021" rel="nofollow">http://bbpress.org/plugins/topic/tinymce/#post-4021</a>) but there is no way to hyperlink things.</p>
<p>Are these the 2 you mean? Is there another program I&#8217;m missing? (I&#8217;m not a developer, just a newbie who taught himself how to muddle though WordPress and bbPress&#8230;am skeptical about my plugin development skills)</p>
<p>LOL, I certainly understand that bbPress is minimalist and not claiming to have everything but the kitchen sink. &#8220;Less (code) is more&#8221; &#8220;Simplicity is a feature&#8221;. But with vBulletin&#8217;s updated licensing costs there is going to be an opening for bbPress to be a vBulletin killer a la what WordPress did to MovableType in 2004. Just saying if bbPress got a little more feature-rich it would go a long way toward positioning itself as that alternative <img src='http://bbpress.org/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Bank</title>
		<link>http://bbpress.org/blog/2009/12/my-bad/comment-page-1/#comment-22404</link>
		<dc:creator>Steve Bank</dc:creator>
		<pubDate>Sun, 20 Dec 2009 16:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/?p=300#comment-22404</guid>
		<description>Chris (GrassRootsPA),

You&#039;ve answered your own question buddy.

&quot;The thing I do not like about bbPress is how reliant everyone/everything is on 3rd party plugins to do basic bulletin board stuff. This is a blessing for those of you who are minimalists but it is a curse for those who want bbPress to be a vBulletin killer.&quot;

This project never claims to be a vBulletin or phpBB killer. It does claim to be minamilist. Look at http://bbpress.org/about/ .

&lt;blockquote&gt;
# Less (code) is more
# Simplicity is a feature
&lt;/blockquote&gt;

# I dream of bbPress being more like feature-rich WordPress where more basic features are added to the Core and more plugins developed to flesh out those features even further.&quot;

&lt;blockquote&gt;
# Simplicity is a feature
&lt;/blockquote&gt;

See mate, you&#039;re projecting your desires onto a product that in no way is going in the same dierction (and never has been). You want all these things that aren&#039;t what BBpress is all about. Heck WordPress is actually a very bare product at the front end (for the user), so i&#039;ve no idea why you think BBpress is going ot go the other way, especially when it says and has always said it wont (cunningly hidden on the About and Feature pages to avoid confusion).

&quot;I really don’t get the hangup re: an OPTIONAL (you can turn it on or off) WYSIWYG editor. It won’t break in future bbPress updates because its in the Core and if you don’t like it, simply turn if off. Blam, everyone is happy.&quot;

Mostly because you already have that feature via a plugin. You can download it and turn it on :)

Ther&#039;s loads of reasons for this:

 Its JavaScript reliant, usually on the latest version of a library that is outwith BBpress&#039;s control.
 The WYSIWYG editors are quite intesive for older machines and browsers - remember most of the world still uses dial up and IE; and if you remove North America from the statistics the percentage of 5-6 year old versions of Windows and usage of IE6 sky rockets. Why would we all get behind a feature will just cause problems throughout the world.
 These things display differntly in every browser, and require a bucketload of testing all on their own. TinyMCE for example, has a testing/development team thats twice the size of BBpress.
 We only have a limited amount of development time, why should something like a WYSIWYG edtor be developed by the BBpress team into the core when any idiot can add 3 lines of javascript code to their theme if they really want it? Why should the BBpress team take the responsability and time to bugfix that?
 Why should users who came to this project based on the Philosophy in the About page have to turn off features that go against this philosophy simply because some people think they&#039;re cool.
 There&#039;s already 2 working WYSIWYG plugins for BBpress. Neither of them are that popular based on downloads, less than 5 of the Top100 websites on CK&#039;s list used them, so why should they be included in the core of plugins that are popular?
 I build my custom WYSIWYG plugin in about 4 hours. Bug fixing took a few hours over the next weeks. If you really want it, you can use TinyMCE (3 lines of JS on your theme),  one of the 2 existing plugins, or build your own like i did.


BBpress is build on certain principles mate, with a very limited development time (currently at 0hours from July 15th-Dec15th). Browser dependant interactive options for the user that administrators have to turn off just is nott part of the remit matey - especially when you have plugins that can do it already (and they aren&#039;t popular).</description>
		<content:encoded><![CDATA[<p>Chris (GrassRootsPA),</p>
<p>You&#8217;ve answered your own question buddy.</p>
<p>&#8220;The thing I do not like about bbPress is how reliant everyone/everything is on 3rd party plugins to do basic bulletin board stuff. This is a blessing for those of you who are minimalists but it is a curse for those who want bbPress to be a vBulletin killer.&#8221;</p>
<p>This project never claims to be a vBulletin or phpBB killer. It does claim to be minamilist. Look at <a href="http://bbpress.org/about/" rel="nofollow">http://bbpress.org/about/</a> .</p>
<blockquote><p>
# Less (code) is more<br />
# Simplicity is a feature
</p></blockquote>
<p># I dream of bbPress being more like feature-rich WordPress where more basic features are added to the Core and more plugins developed to flesh out those features even further.&#8221;</p>
<blockquote><p>
# Simplicity is a feature
</p></blockquote>
<p>See mate, you&#8217;re projecting your desires onto a product that in no way is going in the same dierction (and never has been). You want all these things that aren&#8217;t what BBpress is all about. Heck WordPress is actually a very bare product at the front end (for the user), so i&#8217;ve no idea why you think BBpress is going ot go the other way, especially when it says and has always said it wont (cunningly hidden on the About and Feature pages to avoid confusion).</p>
<p>&#8220;I really don’t get the hangup re: an OPTIONAL (you can turn it on or off) WYSIWYG editor. It won’t break in future bbPress updates because its in the Core and if you don’t like it, simply turn if off. Blam, everyone is happy.&#8221;</p>
<p>Mostly because you already have that feature via a plugin. You can download it and turn it on <img src='http://bbpress.org/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Ther&#8217;s loads of reasons for this:</p>
<p> Its JavaScript reliant, usually on the latest version of a library that is outwith BBpress&#8217;s control.<br />
 The WYSIWYG editors are quite intesive for older machines and browsers &#8211; remember most of the world still uses dial up and IE; and if you remove North America from the statistics the percentage of 5-6 year old versions of Windows and usage of IE6 sky rockets. Why would we all get behind a feature will just cause problems throughout the world.<br />
 These things display differntly in every browser, and require a bucketload of testing all on their own. TinyMCE for example, has a testing/development team thats twice the size of BBpress.<br />
 We only have a limited amount of development time, why should something like a WYSIWYG edtor be developed by the BBpress team into the core when any idiot can add 3 lines of javascript code to their theme if they really want it? Why should the BBpress team take the responsability and time to bugfix that?<br />
 Why should users who came to this project based on the Philosophy in the About page have to turn off features that go against this philosophy simply because some people think they&#8217;re cool.<br />
 There&#8217;s already 2 working WYSIWYG plugins for BBpress. Neither of them are that popular based on downloads, less than 5 of the Top100 websites on CK&#8217;s list used them, so why should they be included in the core of plugins that are popular?<br />
 I build my custom WYSIWYG plugin in about 4 hours. Bug fixing took a few hours over the next weeks. If you really want it, you can use TinyMCE (3 lines of JS on your theme),  one of the 2 existing plugins, or build your own like i did.</p>
<p>BBpress is build on certain principles mate, with a very limited development time (currently at 0hours from July 15th-Dec15th). Browser dependant interactive options for the user that administrators have to turn off just is nott part of the remit matey &#8211; especially when you have plugins that can do it already (and they aren&#8217;t popular).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

