What's your timeframe for finishing this? Will its API change much?
I started doing screencasts of "how to use unittest" today for peepcode.
If this patch is not useful, then it suggests the current
Event.simulateMouse code should be removed as part of the refactoring. Force
people to go looking for a tested, known working library to perform the
simulations rather than attempt to use known non-working code?
On 2/4/08, Tobie Langel <[EMAIL PROTECTED]> wrote:
> The reason I'm not too keen on adding this two unit tests is two-
> First I think it belongs in Prototype core, secondly, I'm in the
> process of rewriting a good deal of unit_tests so I really don't think
> it's a good time to add features to it. I'd rather strengthen it as
> much as possible beforehand.
> On Feb 4, 1:19 pm, "Nic Williams" <[EMAIL PROTECTED]> wrote:
> > Heh. If I am, then I'll be that person "some time in the future" :)
> > I'm trying to work on unittest; which just happens to co-share a repo +
> > mailing list with prototype :)
> > On 2/4/08, Nick Stakenburg <[EMAIL PROTECTED]> wrote:
> > > > Yes there might be a better/more complete possibility, and someone
> > > do
> > > > it in the future
> > > > I think I'd rather see an incremental fix now; AND wait for someone
> > > write
> > > > an even better version later.
> > > > Perhaps once this patch is in, someone else will look at it
> > > You could be that someone ;)
> > --
> > Dr Nic Williamshttp://drnicacademy.com- Ruby/Rails training/dev around
> > (skype) nicwilliams
> > (p) +61 412 002 126 / +61 7 3113 3033
> > (mail) PO Box 583 Ashgrove 4060 QLD Aus
Dr Nic Williams
http://drnicacademy.com - Ruby/Rails training/dev around the world
(p) +61 412 002 126 / +61 7 3113 3033
(mail) PO Box 583 Ashgrove 4060 QLD Aus
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at