You're welcome to attach any code in the related issue http://tacoscomponents.jot.com/BugReporter/Bug110
We have 2 ways to implement this: - Add a new component, let's say RichTextArea which will be like yours + translators and validators :) - Add this behaviour to Editor and add conditional logic so that it can work in both ways (as a normal form component and as an in-place-text+html-no-form-needed editor) Option 1 is the easiest but i'd like to see option 2 make it in beta-3 >From Pedro Viegas <[EMAIL PROTECTED]>: > Hi Andy, > > Been away these days. > Got back on the horse today. > Built a simple component just like Tapestry's TextField (without translators > and validators) but witch renders a dojo Editor in a textarea so that it > ties it like a normal submit to the tapestry form. > > Worked like a charm. > Guess like you said dojo has really changed! :-D > Tested it on firefox and no problems whatsoever! ;-) > > Note: I didin't put in nothing of AJAX listeners and updatecomponet alike > properties so it's really simple. I guess it has no use for tacos but if > someone is interested I could put the code in here. > > Regards, > > On 4/21/06, Pedro Viegas <[EMAIL PROTECTED]> wrote: > > > > I'm preciselly using a Textarea and using mainlly firefox! :-( > > Created the report like you asked. > > > > http://tacoscomponents.jot.com/BugReporter/Bug110 > > > > I'll try using a DIV and testing Explorer to see what happens. > > > > > > On 4/21/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > > > > > I remember i had lots of issues when i originally created Editor. > > > Firefox would usually crash if the Editor was replacing a TextArea. > > > > > > So i decided to just make it work as it now is. > > > > > > Of course that's 6 months ago and of course dojo has changed, > > > so i'll give it a look again - just add a bug report :) > > > > > > > > > From Pedro Viegas <[EMAIL PROTECTED]>: > > > > > > > Hi list, > > > > > > > > Been trying to get a Tacos:Editor working like any other input like > > > > component. > > > > It has a value parameter, but also a listener. Since the listener is > > > not > > > > mandatory I though I could use it like say a TextField, just setting > > > the > > > > value with some ognl expression. > > > > Doing so it renders the original ognl expression with the value in the > > > > > > > Editor, nice!, but the submit of the surrounding form doesn't send the > > > value > > > > back to the java page. Always get a null value in the value associated > > > > method. > > > > > > > > Anybody used the Editor like this, just like a TextField? Is it > > > prepared to > > > > work like this? > > > > I'm doing an encapsulation in my own component where I add a Hidden > > > > component with the value so I get a submission back to the page (still > > > > working in the passage of the value from the editor to the Hidden > > > > component), but wouldn't it be expected that the Editor supported this > > > > functionality? Am I doing something wrong? > > > > The example in the Tacos demo uses a listener e nothing like a form > > > like > > > > usage. Anybody has an example more suitable? > > > > > > > > Thanks, > > > > > > > > -- > > > > Pedro Viegas > > > > > > > > > > > > > -- > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Pedro Viegas > > > > > > -- > Pedro Viegas > -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
