Tapestry 5.1.0.5 vs Prototype 1.7 and Scriptaculous 1.9
Hi! Has anyone tried to use T5.1.0.5 with Prototype 1.7 and Scriptaculous 1.9? I'm having some weird JS errors: * Tapestry.Logging not defined. * Tapestry.Messages not defined. * undefinedTypeError: reply.zones is not an object. Are there known Tapestry.js issues with these versions of Prototype 1.7 and Scriptaculous 1.9? Any hints? -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry 5.1.0.5 vs Prototype 1.7 and Scriptaculous 1.9
I do. I'm using tapestry-js-fixes.js (i'm not sure where did i get it, so content inlined) == tapestry-js-fixes.js = Tapestry.ZoneManager.addMethods({ processReply : function(reply) { Tapestry.loadScriptsInReply(reply, function() { /* * In a multi-zone update, the reply.content may be missing, in * which case, leave the curent content in place. TAP5-1177 */ reply.content != undefined this.show(reply.content); /* * zones is an object of zone ids and zone content that will be * present in a multi-zone update response. */ reply.zones Object.keys(reply.zones).each(function(zoneId) { var manager = Tapestry.findZoneManagerForZone(zoneId); if (manager) { var zoneContent = reply.zones[zoneId]; manager.show(zoneContent); } }); }.bind(this)); } }); Tapestry.Palette.prototype.updateHidden = function() { // Every value in the selected list (whether enabled or not) is combined to // form the value. var values = $A(this.selected).map(function(o) { return o.value; }); this.hidden.value = Object.toJSON(values); }; = On Mon, Dec 19, 2011 at 7:58 PM, Thiago H. de Paula Figueiredo thiag...@gmail.com wrote: Hi! Has anyone tried to use T5.1.0.5 with Prototype 1.7 and Scriptaculous 1.9? I'm having some weird JS errors: * Tapestry.Logging not defined. * Tapestry.Messages not defined. * undefinedTypeError: reply.zones is not an object. Are there known Tapestry.js issues with these versions of Prototype 1.7 and Scriptaculous 1.9? Any hints? -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry 5.1.0.5 vs Prototype 1.7 and Scriptaculous 1.9
i include: tapestry-js-fixes.js in my Layout component, which is used in every my page. May be not best approach, but it works. And i also have following lines in my AppModule: //prototype 1.7 support public static void contributeFactoryDefaults(MappedConfigurationString, String configuration) { configuration.override(tapestry.scriptaculous.path, ru/partlink/tapx/prototype); } public static void contributeComponentClassResolver(final ConfigurationLibraryMapping configuration) { configuration.add(new LibraryMapping(tapx, ru.partlink.tapx.prototype)); } On Mon, Dec 19, 2011 at 8:07 PM, Dmitriy Vsekhvalnov dvsekhval...@gmail.com wrote: I do. I'm using tapestry-js-fixes.js (i'm not sure where did i get it, so content inlined) == tapestry-js-fixes.js = Tapestry.ZoneManager.addMethods({ processReply : function(reply) { Tapestry.loadScriptsInReply(reply, function() { /* * In a multi-zone update, the reply.content may be missing, in * which case, leave the curent content in place. TAP5-1177 */ reply.content != undefined this.show(reply.content); /* * zones is an object of zone ids and zone content that will be * present in a multi-zone update response. */ reply.zones Object.keys(reply.zones).each(function(zoneId) { var manager = Tapestry.findZoneManagerForZone(zoneId); if (manager) { var zoneContent = reply.zones[zoneId]; manager.show(zoneContent); } }); }.bind(this)); } }); Tapestry.Palette.prototype.updateHidden = function() { // Every value in the selected list (whether enabled or not) is combined to // form the value. var values = $A(this.selected).map(function(o) { return o.value; }); this.hidden.value = Object.toJSON(values); }; = On Mon, Dec 19, 2011 at 7:58 PM, Thiago H. de Paula Figueiredo thiag...@gmail.com wrote: Hi! Has anyone tried to use T5.1.0.5 with Prototype 1.7 and Scriptaculous 1.9? I'm having some weird JS errors: * Tapestry.Logging not defined. * Tapestry.Messages not defined. * undefinedTypeError: reply.zones is not an object. Are there known Tapestry.js issues with these versions of Prototype 1.7 and Scriptaculous 1.9? Any hints? -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry 5.1.0.5 vs Prototype 1.7 and Scriptaculous 1.9
Thank you, Dmitriy! Works like a charm! Now I'm chasing a non-related IE-specific JavaScript bug (sigh). Hugi, please pay the beers you owe me to Dmitriy! :D On Mon, 19 Dec 2011 15:07:10 -0200, Dmitriy Vsekhvalnov dvsekhval...@gmail.com wrote: I do. I'm using tapestry-js-fixes.js (i'm not sure where did i get it, so content inlined) == tapestry-js-fixes.js = Tapestry.ZoneManager.addMethods({ processReply : function(reply) { Tapestry.loadScriptsInReply(reply, function() { /* * In a multi-zone update, the reply.content may be missing, in * which case, leave the curent content in place. TAP5-1177 */ reply.content != undefined this.show(reply.content); /* * zones is an object of zone ids and zone content that will be * present in a multi-zone update response. */ reply.zones Object.keys(reply.zones).each(function(zoneId) { var manager = Tapestry.findZoneManagerForZone(zoneId); if (manager) { var zoneContent = reply.zones[zoneId]; manager.show(zoneContent); } }); }.bind(this)); } }); Tapestry.Palette.prototype.updateHidden = function() { // Every value in the selected list (whether enabled or not) is combined to // form the value. var values = $A(this.selected).map(function(o) { return o.value; }); this.hidden.value = Object.toJSON(values); }; = On Mon, Dec 19, 2011 at 7:58 PM, Thiago H. de Paula Figueiredo thiag...@gmail.com wrote: Hi! Has anyone tried to use T5.1.0.5 with Prototype 1.7 and Scriptaculous 1.9? I'm having some weird JS errors: * Tapestry.Logging not defined. * Tapestry.Messages not defined. * undefinedTypeError: reply.zones is not an object. Are there known Tapestry.js issues with these versions of Prototype 1.7 and Scriptaculous 1.9? Any hints? -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry 5.1.0.5 vs Prototype 1.7 and Scriptaculous 1.9
Thank you, Dmitriy! Works like a charm! Now I'm chasing a non-related IE-specific JavaScript bug (sigh). Hugi, please pay the beers you owe me to Dmitriy! :D Sure — just have him contact me next time he's here in Reykjavik, Iceland (yes: that's how I can afford to promise beer to everyone, mahaha :o). Cheers, - hugi - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org