Select to expand quote
sav911 said..
Not at all, always keen for advice. I used to write a lot of GPL software in the 90's and early 2000's. What you mentioned is an old pitfall: Somebody gives you a great idea and they are really super keen to be a user of it. You develop it, and some time down the track when it gets developed, they are not interested in using it. Long story short: I know what you are talking about. In the commercial world, this isn't a problem. When you give away software, it is.
I need a good application as an exercise (it's hard learning an API without a useful application). If a few people are interested in this rigging reckoner (even given the above mentioned pitfall), I'll risk writing it. I'm deciding to make it fuzzy logic/formula based, or statistical based (or both). However, I am thinking of making it statistical. I've got a few ideas on how to implement it. Of course, it will need to be written for the impatient
The factors I will be using are: equipment details and configuration (user can preenter, group for easy selection, or enter them after the session, or put don't know/don't care if they are lazy), location (map selectable), water type, ocean/lake floor clutter, wind speed, wind direction, temperature, pressure (BOM/Seabreeze query, or measurement), water type, condition time (ie: seabreeze, trade wind, frontal etc), sailor type, sailor experience etc. The App will be written to memorise preentered data, and grow information about a location or a rig setup etc so the fields are pre-filled.
With statistical base, it's should be a few buttons before the session, and then a few buttons after the session. An alarm notification will prompt the user after session and ask them to give session rating out of 10. App will note condition(s) and what gear(s) they used. Over time, it will be able to statistically match a given session/location/date with gear. Of course, the Garbage-in-garbage-out rule applies if users get into the habit of using "don't care" values. The App will also have a means to exchange data so queries on other sailors can be done without needing to ask them (ie: they are not there).