That's interesting, Robert. I actually have a paid subscription to the
Ext library but haven't seen this. Does this actually help show where
the error is *in my code*? Because that's the problem I've always had
with Ext. I'll miss a comma or brace or mistype the option or some
such and then one of two things happens:
1: Absolutely nothing. This problem isn't specific to Ext, it is a
common problem I've seen across most javascript. If you get an
attribute name wrong or something it just ignores it and goes on, not
throwing an error, it just doesn't work.
2: Throws an error but the error is within the main Ext library
instead of pointing to an error in the code that I was writing that
actually triggered the error.
Those two things are what I absolutely hate most about writing Javascript.
Judah
On Thu, Jul 1, 2010 at 10:49 AM, Robert Munn <cfmuns...@gmail.com> wrote:
>
> Funny, I've been using ExtJS, and I always had the same problem with
> the error isolation, until I got into the subscription-only forums,
> where someone actually answered my question and provided a link in the
> forum to a way to automatically include the source (individual) JS
> files for Ext, which makes debugging far, far easier. There was an old
> CF solution for the includes that I updated to the latest ExtJS
> (3.2.1), here is the code below. I like Ext, but I don't appreciate
> how they make you pay to get much in the way of useful help. I always
> liked how Allaire, then Macromedia, now Adobe had free forums where
> you could get help.
>
>
> <script type="text/javascript"
> src="/scripts/ext/adapter/ext/ext-base.js"></script>
>
> <cffile
> action = "read"
> file = "#GetDirectoryFromPath(ExpandPath("*.*"))#scripts\ext\ext.jsb2"
> variable = "doc">
> <cfset docs = DeserializeJSON(doc)/>
>
> <cfscript>
> tpl = '<script type="text/javascript"
> src="/scripts/ext/{file}"></script>';
> pkgstruct = structnew();
> for (i = 1; i LTE ArrayLen(docs.pkgs); i++)
> {
> pkgstruct[docs.pkgs[i].file] = docs.pkgs[i].fileIncludes;
>
> if(docs.pkgs[i].file eq "ext-all.js"){
> deps = docs.pkgs[i].pkgDeps;
> //break;
> }
> }
>
> for(j=1;j LTE arraylen(deps); j++){
> for(k=1;k lte arraylen(pkgstruct[deps[j]]);k++){
> jsFile = pkgstruct[deps[j]][k].path &
> pkgstruct[deps[j]][k].text;
> writeOutput(Replace(tpl,'{file}',jsFile));
> }
>
> }
> </cfscript>
>
> On Thu, Jul 1, 2010 at 9:56 AM, Judah McAuley <ju...@wiredotter.com> wrote:
>>
>> I've just started a new admin using JQuery UI and jqGrid. Pretty nice
>> so far and more light weight than ExtJS that I was using before. The
>> biggest thing that I like about it, so far, is that errors are easier
>> to isolate. Whenever I had an error in my ExtJS code, the actual JS
>> error would be thrown in the middle of the Ext library file which is
>> of no help what so ever. With the JQuery stuff, thus far, my errors
>> have been easier to figure out and that is a big help.
>>
>> Judah
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:322441
Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm
