One of the things that has made Sailwave popular is usability. But as more and more things need to be user pre-defined - new points systems, rating systems, rating values, publishing options, templates, styles etc etc, competitors, starts, usability could get compromised
Currently the approach has been for the user to create ASCII files by hand and point Sailwave at them (or force them to be created in a specific folder). This is OK for confident computer users but is it onerous for other users? Would it be better if there was a single Tools+Setup item that displayed a tree of all the stuff the user could define and have a dedicated editing window (etc) for each.
I would envisage all this setup data being stored in a single ASCII (XML) file so that 'expert' users could still edit it by hand if required.
Colin,
I agree with you that usability is key. Some of us are not ASCII savy.
Regards,
Bette
Lake Champlain Yacht Club
···
-----Original Message-----
From: Colin Jenkins [mailto:colin@sailwave.com]
Sent: Wednesday, January 12, 2005 4:11 AM
To: Sailwave User Group
Subject: [sailwave] usability
Hi,
One of the things that has made Sailwave popular is usability. But as
more and more things need to be user pre-defined - new points systems,
rating systems, rating values, publishing options, templates, styles etc
etc, competitors, starts, usability could get compromised
Currently the approach has been for the user to create ASCII files by
hand and point Sailwave at them (or force them to be created in a
specific folder). This is OK for confident computer users but is it
onerous for other users? Would it be better if there was a single
Tools+Setup item that displayed a tree of all the stuff the user could
define and have a dedicated editing window (etc) for each.
I would envisage all this setup data being stored in a single ASCII
(XML) file so that 'expert' users could still edit it by hand if required.
My suggestion would be to keep the configuration in human read/editable files and perhaps write small standalone wizards to help the folks that need them.
I have never knowingly created an ASC11 file? Should I have done. I use the program frequenly for all sorts of things.
Mike Butterfield
···
----- Original Message ----- From: "Colin Jenkins" <colin@sailwave.com>
To: "Sailwave User Group" <sailwave@yahoogroups.com>
Sent: Wednesday, January 12, 2005 12:11 PM
Subject: [sailwave] usability
Hi,
One of the things that has made Sailwave popular is usability. But as
more and more things need to be user pre-defined - new points systems,
rating systems, rating values, publishing options, templates, styles etc
etc, competitors, starts, usability could get compromised
Currently the approach has been for the user to create ASCII files by
hand and point Sailwave at them (or force them to be created in a
specific folder). This is OK for confident computer users but is it
onerous for other users? Would it be better if there was a single
Tools+Setup item that displayed a tree of all the stuff the user could
define and have a dedicated editing window (etc) for each.
I would envisage all this setup data being stored in a single ASCII
(XML) file so that 'expert' users could still edit it by hand if required.
My suggestion would be to keep the configuration in human read/editable files and perhaps write small standalone wizards to help the folks that need them.
Mike
+---------------------------------------------------------------------
> Mike McKeever - Denver Sailing Association - Denver, Colorado, USA
> mckeever@dimensional.com
> 303.530.4503 (7a-9p mtn)
Not necessarily - only if you wanted your own locale, publishing template, publishing style or rating values. But this will be extended in the next version to user defined rating systems and points systems (as opposed to the single 'custom' stuff available) now - so i've been wondering of the text file method is usable or not - 'cos there'll be more of the same soon.
I have never knowingly created an ASC11 file? Should I have done. I use the program frequenly for all sorts of things.
Mike Butterfield
----- Original Message ----- From: "Colin Jenkins" <colin@sailwave.com>
To: "Sailwave User Group" <sailwave@yahoogroups.com>
Sent: Wednesday, January 12, 2005 12:11 PM
Subject: [sailwave] usability
Hi,
One of the things that has made Sailwave popular is usability. But as
more and more things need to be user pre-defined - new points systems,
rating systems, rating values, publishing options, templates, styles etc
etc, competitors, starts, usability could get compromised
Currently the approach has been for the user to create ASCII files by
hand and point Sailwave at them (or force them to be created in a
specific folder). This is OK for confident computer users but is it
onerous for other users? Would it be better if there was a single
Tools+Setup item that displayed a tree of all the stuff the user could
define and have a dedicated editing window (etc) for each.
I would envisage all this setup data being stored in a single ASCII
(XML) file so that 'expert' users could still edit it by hand if required.
One of the things that has made Sailwave popular is usability. But as
more and more things need to be user pre-defined - new points systems,
rating systems, rating values, publishing options, templates, styles etc
etc, competitors, starts, usability could get compromised
Currently the approach has been for the user to create ASCII files by
hand and point Sailwave at them (or force them to be created in a
specific folder). This is OK for confident computer users but is it
onerous for other users? Would it be better if there was a single
Tools+Setup item that displayed a tree of all the stuff the user could
define and have a dedicated editing window (etc) for each.
I would envisage all this setup data being stored in a single ASCII
(XML) file so that 'expert' users could still edit it by hand if required.
Also I need some fundamental UI changes to accommodate the necessary functionality that we've been talking about for ages (PH systems, app C/D etc) without compromising usability... The current platform just can't handle it...
One of the things that has made Sailwave popular is usability. But as
more and more things need to be user pre-defined - new points systems,
rating systems, rating values, publishing options, templates, styles etc
etc, competitors, starts, usability could get compromised
Currently the approach has been for the user to create ASCII files by
hand and point Sailwave at them (or force them to be created in a
specific folder). This is OK for confident computer users but is it
onerous for other users? Would it be better if there was a single
Tools+Setup item that displayed a tree of all the stuff the user could
define and have a dedicated editing window (etc) for each.
I would envisage all this setup data being stored in a single ASCII
(XML) file so that 'expert' users could still edit it by hand if required.