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".<div>
<br></div><div>Created: <a href="https://jira.jboss.org/jira/browse/RF-6452">https://jira.jboss.org/jira/browse/RF-6452</a> </div><div><br></div><div>-Jay</div><div><div><br></div><div><br><div class="gmail_quote">On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I'm digging up an old thread here...<br><br>Would it be possible for the tinyMCE component to output a more standard wiki syntax as well, such as textile (<a href="http://www.textism.com/tools/textile/" target="_blank">http://www.textism.com/tools/textile/</a>)? As complete as it may be, the Seam formatted text is yet another wiki syntax and the world has so many already. For people using Seam in an existing system/environment, it may be necessary to adapt. We can't support every syntax, but we can pick the most prevalent.<br>
<br>Also, when I imagine how this component would work, I figured that all the conversation is handled by the JSF life cycle.<br><br>When the editor is loaded wiki text is converted to html and displayed in the TinyMCE editor<br>
When the form is saved, the html is converted to wiki text and copied back to the model<br><br>You do stand to lose some control with this approach if the wiki syntax has special hooks. But then again, if someone wants that contorl, I suppose they can just edit the wiki text directly.<br>
<br>-Dan<div><div></div><div class="Wj3C7c"><br><br><div class="gmail_quote">On Fri, Oct 3, 2008 at 8:07 AM, Jay Balunas <span dir="ltr"><<a href="mailto:tech4j@gmail.com" target="_blank">tech4j@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div dir="ltr">Hi Christian,<br><br>They are developing a richfaces component that implements tinyMCE (<a href="http://tinymce.moxiecode.com/" target="_blank">http://tinymce.moxiecode.com/</a>) as a JSF component.<br><br>
The goal is that it also supports seam text conversion on the server side (afaict) which is why they are bringing up questions on proper conversion.<br>
<br>Two places where I have run into the issue below is when creating an outline/draft document that I am not ready to post, but want to save, the other is when I have a section that I do not need introduction text for and would instead like to begin the first sub-section immediately.<br>
<br>
+header 1<br>
++header 2<br><br>Is this a change to seam text grammar that would be acceptable?<br><br>-Jay<div><div></div><div><br><br><br><div class="gmail_quote">On Fri, Oct 3, 2008 at 8:37 AM, Christian Bauer <span dir="ltr"><<a href="mailto:cbauer@redhat.com" target="_blank">cbauer@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex"><div><br>
On Oct 03, 2008, at 14:33 , Ilya Shaikovsky wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
html allows us to use next code<br>
<br>
<h1>header 1<h1><br>
<h2>header 2<h2><br>
<br>
but next code<br>
<br>
+header 1<br>
++header 2<br>
</blockquote>
<br></div>
It wasn't done on purpose but I'm quite happy with requiring text between headlines. That's how real texts are written, it's good style.<div><br>
<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
How about your opinion on this?<br>
</blockquote>
<br></div>
I have no idea what you guys are doing but if you want to submit reasonable changes to the seam-text.grammar, go ahead._______________________________________________<div><div></div><div><br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br>
</div>
<br>_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br></div></div>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>from my email. If you contact me, but don't hear back for more than a week,<br>
it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>you feel that it did not reach my attention.<br>
</blockquote></div><br><br clear="all"><br>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay">http://in.relation.to/Bloggers/Jay</a><br>
</div></div>