(Unofficial) FilteringTable enhancements

[Tom Trenka]

Sorry--been slowing abandoning looking over the Interest list in favor of the new forums (http://dojotoolkit.org/forum)...if I remember correctly, Ross is right: there are issues with trying to run file-based code in IE7.  From the errors you've posted, it looks to me like you aren't coming close to even loading the FilteringTable code...I know there were some loader changes in 0.4.2 which might be the issue here.

trt

PS.  That's "The New Forums Over at the Dojo Site", at http://dojotoolkit.org/forum.

:)

Ross Thomas wrote:

jezza wrote:

I agree with you entirely with regards to IE7.  I have had nothing but trouble since it was released.

Heh!  Yeah.  Most of our clients have reverted to IE6 after various levels of
frustration with IE7.  I keep recommending FF -- some have listened. :-)

I think you are right about it being a permission thing.  The behaviour seems to be the same regardless of whether I am using the patched version or the original version.  To make matters more confusing, it now appears to be working when I place the test file inside apache or tomcat and view it using http:// ... renderusing.html but is not working when I try to open it as a stand alone file ( e.g. c:\... renderusing.html in the address bar).

Oooo!  I remember a thread about 'file' URLs a month or two ago.  Same
sort of problem.  Not sure if there was a resolution other than 'use a server'.
I'll try a search and see if I can find it.

This strikes me as rather odd, b/c running it inside a web application at work today is where I first noticed the problem.  Unfortunately, I won't be in again until Monday, so I won't be able to run the same tests until then.

Putting a try / catch block in the init function seemed to make no difference, as I think it might be failing before it even gets to it.  Getting IE to break on error gives the following error message:
Error Line: 97
Char: 1
Error: Could not load 'dojo.widget.FilteringTable';last tried '__package__.js
Code: 0
URL: file:///c:/temp/renderusing.html

In light of that, it looks to me that dojo is not loading at all.  If that is the case, I assume is a permission thing IE somewhere that needs to be enabled.  Either way, there is not much you can do about it.

You are right about the failure occuring before we even get to loading data.
However, once we understand the problem, we may be able to provide a
solution even though neither of us is a base developer.

I will have another look on Monday at on the server where I first noticed the issue.  If I come up with anything new, I will let you know.

Cool.  I think a few others on the list would also be happy for a resolution.

Thanks for pointing me in the right direction, and thanks again for providing such a useful function.

NP.  As usual the majority of all kudos go to Tom and the Dojo team for providing
such a great environment to work in.

Ross.

[Sasha Firsov]

There is no big deal with file system on IE7. It does not allow XHR to
work with file system.
Shame on dojo, with all flexibility of io.bind, internal dojo.require
stuck with XHR :(
So solution will be either:
a) embed everything in dojo.js ( read docs how), which is almost
impossible for many reasons.
b) replace default  fetcher with  ActiveX version of XHR. Look for my
post few month back or in the end of
 http://firsov.net/~suns/demos/dojo/FilteringTable_fillCell/dojo-base/dojo.js


Happy coding on file system!
Sasha

Ross Thomas wrote:

> jezza wrote:
>  
>> I agree with you entirely with regards to IE7.  I have had nothing but
>> trouble since it was released.
>>
>>    
>
> Heh!  Yeah.  Most of our clients have reverted to IE6 after various levels
> of
> frustration with IE7.  I keep recommending FF -- some have listened. :-)
>
>
>
>  
>> I think you are right about it being a permission thing.  The behaviour
>> seems to be the same regardless of whether I am using the patched version
>> or the original version.  To make matters more confusing, it now appears
>> to be working when I place the test file inside apache or tomcat and view
>> it using http:// ... renderusing.html but is not working when I try to
>> open it as a stand alone file ( e.g. c:\... renderusing.html in the
>> address bar).
>>
>>    
>
> Oooo!  I remember a thread about 'file' URLs a month or two ago.  Same
> sort of problem.  Not sure if there was a resolution other than 'use a
> server'.
> I'll try a search and see if I can find it.
>
>
>
>  
>> This strikes me as rather odd, b/c running it inside a web application at
>> work today is where I first noticed the problem.  Unfortunately, I won't
>> be in again until Monday, so I won't be able to run the same tests until
>> then.
>>
>> Putting a try / catch block in the init function seemed to make no
>> difference, as I think it might be failing before it even gets to it.
>> Getting IE to break on error gives the following error message:
>> Error Line: 97
>> Char: 1
>> Error: Could not load 'dojo.widget.FilteringTable';last tried
>> '__package__.js
>> Code: 0
>> URL: file:///c:/temp/renderusing.html
>>
>> In light of that, it looks to me that dojo is not loading at all.  If that
>> is the case, I assume is a permission thing IE somewhere that needs to be
>> enabled.  Either way, there is not much you can do about it.
>>
>>    
>
> You are right about the failure occuring before we even get to loading data.
> However, once we understand the problem, we may be able to provide a
> solution even though neither of us is a base developer.
>
>
>
>  
>> I will have another look on Monday at on the server where I first noticed
>> the issue.  If I come up with anything new, I will let you know.
>>
>>    
>
> Cool.  I think a few others on the list would also be happy for a
> resolution.
>
>
>
>  
>> Thanks for pointing me in the right direction, and thanks again for
>> providing such a useful function.
>>
>>    
>
> NP.  As usual the majority of all kudos go to Tom and the Dojo team for
> providing
> such a great environment to work in.
>
> Ross.
>  

_______________________________________________
FAQ: http://dojotoolkit.org/support/faq
Book: http://dojotoolkit.org/docs/book
Forums: http://dojotoolkit.org/forum
Dojo-interest@...
http://dojotoolkit.org/mailman/listinfo/dojo-interest

[James Burke-3]

Be careful forcing the use of the ActiveX XMLHttpRequest object in
IE7. There are some undesirable side effects:

http://www.ashleyit.com/blogs/brentashley/2006/06/05/ie7-make-sure-you-invoke-native-xmlhttprequest-object/

James

On 4/16/07, Sasha Firsov <Sasha@...> wrote:

> There is no big deal with file system on IE7. It does not allow XHR to
> work with file system.
> Shame on dojo, with all flexibility of io.bind, internal dojo.require
> stuck with XHR :(
> So solution will be either:
> a) embed everything in dojo.js ( read docs how), which is almost
> impossible for many reasons.
> b) replace default  fetcher with  ActiveX version of XHR. Look for my
> post few month back or in the end of
>  http://firsov.net/~suns/demos/dojo/FilteringTable_fillCell/dojo-base/dojo.js
>
>
> Happy coding on file system!
> Sasha
>
> Ross Thomas wrote:
> > jezza wrote:
> >
> >> I agree with you entirely with regards to IE7.  I have had nothing but
> >> trouble since it was released.
> >>
> >>
> >
> > Heh!  Yeah.  Most of our clients have reverted to IE6 after various levels
> > of
> > frustration with IE7.  I keep recommending FF -- some have listened. :-)
> >
> >
> >
> >
> >> I think you are right about it being a permission thing.  The behaviour
> >> seems to be the same regardless of whether I am using the patched version
> >> or the original version.  To make matters more confusing, it now appears
> >> to be working when I place the test file inside apache or tomcat and view
> >> it using http:// ... renderusing.html but is not working when I try to
> >> open it as a stand alone file ( e.g. c:\... renderusing.html in the
> >> address bar).
> >>
> >>
> >
> > Oooo!  I remember a thread about 'file' URLs a month or two ago.  Same
> > sort of problem.  Not sure if there was a resolution other than 'use a
> > server'.
> > I'll try a search and see if I can find it.
> >
> >
> >
> >
> >> This strikes me as rather odd, b/c running it inside a web application at
> >> work today is where I first noticed the problem.  Unfortunately, I won't
> >> be in again until Monday, so I won't be able to run the same tests until
> >> then.
> >>
> >> Putting a try / catch block in the init function seemed to make no
> >> difference, as I think it might be failing before it even gets to it.
> >> Getting IE to break on error gives the following error message:
> >> Error Line: 97
> >> Char: 1
> >> Error: Could not load 'dojo.widget.FilteringTable';last tried
> >> '__package__.js
> >> Code: 0
> >> URL: file:///c:/temp/renderusing.html
> >>
> >> In light of that, it looks to me that dojo is not loading at all.  If that
> >> is the case, I assume is a permission thing IE somewhere that needs to be
> >> enabled.  Either way, there is not much you can do about it.
> >>
> >>
> >
> > You are right about the failure occuring before we even get to loading data.
> > However, once we understand the problem, we may be able to provide a
> > solution even though neither of us is a base developer.
> >
> >
> >
> >
> >> I will have another look on Monday at on the server where I first noticed
> >> the issue.  If I come up with anything new, I will let you know.
> >>
> >>
> >
> > Cool.  I think a few others on the list would also be happy for a
> > resolution.
> >
> >
> >
> >
> >> Thanks for pointing me in the right direction, and thanks again for
> >> providing such a useful function.
> >>
> >>
> >
> > NP.  As usual the majority of all kudos go to Tom and the Dojo team for
> > providing
> > such a great environment to work in.
> >
> > Ross.
> >
>
> _______________________________________________
> FAQ: http://dojotoolkit.org/support/faq
> Book: http://dojotoolkit.org/docs/book
> Forums: http://dojotoolkit.org/forum
> Dojo-interest@...
> http://dojotoolkit.org/mailman/listinfo/dojo-interest
>

_______________________________________________
FAQ: http://dojotoolkit.org/support/faq
Book: http://dojotoolkit.org/docs/book
Forums: http://dojotoolkit.org/forum
Dojo-interest@...
http://dojotoolkit.org/mailman/listinfo/dojo-interest

[Sasha Firsov]

Agree, on http/https or ftp,  native XHR works better for many reasons.
In case of file:// protocol+IE7, there is no choice.
So it is more appropriately to ask how to make this substitution
optional and correctly.
Answer: Use for web URLs native XHR, and ActiveX for file system.
This method work well if there is no mix of protocols (file vs.
network). So far so good.

For mixed protocols:
    - for dojo.require() , XHR implementation replacement need to be
done on another method - dojo.hostenv.getText(), I guess. It accepts URL
parameter and creates XHR for dojo.require().
    - You still need to be aware of other narrow spots, like
FilteringTable, which uses XHR (not io.bind).

May be someone could offer wrapper with XHR interface, capable of
switching protocols ?
It will make an easier, unified patch for whole dojo.
Also, based *only* on this wrapper, extra FS could be supported, JAR
archive or offline run, for example !

If there is an interest, make a request here.

Sasha

James Burke wrote:

> Be careful forcing the use of the ActiveX XMLHttpRequest object in
> IE7. There are some undesirable side effects:
>
> http://www.ashleyit.com/blogs/brentashley/2006/06/05/ie7-make-sure-you-invoke-native-xmlhttprequest-object/
>
> James
>
> On 4/16/07, Sasha Firsov <Sasha@...> wrote:
>  
>> There is no big deal with file system on IE7. It does not allow XHR to
>> work with file system.
>> Shame on dojo, with all flexibility of io.bind, internal dojo.require
>> stuck with XHR :(
>> So solution will be either:
>> a) embed everything in dojo.js ( read docs how), which is almost
>> impossible for many reasons.
>> b) replace default  fetcher with  ActiveX version of XHR. Look for my
>> post few month back or in the end of
>>  http://firsov.net/~suns/demos/dojo/FilteringTable_fillCell/dojo-base/dojo.js
>>
>>
>> Happy coding on file system!
>> Sasha
>>
>> Ross Thomas wrote:
>>    
>>> jezza wrote:
>>>
>>>      
>>>> I agree with you entirely with regards to IE7.  I have had nothing but
>>>> trouble since it was released.
>>>>
>>>>
>>>>        
>>> Heh!  Yeah.  Most of our clients have reverted to IE6 after various levels
>>> of
>>> frustration with IE7.  I keep recommending FF -- some have listened. :-)
>>>
>>>
>>>
>>>
>>>      
>>>> I think you are right about it being a permission thing.  The behaviour
>>>> seems to be the same regardless of whether I am using the patched version
>>>> or the original version.  To make matters more confusing, it now appears
>>>> to be working when I place the test file inside apache or tomcat and view
>>>> it using http:// ... renderusing.html but is not working when I try to
>>>> open it as a stand alone file ( e.g. c:\... renderusing.html in the
>>>> address bar).
>>>>
>>>>
>>>>        
>>> Oooo!  I remember a thread about 'file' URLs a month or two ago.  Same
>>> sort of problem.  Not sure if there was a resolution other than 'use a
>>> server'.
>>> I'll try a search and see if I can find it.
>>>
>>>
>>>
>>>
>>>      
>>>> This strikes me as rather odd, b/c running it inside a web application at
>>>> work today is where I first noticed the problem.  Unfortunately, I won't
>>>> be in again until Monday, so I won't be able to run the same tests until
>>>> then.
>>>>
>>>> Putting a try / catch block in the init function seemed to make no
>>>> difference, as I think it might be failing before it even gets to it.
>>>> Getting IE to break on error gives the following error message:
>>>> Error Line: 97
>>>> Char: 1
>>>> Error: Could not load 'dojo.widget.FilteringTable';last tried
>>>> '__package__.js
>>>> Code: 0
>>>> URL: file:///c:/temp/renderusing.html
>>>>
>>>> In light of that, it looks to me that dojo is not loading at all.  If that
>>>> is the case, I assume is a permission thing IE somewhere that needs to be
>>>> enabled.  Either way, there is not much you can do about it.
>>>>
>>>>
>>>>        
>>> You are right about the failure occuring before we even get to loading data.
>>> However, once we understand the problem, we may be able to provide a
>>> solution even though neither of us is a base developer.
>>>
>>>
>>>
>>>
>>>      
>>>> I will have another look on Monday at on the server where I first noticed
>>>> the issue.  If I come up with anything new, I will let you know.
>>>>
>>>>
>>>>        
>>> Cool.  I think a few others on the list would also be happy for a
>>> resolution.
>>>
>>>
>>>
>>>
>>>      
>>>> Thanks for pointing me in the right direction, and thanks again for
>>>> providing such a useful function.
>>>>
>>>>
>>>>        
>>> NP.  As usual the majority of all kudos go to Tom and the Dojo team for
>>> providing
>>> such a great environment to work in.
>>>
>>> Ross.
>>>
>>>      
>> _______________________________________________
>> FAQ: http://dojotoolkit.org/support/faq
>> Book: http://dojotoolkit.org/docs/book
>> Forums: http://dojotoolkit.org/forum
>> Dojo-interest@...
>> http://dojotoolkit.org/mailman/listinfo/dojo-interest
>>
>>    
> _______________________________________________
> FAQ: http://dojotoolkit.org/support/faq
> Book: http://dojotoolkit.org/docs/book
> Forums: http://dojotoolkit.org/forum
> Dojo-interest@...
> http://dojotoolkit.org/mailman/listinfo/dojo-interest
>
>  

_______________________________________________
FAQ: http://dojotoolkit.org/support/faq
Book: http://dojotoolkit.org/docs/book
Forums: http://dojotoolkit.org/forum
Dojo-interest@...
http://dojotoolkit.org/mailman/listinfo/dojo-interest

[Ross Thomas]

Quick update regarding these patches & the Dojo 0.4.3 release.

The latest posted FilteringTable render & null patches for 0.4.2 will
work unchanged with 0.4.3.

If anybody is actually using these patches please post here.  The 0.9
Grid widget will obsolete the FilteringTable (and therefore these patches)
and I would like to know whether to bother maintaining this patch-set
publicly.

Ross.