Re: [T4.1.5] with Dojo 1.1.1 Using Beyond Dojo
Thanks, Kalle. I'll look into Tacos. You're right about 0.4.3. It has worked extremely well for me too. But I've run into a serious problem with event.connect that is most likely a bug. I don't want to get into what I suspect will be extremely time-consuming debugging against such an old version of Dojo and couldn't reasonably expect much help from the Dojo community in doing so. I've always wanted separation of Tapestry/Dojo so this seemed a good time to consider the adapter. Best regards Richard Kalle Korhonen wrote: Tacos already does Dojo 1.0.2 integration almost out-of-the-box ( http://tacos.sourceforge.net/tacos4.1/tacos-dojo/index.html). If you need 1.1, you could probably just follow the Tacos source and do the same, or better yet, contribute dojo 1.1 integration back to Tacos. What features of Dojo 1.1 are you looking for? I have to say that while I've been using 1.0 in some projects, 0.4.3 has generally worked for me extremely well. Kalle On Mon, Jul 21, 2008 at 2:50 AM, Richard Hoberman [EMAIL PROTECTED] wrote: I'm considering upgrading to the latest Dojo library using the mechanism described at: http://tapestry.apache.org/tapestry4.1/ajax/beyonddojo.html Has anyone managed to use this? How time-consuming was it? Does anyone have an implementation they'd be willing to share? If not, how much interest is there in co-operating on creating one? Thanks Richard Hoberman FYI, this was discussed at: [1] http://www.nabble.com/T4.1.3---Upgrade-Dojo-td13621341.html#a14341740 [2] http://www.nabble.com/-T4.1--Alternate-JS-library-and-tapestry.event.buildEventProperties-td15470996.html#a15470996 -- View this message in context: http://n2.nabble.com/-T4.1.5--with-Dojo-1.1.1-Using-Beyond-Dojo-tp574931p574931.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://n2.nabble.com/-T4.1.5--with-Dojo-1.1.1-Using-Beyond-Dojo-tp574931p576230.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T4.1.5] with Dojo 1.1.1 Using Beyond Dojo
Hi - partly due to the recent interest and partly due to our own desire to eventually upgrade to a newer dojo version, i've resumed work on this as well since today... Interestingly, i've selected to work and finish tacos-jquery first, the idea being that fully integrating another library will 100% validate if all has been done correctly So, I'd like to share some thoughts on the missing features you've mentioned (as stated, this will relate to jquery) - Validation script processing: i consider those fairly trivial - so i expect to have them by later today - Widgets: that's a bit more problematic - dojo offers a lot of'em (moved into digit), jquery has a lot floating around and also jqueryUI. The main issue with our widgets is that current ones are too tightly bound to dojo0.4.3 to try to generify them... For the record, those are: DropdownDatePicker, DropdownTimePicker, Dialog, Autocompleter So, what i've already done is have a custom ComponentSpecificationResolver (already committed in tacos) that is able to 'rename' components (on template loading time), so you're able to configure this resolver like this: contribution configuration-id=tacos.services.ComponentSubstitutions rename component=DropdownDatePicker to=DatePicker/ rename component=DropdownTimePicker to=DatePicker/ rename component=GTimePicker to=DatePicker/ rename component=Autocompleter to=jquery:Autocompleter/ /contribution and all the different datepickers will really be replaced by the simple DatePicker (until a jquery specific component gets added) while the autocompleter is replaced by a jquery one Of course, the purpose here is to ease migration of existing applications + making it easy for devs to just try other libs. Anyway, so, if ppl want to help 'right here, right now' I guess the next step for dojo 1.1.1 would be to checkout https://tacos.svn.sourceforge.net/svnroot/tacos/tacos-4.1/trunk/tacos-dojo make the few changes to move it from dojo 1.0.2 to 1.1.1 and then port tapestry's DropdownDatePicker, DropdownTimePicker, Dialog, Autocompleter to that. And I'd be happy to review and commit patches for the above (sent to the tacos ML) or even discuss alternative approaches On Tue, Jul 22, 2008 at 1:21 PM, Martino Piccinato [EMAIL PROTECTED] wrote: The tacos implementation is missing validation, widgets and processing scripts returned in an ajax response. In my opinion there are two main reasons to upgade to 1.x dojo version: 1) 0.4.x is not supported/developed anymore, there's been a substantial API change in 1.x (that is supposed to be stable for quite a while) 2) 0.4.x is quite slow Minor reasons might be new widgets. Martino On Mon, Jul 21, 2008 at 10:12 PM, Kalle Korhonen [EMAIL PROTECTED] wrote: Tacos already does Dojo 1.0.2 integration almost out-of-the-box ( http://tacos.sourceforge.net/tacos4.1/tacos-dojo/index.html). If you need 1.1, you could probably just follow the Tacos source and do the same, or better yet, contribute dojo 1.1 integration back to Tacos. What features of Dojo 1.1 are you looking for? I have to say that while I've been using 1.0 in some projects, 0.4.3 has generally worked for me extremely well. Kalle On Mon, Jul 21, 2008 at 2:50 AM, Richard Hoberman [EMAIL PROTECTED] wrote: I'm considering upgrading to the latest Dojo library using the mechanism described at: http://tapestry.apache.org/tapestry4.1/ajax/beyonddojo.html Has anyone managed to use this? How time-consuming was it? Does anyone have an implementation they'd be willing to share? If not, how much interest is there in co-operating on creating one? Thanks Richard Hoberman FYI, this was discussed at: [1] http://www.nabble.com/T4.1.3---Upgrade-Dojo-td13621341.html#a14341740 [2] http://www.nabble.com/-T4.1--Alternate-JS-library-and-tapestry.event.buildEventProperties-td15470996.html#a15470996 -- View this message in context: http://n2.nabble.com/-T4.1.5--with-Dojo-1.1.1-Using-Beyond-Dojo-tp574931p574931.html Sent from the Tapestry Users mailing list archive at Nabble.com. - 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] -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[T4.1.5] with Dojo 1.1.1 Using Beyond Dojo
I'm considering upgrading to the latest Dojo library using the mechanism described at: http://tapestry.apache.org/tapestry4.1/ajax/beyonddojo.html Has anyone managed to use this? How time-consuming was it? Does anyone have an implementation they'd be willing to share? If not, how much interest is there in co-operating on creating one? Thanks Richard Hoberman FYI, this was discussed at: [1] http://www.nabble.com/T4.1.3---Upgrade-Dojo-td13621341.html#a14341740 [2] http://www.nabble.com/-T4.1--Alternate-JS-library-and-tapestry.event.buildEventProperties-td15470996.html#a15470996 -- View this message in context: http://n2.nabble.com/-T4.1.5--with-Dojo-1.1.1-Using-Beyond-Dojo-tp574931p574931.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T4.1.5] with Dojo 1.1.1 Using Beyond Dojo
Hi Richard, I'll be very interested in co-operating to have a dojo-1.x implementation. In my opinion at the moment being stuck with dojo 0.4.3 is the only big tapestry 4 pitfall. Martino On Mon, Jul 21, 2008 at 11:50 AM, Richard Hoberman [EMAIL PROTECTED] wrote: I'm considering upgrading to the latest Dojo library using the mechanism described at: http://tapestry.apache.org/tapestry4.1/ajax/beyonddojo.html Has anyone managed to use this? How time-consuming was it? Does anyone have an implementation they'd be willing to share? If not, how much interest is there in co-operating on creating one? Thanks Richard Hoberman FYI, this was discussed at: [1] http://www.nabble.com/T4.1.3---Upgrade-Dojo-td13621341.html#a14341740 [2] http://www.nabble.com/-T4.1--Alternate-JS-library-and-tapestry.event.buildEventProperties-td15470996.html#a15470996 -- View this message in context: http://n2.nabble.com/-T4.1.5--with-Dojo-1.1.1-Using-Beyond-Dojo-tp574931p574931.html Sent from the Tapestry Users mailing list archive at Nabble.com. - 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]
Re: [T4.1.5] with Dojo 1.1.1 Using Beyond Dojo
Tacos already does Dojo 1.0.2 integration almost out-of-the-box ( http://tacos.sourceforge.net/tacos4.1/tacos-dojo/index.html). If you need 1.1, you could probably just follow the Tacos source and do the same, or better yet, contribute dojo 1.1 integration back to Tacos. What features of Dojo 1.1 are you looking for? I have to say that while I've been using 1.0 in some projects, 0.4.3 has generally worked for me extremely well. Kalle On Mon, Jul 21, 2008 at 2:50 AM, Richard Hoberman [EMAIL PROTECTED] wrote: I'm considering upgrading to the latest Dojo library using the mechanism described at: http://tapestry.apache.org/tapestry4.1/ajax/beyonddojo.html Has anyone managed to use this? How time-consuming was it? Does anyone have an implementation they'd be willing to share? If not, how much interest is there in co-operating on creating one? Thanks Richard Hoberman FYI, this was discussed at: [1] http://www.nabble.com/T4.1.3---Upgrade-Dojo-td13621341.html#a14341740 [2] http://www.nabble.com/-T4.1--Alternate-JS-library-and-tapestry.event.buildEventProperties-td15470996.html#a15470996 -- View this message in context: http://n2.nabble.com/-T4.1.5--with-Dojo-1.1.1-Using-Beyond-Dojo-tp574931p574931.html Sent from the Tapestry Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
