Thanks Jesse! A coworker pulled down the new snapshot and palette is working properly again. I'll take a look at AjaxShellDelegate and see if we can get that path at the top fixed.
-----Original Message----- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Friday, December 08, 2006 3:25 PM To: Tapestry users Subject: Re: Tapestry 4.1.1 dojo issue Ok, fixed and deploying now. Sorry about that. I had recently refactored some of the palette javascript to use friendlier package conventions by attaching all functions to the global "tapestry" javascript object. In this instance I forgot to fix the form event connections so it ended up generating: dojo.event.connect("formClientId", "onsubmit", "tapestry.palette_onSubmit"); when it really should have been: dojo.event.connect("formClientId", "onsubmit", tapestry, "palette_onSubmit"); Thanks and sorry for the hiccup. On 12/8/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > "Oh" (adjusting collar slightly ) > > I'll fix this while I'm fixing another issue now. Should be available > in an hour or so if you use the snapshot repos. > > On 12/8/06, Anna Vo <[EMAIL PROTECTED]> wrote: > > Jesse- > > > > If you only select Red and Orange from the example (by double-clicking > > on each of them individually) and click Update it will only display > > Orange on the next page if Orange is the one that is highlighted in the > > Selected list. > > > > If you select multiples and all of these are selected/highlighted on the > > Selected list than all the ones that are highlighted in the Selected > > list will show. > > > > It only recognizes what is currently highlighted of those selected in > > the Selected list. > > > > http://opencomponentry.com:8080/workbench/Home,$Border.pageLink.sdirect? > > sp=SPalette" > > > > Anna > > > > -----Original Message----- > > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] > > Sent: Friday, December 08, 2006 2:07 PM > > To: Tapestry users > > Subject: Re: Tapestry 4.1.1 dojo issue > > > > Hi Ben, > > > > Thanks for being brave and trying out 4.1.1, I'm sure others will > > appreciate whatever improvements can be made at the expense of your > > initial set of problems faced. > > > > The line dojo.registerModulePath is output by the AjaxShellDelegate > > (http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/dojo > > /AjaxShellDelegate.html) > > - which is used by both the Shell and ScriptIncludes components , > > depending on your needs. > > (http://tapestry.apache.org/tapestry4.1/components/general/shell.html, > > http://tapestry.apache.org/tapestry4.1/components/general/scriptincludes > > .html > > ). > > > > This tells dojo what the base sort of url is to resolve all > > dojo.require("tapestry.<foo>") resources from. It is ~also~ used by > > the tapestry dojo namespace (http://dojo.jot.com/Dojo0.4PortingGuide ) > > to detect the right path and register it appropriately for widgets > > being resolved. > > > > I'm not sure what path issues you've had based on your message (maybe > > I just missed that part), but more elaboration might help me provide a > > better answer. > > > > The Palette component ~should~ work correctly, as can be seen here: > > > > http://opencomponentry.com:8080/workbench/Home,$Border.pageLink.sdirect? > > sp=SPalette > > > > Again, more specifics on your usage here and where/how/why it's not > > working would help me figure out what the exact issue is. > > > > On 12/8/06, Ben Dotte <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > > > > > > > We recently upgraded to 4.1.1 from 4.0.2 and are still having some > > > issues with dojo-related stuff. Right now, we are on the snapshot > > build > > > from 12-4. One thing I can't figure out is where the path for this is > > > getting generated in the rendered html: > > > > > > > > > > > > dojo.registerModulePath("tapestry", "/assets/static/tapestry"); > > > > > > > > > > > > That looks like the generic path used for the djConfig > > baseRelativePath, > > > dojo.js, and tapestry's core.js. But I have replaced the path > > > successfully for those three in the Shell component. > > > > > > > > > > > > One specific problem we have seen is in the contrib Palette. When I > > > submit a form, it is supposed to call a select-all javascript function > > > in order to capture the changes. This is supposed to happen through a > > > call at the end something like dojo.event.connect('formName', > > > 'onsubmit', selectAllFunction) but that select all function never gets > > > called. A workaround we have found is to provide an onclick event to > > > that same selectAllFunction when the submit button is clicked, but > > that > > > is pretty hackish and ugly. > > > > > > > > > > > > I'm not sure if the Palette issue is related to the path issue > > mentioned > > > above, but it seems that certain dojo-related things just aren't > > > working. Others, like the autocompleter, work fine though. > > > > > > > > > > > > Any suggestions/pointers would be much appreciated. > > > > > > > > > > > > Thanks, > > > > > > Ben > > > > > > > > > > > > > > > -- > > 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] > > > > > > --------------------------------------------------------------------- > > 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 > -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
