> I've been using dojo for a while now. In fact, I think it was a > posting from Scott that got me on to it!
That's it blame me!!! LOL! I agree with you Aaron, I DETESTED writing my own javascript with all the browser crap that I had to keep in the back of my head and what. Dojo did improve on my feeling about using javascript somewhat. However, when I found jQuery, it was like a whole new world opened up. I actually wanted to write javascript, well at least writing it the jQuery way ;-). jQuery uses XPath for traversing the DOM and is quite quick at it. jQuery's has a plugin architecture for extending the jQuery core which is surprisingly elegant and simple. I find myself writing much less code now that I am using jQuery. You will be amazed at what you can to in just 10 lines of jQuery. jQuery also has a very active community and a plethora of 3rd party plugins already available. I dunno jQuery just "feels" right if that makes sense. It is the same feeling I got when I started using Spring. Okay, I will get off my soap box now ;-) p.s. Actually one of our biggest performance hang-ups (after widgets) was the DOJO packaging system. IIRC, any time you "include" a package an XMLHttpRequest is issued to the server to grab the code. From what I have seen and I may be wrong, browsers do not cache XMLHttpRequests, well at least not without jumping through nasty hoops on the server side and even then I don't know if you can get the browser to cache. -scott > -----Original Message----- > From: Aaron Evans [mailto:[EMAIL PROTECTED] > Sent: Monday, April 23, 2007 11:11 AM > To: Jetspeed Developers List > Subject: Re: Modifying the Jetspeed Desktop > > I've been using dojo for a while now. In fact, I think it was a > posting from Scott that got me on to it! > > We're using a custom build for it so I am not sure that I'll be able > to easily merge my build with the one that is used for desktop, but I > haven't tried. > > I hear all those frustrations with dojo, but they claim they're going > to address a bunch of them and finally release a 1.0 soon. In any > event, if you guys ultimately decide to switch I don't think it would > really matter to me in the long run. > > My biggest problem has been with widgets. At this point, they should > only be used sparsely because they just kill page load time if you use > a bunch of them in a page. So I've started moving away from them and > only using them here and there. > > Wrt the "re-writing" of javascript to be more like Java that Scott > mentioned, maybe Scott is right and this leads to problems. However, I > can tell you that I HATED coding javascript until I started using > dojo's packaging model. But then again, most of my experience with > javascript was back in the days of HTML 1.0 when it really did suck. > There are a ton of things you can do now that I had no idea you could > do. > > Anyhow, just my 2 cents... > > On 4/23/07, David Sean Taylor <[EMAIL PROTECTED]> wrote: > > > > On Apr 23, 2007, at 4:07 PM, Weaver, Scott wrote: > > > > > Sounds good to me I would love to get back in the game as it were :) > > > > Yeah, what happened to you dude, did you go on a road trip with Ken > > Kesey or what ;-) ? > > OK ... I need to get creative and come up with a way to get us > > together for the big summit.... > > > > > > > One of DOJO's biggest downfalls was their attempt to "rewrite" how > > > javascript works and trying to make it more "java-like". This just > > > compounds the complexity exponentially when coupled with the fact that > > > the documentation is so sparse. > > > > > > > Yeah, I must say my productivity was way done using this framework, > > frustration way up > > That said it does work nicely at times > > > > Be interested to see what Steve says when he gets back from vacation.... > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > 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]
