6:50 p.m.
Christian,
I've asked Pete a few questions about SeamText and he said I should ask you
about one...
Exploring SeamText 2.1.0.beta1 ANTLR grammar we've discovered that
form/input elements are legal to use, so it is valid to write:
<form action="http://somesite.com"><input type="file"
/><input type="submit"
/></form>
I suppose it is not safe that the user is possible to type in forms. What do
you think about it?
Best regards,
Nick Belaevski
7:50 p.m.
Please consider the following example:
<html xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:rich="http://richfaces.org/rich"
xmlns:s="http://jboss.com/products/seam/taglib">
<body>
<h:form id="Form">
<s:formattedText value="#{bean.seamText}"/>
<h:commandButton value="Submit!"/>
</h:form>
</body>
</html>
bean.seamText =>
public String getSeamText() {
return "<br></form><form
action=\"http://www.jboss.org\"></br>";
}
Pressing "Submit!" command button will submit form to jboss.org instead of
the application host, so one can potentially spy other users.
Tested with Seam 2.1.0.beta1.
Best regards,
Nick Belaevski
-----Original Message-----
From: Christian Bauer [mailto:cbauer@redhat.com]
Sent: Thursday, October 02, 2008 7:56 PM
To: Nick Belaevski
Cc: seam-dev(a)lists.jboss.org; Ilya Shaikovsky; Sergey Smirnov
Subject: Re: Form, Input Elements and SeamText
On Oct 02, 2008, at 18:50 , Nick Belaevski wrote:
> <form action="http://somesite.com"><input type="file"
/><input
> type="submit" /></form>
>
> I suppose it is not safe that the user is possible to type in forms.
Why not? Your browser can send whatever forms it wants to whatever site.
1:14 a.m.
On Oct 02, 2008, at 19:50 , Nick Belaevski wrote:
Pressing "Submit!" command button will submit form to
jboss.org
instead of
the application host, so one can potentially spy other users.
http://fisheye.jboss.com/changelog/Seam?cs=9179
2:33 p.m.
Hi Christian,
One more case question. If you've looked through initial Editor RS doc -
you could see that we defined seamText converter creation instead of
client-side plugin development. So nothing changed on client side (tiny
generates just the same html and it's converted on server side) And
we've found next general problem:
html allows us to use next code
/<h1>header 1<h1>
<h2>header 2<h2>/
but next code
/+header 1
++header 2 /
not valid for seam text (there should be some text after each header to
make it valid). I'm sure we could find more such usage restrictions.
User will not understand why his text looks fine and valid in wysiwyg
editor but throws validation message after submit.
According to this we could:
1) Refuse converters usage and write client side plugin as for BBCode
exist. But this work estimated as much more difficult and has another
problems and questions on client side. And more important - the problem
remains and we'll also have to write some stubs for such cases. But in
this case script will handle such cases and not allow to submit
incorrect text.
2) Use converter as designed and use your jira in order to get such
cases fixed. But this causes editor to be fully compatible only with
latest seam version.
3) Use converter as designed but workaround such cases (for the
particular case insert empty spans after headers). We also not sure if
this looks a good way..
How about your opinion on this?
Regards!
Christian Bauer ?????:
On Oct 02, 2008, at 19:50 , Nick Belaevski wrote:
> Pressing "Submit!" command button will submit form to jboss.org
> instead of
> the application host, so one can potentially spy other users.
http://fisheye.jboss.com/changelog/Seam?cs=9179
2:37 p.m.
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.
2:46 p.m.
New subject: Seam, JBoss5 and resources location
Useful to know:
- https://jira.jboss.org/jira/browse/JBAS-6029
-Ales
8:34 p.m.
New subject: Seam, JBoss5 and resources location
I noticed that components.properties was ending up in the root of the
WAR when I was working on some other things last week and thought it
was likely an error, but didn't give it much notice. Did this get
filed as a Seam bug? Not too difficult of a fix.
-Dan
On Fri, Oct 3, 2008 at 8:46 AM, Ales Justin <ales.justin(a)gmail.com> wrote:
Useful to know:
- https://jira.jboss.org/jira/browse/JBAS-6029
-Ales
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Dan Allen
Software consultant | 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.
9:08 p.m.
New subject: Seam, JBoss5 and resources location
Did this get filed as a Seam bug? Not too difficult of a fix.
Yes.
Pete filed a couple of JIRAs:
-
http://www.seamframework.org/Community/SEAM210CR1AndJbossAS50CR2#comment4...
10:28 p.m.
New subject: Seam, JBoss5 and resources location
I want to check why the servlet context isn't finding it though - but
I agree the correct solution is to put it into WEB-INF/classes
On 3 Oct 2008, at 20:08, Ales Justin wrote:
> Did this get filed as a Seam bug? Not too difficult of a fix.
Yes.
Pete filed a couple of JIRAs:
- http://www.seamframework.org/Community/SEAM210CR1AndJbossAS50CR2#comment4...
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
12:17 a.m.
New subject: Seam, JBoss5 and resources location
Pete, I'll fix the seam-gen bug.
Btw, are we out of code freeze? Sorry if I missed the announcement.
-Dan
On Fri, Oct 3, 2008 at 4:28 PM, Pete Muir <pmuir(a)redhat.com> wrote:
I want to check why the servlet context isn't finding it though -
but I
agree the correct solution is to put it into WEB-INF/classes
On 3 Oct 2008, at 20:08, Ales Justin wrote:
>> Did this get filed as a Seam bug? Not too difficult of a fix.
>
> Yes.
>
> Pete filed a couple of JIRAs:
> -
> http://www.seamframework.org/Community/SEAM210CR1AndJbossAS50CR2#comment4...
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
--
Dan Allen
Software consultant | 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.
12:17 p.m.
New subject: Seam, JBoss5 and resources location
Yes, we are out of the code freeze. Sorry, I think it was mentioned in
passing rather than definitively ;-)
On 3 Oct 2008, at 23:17, Dan Allen wrote:
Pete, I'll fix the seam-gen bug.
Btw, are we out of code freeze? Sorry if I missed the announcement.
-Dan
On Fri, Oct 3, 2008 at 4:28 PM, Pete Muir <pmuir(a)redhat.com> wrote:
> I want to check why the servlet context isn't finding it though -
> but I
> agree the correct solution is to put it into WEB-INF/classes
>
> On 3 Oct 2008, at 20:08, Ales Justin wrote:
>
>>> Did this get filed as a Seam bug? Not too difficult of a fix.
>>
>> Yes.
>>
>> Pete filed a couple of JIRAs:
>> -
>> http://www.seamframework.org/Community/SEAM210CR1AndJbossAS50CR2#comment4...
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
--
Dan Allen
Software consultant | 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.
3:07 p.m.
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> 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
6:33 p.m.
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> 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> 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.
1:44 a.m.
I think the Seam Text really has two somewhat orthogonal features:
- Seam text markup in a proprietary language that might make sense for
some one-off feature requests, when you really need it.
- A validated and sanitized subset of HTML; you can use the Seam Text
parser and feed it HTML input, and it will tell you if it's XSS safe
or not. If you have some rich client text editor that produces HTMl,
that is useful.
I'm not sure we should do anything more/less than that inside Seam.
On Fri, Feb 27, 2009 at 6:33 PM, Dan Allen <dan.j.allen(a)gmail.com> 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> 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> 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.
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
12:52 p.m.
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
On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen <dan.j.allen(a)gmail.com> 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> 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>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
1:54 p.m.
On Mon, Mar 2, 2009 at 6:52 AM, Jay Balunas <tech4j(a)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.
8:09 p.m.
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&a...;.
It looked like a straight carry over of the tag description from the base.
Is there an example of this? We need to make this more obvious and perhaps
provide some examples of how to use it.
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?
On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen <dan.j.allen(a)gmail.com> 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> 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>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
8:12 p.m.
I updated the jira with this, also we should move this to the Design of
RichFaces forums if there is more discussion needed.
On Mon, Mar 2, 2009 at 2:09 PM, Jay Balunas <tech4j(a)gmail.com> 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&a...;.
It looked like a straight carry over of the tag description from the base.
Is there an example of this? We need to make this more obvious and perhaps
provide some examples of how to use it.
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?
>
>
> On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen <dan.j.allen(a)gmail.com>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> 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>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
--
blog: http://in.relation.to/Bloggers/Jay
9:32 p.m.
On Mon, Mar 2, 2009 at 3:08 PM, Nick Belaevski <nbelaevski(a)exadel.com>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&a...;.
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?
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.
>
>
> On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen <dan.j.allen(a)gmail.com>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> 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>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
9:31 p.m.
On Mar 2, 2009, at 5:52 PM, Nick Belaevski wrote:
Jay Balunas wrote:
>
>
>
> On Mon, Mar 2, 2009 at 3:08 PM, Nick Belaevski
> <nbelaevski(a)exadel.com> 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?
Lets move this to RF design forums.
>
>
>>
>>
>>>
>>> On Fri, Feb 27, 2009 at 12:33 PM, Dan Allen
>>> <dan.j.allen(a)gmail.com> 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>
>>> 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> 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
5534
days inactive
5686
days old
23 comments
8 participants
participants (8)
-
Ales Justin -
Christian Bauer -
Christian Bauer -
Dan Allen -
Ilya Shaikovsky -
Jay Balunas -
Nick Belaevski -
Pete Muir