3 Oct 2007 11:14 AM #1
[2.0a1][CLOSED] feed viewer 3 from extjs.com
i am running with FF220.127.116.11 + win xp sp2 from australia.
when i run the same page from extjs.com with IE, it is fine.
when i run feed viewer 3 example from the local box with FF, it is fine.
i guess this is because of the speed of my internet connection??
BTW, extjs is awesome.
sorry, please refer to the attachment for the details.
3 Oct 2007 8:24 PM #2
3 Oct 2007 9:31 PM #3
3 Oct 2007 10:43 PM #4
4 Oct 2007 1:51 AM #5
i just purchased the Ext - Single Developer License and hope the others will support this project as well. to be honest, it is easy for jack to get another job with a stable income. please don't let him go...
4 Oct 2007 1:54 AM #6
Maybe some kind of network error occurs over the wire? I can't reproduce the issue.
Short of going to Australia, any ideas?Jack Slocum
Sencha Co-Founder, Ext JS Founder
Original author of Ext JS 1, 2 & 3.
7 May 2008 4:03 PM #7
Feed Viewer eample not working on local page
We are trying to run the feed viewer example on our local machine but it does not work. We have not done anying at all. Just downloaded extjs and tried to run Feed viewer example. Everything works except that when we click on My feeds in the left pane it does not populate the right pane.
7 May 2008 10:28 PM #8
9 May 2008 11:46 AM #9
I'm closing this thread. @berrett, in the future, please post questions like this as a new thread in the help forum as your starting point. Also, if you feel you have found a bug, it's better to start a new thread rather than reopening one that's not directly related to your issue.
16 Jun 2008 10:27 AM #10
My problem turned out to be what mystix suggested...the lack of a PHP-enabled web server. That dependency is a little surprising, at least to me. What I would have liked to see on this thread is an explanation of why it is needed. The answer I found out eventually is summarized here:
"The one BIG limitation with browsers and AJAX is that, in general, the AJAX requests must be to the same server that server the original HTML document." [...] "That means that if you want to use additional content that is not served by your own web server, you have a problem. Invoking a remote WebService to return the weather conditions, getting an RSS-feed with headlines, scraping HTML content from another website: it will not fly." [...] "So what can you do if you really want to use content from other origins - which is quite likely by the way? Basically there seem to be a few options, some of which are limited to specific browsers:" [...] "Use a proxy do make the requests for you: if you cannot make the AJAX requests to remote sites because all requests have to go to the orginal site that served the HTML document, than we should make our AJAX request to that server, to a proxy component that reroutes the request to where we want it to go and returns the results to us in the client!"
Someone unfamiliar with the arcane magic of web browser programming might ask how this could be the case, given the paging.js example. It seems to work just fine retrieving data off of a remote feed:
It is clear that the people working on extjs know a lot and are doing very cutting-edge work. But these details are far from obvious to Ajax n00bs like myself. I'm not saying these things *can't* be figured out by someone who's willing to do a little legwork (took me a couple hours), but it would seem to me that a comment or two to this effect in the source would save people hours of time...
For starters, I'd propose that the RSS Feed demo should have some kind of alert that says 'requires PHP-enabled web server'...similar to how the Task Management demo says 'requires Google Gears'. Then I would link to a short explanation of why the dependency is necessary.