No that's my fault. I banished it from core because I was worried it would behave unexpectedly (a worry seen to be true by the jira issues created from it existing in Tacos alone) and cause too many overall headaches...
If I can help it it will never see the light of day in core. :) On 3/2/07, Diego <[EMAIL PROTECTED]> wrote:
Thanks Andy, That looks good, I will update to Tacos 4.1.1. I have seen that some tapestry dojo components moved to tapestry and back. But wouldn't DojoWidget or Widget belong in Tapestry core, because its a really generic component? Regards Diego On 3/1/07, andyhot <[EMAIL PROTECTED]> wrote: > > http://tacos.sourceforge.net/tacos4.1/tacos-core/tapdoc/index.html > > http://tacos.sourceforge.net/tacos4.1/tacos-core/quick-start/downloading.html > > Take a look at the dojo:Widget component > > > Diego wrote: > > Is there a alternative way of using dojo Widgets in tapestry 4.1.1. > > > > If I don't set parseWidgets = "true", then the widgets aren't parsed. > > But the text of the Shell says: "..... It is highly reccomended that you > > keep this at its default value of false." > > > > > > Regards, > > Diego > > > > > -- > Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr > Tapestry / Tacos developer > Open Source / J2EE Consulting > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
