Yeah we can definitely. I think some sort of charter will need to be drafted to figure things out when tapestry moves to a TLP and some sort of component / contrib sub project is created.

As for tacos and dojo, I'd prefer if we developed js toolkit components that they used dojo widget equivalents (when they exist and are up to snuff), but am not completely against the idea. (As witnessed by the new DatePicker addition).

As for the rico stuff specifically, I think that dojo already has an accordion widget. I think I also remember hearing that the rico creator / lead developer is now working at yahoo which has made the project more or less dead. Has it had a resurgence of new life that I don't know about?

On 4/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
No, i prefer it in tacos. I just wanted to make sure that dhtml-only or
non-dojo components are ok here.
Also, I've recently played with openrico a bit and added their
accordion to tapfx. In my mind, this couldn't / shouldn't coexist with tacos
dojo. But i may be wrong. How do you guys feel about this? Can we determine
a set of 'rules' or descriptions of what should go in and what shouldn't?


From Jesse Kuhnert < [EMAIL PROTECTED]>:

> Yes I think we'd love to see it in tacos :) Of course if you ~want~ to put
> it in tapfx that's ok too but then we'd be sad. :(
>
> On 4/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > First, a note for those having problems with beta2 on IE.
> > Due to a recent dojo change, you may have to disable
> > tapestry's rendering of the BASE tag (if you're using @Shell)
> >
> > Secondly, a question for the devs. I'm writting  a googlemaps
> > component and it's turning out real nice! i was about to commit
> > it in my own tapfx (out of habit), but just then i thought of tacos.
> > So, what kind of components should generally be accepted by tacos?
> > For the time being, i don't have any plans of making it use the ajax
> > direct
> > service or dojo, so it just uses its own .js
> > Its name is GMap and I believe the correct package for it is
> > net.sf.tacos.components.maps
> > So, does it fit with tacos?
> >
> >
> > --
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> > language
> > that extends applications into web and mobile media. Attend the live
> > webcast
> > and join the prime developer group breaking into this new coding
> > territory!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> > _______________________________________________
> > Tacos-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/tacos-devel
> >
>
>
>
> --
> Jesse Kuhnert
> Tacos/Tapestry, team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind.  http://opennotion.com
>


--




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel



--
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around dojo/tapestry/tacos/hivemind.  http://opennotion.com

Reply via email to