Development to-do list #2

Here we go again, then. I won’t get through all of these this weekend but I’ll make a start…

For the Firefox add-on, do nothing if trying to toggle back to an original URL that doesn’t start “http”. This can happen if, for example, you’d typed “” on the Textise home page. Textise can deal with this sort of abbreviated URL and, in fact, so can Firefox, but for some reason it doesn’t like using an incomplete URL as a location.href.

Change the copyright to extend to 2011 (on home page).

Check and, if necessary, fix the HTTP method when coming back from the Options page. I have a suspicion that POST is used, which was originally how Textise worked. However, I’ve since changed to GET so that bookmarking is possible (i.e. the URL contains all the necessary info, including the URL of the page you’re trying to Textise).

Have a look at the code to remove images. I’ve seen a couple of Out Of Memory exception (on the Kindle, as it happens) that refer to that part of the code.

Double-check the release status of the published code – shouldn’t be DEBUG!

Have a think about removing the actual .NET error description from error messages. The error message could simply ask the user to report the URL they tried to Textise, not cut and paste the whole thing. This might make Textise seem a bit more pro (!). I might still like to see the errors, of course, just in case I can’t replicate them, so I’m also wondering about creating an error RSS feed that I can subscribe to…

Fix internal bookmarks (e.g. “<div id=’mainContent’>”. At the moment, Textise reduces these to just “<div>” because sometimes they also contain formatting. If I could keep just the bookmark info (the “id=” bit) it would really help with sites that have reams of links at the top of each page. Might slow the program down somewhat, though, as it’s another trawl through the whole page.


One response to “Development to-do list #2

  1. Done today:

    Copyright years corrected (quite a technical challenge!).
    Internal bookmarks retained. Textise does what it can but most web sites are quite flaky in this area. I’m a little concerned that the new code slows down response times a bit too much so I might make this optional.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s