To Do List

Apart from fixing serious bugs there are some thoughts of future enhancements, like:

• Recognition and supprot for more logbook formats (other than ADIF)
• Re-design of the Applet window (by separating the option and preview area into two different windows) in order to reduce its size which is causing problems when displayed in low screen resolutions. SV1BSX suggests to break the window into two steps, one concerning the main applet options (logbooks and bands) and when finished with them to move in the second step concerning the rest of the parameters (mainly display options) together with the applet previewing and generation.
• Full merge of the database building part with the applet creation part of the software. This might make things much simpler (e.g. no separate .jls and .apl files - all user options saved in a single file) and easier to manage and work with. This requires re-design of the whole software but it's a good reason to move jsLogSearch into version 4.0 (probably using AJAX technology for making everything more robust).
• Optional display of the callsign in the exact searche results. At the moment this is possible only if the user manually selects the callsign field to be incuded in the database which makes the actual database larger by the repeated data (the callsign info is automatically included in the database).
• Display of a logo with appropriate link under the applet's search form instead of the simple small font hyperlink that exists which is almost unreadable as reported by some (thanks SV1BSX for suggesting).
• Implementation of floating table column titles (during table scrolling). This is a well-known problem that all browsers have when displaying long tables (the column titles shoot-off the top of the screen as you scroll down the table) and as jsLogSearch uses tables for the display of the search results, it suffers from this problem under certain conditions i.e. when the search results don't fit in a single page. There have been various suggestions for dealing with this problem and I am at the stage of finding the best suitable way to handle it for the jsLogSearch purposes. Future web browsers promise a definite solution for this problem.
• Incremental logbook uploading (uploading only new QSOs) {requires techniques that are mainly supported by data base servers and I don't believe that I will ever try it to implemented - anyway it's a good idea (thanks G4IRN for suggesting)}

Last Page Update: 27 Jan 2007 by Vagelis