> I thought the general consensus was to ditch the Dojo wrapping? Well, i guess so. But we are still keeping the dojo theme, just that it might not be the default ajax theme. Am i right to say this? After looking into the code a bit, I suppose we could remove the rich text editor, cause text area component in ajax theme will work like a dojo rich text editor, so i guess its a duplicate. rgds ----- Original Message ---- From: Don Brown <[EMAIL PROTECTED]> To: Struts Developers List <dev@struts.apache.org> Sent: Friday, 14 July, 2006 2:11:58 AM Subject: Re: [s2] Dojo widgets?
I can kind of understand with the calendar tag, since I had to write a custom Dojo component, but the editor is a simple wrapper around the Dojo component. There isn't any additional value in the UI tag, only more code to maintain for us. I thought the general consensus was to ditch the Dojo wrapping? Don tm jee wrote: > I'd prefer to keep them both. > > > ----- Original Message ---- > From: Don Brown <[EMAIL PROTECTED]> > To: Struts Developers List <dev@struts.apache.org> > Sent: Friday, 14 July, 2006 1:26:08 AM > Subject: Re: [s2] Dojo widgets? > > Perhaps I'm reading your reply wrong, but my proposal was to get rid of the > Struts calendar and editor tags, since they weren't providing much value. > Instead, we'd point users to this new OpenSymphony project if they wanted a > fully-featured calendar or editor tag. > > Do you want to move the calendar and editor UI tags to Opensympyhony, keep > the > Dojo ones here, or both? > > Don > > tm jee wrote: >> I like Don's proposal, and would prefer to keep to dojo's calendar, rich >> text editor etc. >> >> rgds >> >> ----- Original Message ---- >> From: Don Brown <[EMAIL PROTECTED]> >> To: Struts Developers List <dev@struts.apache.org> >> Sent: Thursday, 13 July, 2006 12:23:34 PM >> Subject: Re: [s2] Dojo widgets? >> >> To kind of answer my own question, I have a proposal: put the original >> date picker and rich text editor UI tags in a new OpenSymphony project >> titled something like "Struts Optional Components" or perhaps >> something more original. Anyways, the point would be to create an >> outside ASF project that: >> >> 1. Provides a home for excellent components that depend on LGPL >> Javascript libraries, a no-no for ASF >> 2. Shows how easy it is to create your own components and perhaps >> fosters a community, much like MyFaces Tomahawk >> >> Even if we keep Dojo, I think we'd be doing our Webwork users a >> disservice to try to get them to use these components instead. There >> are just a lot of features the WW ones have that the Dojo ones don't. >> Of course it doesn't hurt that the move would close a few of our >> tickets and get us that much closer to a stable release :) >> >> Don >> >> >> >> On 7/12/06, Don Brown <[EMAIL PROTECTED]> wrote: >>> We have two UI tags, datePicker and richTextEditor, which used to be >>> backed by Javascript libraries, but are now simple wrappers for their >>> respective Dojo widgets. In the case of the date picker, I had to >>> extend the Dojo widget to have the correct popup behavior we had before. >>> >>> My question is should I bother aligning the documentation, Javadocs, and >>> component classes to the new widgets and their attributes, or are we >>> dropping any components that simply wrap Dojo widgets? >>> >>> I'd like to get this issue resolved so we can move on to the public beta >>> phase. Thanks, >>> >>> Don >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
