[mochikit] developing with / for internet explorer

2006-07-15 Thread GHUM
Hello, I created some rather complex Intranet Application, using lots of JavaScript, DOM-Maninpulation and XMLHTTPRequest communication. I developed on FireFox, with the excellent firebug ... every misstake was given back with a fine, fine traceback; exactly pointing to the code at error. My co

[mochikit] Re: developing with / for internet explorer

2006-07-15 Thread SMooney
I know it's trivial, but have you tried throwing some alert()'s in there to get your bearings? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegr

[mochikit] Re: developing with / for internet explorer

2006-07-15 Thread GHUM
SMooney, > I know it's trivial, but have you tried throwing some alert()'s in > there to get your bearings? yes. I started doing this, but that feels so 1999ish, and takes ages. Having started my programming career on C64, of course there are methods to track down an error in a 500 line javascr

[mochikit] Re: developing with / for internet explorer

2006-07-15 Thread Steven Mooney
Agreed.  That's all I really had to contribute... other than...   It's line 266!  :-)  On 7/15/06, GHUM <[EMAIL PROTECTED]> wrote: SMooney,> I know it's trivial, but have you tried throwing some alert()'s in> there to get your bearings? yes. I started doing this, but that feels so 1999ish, and take

[mochikit] Re: developing with / for internet explorer

2006-07-15 Thread Zachery Bir
Drop the alerts, and liberally log() your way through the app, then use MochiKit's logging bookmarklet. "MochiKit.Logging - we're all tired of alert()" Zac --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Moc

[mochikit] Re: setElementClass question

2006-07-15 Thread .M.
Thanks very much for all the help. Working now. A couple of suggestions for the doco: It might help if there was a top level nav on the site so you can navigate the different Mochikit reference pages more easily. I was trying to create my signal code without understanding how things interrelate.

[mochikit] Re: developing with / for internet explorer

2006-07-15 Thread Steven Mooney
Excellent point. On 7/15/06, Zachery Bir <[EMAIL PROTECTED]> wrote: Drop the alerts, and liberally log() your way through the app, thenuse MochiKit's logging bookmarklet.   "MochiKit.Logging - we're all tired of alert()"Zac --~--~-~--~~~---~--~~ You received this me

[mochikit] MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Andrew
Hi, I have just downloaded the latest, svn, version of MochiKit and am using it (packed) in conjunction with dojo 0.3.1. I attempt to create a new DOM like so: MochiKit.DOM.createDOM(data) - data being an xhtml document and I get the following error message via FireBug: uncaught exception: [Exc

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Zachery Bir
On Jul 15, 2006, at 12:31 PM, Andrew wrote: > Hi, > I have just downloaded the latest, svn, version of MochiKit and am > using it (packed) in conjunction with dojo 0.3.1. I attempt to > create a > new DOM like so: > > MochiKit.DOM.createDOM(data) - data being an xhtml document > > and I get the

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Andrew
Hi, on a further note > MochiKit.DOM.createDOM(data) - data being an xhtml document it turns out that the error was mine as I never explicitly declared the variable xml! When I do an alert on divList I get 'null'. I thought mochikit dom avoided that?! var x = new dojo.io.FormBind({ for

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Andrew
Hi Zac, what I'm attempting to do is getting the returned page from a submit and then taking out element output which is the id of a div tag in the returned document. So it's basicall the other way round of what you have mentioned: my_doc = createDOM(data); dojo.ById("myDIV") = my_doc.getElementB

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Andrew
One of those days! > dojo.ById("myDIV") = my_doc.getElementById("output"); this should be dojo.ById("myDIV").innerHTML = my_doc.getElementById("output").innerHTML; regards Andrew --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Zachery Bir
On Jul 15, 2006, at 12:58 PM, Andrew wrote: > Hi Zac, > what I'm attempting to do is getting the returned page from a submit > and then taking out element output which is the id of a div tag in the > returned document. So it's basicall the other way round of what you > have mentioned: Doesn't ma

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Andrew
Ok, my bad, I understand now. So my next question is, is there any way in mochikit to create a DOM document from a string or xml type of document? regards Andrew --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Mo

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Bob Ippolito
On Jul 15, 2006, at 9:31 AM, Andrew wrote: > > Hi, > I have just downloaded the latest, svn, version of MochiKit and am > using it (packed) in conjunction with dojo 0.3.1. I attempt to > create a > new DOM like so: > > MochiKit.DOM.createDOM(data) - data being an xhtml document > > and I get t

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Andrew
Hi Bob, you are correct. What I was after was: xml = dojo.dom.createDocumentFromText(data); divList = xml.getElementsByTagName("div"); dojo.byId('output').innerHTML = dojo.dom.innerXML(divList.item(2)); Just wondered whether there was a nicer, more intuitive, way of doing thing

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Bob Ippolito
On Jul 15, 2006, at 10:21 AM, Andrew wrote: > Ok, my bad, I understand now. So my next question is, is there any way > in mochikit to create a DOM document from a string or xml type of > document? No, you'll have to use the browser's native way to do that. The only really portable way is to u

[mochikit] Re: MochiKit.DOM.createDOM problem.....

2006-07-15 Thread Zachery Bir
On Jul 15, 2006, at 1:28 PM, Andrew wrote: > Hi Bob, > you are correct. What I was after was: > > xml = dojo.dom.createDocumentFromText(data); > divList = xml.getElementsByTagName("div"); > dojo.byId('output').innerHTML = > dojo.dom.innerXML(divList.item(2)); > > Just wondered w

[mochikit] Safari onkeyup events

2006-07-15 Thread [EMAIL PROTECTED]
I'm using MochiKit to attach an onkeyup event, but it emits two onkeyup events for every key press in Safari. Is this a known issue? If not, I can create a test case. -ryan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google G

[mochikit] Re: Safari onkeyup events

2006-07-15 Thread Bob Ippolito
On Jul 15, 2006, at 3:31 PM, [EMAIL PROTECTED] wrote: > I'm using MochiKit to attach an onkeyup event, but it emits two > onkeyup > events for every key press in Safari. Is this a known issue? If not, I > can create a test case. This is a known bug in Safari. I'm surprised it's not in the doc

[mochikit] Rounded edges technique for an input submit button with an added css class def.

2006-07-15 Thread Andrew Madu
Hi,I have defined a button css class for an input submit button. When the class is applied to the input tag the formerly, standard, rounded edges of the normal input type="submit" buttons are now nice and square!! Can I apply the rounded technique in this instance? My css class is as follows: .butt

[mochikit] Re: Rounded edges technique for an input submit button with an added css class def.

2006-07-15 Thread Bob Ippolito
On Jul 15, 2006, at 6:06 PM, Andrew Madu wrote: > I have defined a button css class for an input submit button. When > the class is applied to the input tag the formerly, standard, > rounded edges of the normal input type="submit" buttons are now > nice and square!! Can I apply the rounded

[mochikit] Re: Safari onkeyup events

2006-07-15 Thread Bob Ippolito
On Jul 15, 2006, at 7:26 PM, Ryan King wrote:On 7/15/06, Bob Ippolito <[EMAIL PROTECTED]> wrote: On Jul 15, 2006, at 3:31 PM, [EMAIL PROTECTED] wrote:> I'm using MochiKit to attach an onkeyup event, but it emits two> onkeyup> events for every key press in Safari. Is this a known issue? If not, I >

[mochikit] Re: developing with / for internet explorer

2006-07-15 Thread Jason Bunting
> -Original Message- > From: mochikit@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Zachery Bir > Sent: Saturday, July 15, 2006 6:47 AM > Subject: [mochikit] Re: developing with / for internet explorer > > Drop the alerts, and liberally log() your way through the app, then >

[mochikit] Re: Traversing large DOM trees

2006-07-15 Thread Tom W.M.
I recently did this for a code highlighting script. I was mainly interested in text nodes, but I tried to keep my solution fairly general. It involves two scripts: http://freecog.net/scripts/AsyncQueue.js?pretty http://freecog.net/2006/syntaxhighlighter/syntaxhighlighter.js?pretty The AsyncQ