Hi,
My name is John Cody and I am a windows mobile developer. I recently released a neat little utility called "John Cody's SkweezeIt!" that allows users to automatically filter a URL through skweezer.net so it will load quicker and be better formatted for their devices' smaller screen:
http://www.omnisoft.com/forums/forum_posts.asp?TID=669&PN=1&TPN=1
As you know, many stories displayed in mDigger have links in the story (especially the "Read More") that point to webpages that are designed for full-sized (desktop) browsers and can take forever to load in a mobile browser :(
It appears that when a mDigger user selects one of these links, your mDigger app is hard-wired to *only* launch "iexplore.exe" (on windows mobile devices) to display those pages. This "hard-wired" method of launching the browser exe file instead of launching it using "association", prevents my "Skweezeit!" app from intercepting the URL request and allowing the user to filter it through skweezer.net.
Being a programmer myself, I'm guessing that you are using the "CreateProcess" API to launch iexplore.exe app with the desired URL as the parameter.
May I suggest that you instead use one of the following methods to launch the "default" browser to the desired URL:
· ShellExecuteEx "http://www.the-url.com" (non-managed/Win32 method)
· System.Diagnostics.Process.Start("http://www.the-url.com", Params) (managed method)
Using either of the above methods will launch the default application assigned to handle "HTTP" URL types (i.e default browser), and will allow my skweezeit app to intercept the launch and allow the user to filter it through skweezer.net.
I am only suggesting this because I bet most of your users aren't clicking on any of those external links because they know how painful it will be to load those pages into their browser. My suggestion will instead make it pleasant experience to do so.
Thanks for your consideration.
-John Cody