It seems that, globally, HbA1c will be changing how it is reported: the current % units will change to mmol/mol. In the UK this will start in June 2009 with dual use of mmol/mol and %; In 2011 the use of % will be phased out. More information is available in these links.
i. http://www.acb.org.uk/docs/hba1clabprofessional.pdf
ii. http://www.pubmedcentral.nih.gov/articlerender.fcgi?artid=2282401

Changes:

• Updated: HbA1c graph report now supports mmol/mol units. If the reporting period inlcudes HbA1c values above 15.0 these are assumed to be mmol/mol and the graph switches to these units: any values found below this will be converted to mmol/mol, hovering the mouse over the graph will show the original value. If no values are above 15.0 the original % units are used.
• Updated: The default HbA1c standardisation scheme for current % values is set to the US NGSP. Published research papers indicate two other standardisation schemes: Japan's JDS/JSCC; Sweden's. Support for converting to mmol/mol from these three schemes is included. To switch schemes one of the following commands must be run in the Terminal.app:
  • defaults write com.Nesfield.DiabetesLogbookX HbA1cStandard NGSP
  • defaults write com.Nesfield.DiabetesLogbookX HbA1cStandard JDS/JSCC
  • defaults write com.Nesfield.DiabetesLogbookX HbA1cStandard Swedish
• Updated: HbA1c fields no longer include number formating with %.
• Fixed: Corrected a bug caused all imported events to be set to the current month.

Available clicking here.

Changes:

• Updated: Now supports Note templates for user created Event types: when creating an Event type enter the event name and then use '{&&}' to indicate that all text after it is the Note template, and use '{lf}' to start a newline.

• Updated: Average Medication Summary report now inlcudes the number of doses occurring in each period.

• Fixed: Corrected detailed and summary reports to show all recorded insulin and medicine events for a given date and timestamp. Previously, when two or more events with the same date and timestamp had insulin/medicine records only the last instance of each would be displayed in the report. Now these multiple events are displayed as one event in these reports.
• Fixed: Average Medication Summary report to include all insulin and medicines events, even those without blood glucose tests. Also fixed to include multiple events for the same date and timestamp.

Available clicking here.

• Added: Importing CSV data files now supports direct import from a web URL. Currently tested using HanDBase for iPhone.
  
• Updated: PDA import file format:
  • 12-hr format times in the PDA import file format now supports uppercase AM/PM as well as lowercase am/pm.
    
  • Added extra filters when process text for Period, Units, Inhalers, Medicines, Breath, Health and Event. If these are "NO VALUE" or start with "--" it is assumed that the field value is to be ignore. Extra string keys in the localisation files have been added for easy definition of new exclusion strings.
• Fixed: Corrected minor display bug in logbook reports for periods where no Peak Flows have been recorded.

An additional example iPhone HanDBase database, in English, has been added to the download pack to demonstrate how to setup Popup fields for: Period, Units etc. These fields use a 'null' default value such as "-- default time period --". During import, when the leading "--" is detected the field is seen as "". Some fields when they are "" will then get a default value assigned from the Mac Logbook.

With the release of Version 1.5.1 it is now possible to import CSV data direct from a web URL. So how does it work?

Here I'll walk through downloading a CSV file from HanDBase on the iPhone.

There are example HanDBase database templates available on the downloads page. Use HanDBase's Desktop Connect feature to uploaded to the iPhone.

To make is as easy as possible to connect to the iPhone it is best if the IP address is always the same. To do this you must have access to your network and be able to configure static IP address assignments. On the Airport base stations this is possible using the Internet settings in Airport Utility: Select the DHCP tab and add a DHCP Reservation for you iPhone. The reservation needs the MAC address [format 00:xx:xx:xx:xx:xx] of the iPhone's network interface: this information is available via the iPhone Settings in the About screen's Wi-Fi Address field.

We first need to find the URL of the CSV file: launch HanDBase on the iPhone and open Desktop Connect. This starts the built-in web server and displays the URL to use in your browser: in this case it is http://192.168.1.119:8080 .

Now browse to the web server using the URL and {ctrl}-click the C,S,V icon of the Logbook X database. Choose 'Copy Link' to get the URL of the CSV file: in this case it copies the URL "http://192.168.1.119:8080/export.csv?db=Diabetes_Longbook_X.PDB"

OK, so we now have the URL. Now we need to do something with it. Open up the Mac Logbook and click 'Import' to display the Data Import window. Then select the second Data Source:

If you haven't been recording fields that have default values click the relevant import checkboxes, and select whether to import 'All events' or just those dated after the last imported event. Now click 'Select file and Inspect Data' to enter the URL where the download file is located. Paste in the copied URL from the web site then click 'OK':

The URL will be checked for availability and the page's contents will be read into the Logbook ready for processing: during this time the progress indicator will display a 'barbers pole' to show that it is working.

The import will now continue exactly as if a file had been selected from the Mac's filesystem and the event data will be extracted and displayed before asking whether to complete the import or cancel it.

The default function during importing data files has been to ignore any value entered into the time period data field. The time period is then calculated using the imported event's time data and the Logbook's User Settings for start and end periods.

In version 1.5.1 an additional method has been added: import the data file's time periods, if they exist, and only calculate them if they do not. It option is not directly available from within the User Settings or Import window preferences, rather it is a 'hidden' option requiring a UNIX command to be run in Apple's Terminal.app.

To enable this new way of importing time period data open the Terminal.app type in the following command and then press the {return} key:

defaults write com.Nesfield.DiabetesLogbookX ImportTimePeriods YES

If you want to return to the normal way and ignore time periods during import and let the Logbook work them out, do the same as before but use this command:

defaults write com.Nesfield.DiabetesLogbookX ImportTimePeriods NO

This option is kept hidden as it is fairly important that the time period names are kept consistent and mis-typing them in handmade CSV files can cause additional periods to appear, such as:

Night may become NIGHT or night. That would be three time periods.

Having extra unwanted time periods would also impact the layout of the reports with them squashing the data into thin columns.

• Fixed: Added a database save after importing events, ready for creating reports.
• Update: Minor adjustment to improve importing of CSV files from mobile database apps. Now supports CSV format where selected fields are enclosed with double-quotes.

A small fix has been added to the current release. Previously after importing data the database was immediately saved, which resulted that any reports would not 'see' the new data until an event Add/Edit/Delete or the Save Settings button was clicked.

See the online User Guide (Technical notes, Mobile DB data imports) for full information on the import file format and the support for localised date, time and float data types. Also, how to use HanDBase on the iPhone to record events on the move.

I've created set of database files, one per supported language: English, French, German, Italian and Spanish.

The database file can by used by HanDBase Database Manager for iPhone (and other mobile devices) to record all the information that the Logbook does on the Mac. Uploading the database file is done through a built-in web server in the HanDBase app.

Data is retrieved again through the web server, and can be downloaded as a CSV file. The file can be imported straight away into the Logbook.

If anyone has HanDBase then you may want to give these as try.

A quick follow-up on the iPhone app support question.

Having already coded the Logbook to import from some Palm OS general database apps I decided to see what was available for the iPhone [and I also mean iPod touch when I say iPhone]. HanDBase is a long-time Palm OS DB manager application and has now been migrated to the iPhone, as it was a name I knew and supports the data types I need I decided to pay-up and try it out. The iPhone app is $9.99 (£5.99) and, if you need it, the HanDBase desktop app is $9.99.

Having created a database, with pop-up lists and a few different views, I found that its built-in web server was an easy way to export CSV files of the data, and that these were ready to be imported by the Mac Logbook. Further investigation revealed that this wasn’t a 100% successful solution, as while my UK format iPod works other iPhones with different region settings may not.

My iPod touch is setup with UK format date, times and decimal mark so the default HanDBase export format is handled by Logbook X. However, other iPhone region settings change the decimal mark to a {comma} and the HanDBase surrounds any exported field data with {quote} characters: “12,5”. These region settings may also use {comma} in the time format too.

The current (v1.4.9) import rules for {comma} delimited files include:

Dates

• D/M/Y
• M/D/Y
• D.M.Y
• M.D.Y
• D-M-Y
• M-D-Y

The date's year may be either 2 or 4 digits long, for example 07 or 2007.

Times

• HH:MM
• HH:MM am/pm
• HH.MM
• HH.MM am/pm

Time formats with {comma} separation are only supported when {tab} delimiting is used:

• HH,MM
• HH,MM am/pm

24hr time is 00:00 to 23:59.

The time format from HandDBase includes seconds. The import into Logbook X handles this format and strips off the seconds.

Numbers

• Floating point format with a period, ".", as the decimal mark.

Examples of permitted values: 12.5 ; 0.05 ; 1.0

The current version of Logbook X doesn’t fully handle interpreting "12,5" style number fields during import, yet. Though I have a fix being tested that it seems to resolve this.

So, as of now, HanDBase can be used to record event data and it can then be imported as follows:

• In regions where "." is used as the decimal mark the exported CVS file can be imported directly into Logbook X.
  
• In regions that use "," as the decimal mark:
  • The HanDBase Desktop application can be used to open a downloaded copy of the database (use the built-in web server to get the copy). Then export the data as a {comma} delimited file, include a header row, and selected to enclose all fields in {quote}.
  • Alternatively, use a text editor to edit the exported CSV file from the iPhone and make sure that every field is enclosed by {quote}, even fields with empty data. Or use a text editor to edit the exported CSV file from the iPhone and make sure that no fields are enclosed by {quote}.

The current Logbook X code will strip {quote} characters but it is rather strict and looks for either {quote}{comma}{quote} or {quote}{tab}{quote}. Changing this, using the mentioned fix, to be less strict fixes the problem.

Anyway, that is where I've got to. I hope to test further, but in the meantime if anyone wants a beta version of Logbook X and/or the HandBase database template file just use the Support form to contact me.

There are other database apps available, but I picked HanDBase first because the online documentation and supporting information indicated it could do the job. I didn't want to buy three or four apps only to find that they don't export data easily or that the database template file cannot be shared with others. I also tested the database template file, created on the iPod, on a trial version of the Palm OS app and it worked. I also see that HanDBase has database apps for other mobile devices too.

Recently, I’ve been asked many times about an iPhone app and direct download from meters. So here is the current situation ...

I thought about developing an iPhone app but decided against it for a number of reasons, most of them based around two points:

1. I believe that to fully support any application I write we need to be a regular users too. I have an iPod touch but it’s my wife that would be using a mobile app, and she is happy with her phone.
2. There are quite a number of iPhone logbook app appearing now, so why not import data from them.

So, I’ve purchased/downloaded a few iPhone logbook apps that say they have export functionality and I’m now looking at which ones export data that can be imported easily (CSV file, saved email text) using the same principles that are already used to support the various Palm OS apps. Another alternative app type is a general database app.

I haven’t started work on coding support for these just yet, as I thought that most needed a while to stabilise, especially in the data export areas. However, I will definitely be working on this feature and have contacted a couple of the app developers.

Onto direct meter download: the situation is still the same as when I last wrote about this subject (see here). I did looked at it again, briefly, but don’t expect this to happen. Sorry if that isn’t the answer you want to hear. Again the reason is that we won’t use the feature since we would have to edit every entry to add more data anyway, and I still haven’t worked out how to code it.

Changes:

• Added: New report added showing a summary of average insulin/medicine doses by time period and by day. The new report is visible in the all reports (except Notes) when Insulin and/or Medicine data is selected for inclusion in the report.
• Fixed: Localisation files may not have shown 'accented' characters correctly in the generated reports when shown in the Reports window [saved reports display correctly in Safari].

A new upload of v1.4.8 has been posted in the Downloads area.

This corrects a minor (but annoying) display bug in the main logbook window of the English version: in moving from Xcode v2 to v3 the decimal number formatting on Mac OS X 10.4 (Tiger) got mixed and used a comma instead of a period.

Update (17:25 BST): Yet another Xcode v3 bug with the User Settings drawer not opening. That’s now fixed too.

Changes:

• Corrects the summary graph layout due to changes in Web Kit (i.e. Safari 3).
• Add Spanish localisation.

Before using the software and when migrating to a localised language version, please read the User Guide.

1. Leopard compatibility fixes:
   • Fixed Add Event bug caused by Applescript changes.
     
   • Fixed selecting From/To date range when system localised date formats have been customised. Bug caused by Applescript changes.
     
   • Addressed minor display issue in the Event panel caused by font changes.
2. Updated: extended insulin and medicine entry (fields A, B, and C) to support values with a precision of 0.01 units, as requested by pump users.
   
3. Updated: daily auto-backup of the data to ~/Documents/Diabetes Logbook X/Backup now retains an archive of the previous data file if it is bigger than the current data file.
   
4. Updated: improved data import flexibility to handle text files created by JPilot-DB, a freeware Java desktop application that is a companion of the freeware Palm OS Pilot-DB database application. [Example Palm OS Pilot-DB, databases for recording logbook events while away from the Mac, are available for download from the website.]

Here is a a beta release of the Logbook that fixes an issue that arises from Leopard's removal of support for setting a red/amber/green progress bar's maximum and minimum values using normal Applescript commands.

For those interested in Applescript and controling NSLevelIndicator elements in Xcode projects. This Applescript, that worked in Tiger:

    tell window "myWindow"
        set maximum value of control "myNSLevelIndicator" to 22
        set minimum value of control "myNSLevelIndicator" to 0
    end tell

Now needs to be replaced with this in Leopard:

    tell window "myWindow"
        call method "setMaxValue:" of control "myNSLevelIndicator" with parameters {22}
        call method "setMinValue:" of control "myNSLevelIndicator" with parameters {0}
    end tell

I haven't seen this discussed anywhere yet.

One further bug that I haven't been able to address yet occurs if you have set a custom date format in System Preferences: most of you won't have done this so don't worry.

If you have and you experience the 'From' date in the Reports date selector providing an unexpected start date then you will need to reset back to the default date format within System Preferences -> International -> Formats: the easiest way is to select another Region and then reselect your own Region again. I hope to fix this soon.

I have raised both these bugs with Apple.

At present I have an installation of Leopard on an external drive for testing purposes, but I am holding off migrating my Mini until early-adopter issues are fixed by Apple: hopefully in 10.5.1. Until then, this is how I've installed Leopard at present.

1. Reports: Added Y-axis scale to the glucose graphs.
   
2. Reports: Added average glucose value into the legend of the glucose scatter graph.
   
3. Reports: Cleaned up detailed and summary reports to omit empty events in some filtered situations.
   
4. Reports: Improved the ordering of time periods that have been manually changed and overlap other periods.
   
5. Events: Updated the Notes template for Clinic events.
   
6. Importing Data: Glucose, Insulin A, Insulin B and Medicine fields that are empty or numerically equivalent to 0 will be felt empty and their associated units/name data filed will be empty too.
   
7. Localisation: Improved Italian built-in help.
   
8. Fixed: Glucose target and critical values being empty created an error, a field will now be reset to a default value if editing leaves it empty.

1. Updated date and time handling routines for importing from Palm OS apps Logbbook DM and UTS Diabetes: supports Palm OS data formats.
   
2. Improved data import flexibility: specifically for PDA database export files (tested with Palm OS apps MobileDB v4 and JFile v5 and Möötjelitt's MPC).
   
3. Minor bug fixes and localisation support changes.

I'm pleased to announce the initial release of Asthma Logbook X.

Based on Diabetes Logbook X, this new application aims to help track asthma related data, and manage supplies, appointments, and medical contacts.

The application is free, but if you want to make a contribution, then a donation to the registered UK charity Diabetes UK is very much appreciated. Why diabetes and not asthma? My son has diabetes Type 1 and I would like him to have life without injecting every day; I have asthma and I live with it, as it is not severe.

The logbook is based on my limited knowledge of asthma management.

1. Added support for creating and updating the Contacts' details in Address Book.
   
2. Updated and expanded built-in help [English & French]: now uses Help Viewer.
   
3. Updated graph reports:
   • Added Body Mass Index (BMI) to graph reports.
     
   • Scatter graph based reports now load faster and take less disk space
     
   • Thickness of critial/target/average indicator lines are reduced.
4. Updated detailed and summary reports:
   • Carbs and health data is now shown in a separate column to insulin and medicines.
     
   • New option to not show insulins in the report.
     
   • Insulins and medicines column is only shown if they have been selected for display in Report Settings.
     
   • Carbs and health column is only shown if they have been selected for display in Report Settings.
     
   • Added BMI to list of displayed health data.
5. Updated all reports:
   • Most unicode (UTF-8) characters should now be displayed correctly.
     
   • Added error correction for dates older than 01/01/1970.
6. Adding/editing events: a lower date limit has been set to 01/01/1970.
   
7. Added md5 checksum test on reporting script before running the script.
   
8. Fixed bug: export files saved using a system number format that does not use '.' as the decimal mark may not have been handled correctly during import:
   • All new export files will be forced to save with a '.' decimal mark.
     
   • All numbers are padded with a preceding '0' where necessary.
     
   • Import now checks all numbers and re-formats them.
     
   • Import supports importing of all previously created export files.

This is a recommended update to all users.

Updated 04/02/2007: Now includes new French built-in help.

1. Fixed bug: events in December were not displayed correctly in the reports.
   
2. Update: added leading zeros to exported date and time values. This does not affect the re-importing of any existing exported data files.

As promised, the User Guide has now been updated to reflect the new features introduced in version 1.4, plus a few that where from version 1.3.

There is also a new page that documents an approach for insulin pump users to use the logbook: this was previously posted under News.

The User Guide is on the website here.

1. Fixed bug: Reports in 12hr time format would not display AM times correctly.

1. Added show/hide columns in logbook table: a limitation within Xcode stops columns being fully hidden.
   
2. Added ‘Notes & Schedules’ menu and window: record important notes, appointments, contacts and supply data. Add re-order todos and appointments to a dedicated calendar within iCal, with preset alarms. Email contacts using your default email application.
   
3. Added ‘Online User Guide’ menu to access the user guide on the web site.
   
4. Added auto-backup of data: while Diabetes Logbook X is running, it automatically backs up the data/preferences when the previous backup is older than 24 hours to ~/Documents/Diabetes Logbook X/Backup. Also creates an XML version of the data.
   
5. Reports now support 12hr time display if OS X system time format is 12hr.
   
6. Y-axes of height and weight graph reports now focus on the range of recorded values.
   
7. HbA1c, height and weight graph reports are now only displayed if the Reports' ‘Health’ option is selected.
   
8. Fixed a bug in the summary graph report that could result in no report being generated.

The user guide will be updated with the new features soon.

As parents of a child with diabetes, making sure that a school can easily care for your child is a great concern.

I've added a few flowcharts that we created for our son's school to help them when checking for hypos, hypers and supervising his lunchtime insulin injection. They are provided as examples and will need to be modified for each individual; we have been told that they have made it a lot easier for his teachers to handle situations.

You can find them here.

OK! It is a bad pun and probably only works in English.

For those users that like to track weight, I've now added support for for this in version 1.3.0 which you can get here: this has been mainly requested by Type II sufferers and I hope it helps.

As for height: this is tracked at my son's clinic, so I suspect it may be useful for younger diabetes sufferers. If nothing else it is useful to keep a record of this for when going to a theme park which has height restrictions on some rides

These new reports are part of the Graph report option. However, each report is only generated if there are any events that record the associated data. I decided it is better to not to show a blank graph as I suspect many users will not want to track this data.

The database is saved within the application's preferences file com.Nesfield.DiabetesLogbookX.plist which is stored in the user's Preferences folder of their Library. It is strongly recommended that this file is regularly backed up: preferably to a volume that is not the same as the one on which your account data is stored; suitable backup volumes would be iDisk, a networked folder, another computer, or to CD or DVD.

To restore the backed up file, without the application running, simple copy the file back into the Preferences folder then restart the application.

We use the OneTouch UltraSmart, plus a couple of Ultras. There are two programs that support upload, at least for the OneTouch meters: HealthEngage Diabetes and The Body Journal. I tried both many times, especially after we got the UltraSmart. The Body Journal is a general medical program and it only downloads the glucose events from the meter. HealthEngage Diabetes downloads all events (if I recall) from the meter. But, for us, the reports didn't meet our needs.

I did try using the OneTouch software within a virtual PC on our Mac: it worked well, but again the reports weren't what we wanted - and there was so much white space I couldn't bring myself to use that much paper.

My wife now only uses the UltraSmart for glucose, with insulin events added when we are away from home. As for adding meter support, I'm not that smart, just a Dad trying to help my boy. I'd love to support meters, but it might not happen.

1. Added tracking of HbA1c, weight and height.
   
2. Added new HbA1c, weight and height scatters graph.

Note: Export data files made with this version cannot be fully imported into earlier versions. Any events recorded with v.1.3.0 and above are not visible in earlier versions.

I was recently contacted by a pump user about how to use Diabetes Logbook X. After a few emails we arrived at this method:

[I'm guided by the pump user as I have no experience with them at all.]

1. For reference, record the pump pattern settings (A, B, and Standard) for the various times of day and insulin units. This can be achieved in a number of ways such as:
   
   • 
     
   • In Notes-only events in the logbook, which then gets displayed in the Notes report. [A Notes-only event only uses the event name, notes and flag fields.]
     
     
   • Create a new iCal calendar for use with the logbook. Then create diary entries/tasks/notes with the pump information. [Use the iCal item in Diabetes Logbook X's Window menu to easily access iCal.]
   
   
2. Setup Diabetes Logbook X insulins:
   
   • 
     
   • Within the logbook User Settings, edit the insulins list and add two entries such as: Basal; Bolus.
     
     
   • Within the logbook User Settings, edit the medicines list and add three entries such as: A; B; Standard.
     
     
   • Within the logbook User Settings, pre-set Insulin A to Bolus, Insulin B to Basal, and Medicine to the appropriate pump pattern (A/B/Standard).
   
   
3. Create events in the logbook:
   
   • 
     
   • Use Insulin A field to record bolus insulin units.
     
     
   • Use Insulin B field to record the basal insulin units.
     
     
   • Use Medicine field to record the pump pattern used for the day.
     
     
   • When recording pumped basal insulin, record it as one event per day as the total pumped [as basal].

1. Added new average glucose by time period graph, with standard deviation error bars.
   
2. Added a couple of missing localised strings.

1. Added Italian localisation: thank you to Claudio at Creative Shield.
   
2. Fixed bug in Logbook report: day names now correctly displayed.

Note: To migrate from the default English language to a localised version, to ensure that the assigned Period names are re-generated into the localised language, you must:

1. export all exisiting events using the Export facility
   
2. delete all events
   
3. import the export data file

This is a recommended update to all users.

1. New interface look-and-feel
   
2. Added double-click to edit an event
   
3. Added duplicate event function
   
4. New warning stops 'quit' if an event is being editted
   
5. Added 'Update ...' menu to access the website
   
6. Added 'Donate ...' menu for Diabetes UK donations
   
7. Added column sorting indicators for the Logbook table
   
8. Added keyboard shortcuts for quick access to select different report periods
   
9. Fixed import data issue: now ignores older events if 'Since last imported event' is selected.

This is a recommended update to all users.

I have had a few questions about using different numbers of insulins and medicines. So here is a brief overview of how these are now handled within Diabetes Logbook X.

There are 2 insulin fields and 1 medicine field, as this seems to be most useful to Type 1 diabetes (which is what we are tracking). However the list of insulins is appended to the list of medicines for the medicines drop down lists and vice versa, so that the 3 fields and their associated defaults can be easily assigned either an insulin or medicine list item.

Insulins and medicine are not handled differently within the application and the distinction is only in the labels on the application interface, which are to help remind the user. Within the reports the 3 different fields are assigned a different colour to aid the reader when scanning the report.

In summary, it is best to assign an insulin/medicine to a specific 'Administered' A/B/C field, if tracking is important for that item: but it won't matter which field, A/B/C, you use.

1. Fixed bug: Logbook DM import failure due to incorrect function call
   
2. Fixed bug: UTS import failure due to variable spacing of text
   
3. Retains size on Logbook and Reports windows between launches
   
4. Insulins & Med lists available to both in IM/MI order
   
5. Viewing/editing event pre-sets insulin & medicine name if the associated value is empty
   
6. Event Panel merged Insulin Administered and Medicine Taken boxes to a single Administered box
   
7. Increased the Event Panel's Notes text field
   
8. Added keyboard shortcuts for quick access to the main buttons

This is a recommended update to all users.

1. Added German localisation: thank you to Christoph Schmitz.
   
2. Logbook table now supports data sort by columns and retains the column order between launches.
   
3. Fixed localisation replacement string issue with Event Name/Notes field template.
   
4. Fixed import data issue: events older than the previously last imported event would not be imported even if "All Events' was selected.

Note: To migrate from the default English language to a localised version, to ensure that the assigned Period names are re-generated into the localised language, you must:

1. export all exisiting events using the Export facility
   
2. delete all events
   
3. import the export data file

This is a recommended update to all users.

I've finally got round to writing the user guide: find it here

1. Added French localisation: thank you to Corentin Cras-Méneur with the help of Josselyne Rochaud.
   
2. Added Event name 'Clinic' with template Notes field for HbA1c, weight, height, B.P. and Next vist layout. The template is used if the Notes field is empty.
   
3. Added Event name 'Starting item' with template Notes field for Item name and Replace date layout.

Note: To migrate from the default English language to a localised version, to ensure that the assigned Period names are re-generated into the localised language, you must:

1. export all exisiting events using the Export facility
   
2. delete all events
   
3. import the export data file

1. Fixed bug in report output: Insulin B name was not displayed correctly.

1. Graph report:
   • added expanding scale so periods with fewer events fill the graph.
     
   • added alternating column colours to separate one day from the next.
     
   • added a legend for the different graph elements
2. Added Print Report button in the Reports window: finally worked out how to print the report without first clicking it to fix the focus.
   
3. Notes only events that contain the text 'HbA1c' will be bolded and slightly larger font in the Notes report.
   
4. Added support for localising (currently only English).

1. New Graph report: scatter graph of upto the last 300 glucose readings.
   
2. New Notes report: events with only Notes field data have a separate report: useful for clinic records, prescription orders etc.
   
3. Report: flagged events are now highlighted and so easier to identify.
   
4. Report generation is significantly faster now it is done solely in PERL.
   
5. Report header now has a small 'legend' of information.
   
6. Added menu links to launch iCal and Address Book.

Update: download updated to fix a small bug in Logbook report, when no events are recorded for a period. Updated application creation time is 20/07/2006 21:51.

1. Fixed a bug introduced in beta 4: 12-hour clock users would have reports listing all events in the morning.

1. Import Data: new option to select either all events from selected import file or only events that are later than the latest event from the last import session.
   
2. Import and report settings are retained between launches.
   
3. Improved report generation speed by off-loading date and time parsing to the PERL report generator script.
   
4. Reports can be selected to be the last 7/14 days, 4/6/12 weeks, 6 months, 1 year.
   
5. Report output changes: changed Notes section in header; notable events now are highlighted in the report.
   
6. Reports: carridge returns, tabulation marks and double quotation marks are passed to the reprort generator correctly. Specifically, characters that have special interpretions by UNIX and PERL are handled correctly. Ostensibly for robustness in handling text in the Notes event field.
   
7. General typos and report tidying up.

I'm pleased to announce the beta of Diabetes Logbook X. This is my attempt at a logbook application that allows data to be both imported and exported, and doesn't trap you data in a closed format.