The Blog is retired. Sailwave news will be posted on sailwave.com. No more posts will be added to this blog. It will be removed at some point in the future.
Update: You can subscribe to the new blog from the Sailwave website. Apologies for the disruption.
Thursday, 1 September 2011
Wednesday, 4 May 2011
Version 2.02 build 7 available for testing
Version 2.02 build 7 has been built with the latest version of the development system I use for Sailwave. You will notice visual changes (better I think) and it should be better on Vista and Windows 7. Please use the Sailwave User Group for feedback or email colin@sailwave.com or leave a comment here.
You can download it here:-
http://sailwave.com/binary/sw202b7.exe
NB: as an interim measure to resolve some issues, Sailwave asks for admin access when it starts.
You can download it here:-
http://sailwave.com/binary/sw202b7.exe
NB: as an interim measure to resolve some issues, Sailwave asks for admin access when it starts.
Thursday, 3 February 2011
Class database and handicap returns
I have for many years talked to various people about using Sailwave to send handicap results back to a central database via Sailwave on an international basis. I have a design now and it will appear in Sailwave soon, but one essential precursor is a list of Sailwave standard class names and IDs.
To that end please do feel free to contribute classes to the new class database here:-
http://www.sailwave.com/home/home.php
You can transfer ownership of the class to somebody else at a later date.
You'll see there is a field called Parent ID. This is essentially for those classes whereby it's useful to have a specific rating but also a rating for the class as a whole. For example F18 and Nacra F18. The parent class of the Nacra F18 would be F18. This can also be used in development classes on an age basis, for example for Cherubs.
The idea of the database is that ratings will be updated every N days and be available for download at any time on an international, national (MNA) or venue basis. Probably regional as well using a tags system.
Sailwave will collect class, elapsed time, date and venue information only. No personal sailor information will be collected. It will be a very easy process. The contributor will need to be logged into the Sailwave website and will be the visible owner of the results.
NB: You will not need to use Sailwave class names in your series (unless you want to) - there'll be a mapping phase when doing the returns which will get cached so you don't have to do it the next time etc.
The raw data will also be available if allowed by the contributor.
Please also feel free to add venues to the web site as each return must reference a Sailwave venue ID.
http://www.sailwave.com/home/home.php
Proposed return data taken from currently separately scored fleets:-
Unique Race ID (Sailwave does this now in fact)
Date and time
Sailwave Venue ID
Sailwave User ID
N * {Sailwave Class ID,Elapsed time,Laps}
To that end please do feel free to contribute classes to the new class database here:-
http://www.sailwave.com/home/home.php
You can transfer ownership of the class to somebody else at a later date.
You'll see there is a field called Parent ID. This is essentially for those classes whereby it's useful to have a specific rating but also a rating for the class as a whole. For example F18 and Nacra F18. The parent class of the Nacra F18 would be F18. This can also be used in development classes on an age basis, for example for Cherubs.
The idea of the database is that ratings will be updated every N days and be available for download at any time on an international, national (MNA) or venue basis. Probably regional as well using a tags system.
Sailwave will collect class, elapsed time, date and venue information only. No personal sailor information will be collected. It will be a very easy process. The contributor will need to be logged into the Sailwave website and will be the visible owner of the results.
NB: You will not need to use Sailwave class names in your series (unless you want to) - there'll be a mapping phase when doing the returns which will get cached so you don't have to do it the next time etc.
The raw data will also be available if allowed by the contributor.
Please also feel free to add venues to the web site as each return must reference a Sailwave venue ID.
http://www.sailwave.com/home/home.php
Proposed return data taken from currently separately scored fleets:-
Unique Race ID (Sailwave does this now in fact)
Date and time
Sailwave Venue ID
Sailwave User ID
N * {Sailwave Class ID,Elapsed time,Laps}
Monday, 13 September 2010
New Sailwave website
The beginnings of a new sailwave website...
http://sailwave.com/home/home.php
Please feel free to play. It is a sister website for the windows scoring client and intended to be a fusion of event management and social networking. You will be able to collect on line entries and publish results directly from the Sailwave windows client.
Login is via social networks for a number of reasons. Users don't need to register with the site - it's very quick to start using it if you have a social network account (twitter/facebook/yahoo/google). Registration needs to be secure, these sites already have very secure processes. Users are able to post content to the new Sailwave website, so by only allowing existing and traceable social network users login, it reduces the potential for spamming.
Login will be extended to include Google and OpenID etc.
Tuesday, 8 June 2010
Updated prize facility
Version 2.02 build 5 has been uploaded to the website with a updated prize facility that uses the standard expression editor to select a group of competitors. You will have to enter expressions for any existing prizes as it was not possible to auto-retro.
You can now allocate the number of prizes available in each prize category. For example you may have a category called "Best Visitors" with 3 available prizes: 1st, 2nd and 3rd. Sailwave will automatically allocate these when publishing if you include a prize table.
In the above example the visitors could be determined by using an expression of the form "club <> myyachtclub" - where myyachtclub is the name used for all local sailors in the club field. Sometimes you may need to add data in fields to get Sailwave to allocate the prizes. For example if you had a prize category called "Best Beginners", you'd need to use one of the fields to identify beginners if one was not available already.
You can now allocate the number of prizes available in each prize category. For example you may have a category called "Best Visitors" with 3 available prizes: 1st, 2nd and 3rd. Sailwave will automatically allocate these when publishing if you include a prize table.
In the above example the visitors could be determined by using an expression of the form "club <> myyachtclub" - where myyachtclub is the name used for all local sailors in the club field. Sometimes you may need to add data in fields to get Sailwave to allocate the prizes. For example if you had a prize category called "Best Beginners", you'd need to use one of the fields to identify beginners if one was not available already.
Tuesday, 13 October 2009
Skandia Sail for Gold 2009
During Sail for Gold 2009 I quickly developed some multi file publishing tools to generate leaderboards and country standings.
leaderboard
country standings
country standings - scrolls after 10sec
Lots more alternatves like a matrix of country placings etc. May formalise. While the pages in this instance used country and class, any two fields could be used...
leaderboard
country standings
country standings - scrolls after 10sec
Lots more alternatves like a matrix of country placings etc. May formalise. While the pages in this instance used country and class, any two fields could be used...
Version 2.02 build 1 available
Download
Change History
Please note that this will resolve any FTP connectivity problems due to a change of hosting from WebFusion to Heart Internet.
Change History
Please note that this will resolve any FTP connectivity problems due to a change of hosting from WebFusion to Heart Internet.
Subscribe to:
Posts (Atom)