<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 2, 2009, at 5:52 PM, Nick Belaevski wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div bgcolor="#ffffff" text="#000000"> <br> <br> Jay Balunas wrote: <blockquote cite="mid:d7a75abd0903021232m4dcc4aa1o2e86f78a7aa0e3b1@mail.gmail.com" type="cite"><br> <br> <div class="gmail_quote">On Mon, Mar 2, 2009 at 3:08 PM, Nick Belaevski <span dir="ltr"><<a moz-do-not-send="true" href="mailto:nbelaevski@exadel.com">nbelaevski@exadel.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 bgcolor="#ffffff" text="#000000"> <div class="Ih2E3d"><br> <br> Jay Balunas wrote: <blockquote type="cite"><br> <br> <div class="gmail_quote">On Mon, Mar 2, 2009 at 1:47 PM, Nick Belaevski <span dir="ltr"><<a moz-do-not-send="true" href="mailto:nbelaevski@exadel.com" target="_blank">nbelaevski@exadel.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 bgcolor="#ffffff" text="#000000"> <div>Jay Balunas wrote: <blockquote type="cite">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 moz-do-not-send="true" href="https://jira.jboss.org/jira/browse/RF-6452" target="_blank">https://jira.jboss.org/jira/browse/RF-6452</a> </div> <div><br> </div> <div>-Jay</div> <div> <div><br> </div> </div> </blockquote> </div> <font face="Arial">It's </font><font face="Arial">possible </font><font face="Arial">to use any converter with rich:editor. If user sets useSeamText=true and doesn't provide his own converter, then rich:editor implicitly creates instance of default SeamText converter and uses it. So the user can provide his own implementation of converter for SeamText or for any other arbitrary markup language.</font></div> </blockquote> <div><br> </div> <div>Are you referring to the converter attribute here: "<a moz-do-not-send="true" href="http://livedemo.exadel.com/richfaces-demo/richfaces/editor.jsf?c=editor&tab=info" target="_blank">http://livedemo.exadel.com/richfaces-demo/richfaces/editor.jsf?c=editor&tab=info</a>". It looked like a straight carry over of the tag description from the base. </div> <div><br> </div> </div> </blockquote> </div> Yes, converter can be set either by using this attribute or nested tag. <div class="Ih2E3d"><br> <blockquote type="cite"> <div class="gmail_quote"> <div>Is there an example of this? We need to make this more obvious and perhaps provide some examples of how to use it.</div> </div> </blockquote> </div> There's no example in livedemo, we can add one for Textile or BB Text in the future. </div> </blockquote> <div>Great - can you update the jira to represent this? </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div bgcolor="#ffffff" text="#000000"><br> </div> </blockquote> </div> </blockquote> Done. <br> <blockquote cite="mid:d7a75abd0903021232m4dcc4aa1o2e86f78a7aa0e3b1@mail.gmail.com" type="cite"> <div class="gmail_quote"> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div bgcolor="#ffffff" text="#000000"> <div class="Ih2E3d"> <blockquote type="cite"> <div class="gmail_quote"> <div><br> </div> <div>Also- if this is the case then "useSeamText" is really "useConverter" in which case we not need it since we should be able to tell is it is set or not. Do you agree? <br> </div> </div> </blockquote> </div> Yes, non-null converter is used if it is present. But in my opinion useSeamText="true" is much more handy for the developer than explicit converter specification . </div> </blockquote> <div>I don't agree with this - especially since if we add Texttile we would need "useTexttile" and I think that is going away from JSF conventions. </div> </div> </blockquote> Yes, you are absolutely right. "useTextile" attribute does not look good at all. The only thing I like in "useSeamText" attribute, is its ability to switch between markup languages (this involves switching of converters and validators) easily. Do we need to support that, how do you think?</div></blockquote>Lets move this to RF design forums.<br><blockquote type="cite"><div bgcolor="#ffffff" text="#000000"><br> <blockquote cite="mid:d7a75abd0903021232m4dcc4aa1o2e86f78a7aa0e3b1@mail.gmail.com" type="cite"> <div class="gmail_quote"> <div> </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div bgcolor="#ffffff" text="#000000"><br> <div> <div class="Wj3C7c"> <blockquote type="cite"> <div class="gmail_quote"> <div> </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div bgcolor="#ffffff" text="#000000"><font face="Arial"><br> </font> <div> <div> <blockquote type="cite"> <div> <div><br> <div class="gmail_quote">On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen <span dir="ltr"><<a moz-do-not-send="true" href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@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;">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 moz-do-not-send="true" 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><br> <br> <div class="gmail_quote">On Fri, Oct 3, 2008 at 8:07 AM, Jay Balunas <span dir="ltr"><<a moz-do-not-send="true" 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 moz-do-not-send="true" 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><br> <br> <br> <div class="gmail_quote">On Fri, Oct 3, 2008 at 8:37 AM, Christian Bauer <span dir="ltr"><<a moz-do-not-send="true" 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><br> seam-dev mailing list<br> <a moz-do-not-send="true" href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br> <a moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br> <a moz-do-not-send="true" 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 moz-do-not-send="true" href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br> <a moz-do-not-send="true" 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 moz-do-not-send="true" href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br> </div> </div> </blockquote> <br> </div> </div> <pre cols="72"><font face="Arial">--
Best regards,
Nick Belaevski</font></pre> </div> </blockquote> </div> <br> <br clear="all"> <br> -- <br> blog: <a moz-do-not-send="true" href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br> </blockquote> <br> </div> </div> <pre cols="72">--
Best regards,
Nick Belaevski</pre> </div> </blockquote> </div> <br> <br clear="all"> <br> -- <br> blog: <a moz-do-not-send="true" href="http://in.relation.to/Bloggers/Jay">http://in.relation.to/Bloggers/Jay</a><br> </blockquote> <br> <pre class="moz-signature" cols="72">--
Best regards,
Nick Belaevski</pre> </div> </blockquote></div><br></body></html>