On Mon, Mar 2, 2009 at 6:52 AM, Jay Balunas <tech4j@gmail.com> wrote:
I believe that the editor component should be open to support any number of markup formats.  It should be the option of the user as to what is converted.  I like the idea of using jsf converters.  It could allow people to really generate their own conversion support. However this is not how it is currently designed.  atm it uses a simple flag for "useSeamText".

Yeah, the propriety attribute does seem a bit limiting. Considering the fact that the rich text editors are more than likely designed to work on HTML, they should definitely be used as a way to capture the markup the user wants, then the converters handle what is actually saved. Having a Seam Text converter is then advantageous because it can automatically handle concerns such as sanitizing the HTML, etc. Though it is more work on the component developer, it also gives the component developer a lot of power. Perhaps some sort of converter base class would be appropriate to help parse the HTML. Just thinking out loud.

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.