i have agonised about this for about a year and
tried all sorts of approaches.
bottom line - all advice says "mobile first/ready" - i.e. when
designing a new app design for mobile first (or as well as) and by
mobile i mean smart phone and tablet. my tablet (nexus 7) has the
same resolution as my desktop - we are entering a mobile era.
i'm using html5/css/javascript with jquery mobile and some other
I’m not sure where the files would be saved but if on Sailwave server does there need to be some form of login (twitter/Facebook) so that data is not (accidentally) overwritten by different users (from different clubs) but enables files to be picked up from club members on potentially different devices
Also at present hitting ‘back’ takes you to options screen. Main menu might be better and perhaps add save/ exit as options on that menu
thanks will - yes
there will be authentication etc - but have got bogged down in
stuff like that before and not got to sailwave bits - ignoring
for now. back should take you to previous page - i’v not
hijacked it and wanted it to work natually. there will be two
constant icons in the header app home and series home.
I'm not sure where the files would be saved but if on
Sailwave server does there need to be some form of login
(twitter/Facebook) so that data is not (accidentally)
overwritten by different users (from different clubs) but
enables files to be picked up from club members on
potentially different devices
Also at present hitting 'back' takes you to options
screen. Main menu might be better and perhaps add save/
exit as options on that menu
Best of luck!
Regards
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 09:36, Colin Jenkins <colin@sailwave.com >
wrote:
i have agonised about this
for about a year and tried all sorts of
approaches.
bottom line - all advice says "mobile first/ready"
i.e. when designing a new app design for mobile
first (or as well as) and by mobile i mean smart
phone and tablet. my tablet (nexus 7) has the same
resolution as my desktop - we are entering a
mobile era.
i'm using html5/css/javascript with jquery mobile
and some other assets like backbone.js and
underscore.js
advantages:-
- layout responsive to screen size (smartphone,
tablet).
-
*offline
operation when web is not available (manifest and
local storage).*
-
save
series files to sailwave server, cloud services
(dropbox, amazon, google drive etc) and local file
system
- l ocal
caching while working on a file so its there when
you come back to it - i.e. close browser - open
browser
- can
be converted into native ios and android apps via
phonegap (now cordova) or adobe air (etc).
-
user
contributed plugins and scoring systems etc via
javascript - a lot of stuff will be ‘scripted’
not hard wired.
disadvantages:-
-
no
planned linux native app (but possible via older
adobe air versions - adobe dropped linux as a
target)
- must
be modern browser (html5)
development will be at:-
-
my original approach - the easiest - using php to
generate a web ‘app’ (ish) is old hat. such an
approach cannot be cached locally nor turned into
a native app. there is some backend server
stuff to save files to sailwave - but you can also
save files locally - all the server stuff is
optional.
the new app spec dumps aliases and replaces them
with the ability to apply N scoring systems
keeping N sets of results. all objects like
competitors (called entries now) and races etc
have user definable content via templates. the
new design is in fact much more flexible than the
old one. lots of other changes like have N
penalty codes and redress codes in addition to
retirement codes. user will be able ablt to write
their own scoring systems using javascript. i
will suppoy appendix a initially. addendum c
later unless somebody else does it…
ps: the current (few) pages are smartphone
orientated - jquery mobile tablet support is on
its way - what will happen is that the menus will
stay fixed on the left with content on the right
rather than a new page when a menu it hit as phone
smart phones.
massive amout of work
i will probably charge something nominal a year
(subscription) to use this new sailwave.
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 - Release Date:
08/29/12
I appreciate it’s one step at a time, and a case of prioritising those steps. But suggestions hopefully help somewhat.
Cheers
William Carruthers
/)/)/)___/)
(_(___(__
···
thanks will - yes
there will be authentication etc - but have got bogged down in
stuff like that before and not got to sailwave bits - ignoring
for now. back should take you to previous page - i’v not
hijacked it and wanted it to work natually. there will be two
constant icons in the header app home and series home.
I'm not sure where the files would be saved but if on
Sailwave server does there need to be some form of login
(twitter/Facebook) so that data is not (accidentally)
overwritten by different users (from different clubs) but
enables files to be picked up from club members on
potentially different devices
Also at present hitting 'back' takes you to options
screen. Main menu might be better and perhaps add save/
exit as options on that menu
Best of luck!
Regards
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 09:36, Colin Jenkins <colin@sailwave.com >
wrote:
i have agonised about this
for about a year and tried all sorts of
approaches.
bottom line - all advice says "mobile first/ready"
i.e. when designing a new app design for mobile
first (or as well as) and by mobile i mean smart
phone and tablet. my tablet (nexus 7) has the same
resolution as my desktop - we are entering a
mobile era.
i'm using html5/css/javascript with jquery mobile
and some other assets like backbone.js and
underscore.js
advantages:-
- layout responsive to screen size (smartphone,
tablet).
-
*offline
operation when web is not available (manifest and
local storage).*
-
save
series files to sailwave server, cloud services
(dropbox, amazon, google drive etc) and local file
system
- l ocal
caching while working on a file so its there when
you come back to it - i.e. close browser - open
browser
- can
be converted into native ios and android apps via
phonegap (now cordova) or adobe air (etc).
-
user
contributed plugins and scoring systems etc via
javascript - a lot of stuff will be ‘scripted’
not hard wired.
disadvantages:-
-
no
planned linux native app (but possible via older
adobe air versions - adobe dropped linux as a
target)
- must
be modern browser (html5)
development will be at:-
-
my original approach - the easiest - using php to
generate a web ‘app’ (ish) is old hat. such an
approach cannot be cached locally nor turned into
a native app. there is some backend server
stuff to save files to sailwave - but you can also
save files locally - all the server stuff is
optional.
the new app spec dumps aliases and replaces them
with the ability to apply N scoring systems
keeping N sets of results. all objects like
competitors (called entries now) and races etc
have user definable content via templates. the
new design is in fact much more flexible than the
old one. lots of other changes like have N
penalty codes and redress codes in addition to
retirement codes. user will be able ablt to write
their own scoring systems using javascript. i
will suppoy appendix a initially. addendum c
later unless somebody else does it…
ps: the current (few) pages are smartphone
orientated - jquery mobile tablet support is on
its way - what will happen is that the menus will
stay fixed on the left with content on the right
rather than a new page when a menu it hit as phone
smart phones.
massive amout of work
i will probably charge something nominal a year
(subscription) to use this new sailwave.
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 - Release Date:
08/29/12
I appreciate it's one step at a time, and a case of
prioritising those steps. But suggestions hopefully help
somewhat.
Cheers
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 10:01, Colin Jenkins <colin@sailwave.com >
wrote:
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 - Release Date:
08/29/12
thanks
will - yes there will be authentication etc - but
have got bogged down in stuff like that before and
not got to sailwave bits - ignoring for now. back
should take you to previous page - i’v not
hijacked it and wanted it to work natually. there
will be two constant icons in the header app home
and series home.
but if on Sailwave server does there need to be
some form of login (twitter/Facebook) so that
data is not (accidentally) overwritten by
different users (from different clubs) but
enables files to be picked up from club members
on potentially different devices
Also at present hitting 'back' takes you to
options screen. Main menu might be better and
perhaps add save/ exit as options on that menu
Best of luck!
Regards
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 09:36, Colin Jenkins <colin@sailwave.com
>
wrote:
i have agonised
about this for about a year and tried
all sorts of approaches.
bottom line - all advice says "mobile
first/ready" - i.e. when designing a new
app design for mobile first (or as well
as) and by mobile i mean smart phone and
tablet. my tablet (nexus 7) has the same
resolution as my desktop - we are
entering a mobile era.
i'm using html5/css/javascript with
jquery mobile and some other assets like
backbone.js and underscore.js
advantages:-
- layout responsive to screen size
(smartphone, tablet).
- *offline
operation when web is not available
(manifest and local storage).*
- save series
files to sailwave server, cloud services
(dropbox, amazon, google drive etc) and
local file system
- l
ocal
caching while working on a file so its
there when you come back to it - i.e.
close browser - open browser
- can be
converted into native ios and android
apps via phonegap (now cordova) or adobe
air (etc).
- user
contributed plugins and scoring systems
etc via javascript - a lot of stuff
will be ‘scripted’ not hard wired.
disadvantages:-
- no planned
linux native app (but possible via older
adobe air versions - adobe dropped linux
as a target)
- must be
modern browser (html5)
development will be at:-
-
my original approach - the easiest -
using php to generate a web ‘app’ (ish)
is old hat. such an approach cannot be
cached locally nor turned into a native
app. there is some backend server
stuff to save files to sailwave - but
you can also save files locally - all
the server stuff is optional.
the new app spec dumps aliases and
replaces them with the ability to apply
N scoring systems keeping N sets of
results. all objects like competitors
(called entries now) and races etc have
user definable content via templates.
the new design is in fact much more
flexible than the old one. lots of
other changes like have N penalty codes
and redress codes in addition to
retirement codes. user will be able
ablt to write their own scoring systems
using javascript. i will suppoy
appendix a initially. addendum c later
unless somebody else does it…
ps: the current (few) pages are
smartphone orientated - jquery mobile
tablet support is on its way - what will
happen is that the menus will stay fixed
on the left with content on the right
rather than a new page when a menu it
hit as phone smart phones.
massive amout of work
i will probably charge something nominal
a year (subscription) to use this new
sailwave.
No
virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 -
Release Date: 08/29/12
I'm not sure where the files would be saved but if on
Sailwave server does there need to be some form of login
(twitter/Facebook) so that data is not (accidentally)
overwritten by different users (from different clubs) but
enables files to be picked up from club members on
potentially different devices
Also at present hitting 'back' takes you to options
screen. Main menu might be better and perhaps add save/
exit as options on that menu
Best of luck!
Regards
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 09:36, Colin Jenkins <colin@sailwave.com >
wrote:
i have agonised about this
for about a year and tried all sorts of
approaches.
bottom line - all advice says "mobile first/ready"
i.e. when designing a new app design for mobile
first (or as well as) and by mobile i mean smart
phone and tablet. my tablet (nexus 7) has the same
resolution as my desktop - we are entering a
mobile era.
i'm using html5/css/javascript with jquery mobile
and some other assets like backbone.js and
underscore.js
advantages:-
- layout responsive to screen size (smartphone,
tablet).
-
*offline
operation when web is not available (manifest and
local storage).*
-
save
series files to sailwave server, cloud services
(dropbox, amazon, google drive etc) and local file
system
- l ocal
caching while working on a file so its there when
you come back to it - i.e. close browser - open
browser
- can
be converted into native ios and android apps via
phonegap (now cordova) or adobe air (etc).
-
user
contributed plugins and scoring systems etc via
javascript - a lot of stuff will be ‘scripted’
not hard wired.
disadvantages:-
-
no
planned linux native app (but possible via older
adobe air versions - adobe dropped linux as a
target)
- must
be modern browser (html5)
development will be at:-
-
my original approach - the easiest - using php to
generate a web ‘app’ (ish) is old hat. such an
approach cannot be cached locally nor turned into
a native app. there is some backend server
stuff to save files to sailwave - but you can also
save files locally - all the server stuff is
optional.
the new app spec dumps aliases and replaces them
with the ability to apply N scoring systems
keeping N sets of results. all objects like
competitors (called entries now) and races etc
have user definable content via templates. the
new design is in fact much more flexible than the
old one. lots of other changes like have N
penalty codes and redress codes in addition to
retirement codes. user will be able ablt to write
their own scoring systems using javascript. i
will suppoy appendix a initially. addendum c
later unless somebody else does it…
ps: the current (few) pages are smartphone
orientated - jquery mobile tablet support is on
its way - what will happen is that the menus will
stay fixed on the left with content on the right
rather than a new page when a menu it hit as phone
smart phones.
massive amout of work
i will probably charge something nominal a year
(subscription) to use this new sailwave.
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 - Release Date:
08/29/12
Good to hear there is a mobile device enabled sailwave coming, I will be happy to pick it up on my iPhone. But please also keep the old version, or a version which will stand alone as many clubs have no or poor mobile signals, and no broadband or phone line.
I take Sailwave on my laptop to Yorkshire & Humberside Youth travelers series events http://yhysa.org/ (16 meetings at different clubs in the area split into Summer and Autumn series, Paul Goodison first sailed with us. ) About half the clubs we visit already have sailwave and do their own results. It works well, at individual events and for the series scores (though it perplexes me that I need event files and a separate series file).
I am still surprised at how many clubs try to use spreadsheet, other self developed systems or even hand calculated results (Appendix A7 and A8 are normally not covered correctly in these systems). The converts to Sailwave we have achieved will not be happy if it keeps changing, so would ask for a similar look and feel.
Colin J
[http://sailwave.com](http://sailwave.com/)
On 30/08/2012 10:20, Bassenthwaite SC wrote:
Thanks Colin
I appreciate it's one step at a time, and a case of
prioritising those steps. But suggestions hopefully help
somewhat.
Cheers
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 10:01, Colin Jenkins <colin@sailwave.com > > > wrote:
thanks
will - yes there will be authentication etc - but
have got bogged down in stuff like that before and
not got to sailwave bits - ignoring for now. back
should take you to previous page - i’v not
hijacked it and wanted it to work natually. there
will be two constant icons in the header app home
and series home.
Cheers,
Colin J
[http://sailwave.com](http://sailwave.com/)
On 30/08/2012 09:57, Bassenthwaite SC wrote:
What an interesting challenge!
I'm not sure where the files would be saved
but if on Sailwave server does there need to be
some form of login (twitter/Facebook) so that
data is not (accidentally) overwritten by
different users (from different clubs) but
enables files to be picked up from club members
on potentially different devices
Also at present hitting 'back' takes you to
options screen. Main menu might be better and
perhaps add save/ exit as options on that menu
Best of luck!
Regards
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 09:36, Colin Jenkins <colin@sailwave.com > > > > > > > > > wrote:
i have agonised
about this for about a year and tried
all sorts of approaches.
bottom line - all advice says "mobile
first/ready" - i.e. when designing a new
app design for mobile first (or as well
as) and by mobile i mean smart phone and
tablet. my tablet (nexus 7) has the same
resolution as my desktop - we are
entering a mobile era.
i'm using html5/css/javascript with
jquery mobile and some other assets like
backbone.js and underscore.js
advantages:-
- layout responsive to screen size
(smartphone, tablet).
- *offline
operation when web is not available
(manifest and local storage).*
- save series
files to sailwave server, cloud services
(dropbox, amazon, google drive etc) and
local file system
- l
ocal
caching while working on a file so its
there when you come back to it - i.e.
close browser - open browser
- can be
converted into native ios and android
apps via phonegap (now cordova) or adobe
air (etc).
- user
contributed plugins and scoring systems
etc via javascript - a lot of stuff
will be ‘scripted’ not hard wired.
disadvantages:-
- no planned
linux native app (but possible via older
adobe air versions - adobe dropped linux
as a target)
- must be
modern browser (html5)
development will be at:-
- [http://mysail.co.uk](http://mysail.co.uk/)
my original approach - the easiest -
using php to generate a web ‘app’ (ish)
is old hat. such an approach cannot be
cached locally nor turned into a native
app. there is some backend server
stuff to save files to sailwave - but
you can also save files locally - all
the server stuff is optional.
the new app spec dumps aliases and
replaces them with the ability to apply
N scoring systems keeping N sets of
results. all objects like competitors
(called entries now) and races etc have
user definable content via templates.
the new design is in fact much more
flexible than the old one. lots of
other changes like have N penalty codes
and redress codes in addition to
retirement codes. user will be able
ablt to write their own scoring systems
using javascript. i will suppoy
appendix a initially. addendum c later
unless somebody else does it…
ps: the current (few) pages are
smartphone orientated - jquery mobile
tablet support is on its way - what will
happen is that the menus will stay fixed
on the left with content on the right
rather than a new page when a menu it
hit as phone smart phones.
massive amout of work
i will probably charge something nominal
a year (subscription) to use this new
sailwave.
–
Cheers,
Colin J
[http://sailwave.com](http://sailwave.com/)
I'm not sure where the files would be saved but if on
Sailwave server does there need to be some form of login
(twitter/Facebook) so that data is not (accidentally)
overwritten by different users (from different clubs) but
enables files to be picked up from club members on
potentially different devices
Also at present hitting 'back' takes you to options
screen. Main menu might be better and perhaps add save/
exit as options on that menu
Best of luck!
Regards
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 09:36, Colin Jenkins <colin@sailwave.com >
wrote:
i have agonised about this
for about a year and tried all sorts of
approaches.
bottom line - all advice says "mobile first/ready"
i.e. when designing a new app design for mobile
first (or as well as) and by mobile i mean smart
phone and tablet. my tablet (nexus 7) has the same
resolution as my desktop - we are entering a
mobile era.
i'm using html5/css/javascript with jquery mobile
and some other assets like backbone.js and
underscore.js
advantages:-
- layout responsive to screen size (smartphone,
tablet).
-
*offline
operation when web is not available (manifest and
local storage).*
-
save
series files to sailwave server, cloud services
(dropbox, amazon, google drive etc) and local file
system
- l ocal
caching while working on a file so its there when
you come back to it - i.e. close browser - open
browser
- can
be converted into native ios and android apps via
phonegap (now cordova) or adobe air (etc).
-
user
contributed plugins and scoring systems etc via
javascript - a lot of stuff will be ‘scripted’
not hard wired.
disadvantages:-
-
no
planned linux native app (but possible via older
adobe air versions - adobe dropped linux as a
target)
- must
be modern browser (html5)
development will be at:-
-
my original approach - the easiest - using php to
generate a web ‘app’ (ish) is old hat. such an
approach cannot be cached locally nor turned into
a native app. there is some backend server
stuff to save files to sailwave - but you can also
save files locally - all the server stuff is
optional.
the new app spec dumps aliases and replaces them
with the ability to apply N scoring systems
keeping N sets of results. all objects like
competitors (called entries now) and races etc
have user definable content via templates. the
new design is in fact much more flexible than the
old one. lots of other changes like have N
penalty codes and redress codes in addition to
retirement codes. user will be able ablt to write
their own scoring systems using javascript. i
will suppoy appendix a initially. addendum c
later unless somebody else does it…
ps: the current (few) pages are smartphone
orientated - jquery mobile tablet support is on
its way - what will happen is that the menus will
stay fixed on the left with content on the right
rather than a new page when a menu it hit as phone
smart phones.
massive amout of work
i will probably charge something nominal a year
(subscription) to use this new sailwave.
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 - Release Date:
08/29/12
but if on Sailwave server does there need to be
some form of login (twitter/Facebook) so that
data is not (accidentally) overwritten by
different users (from different clubs) but
enables files to be picked up from club members
on potentially different devices
Also at present hitting 'back' takes you to
options screen. Main menu might be better and
perhaps add save/ exit as options on that menu
Best of luck!
Regards
William Carruthers
Sent from my iPhone
/)/)/)___/)
(_(___(__
On 30 Aug 2012, at 09:36, Colin Jenkins <colin@sailwave.com
>
wrote:
i have agonised
about this for about a year and tried
all sorts of approaches.
bottom line - all advice says "mobile
first/ready" - i.e. when designing a new
app design for mobile first (or as well
as) and by mobile i mean smart phone and
tablet. my tablet (nexus 7) has the same
resolution as my desktop - we are
entering a mobile era.
i'm using html5/css/javascript with
jquery mobile and some other assets like
backbone.js and underscore.js
advantages:-
- layout responsive to screen size
(smartphone, tablet).
- *offline
operation when web is not available
(manifest and local storage).*
- save series
files to sailwave server, cloud services
(dropbox, amazon, google drive etc) and
local file system
- l
ocal
caching while working on a file so its
there when you come back to it - i.e.
close browser - open browser
- can be
converted into native ios and android
apps via phonegap (now cordova) or adobe
air (etc).
- user
contributed plugins and scoring systems
etc via javascript - a lot of stuff
will be ‘scripted’ not hard wired.
disadvantages:-
- no planned
linux native app (but possible via older
adobe air versions - adobe dropped linux
as a target)
- must be
modern browser (html5)
development will be at:-
-
my original approach - the easiest -
using php to generate a web ‘app’ (ish)
is old hat. such an approach cannot be
cached locally nor turned into a native
app. there is some backend server
stuff to save files to sailwave - but
you can also save files locally - all
the server stuff is optional.
the new app spec dumps aliases and
replaces them with the ability to apply
N scoring systems keeping N sets of
results. all objects like competitors
(called entries now) and races etc have
user definable content via templates.
the new design is in fact much more
flexible than the old one. lots of
other changes like have N penalty codes
and redress codes in addition to
retirement codes. user will be able
ablt to write their own scoring systems
using javascript. i will suppoy
appendix a initially. addendum c later
unless somebody else does it…
ps: the current (few) pages are
smartphone orientated - jquery mobile
tablet support is on its way - what will
happen is that the menus will stay fixed
on the left with content on the right
rather than a new page when a menu it
hit as phone smart phones.
massive amout of work
i will probably charge something nominal
a year (subscription) to use this new
sailwave.
No
virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 -
Release Date: 08/29/12
Thanks for the feedback.
I can't keep the same look and feel but i have kept the same
concepts. compare for example facebook app and facebook
website. I’ve tried using a desktop design and ‘living with it’
on mobiles but it simply doesn’t work - the design must be
‘mobile and tablet first’.
nb: it will (when done - thats bit is not there yet) work
without connection (after its been connected once) - that was
one of the requirements I made on it after the last discussion
about a web app.
I will keep Sailwave windows app yes and maintain/tweak but
device enabled sailwave coming, I will be happy to
pick it up on my iPhone. But please also keep the old
version, or a version which will stand alone as many
clubs have no or poor mobile signals, and no broadband
or phone line.
I
take Sailwave on my laptop to
Yorkshire & Humberside Youth travelers series
events http://yhysa.org/ (16 meetings at
different clubs in the area split into Summer and
Autumn series, Paul Goodison first sailed with us. )
About half the clubs we visit already have sailwave
and do their own results. It works well, at
individual events and for the series scores (though
it perplexes me that I need event files
and a separate series
file).
I
am still surprised at how many clubs try to use
spreadsheet, other self developed systems or even
hand calculated results (Appendix A7 and A8 are
normally not covered correctly in these systems).
The converts to Sailwave we have achieved will not
be happy if it keeps changing, so would ask for a
similar look and feel.
Thanks for a great system
William Redman
Chairman Yorkshire &
Humberside Youth Sailing Association.
From:
Colin Jenkins Thursday, 30 August 2012, 10:24
Re: [sailwave] the next generation sailwave
absolutely…
Cheers,
Colin J
[http://sailwave.com](http://sailwave.com/)
On 30/08/2012 10:20, Bassenthwaite SC
wrote:
Thanks Colin
I appreciate it's one step at a
time, and a case of prioritising those
steps. But suggestions hopefully help
somewhat.
yes there will be
authentication etc - but have
got bogged down in stuff like
that before and not got to
sailwave bits - ignoring for
now. back should take you to
previous page - i’v not
hijacked it and wanted it to
work natually. there will be
two constant icons in the
header app home and series
home.
Cheers,
Colin J
[http://sailwave.com](http://sailwave.com/)
On 30/08/2012 09:57,
Bassenthwaite SC wrote:
What an interesting
challenge!
I'm not sure where the
files would be saved but if
on Sailwave server does
there need to be some form
of login (twitter/Facebook)
so that data is not
(accidentally) overwritten
by different users (from
different clubs) but enables
files to be picked up from
club members on potentially
different devices
Also at present hitting
‘back’ takes you to options
screen. Main menu might be
better and perhaps add save/
exit as options on that menu
have agonised about
this for about a
year and tried all
sorts of approaches.
bottom line - all
advice says “mobile
first/ready” - i.e.
when designing a new
app design for
mobile first (or as
well as) and by
mobile i mean smart
phone and tablet. my
tablet (nexus 7) has
the same resolution
as my desktop - we
are entering a
mobile era.
i'm using
html5/css/javascript
with jquery mobile
and some other
assets like
backbone.js and
underscore.js
advantages:-
- layout responsive
to screen size
(smartphone,
tablet).
-
*offline
operation when web
is not available
(manifest and local
storage).*
- save
series files to
sailwave server,
cloud services
(dropbox, amazon,
google drive etc)
and local file
system
- l
ocal
caching while
working on a file so
its there when you
come back to it -
i.e. close browser -
open browser
- can
be converted into
native ios and
android apps via
phonegap (now
cordova) or adobe
air (etc).
-
user
contributed plugins
and scoring systems
etc via javascript -
a lot of stuff
will be ‘scripted’
not hard wired.
disadvantages:-
- no
planned linux native
app (but possible
via older adobe air
versions - adobe
dropped linux as a
target)
- must
be modern browser
(html5)
development will be
at:-
- [http://mysail.co.uk](http://mysail.co.uk/)
my original approach
the easiest -
using php to
generate a web ‘app’
(ish) is old hat.
such an approach
cannot be cached
locally nor turned
into a native app.
there is some
backend server stuff
to save files to
sailwave - but you
can also save files
locally - all the
server stuff is
optional.
the new app spec
dumps aliases and
replaces them with
the ability to apply
N scoring systems
keeping N sets of
results. all
objects like
competitors (called
entries now) and
races etc have user
definable content
via templates. the
new design is in
fact much more
flexible than the
old one. lots of
other changes like
have N penalty codes
and redress codes in
addition to
retirement codes.
user will be able
ablt to write their
own scoring systems
using javascript. i
will suppoy appendix
a initially.
addendum c later
unless somebody else
does it…
ps: the current
(few) pages are
smartphone
orientated - jquery
mobile tablet
support is on its
way - what will
happen is that the
menus will stay
fixed on the left
with content on the
right rather than a
new page when a menu
it hit as phone
smart phones.
massive amout of
work
i will probably
charge something
nominal a year
(subscription) to
use this new
sailwave.
--
Cheers,
Colin J
[http://sailwave.com](http://sailwave.com/)
No
virus found in this message.
Checked by AVG - [www.avg.com](http://www.avg.com/)
Version: 2012.0.2197 / Virus
Database: 2437/5234 - Release
Date: 08/29/12
No virus found
in this message.
Checked by AVG - [www.avg.com](http://www.avg.com/)
Version: 2012.0.2197 / Virus Database:
2437/5234 - Release Date: 08/29/12
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 - Release Date:
08/29/12
You may be far enough along now to not consider a change of platform, but what about doing the development in .NET/Mono? There's a .NET development platform for Android (it costs USD$400, but I think you could convince us Sailwave users to defray your cost). That would give you something that would be cross-platform compatible between Android, Windows and Linux. There is even an IOS development platform for .NET.
Additionally, I think I could convince Charlie to offer up some features of Committee Boat Suite, which is written in .NET. Possibly some sort of modular approach that would allow plugging in things like course design, finish times, course time prediction, etc. (Charlie is probably rolling his eyes as he reads this! )
Have you considered open-sourcing the project? That's worked really well for all sorts of products, and can take a lot of the work off your shoulders. I would also suggest separating the scoring engine from the web app, so people could experiment with different user interfaces or platforms. Speaking of platforms, making the scoring engine portable, e.g. portable C++, seems like a good long-term move too.
i have a notion to take micro payments for the ui - having lost
a shedload of pension in 2008! - however, yes, the actual
scoring api is totally separate and (will be) available in
various ways - firstly a json web ajax interface (probably) -
send it the data - get back the scores - my UI(s) will use this
interface and it will be PD and I hope other people will use it
for their own UIs. I may make the API (engine) open source but
not my UI… there will also be resources that users can add to
like rating libraries and scoring systems etc etc - those
mechanisms could be open source too.
Have you considered open-sourcing the project? That's
worked really well for all sorts of products, and can take
a lot of the work off your shoulders. I would also suggest
separating the scoring engine from the web app, so people
could experiment with different user interfaces or
platforms. Speaking of platforms, making the scoring
engine portable, e.g. portable C++, seems like a good
long-term move too.
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2437/5263 - Release Date:
09/11/12
You may be far enough along now to not consider a change
of platform, but what about doing the development in
.NET/Mono? There’s a .NET development platform for Android
(it costs USD$400, but I think you could convince us
Sailwave users to defray your cost). That would give you
something that would be cross-platform compatible between
Android, Windows and Linux. There is even an IOS
development platform for .NET.
Additionally, I think I could convince Charlie to offer up
some features of Committee Boat Suite, which is written in
.NET. Possibly some sort of modular approach that would
allow plugging in things like course design, finish times,
course time prediction, etc. (Charlie is probably rolling
his eyes as he reads this! )
Talk about a killer sail management app!
Andy
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5234 - Release Date:
08/29/12
)