Comments on: Why combining RichTextEditor and StyleSheets is a pain http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain Ruben writes flashy writings Fri, 25 Jul 2008 06:46:04 +0000 http://wordpress.org/?v=2.5.1 By: CustomRichTextEditor with XHTML text | Axelology http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-22548 CustomRichTextEditor with XHTML text | Axelology Mon, 24 Mar 2008 15:03:06 +0000 http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-22548 [...] Ruben’s post [...] [...] Ruben’s post [...]

]]> By: Ruben http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-20397 Ruben Sun, 02 Mar 2008 16:41:37 +0000 http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-20397 Hmm, that's sad. As an alternative, couldn't you re-apply the stylesheet every time the text in the input-field changes? Hmm, that’s sad. As an alternative, couldn’t you re-apply the stylesheet every time the text in the input-field changes?

]]> By: peter http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-19739 peter Tue, 26 Feb 2008 09:11:58 +0000 http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-19739 More pain! Found this note in the support, stylesheets and editable text components don't go together: Note: A text field with a style sheet is not editable. In other words, a text field with the type property set to TextFieldType.INPUT applies the StyleSheet to the default text for the text field, but the content will no longer be editable by the user. Consider using the TextFormat class to assign styles to input text fields. (http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/text/StyleSheet.html) After some projects i've worked on, I must say flex/flash lack of HTML support is so poor, it leaves flex almost unusable for most of our projects. peter More pain!

Found this note in the support, stylesheets and editable text components don’t go together:

Note: A text field with a style sheet is not editable. In other words, a text field with the type property set to TextFieldType.INPUT applies the StyleSheet to the default text for the text field, but the content will no longer be editable by the user. Consider using the TextFormat class to assign styles to input text fields.
(http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/text/StyleSheet.html)

After some projects i’ve worked on, I must say flex/flash lack of HTML support is so poor, it leaves flex almost unusable for most of our projects.

peter

]]> By: Ruben http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-5948 Ruben Fri, 28 Sep 2007 08:16:41 +0000 http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-5948 Spot on nicemandan, let me know if you ever come up with something :) Spot on nicemandan, let me know if you ever come up with something :)

]]> By: nicemandan http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-5829 nicemandan Wed, 26 Sep 2007 20:28:49 +0000 http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-5829 Yep... I ended up here for the same reason! I want to add paragraph styles and change the colour of the URL. I guess the reason TextFormat is used is because you can easily define a start/end index where formatting can be applied. I *think* the content of htmlText is worked out (somewhere!?) after you request it. This means you cannot provide a WYSIWYG editor that matches and shares the same CSS styles between back-end administration and user-facing front end. Which basically renders this component useless for my purposes. Yep… I ended up here for the same reason! I want to add paragraph styles and change the colour of the URL.

I guess the reason TextFormat is used is because you can easily define a start/end index where formatting can be applied. I *think* the content of htmlText is worked out (somewhere!?) after you request it.

This means you cannot provide a WYSIWYG editor that matches and shares the same CSS styles between back-end administration and user-facing front end. Which basically renders this component useless for my purposes.

]]> By: Ruben http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-102 Ruben Tue, 17 Apr 2007 04:48:17 +0000 http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-102 No problem man, when/if I find the time to create a solution for this issue I'll let you know through this blog.. No problem man, when/if I find the time to create a solution for this issue I’ll let you know through this blog..

]]> By: Aaron Fay http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-101 Aaron Fay Tue, 17 Apr 2007 03:59:48 +0000 http://www.rubenswieringa.com/blog/why-combining-richtexteditor-and-stylesheets-is-a-pain#comment-101 Indeed it is a pain, thanks for the heads up. Aaron Indeed it is a pain, thanks for the heads up.

Aaron

]]>