G8PUT Logbook Project Wish List
These are things that have been asked to include in future releases.
How long they will take depends on how difficult they prove to be,
how many people ask for them and which I choose to do first.

Requested Feature Comments

More flexible import and export facilities. I'm working on ADIF import at the moment. The problem I have found is that there are so many standards. What I am providing is a system that will show all the columns you have in the G8PUT logbook, and all the columns that are in the ADIF file, then you will be able to move them to the correct place.
This function should prove useful for importing from various other sytems.
Importing from WAB trackers in nearly complete. I've found a number of differences in the way they were being used, but I think the system should soon be able to deal with them.
If there are any particular systems you would like to be able to import and/or export data to and from, please let me know.

Drag function. It means program could allow move of the position any field if user drage it. Drag and Drop is now included in the ADIF import facility that I'm working on at the moment. I expect to be able to add it easily to the Column Setup within the Administration screen. Changing the order of the columns 'live' has more implications that I need to think about......

Choosing if the date / time of QSO's should be automatic, for normal operation or manual for entering previous QSO's I should be able to arrange a 'switch' on the administration screen to choose between the two. Should be done soon.

Choosing the colours the program uses. This is done and will be in the next release.

QSO Record Number This function might be easily be added, however additional named columns present a little bit of a problem as I have no way of knowing what columns have been set up by users, and which of the 50 columns available have been used.
The answer may be to allow the user to allocate functions like this to a particular column of their choice in the column set up screen. Therefore it would be available in the SILVER and GOLD versions.

Add e-mail field, sex field (OM and YL. OM by default) These and any other fields can now be added by the user with silver registration and above. Values can be set to copy down automatically to the next QSO.
I am unlikely to add further fields with default values, though it is not impossible.

Plan Band/Mode. When user enter frequency, then program auto set the band and mode, as follow: if user enter 14,014, then program auto set data in band field as 20 meters and CW as mode, and so on for each band or part of the band. This should not be too difficult. I think it could be selected as a choice in the administration screen.

Colour column field. It means user can choose any colour for the name of each column I have been asked for options to change the colours. It may happen in the future.

Multicriteria search function. It means program would allow make search for many fields to the same time. The next release includes the option to search columns by name or 'ALL'.

Sound recorder or graber built in. It could allow record qsos, phrases (good for contest) using the sound card of the computer; There's no reason why not. I have some good text to speech functions from other programs I have written, this should consist of a number of relatively simple routines making a good set of features.

3D Maps. For show both stations connected. This should not be too difficult when some of the other features are done.

Scanner QSL cards built in. It could allow scan both side of any qsl associated to any contact previously saved. A nice feature, the existing database structure should be able to accommodate it. Perhaps I need to consider increasing the number of available columns from 50.

Club Database. It will a small database with the following fields: a) # field; b) Member Name; c) Address; d) Born date; e)Phone; f) Call; g) Previous call; h) Date and i) Comments or Remark field. Program would allow make search for any field or fields combinations. This sounds like a request for an additional database. There is no reason why this can't be done. However, I am currently looking into combining the two existing MDB files into one, then there could be links to other databases. The user front end for configuring these could easily become overly complicated. I will think about it.

Silent Key Database. It will a small database for know all ham passed away. Fields: Name, call, Qth, Date and Comments. This small database would allow make search for any field or fields combinations also. I'm not sure where I would get this information from?

Separate for a colour bar each time date change (table showing qsos saved) Colour changes have proved problematical in the past. The administration can be very complicated to achieve simple and rarely used options.
Stopping users from changing the text and the background to the same colour on the administration screen for example.

Talking qso cluster with female or male voice. Users would choose voice. I welcome ideas from anyone who might offer suggestions what this might look like and what it should do.

Talk name of the fields (good for blind hams). It means user will "hear" a male or female voice in the enter data function, each time user enter to any field. Sound like: "call", "name", "qth", "frequency", "mode", "band", "comments" and so on. See how do it ACLOG Speech is not difficult to add, I already have a range of functions from other programs.

Program will show all time (user can hide or unhide box) amount of qsos saved and amount of qsos confirmed. This should be quite simple.

Table show countries worked or confirmed by band and mode This should not be difficult, the display would need to be meaningful.

Graphic statisics by mode, by band, confirmed, worked, waiting qsl, and so on. This should not be too time consuming at some time in the future

DIGITAL MODES BUILT IN. It allow users work rtty, sstv and anothers digital modes. These would be going well beyond the original scope of the project, but it could well happen in the future.

Requested Feature	Comments
More flexible import and export facilities.	I'm working on ADIF import at the moment. The problem I have found is that there are so many standards. What I am providing is a system that will show all the columns you have in the G8PUT logbook, and all the columns that are in the ADIF file, then you will be able to move them to the correct place. This function should prove useful for importing from various other sytems. Importing from WAB trackers in nearly complete. I've found a number of differences in the way they were being used, but I think the system should soon be able to deal with them. If there are any particular systems you would like to be able to import and/or export data to and from, please let me know.
Drag function. It means program could allow move of the position any field if user drage it.	Drag and Drop is now included in the ADIF import facility that I'm working on at the moment. I expect to be able to add it easily to the Column Setup within the Administration screen. Changing the order of the columns 'live' has more implications that I need to think about......
Choosing if the date / time of QSO's should be automatic, for normal operation or manual for entering previous QSO's	I should be able to arrange a 'switch' on the administration screen to choose between the two. Should be done soon.
Choosing the colours the program uses.	This is done and will be in the next release.
QSO Record Number	This function might be easily be added, however additional named columns present a little bit of a problem as I have no way of knowing what columns have been set up by users, and which of the 50 columns available have been used. The answer may be to allow the user to allocate functions like this to a particular column of their choice in the column set up screen. Therefore it would be available in the SILVER and GOLD versions.
Add e-mail field, sex field (OM and YL. OM by default)	These and any other fields can now be added by the user with silver registration and above. Values can be set to copy down automatically to the next QSO. I am unlikely to add further fields with default values, though it is not impossible.
Plan Band/Mode. When user enter frequency, then program auto set the band and mode, as follow: if user enter 14,014, then program auto set data in band field as 20 meters and CW as mode, and so on for each band or part of the band.	This should not be too difficult. I think it could be selected as a choice in the administration screen.
Colour column field. It means user can choose any colour for the name of each column	I have been asked for options to change the colours. It may happen in the future.
Multicriteria search function. It means program would allow make search for many fields to the same time.	The next release includes the option to search columns by name or 'ALL'.
Sound recorder or graber built in. It could allow record qsos, phrases (good for contest) using the sound card of the computer;	There's no reason why not. I have some good text to speech functions from other programs I have written, this should consist of a number of relatively simple routines making a good set of features.
3D Maps. For show both stations connected.	This should not be too difficult when some of the other features are done.
Scanner QSL cards built in. It could allow scan both side of any qsl associated to any contact previously saved.	A nice feature, the existing database structure should be able to accommodate it. Perhaps I need to consider increasing the number of available columns from 50.
Club Database. It will a small database with the following fields: a) # field; b) Member Name; c) Address; d) Born date; e)Phone; f) Call; g) Previous call; h) Date and i) Comments or Remark field. Program would allow make search for any field or fields combinations.	This sounds like a request for an additional database. There is no reason why this can't be done. However, I am currently looking into combining the two existing MDB files into one, then there could be links to other databases. The user front end for configuring these could easily become overly complicated. I will think about it.
Silent Key Database. It will a small database for know all ham passed away. Fields: Name, call, Qth, Date and Comments. This small database would allow make search for any field or fields combinations also.	I'm not sure where I would get this information from?
Separate for a colour bar each time date change (table showing qsos saved)	Colour changes have proved problematical in the past. The administration can be very complicated to achieve simple and rarely used options. Stopping users from changing the text and the background to the same colour on the administration screen for example.
Talking qso cluster with female or male voice. Users would choose voice.	I welcome ideas from anyone who might offer suggestions what this might look like and what it should do.
Talk name of the fields (good for blind hams). It means user will "hear" a male or female voice in the enter data function, each time user enter to any field. Sound like: "call", "name", "qth", "frequency", "mode", "band", "comments" and so on. See how do it ACLOG	Speech is not difficult to add, I already have a range of functions from other programs.
Program will show all time (user can hide or unhide box) amount of qsos saved and amount of qsos confirmed.	This should be quite simple.
Table show countries worked or confirmed by band and mode	This should not be difficult, the display would need to be meaningful.
Graphic statisics by mode, by band, confirmed, worked, waiting qsl, and so on.	This should not be too time consuming at some time in the future
DIGITAL MODES BUILT IN. It allow users work rtty, sstv and anothers digital modes.	These would be going well beyond the original scope of the project, but it could well happen in the future.