Re: [seam-dev] Re: Form, Input Elements and SeamText

Jay Balunas wrote: > > > > On Mon, Mar 2, 2009 at 3:08 PM, Nick Belaevski > <nbelaevski(a)exadel.com&gt; wrote: > > > Jay Balunas wrote: >> >> >> >> On Mon, Mar 2, 2009 at 1:47 PM, Nick Belaevski <nbelaevski(a)exadel.com >> > wrote: >> Jay Balunas 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". >>> >>> Created: https://jira.jboss.org/jira/browse/RF-6452 >>> >>> -Jay >>> >> It's possible 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. >> >> Are you referring to the converter attribute here: "http://livedemo.exadel.com/richfaces-demo/richfaces/editor.jsf?c=editor&tab=info >> ". It looked like a straight carry over of the tag description >> from the base. >> > Yes, converter can be set either by using this attribute or nested > tag. > >> Is there an example of this? We need to make this more obvious >> and perhaps provide some examples of how to use it. > There's no example in livedemo, we can add one for Textile or BB > Text in the future. > Great - can you update the jira to represent this? > Done. >> >> 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? > 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 . > 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. 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?

> > >> >> >>> >>> On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen >>> <dan.j.allen(a)gmail.com&gt; wrote: >>> I'm digging up an old thread here... >>> >>> Would it be possible for the tinyMCE component to output a more >>> standard wiki syntax as well, such as textile (http://www.textism.com/tools/textile/)? >>> 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. >>> >>> Also, when I imagine how this component would work, I figured >>> that all the conversation is handled by the JSF life cycle. >>> >>> When the editor is loaded wiki text is converted to html and >>> displayed in the TinyMCE editor >>> When the form is saved, the html is converted to wiki text and >>> copied back to the model >>> >>> 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. >>> >>> -Dan >>> >>> >>> On Fri, Oct 3, 2008 at 8:07 AM, Jay Balunas <tech4j(a)gmail.com&gt; >>> wrote: >>> Hi Christian, >>> >>> They are developing a richfaces component that implements tinyMCE >>> (http://tinymce.moxiecode.com/) as a JSF component. >>> >>> 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. >>> >>> 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. >>> >>> +header 1 >>> ++header 2 >>> >>> Is this a change to seam text grammar that would be acceptable? >>> >>> -Jay >>> >>> >>> >>> On Fri, Oct 3, 2008 at 8:37 AM, Christian Bauer >>> <cbauer(a)redhat.com&gt; wrote: >>> >>> On Oct 03, 2008, at 14:33 , Ilya Shaikovsky wrote: >>> >>> html allows us to use next code >>> >>> <h1>header 1<h1> >>> <h2>header 2<h2> >>> >>> but next code >>> >>> +header 1 >>> ++header 2 >>> >>> 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. >>> >>> >>> How about your opinion on this? >>> >>> I have no idea what you guys are doing but if you want to submit >>> reasonable changes to the seam-text.grammar, go >>> ahead._______________________________________________ >>> >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >>> >>> >>> -- >>> blog: http://in.relation.to/Bloggers/Jay >>> >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >>> >>> >>> >>> -- >>> 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. >>> >>> >>> >>> -- >>> blog: http://in.relation.to/Bloggers/Jay >> >> -- >> Best regards, >> Nick Belaevski >> >> >> >> -- >> blog: http://in.relation.to/Bloggers/Jay > > -- > Best regards, > Nick Belaevski > > > > -- > blog: http://in.relation.to/Bloggers/Jay -- Best regards, Nick Belaevski