[mochikit] Re: why the interpreter demo can't use help()

On 19-Jun-06, at 11:35 PM, wlt008 wrote: > When I type the help command like help(map), nothing happened... Works for me: >>> help(map) map(fn, lst[, ...]) What browser/platform are you on? Are you using the version at , or from a s

[mochikit] Re: why the interpreter demo can't use help()

I use firefox. I tested dev version and local version and the link from your mail. The result is the same:>>> help(map)blocking on Deferred(2, unfired)... Then no document whould be shown no metter how long I am waitting for.BTW, I have tested in IE, in my IE the result is >>> help(map) documentati

[mochikit] Is there anything similar to the plex DataGrid?

http://www.plextk.org/trac/wiki/SampleDataGrid What is the best way of implementing something similar to be used within TurboGears? Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post

[mochikit] Re: why the interpreter demo can't use help()

FYI, I get the same thing as well in FF and IE on WinXP.   From: mochikit@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Wei Litao Sent: Tuesday, June 20, 2006 3:33 AM To: Beau Hartshorne Cc: MochiKit Subject: [mochikit] Re: why the interpreter demo can't use help()

[mochikit] Re: why the interpreter demo can't use help()

On 20-Jun-06, at 2:33 AM, Wei Litao wrote: > I use firefox. I tested dev version and local version and the link > from your mail. The result is the same: > > >>> help(map) > blocking on Deferred(2, unfired)... > > Then no document whould be shown no metter how long I am waitting for. > > BTW, I

[mochikit] Re: why the interpreter demo can't use help()

On Jun 20, 2006, at 11:42 AM, Beau Hartshorne wrote: > > On 20-Jun-06, at 2:33 AM, Wei Litao wrote: > >> I use firefox. I tested dev version and local version and the link >> from your mail. The result is the same: >> > help(map) >> blocking on Deferred(2, unfired)... >> >> Then no document

[mochikit] Re: window.onunload

On 16-Jun-06, at 12:20 PM, Mc wrote: > Not for the onbeforeunload event. For all other events, sure. But if > you call e.stop() in an onbeforeunload event handler, it gives you the > Confirm/Cancel dialog by itself. So your example pops up a dialog > twice > and it doesn't allow for an extra me

[mochikit] Re: new design of site is cool

On 19-Jun-06, at 3:07 PM, Arnar Birgisson wrote: > Me too. :o) The site is clean and nice. > > There's one thing that bugs the h*ll out of me though. In the docs > main page, which I have bookmarked, it takes a while for the script to > build the table of contents (the expandable thingie). I clic

[mochikit] Re: new design of site is cool

On 6/20/06, Beau Hartshorne <[EMAIL PROTECTED]> wrote: > This has stung me before too. How's this (make sure you do a super > reload): > http://mochikit.com/doc/html/MochiKit/index.html > > Changeset: > http://trac.mochikit.com/changeset/1033 > That nails it. I think I can speak for Arnar as wel

[mochikit] Re: [Fwd: pulsate patch]

I can confirm this problem. Using the latest SVN checkout (on June 20th), attempting to call Highlight produces the following error (via Firebug): this.__init__ is not a functionMochiKit.js (line 5265) This is with the packed code. Is this enough info to reproduce the bug with? Topher