> -----Original Message----- > From: Alexander Klimetschek [mailto:[EMAIL PROTECTED] > Sent: Monday, June 02, 2008 12:17 PM > To: [email protected] > Subject: Re: Dojo Bundles > > On Mon, Jun 2, 2008 at 6:55 PM, Craig L. Ching > <[EMAIL PROTECTED]> wrote:
> > These tyeps of errors in dojo aren't the easiest things to > > track down unless you're familiar with them ;-) > > Yes, and they are sign of a quick dojo hack ;-) > Quick? No, dojo has been like that forever. Hack? Maybe. What they're trying to do is admirable for sure. I don't know if there's another good way to accomplish what they're doing so that it also gives good information on why a script failed to load. I think part of it is a feature that dojo wants that javascript just doesn't support, but I'm not a JS expert by any means. I *thought* there was a way you could get better errors, but that required a custom build of dojo, something you (sling) *don't* want to do since you're providing a general purpose dojo implementation. For my own work, I will not be using Sling's provided dojo bundle, I'll be building my own that provides everything necessary for proper execution of my application in a single, compressed .js script. Anyway, don't mean to be argumentative, but I actually really like dojo's require system. Once you get used to it, it's not so bad tracking down these sorts of problems. Indeed, once you understand it, it rarely comes up because you code against having these sorts of problems by nature. > Alex > > -- > Alexander Klimetschek > [EMAIL PROTECTED] > Cheers, Craig
