<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Page comments</title>
		<link>http://www.silverstripe.org/home/</link>
		<atom:link href="http://www.silverstripe.org/home/" rel="self" type="application/rss+xml" />
		<description></description>

		
		<item>
			<title></title>
			<link>http://www.silverstripe.org/why-tinymce/#PageComment_8587</link>
			<description>I agree with Dave&#39;s comment below.<br />I have about 15 years experience and like Tiny MCE, yet a few bugs annoy me... Such as the way it messes up Google analytics code.<br /><br />It&#39;s a great CMS for small projects but is a little lacking for larger scale projects!</description>
			<pubDate>Thu, 22 Sep 2011 01:17:30 +1200</pubDate>
			<dc:creator>Abe</dc:creator>
			<guid>http://www.silverstripe.org/why-tinymce/#PageComment_8587</guid>
		</item>
		
		<item>
			<title></title>
			<link>http://www.silverstripe.org/why-tinymce/#PageComment_8428</link>
			<description>Some reasons (amongst many) for why TinyMCE annoys me very much:<br /><br />- no support for google analytics code<br />- terrible iframe support<br />- no ability to embed videos through javascript<br />- no direct way to change the colour of text<br /><br />I&#39;m not a developer. I don&#39;t know how to write code and adapt how to accomplish the things above. However should I really have to? Should I have to hassle a developer just to be able to do the simple things above?</description>
			<pubDate>Wed, 17 Aug 2011 23:04:44 +1200</pubDate>
			<dc:creator>Dave</dc:creator>
			<guid>http://www.silverstripe.org/why-tinymce/#PageComment_8428</guid>
		</item>
		
		<item>
			<title></title>
			<link>http://www.silverstripe.org/why-tinymce/#PageComment_7173</link>
			<description>Hello!<br /><br />I stumble upon it and now I saw it&#39;s recommended for Drupal (http://drupalmodules.com/module/whizzywig-a-complete-wysiwyg-editor), so you test how would [http=http://unverse.net/Whizzywig-web-based-rich-text-editor]Whizzywig[/url] suite Silverstrip3.<br /><br /></description>
			<pubDate>Sun, 27 Mar 2011 19:39:19 +1300</pubDate>
			<dc:creator>Gour</dc:creator>
			<guid>http://www.silverstripe.org/why-tinymce/#PageComment_7173</guid>
		</item>
		
		<item>
			<title></title>
			<link>http://www.silverstripe.org/why-tinymce/#PageComment_7154</link>
			<description>Hello!<br /><br />At the moment I&#39;m stil Concrete5 user, but my &#39;official&#39; SilverStripe book is on the way. :-)<br /><br />More and more I read about Silverstripe features, I&#39;m delighted how it is so nice piece of software.<br /><br />You wrote: &amp;quot;Another feature that we are hoping to add to SilverStripe CMS 3.0 is the ability to support different editing styles, such as Markdown...&amp;quot; and I consider it is very high on my top of priorities which will make SilverStripe even better platform.<br /><br />Sure, TinyMCE is cute, but having ability to write content in more appropriate markup (like extended Markdown) which can be kept under VCS is great (I&#39;m coming from Haskell and familiar with Pandoc and its extensions).<br /><br />Since I&#39;m just starting with SilverStripe I do no want to bother joining dev-list (not having much to offer atm), but, please, don&#39;t forget support for Markdown for 3.0!!<br /></description>
			<pubDate>Sat, 26 Mar 2011 22:40:59 +1300</pubDate>
			<dc:creator>Gour</dc:creator>
			<guid>http://www.silverstripe.org/why-tinymce/#PageComment_7154</guid>
		</item>
		
		<item>
			<title></title>
			<link>http://www.silverstripe.org/why-tinymce/#PageComment_7024</link>
			<description>Hiya,<br /><br />reading about SS as potential replacement for Concrete5 and (better) alternative than MODX...I&#39;m glad to see about &amp;quot;the ability to support different editing styles, such as Markdown&amp;quot;.<br /><br /></description>
			<pubDate>Fri, 18 Mar 2011 10:30:25 +1300</pubDate>
			<dc:creator>Gour</dc:creator>
			<guid>http://www.silverstripe.org/why-tinymce/#PageComment_7024</guid>
		</item>
		
		<item>
			<title></title>
			<link>http://www.silverstripe.org/why-tinymce/#PageComment_6490</link>
			<description>Well said Sam - couldn&#39;t agree more! TinyMCE also makes it easy to control elements, attributes, etc  in the HTML (through valid_elements for example, which Silver Stripe CMS has given some control to through _config).<br />On a side note - in certain cases, I&#39;ve seen people look at all the buttons offered with TinyMCE and mistake that area for Microsoft Word (or another notepad editor). In a broad perspective, they are not completely wrong in their thinking; however, the reality is they are two completely distant technologies and serve different applications. People simply expect a lot from anything that they already know can be accomplished (even if the tool in front of them isn&#39;t connected in any way to that other tool they are thinking of). For us, it&#39;s simply a matter of communicating what to expect from the editor up front, and how to use it properly. <br />Further still, in most situations, we&#39;re finding the best solutions are those that don&#39;t use the WYSIWYG at all. For example; let&#39;s assume a client needs a page to manage hockey teams - instead of simply providing the WYSIWIG and training someone on how to use the various WYSIWYG buttons (like creating a table, adding a row for the new hockey team, inserting a picture in one of the cells, etc) we&#39;re finding the better solution (for the CMS user) is to make a Hockey-Team-specific-page that breaks those tasks into specific fields (i.e. &#39;Add new hockey team&#39; button via DataObjectManager, with a field for the team name, an image field for the picture, etc). The unfortunate reality here, is that building custom solutions like this takes time, and not all projects can budget these tailored solutions.<br /></description>
			<pubDate>Thu, 17 Feb 2011 09:38:00 +1300</pubDate>
			<dc:creator>Rob M</dc:creator>
			<guid>http://www.silverstripe.org/why-tinymce/#PageComment_6490</guid>
		</item>
		

	</channel>
</rss>