- Parse downloaded file and get some additional information out of headers
- and parsed data - title, for example. Or redirects using <META HTTP-Equiv>.
- (Partially done - now extracting title).
+Get and store icon.
- Documentation.
+Cleanup HTML before parsing using BeautifulSoap or Tidy.
+Parse (or interpret) downloaded file and get javascript redirects.
- Merge "writers" to storage managers.
- New storage managers: shelve, SQL, ZODB, MetaKit.
- Robots (URL checkers): threading, asyncore-based.
- Aliases in bookmarks.html.
+More and better documentation.
- Configuration file for configuring defaults - global defaults for the system
- and local defaults for subsystems.
+Merge "writers" to storage managers.
+New storage managers: shelve, SQL, ZODB, MetaKit.
+More robots (URL checkers): threading, asyncore-based.
- Ruleset-based mechanisms to filter out what types of URLs to check: checking
- based on URL schema, host, port, path, filename, extension, etc.
+Configuration file to configure defaults - global defaults for the system
+and local defaults for subsystems.
- Detailed reports on robot run - what's old, what's new, what was moved,
- errors, etc.
- WWW-interface to the report.
+Ruleset-based mechanisms to filter out what types of URLs to check: checking
+based on URL schema, host, port, path, filename, extension, etc.
- Bigger database. Multiuser database. Robot should operate on a part of
- the DB.
- WWW-interface to the database. User will import/export/edit bookmarks,
- schedule robot run, etc.
+Detailed reports on robot run - what's old, what's new, what has been moved,
+errors, etc.
+WWW-interface to the report.
+
+Bigger database. Multiuser database. Robot should operates on a part of
+the DB.
+WWW-interface to the database. User should import/export/edit bookmarks,
+schedule robot run, etc.