No I hadn't known this component existed at all. I had discovered windows WSH (web scripting host) which allows js based unit tests to run with a real IE backing up the window/document objects.
Mozilla is a little trickier, but thanks to IBM we have java XPCOM which allows basically the same thing. (I am guessing floyd is using this) I had planned on delving further into the XPCOM api but now that I see this I will invesitgate it instead :) Thank you ~SO~ much. You have no idea how much the ajax sort of community has needed/wanted something like this. Will have to try it out to see if it's really what it says it is. On 5/31/06, Kalle Korhonen <[EMAIL PROTECTED]> wrote:
OT, but since you mentioned it, are you aware of Floyd (https://floyd.dev.java.net/ and http://www.openqa.org/floyd/HowToUnitTestTheUserInterfaceOfWebApplications.pdf ). If yes, how does it compare to the stuff you are using and would you see any problems in using Floyd for Tapestry specific apps? Kalle On 5/26/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > P.S. I found a way to let us have complete in-browser tests for mozilla as > well. (ie using gecko/spidermonkey as the rendering/js engine ). Combined > with wsh for ie we'll be able to have complete in-browser unit tests. ....Am > probably not going to do the mozilla thing for a while still as it'll > require too much concentrated effort. > > On 5/26/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > > Looks like it. The checkin was a little incomplete, just making sure I > > could tell the difference between incoming patches and existing code. > > > > > > On 5/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > From [EMAIL PROTECTED]: > > > > > > > > > ============================================================================== > > > > --- tapestry/tapestry4/trunk/framework/src/js/tapestry/event.js > > > (added) > > > > +++ tapestry/tapestry4/trunk/framework/src/js/tapestry/event.js Fri > > > May 26 > > > > > > > + > > > > + if(event["type"]) props.type=event.type; > > > > + if(event["keys"]) props.keys=encodeUriComponent( > > > event.keys); > > > > + if(event["pageX"]) props.pageX=evt.pageX; > > > > + if(event["pageY"]) props.pageY=evt.pageY; > > > > + if(event["layerX"]) props.layerX=evt.layerX; > > > > + if(event["layerY"]) props.layerY=evt.layerY; > > > > > > Haven't tried this, but isn't 'evt' in the 4 previous lines a typo ? > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Jesse Kuhnert > > Tacos/Tapestry, team member/developer > > > > Open source based consulting work centered around > > dojo/tapestry/tacos/hivemind. > > > > > > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
