The impact on IE7 on DX Widgets

Prepare your RSS widgets!

from WinCustomize Forums
DesktopX Developers and users beware - IE7 may well cause some DesktopX widgets to fail because of it's new functionality.

That's not to say that all will be affected by this, but many of the widgets relying on RSS feeds for their data may struggle. The issue is that IE7 kindly interprets RSS feeds and displays the data in a more visually friendly format. While this is to be applauded, it does have implications.

Where a DesktopX widget uses a Web Browser control to load RSS data, and subsequently interprets it, things may fail to work. Both the InnerText and InnerHTML content of the page will be different because of the new interpretation of content, hence tags and content that a widget may search for could cease to work.

The safest solution will be for developers to start using the XMLHTTP object to load and manipulate XML feeds if they use them ... though I'm open to better ideas.

As an appeal to users, please don't expect developers to update object to do this. I know personally that I won't have the time to do this, even with the best will in the world, and other developers may be in the same boat.
desktopx
13,073 views 19 replies
Reply #1 from WinCustomize Forums Top
Thanks for the heads up. Hopefully most of the users will understand and be patient with the developers who choose to update their widgets, and learn to deal that most of the developers will be too busy to even think about it.
Reply #2 from WinCustomize Forums Top
Thanks for the info Martin.
Galactic Civilizations III
Reply #3 from WinCustomize Forums Top
That's a shame.

Lately, everytime I update my computer, a widget stops working.

Now with the new IE, your telling me the RSS feed widgets won't work too?
*sigh*

That sucks LOL When will their be a standard RSS reader that people can copy and use be available? When IE7 comes out I guess, right?
Reply #4 from WinCustomize Forums Top
What about using CreateObject("Microsoft.XMLDOM") to parse the RSS feed? They you wouldn't be relying on IE.
Reply #5 from WinCustomize Forums Top
Thomassen,

XMLDOM is a valid solution, however, for the "average" developer, the XMLHTTP object returns a string that is easy to manipulate using standard VBScript like Left, Right, Len and InStr. From memory use of the XMLDOM object requires far more use of the object model.
Reply #6 from WinCustomize Forums Top
One word-- Opera

(Not that I've become prejudiced over the last week...)
Reply #7 from WinCustomize Forums Top
What does Opera have to do with RSS widgets?
Reply #8 from WinCustomize Forums Top
aimzzz - the only browsing capability that a developer can guarantee is on a users machine is IE. This means that users cannot develop based on something that not everyone has.
Reply #9 from WinCustomize Forums Top
Oh Thomassen,
I do have some Functions that I have been working on that will remove the need for users to master the XMLDOM model so I will release these some time shortly. These will allow things like GetXMLfromXML, GetTextFromXML, GetAttribute etc etc
Reply #10 from WinCustomize Forums Top
Good thing I built my RSS reader using XMLHTTP right from the start... saves me a lengthly re-write.
Reply #11 from WinCustomize Forums Top
Martin, is that your own functions you have put together?
Reply #12 from WinCustomize Forums Top
Yes - all nice and user friendly
Reply #13 from WinCustomize Forums Top
CerebroJD,

The only issue with the XMLHTTP object from memory is that you need to force the rest of DX to pause while the page loads. This isn't an issue with most modern connections, but as someone who was recently migrated from dial up it was a problem.
Reply #14 from WinCustomize Forums Top
Doesn't XMLHTTP give any notification when the data is done loading?
Or give any info on it's status. If it does you can make a script in a separate thread to loop until it's done loading. Then it'd notify the main script when it was done. Now, I'm not sure if you can call a different script when one is running in a separate thread... If that's the case it could possibly be worked around by changing the state of the main script (that would be possible , right). And then the main script could react to the statechange.

mm.... wait... then how would you tranfer the data from the looping script...? doh!
...perhaps I'm complicating things a bit here....
Reply #15 from WinCustomize Forums Top
Yes, you can do a loop to check status, but that's not particularly efficient way of doing things. I think I may be able to purely use XMLDOM and avoid this.
Reply #16 from WinCustomize Forums Top
Martin- I understand- just being obnoxious
Reply #17 from WinCustomize Forums Top
I'd be highly surprised if there isn't a way to turn that off. If there really isn't, report it as a bug!
Reply #19 from WinCustomize Forums Top
Turn what off Green,the waiting until the page has loaded? If so then yes, you can do that, but it's not as easy then to perform actions on the page contents immediately.