I’ve been writing Javascript a lot recently and realised a useful
publishing aaddition (doh). Publish to ‘javascript’ - what happens
is that a browser fires up containing some Sailwave contributed
javascript - essentially a load of object declarations representing
the series/results - and some user contributed javascript spliced in
from a file.
Your options are then endless - you can enumerate the objects to
create HTML/XML/JSON or - more usefully - use Ajax (for example) to
update something server-side - e.g. a mysql database.
In this way you have complete control of the results - and not only
results - you can generate anything you like - from the sailwave
data…
In progress.
This is also the way to go WRT scripting - use Javascript - it's a
but trickier because Javascript can’t write local files but there is
a way around that.
lot recently and realised a useful publishing aaddition
(doh). Publish to ‘javascript’ - what happens is that a
browser fires up containing some Sailwave contributed
javascript - essentially a load of object declarations
representing the series/results - and some user
contributed javascript spliced in from a file.
Your options are then endless - you can enumerate the
objects to create HTML/XML/JSON or - more usefully - use
Ajax (for example) to update something server-side -
e.g. a mysql database.
In this way you have complete control of the results -
and not only results - you can generate anything you
like - from the sailwave data…
In progress.
This is also the way to go WRT scripting - use
Javascript - it’s a but trickier because Javascript
can’t write local files but there is a way around that.
--
No virus found in
this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 - Release Date:
02/08/11
On Tue, 08 Feb 2011 13:56:08 +0000, Colin Jenkins wrote:
I’ve been writing Javascript a lot recently and realised a useful publishing aaddition (doh). Publish to ‘javascript’ - what happens is that a browser fires up containing some Sailwave contributed javascript - essentially a load of object declarations representing the series/results - and some user contributed javascript spliced in from a file.
Your options are then endless - you can enumerate the objects to create HTML/XML/JSON or - more usefully - use Ajax (for example) to update something server-side - e.g. a mysql database.
In this way you have complete control of the results - and not only results - you can generate anything you like - from the sailwave data…
In progress.
This is also the way to go WRT scripting - use Javascript - it’s a but trickier because Javascript can’t write local files but there is a way around that.
–
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 - Release Date: 02/08/11
yes, but the installer installs it when it
installs an adobe air app if not already installed. it had the
advantage of being aboe to write client side files… closing the
loop back to Sailwave… I’d prefer to use vanilla JS but Air has
another advantage in that it would be a standardized JS env, not
an arbotrary one based on the browser, so assumptions could me
made in scripts. Just thinnking aloud at this stage. I was gong
to use Lua but I’ve gone off it - it’s too ‘academic’.
and realised a useful publishing aaddition
(doh). Publish to ‘javascript’ - what happens
is that a browser fires up containing some
Sailwave contributed javascript - essentially
a load of object declarations representing the
series/results - and some user contributed
javascript spliced in from a file.
Your options are then endless - you can
enumerate the objects to create HTML/XML/JSON
or - more usefully - use Ajax (for example) to
update something server-side - e.g. a mysql
database.
In this way you have complete control of the
results - and not only results - you can
generate anything you like - from the sailwave
data…
In progress.
This is also the way to go WRT scripting - use
Javascript - it’s a but trickier because
Javascript can’t write local files but there
is a way around that.
--
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 -
Release Date: 02/08/11
Colin,
Is Sailwave up to date on the Snipe 20% penalty for premature starters when a Z Flag has been raised? If they do it twice under a Z flag for the same race, it goes to 40%, etc…
lot recently and realised a useful publishing aaddition
(doh). Publish to ‘javascript’ - what happens is that a
browser fires up containing some Sailwave contributed
javascript - essentially a load of object declarations
representing the series/results - and some user
contributed javascript spliced in from a file.
Your options are then endless - you can enumerate the
objects to create HTML/XML/JSON or - more usefully - use
Ajax (for example) to update something server-side -
e.g. a mysql database.
In this way you have complete control of the results -
and not only results - you can generate anything you
like - from the sailwave data…
In progress.
This is also the way to go WRT scripting - use
Javascript - it’s a but trickier because Javascript
can’t write local files but there is a way around that.
--
No virus found in
this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 - Release Date:
02/08/11
That's very interesting, particularly in light of the discussion about Joomla integration. Just having a method for updating the database on the server, and then having a Joomla module that takes that data and displays it, would be a great way to integrate with Joomla.
At the risk of hijacking this thread, anyone have thoughts on what a Joomla module for Sailwave results might look like? I'm thinking you could create some sort of Section / Category methodology similar to the way Articles are published now, the "Section" being the event and "Category" being race or something.
I agree - it seems like a simple and very flexible way to update
any server side stuff, esp using Ajax. I’ll get something working
ASAP. It wcould update results, competitor lists - anything that
is in sailwave to be exploited in fact…
That's very interesting, particularly in light of the discussion about Joomla integration. Just having a method for updating the database on the server, and then having a Joomla module that takes that data and displays it, would be a great way to integrate with Joomla.
At the risk of hijacking this thread, anyone have thoughts on what a Joomla module for Sailwave results might look like? I'm thinking you could create some sort of Section / Category methodology similar to the way Articles are published now, the "Section" being the event and "Category" being race or something.
------------------------------------
-!- -!- -!- -!- On-Line Sailwave help...http://sailwave.com/help/HTML ~ Mark Townsend's Sailwave User Guide is available from ~ Convert to daily digest of emails send blank email to ~ To unsubscribe from the SUG please send blank email to Yahoo! Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
-----
No virus found in this message.
Checked by AVG - Version: 10.0.1204 / Virus Database: 1435/3431 - Release Date: 02/08/11
On Tue, 08 Feb 2011 13:56:08 +0000, Colin Jenkins wrote:
I've been writing
Javascript a lot recently and realised a useful
publishing aaddition (doh). Publish to ‘javascript’
what happens is that a browser fires up containing
some Sailwave contributed javascript - essentially a
load of object declarations representing the
series/results - and some user contributed
javascript spliced in from a file.
Your options are then endless - you can enumerate
the objects to create HTML/XML/JSON or - more
usefully - use Ajax (for example) to update
something server-side - e.g. a mysql database.
In this way you have complete control of the results
and not only results - you can generate anything
you like - from the sailwave data…
In progress.
This is also the way to go WRT scripting - use
Javascript - it’s a but trickier because Javascript
can’t write local files but there is a way around
that.
--
No virus found
in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 - Release
Date: 02/08/11
This is not something that Sailwave would know about, it is
something that can be set-up in Sailwave though. You just need to
create additional scoring codes ZFP40, ZFP60 etc as ZFP is
already defined for an initial starting penalty under RRS 30.2 Z
Flag Rule.
In case you are not aware of how to create the additional scoring
codes:
click scoring button on toolbar
click scoring codes tab in window that pops up
click ZFP code at bottom of list to highlight then click New
button on right hand side an dthis will create a copy of the ZFP
code called New ZFP
double click New ZFP to edit
rename code ZFP40 in code field
change value to 40 in Value field
click OK to save
repeat steps 3 to 7 and in step 5 rename code to ZFP60 and
change value to 60
click OK in Edit Scoring System window to exit and the save
the file.
If you need you can also repeat steps to create a code for an 80%
penalty in the same way etc.
Save the Sailwave file
**Note** -
these changes are only saved in the Sailwave file you have open
unless you have edited a Sailwave you are using as a template for
future events.
On Tue, 08 Feb 2011 13:56:08 +0000, Colin Jenkins wrote:
I've been writing
Javascript a lot recently and realised a
useful publishing aaddition (doh). Publish
to ‘javascript’ - what happens is that a
browser fires up containing some Sailwave
contributed javascript - essentially a load
of object declarations representing the
series/results - and some user contributed
javascript spliced in from a file.
Your options are then endless - you can
enumerate the objects to create
HTML/XML/JSON or - more usefully - use Ajax
(for example) to update something
server-side - e.g. a mysql database.
In this way you have complete control of the
results - and not only results - you can
generate anything you like - from the
sailwave data…
In progress.
This is also the way to go WRT scripting -
use Javascript - it’s a but trickier because
Javascript can’t write local files but there
is a way around that.
--
No
virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 -
Release Date: 02/08/11
On Tue, 08 Feb 2011 13:56:08 +0000, Colin Jenkins wrote:
I've been writing
Javascript a lot recently and realised a
useful publishing aaddition (doh). Publish
to ‘javascript’ - what happens is that a
browser fires up containing some Sailwave
contributed javascript - essentially a load
of object declarations representing the
series/results - and some user contributed
javascript spliced in from a file.
Your options are then endless - you can
enumerate the objects to create
HTML/XML/JSON or - more usefully - use Ajax
(for example) to update something
server-side - e.g. a mysql database.
In this way you have complete control of the
results - and not only results - you can
generate anything you like - from the
sailwave data…
In progress.
This is also the way to go WRT scripting -
use Javascript - it’s a but trickier because
Javascript can’t write local files but there
is a way around that.
--
No
virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 -
Release Date: 02/08/11
Unless they've said something specific to make it always be 40% for two infractions then you have to be careful with this - because of rounding, two 20% penalties might not be exactly the same as one 40% penalty.
···
On 10/02/2011 5:40 a.m., Huw Pearce wrote:
Hi Fred,
This is not something that Sailwave would know about, it is something
that can be set-up in Sailwave though. You just need to create
additional scoring codes ZFP40, ZFP60 /etc/ as ZFP is already defined
for an initial starting penalty under RRS 30.2 Z Flag Rule.
In case you are not aware of how to create the additional scoring codes:
1. click scoring button on toolbar
2. click scoring codes tab in window that pops up
3. click ZFP code at bottom of list to highlight then click New
button on right hand side an dthis will create a copy of the ZFP
code called New ZFP
4. double click New ZFP to edit
5. rename code ZFP40 in code field
6. change value to 40 in Value field
7. click OK to save
8. repeat steps 3 to 7 and in step 5 rename code to ZFP60 and change
value to 60
9. click OK in Edit Scoring System window to exit and the save the file.
If you need you can also repeat steps to create a code for an 80%
penalty in the same way /etc/.
Save the Sailwave file
*Note *- these changes are only saved in the Sailwave file you have open
unless you have edited a Sailwave you are using as a template for future
events.
Hope t his helps.
Kind regards,
Huw
On 09/02/2011 15:43, Colin Jenkins wrote:
Pass on taht Fred - Huw may know - you';l; have to try it...
Colin,
Is Sailwave up to date on the Snipe 20% penalty for premature
starters when a Z Flag has been raised? If they do it twice under a Z
flag for the same race, it goes to 40%, etc....
On Tue, 08 Feb 2011 13:56:08 +0000, Colin Jenkins >>>> <colin@sailwave.com> wrote:
I've been writing Javascript a lot recently and realised a
useful publishing aaddition (doh). Publish to 'javascript' -
what happens is that a browser fires up containing some Sailwave
contributed javascript - essentially a load of object
declarations representing the series/results - and some user
contributed javascript spliced in from a file.
Your options are then endless - you can enumerate the objects to
create HTML/XML/JSON or - more usefully - use Ajax (for example)
to update something server-side - e.g. a mysql database.
In this way you have complete control of the results - and not
only results - you can generate anything you like - from the
sailwave data...
In progress.
This is also the way to go WRT scripting - use Javascript - it's
a but trickier because Javascript can't write local files but
there is a way around that.
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 10.0.1204 / Virus Database: 1435/3430 - Release Date: 02/08/11
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 10.0.1204 / Virus Database: 1435/3431 - Release Date: 02/08/11
In a twelve boat fleet, 20% is 2.4 which when rounded give a 2 point scoring penaly. However when a boat receives two ZFP, two 20% penalties is equal to 4 points, but if you use a 40% penalty instead, 40% is 4.8 which rounds to 5 points, which is wrong.
Hi Fred,
This is not something that Sailwave would know about, it is something that can be set-up in Sailwave though. You just need to create additional scoring codes ZFP40, ZFP60 etc as ZFP is already defined for an initial starting penalty under RRS 30.2 Z Flag Rule.
In case you are not aware of how to create the additional scoring codes:
click scoring button on toolbar
click scoring codes tab in window that pops up
click ZFP code at bottom of list to highlight then click New button on right hand side an dthis will create a copy of the ZFP code called New ZFP
double click New ZFP to edit
rename code ZFP40 in code field
change value to 40 in Value field
click OK to save
repeat steps 3 to 7 and in step 5 rename code to ZFP60 and change value to 60
click OK in Edit Scoring System window to exit and the save the file.
If you need you can also repeat steps to create a code for an 80% penalty in the same way etc.
Save the Sailwave file Note - these changes are only saved in the Sailwave file you have open unless you have edited a Sailwave you are using as a template for future events.
Hope t his helps.
Kind regards,
Huw
On 09/02/2011 15:43, Colin Jenkins wrote:
Pass on taht Fred - Huw may know - you’;l; have to try it…
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
On 09/02/2011 13:14, Fred Welker wrote:
Colin,
Is Sailwave up to date on the Snipe 20% penalty for premature starters when a Z Flag has been raised? If they do it twice under a Z flag for the same race, it goes to 40%, etc…
On Tue, 08 Feb 2011 13:56:08 +0000, Colin Jenkins colin@sailwave.com wrote:
I’ve been writing Javascript a lot recently and realised a useful publishing aaddition (doh). Publish to ‘javascript’ - what happens is that a browser fires up containing some Sailwave contributed javascript - essentially a load of object declarations representing the series/results - and some user contributed javascript spliced in from a file.
Your options are then endless - you can enumerate the objects to create HTML/XML/JSON or - more usefully - use Ajax (for example) to update something server-side - e.g. a mysql database.
In this way you have complete control of the results - and not only results - you can generate anything you like - from the sailwave data…
In progress.
This is also the way to go WRT scripting - use Javascript - it’s a but trickier because Javascript can’t write local files but there is a way around that.
–
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430 - Release Date: 02/08/11
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3431 - Release Date: 02/08/11
This is not something that Sailwave would know about,
it is something that can be set-up in Sailwave though.
You just need to create additional scoring codes
ZFP40, ZFP60 etc as ZFP is already defined for
an initial starting penalty under RRS 30.2 Z Flag
Rule.
In case you are not aware of how to create the
additional scoring codes:
click scoring button on toolbar
click scoring codes tab in window that pops up
click ZFP code at bottom of list to highlight
then click New button on right hand side an dthis
will create a copy of the ZFP code called New ZFP
double click New ZFP to edit
rename code ZFP40 in code field
change value to 40 in Value field
click OK to save
repeat steps 3 to 7 and in step 5 rename code to
ZFP60 and change value to 60
click OK in Edit Scoring System window to exit
and the save the file.
If you need you can also repeat steps to create a code
for an 80% penalty in the same way etc.
Save the Sailwave file
**Note** -
these changes are only saved in the Sailwave file you
have open unless you have edited a Sailwave you are
using as a template for future events.
Hope t his helps.
Kind regards,
Huw
On 09/02/2011 15:43, Colin Jenkins wrote:
�
Pass on taht Fred - Huw
may know - you’;l; have to try it…
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
On 09/02/2011 13:14, Fred Welker wrote:
Colin,
Is Sailwave up to date on the Snipe 20% penalty
for premature starters when a Z Flag has been
raised? If they do it twice under a Z flag for
the same race, it goes to 40%, etc…
Fred Welker
fredwelker@aol.com
Sent via BlackBerry by AT&T
�
I’ve been writing Javascript a lot
recently and realised a useful
publishing aaddition (doh).� Publish
to ‘javascript’ - what happens is
that a browser fires up containing
some Sailwave contributed javascript
essentially a load of object
declarations representing the
series/results - and some user
contributed javascript spliced in
from a file.�
Your options are then endless - you
can enumerate the objects to create
HTML/XML/JSON or - more usefully -
use Ajax (for example) to update
something server-side - e.g. a mysql
database.
In this way you have complete
control of the results - and not
only results - you can generate
anything you like - from the
sailwave data…
In progress.
This is also the way to go WRT
scripting - use Javascript - it’s a
but trickier because Javascript
can’t write local files but there is
a way around that.
--
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
�
�
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database:
1435/3430 - Release Date: 02/08/11
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3431
And in a 13 boat fleet, 20% is 2.6 rounded to 3 and 2 ZFP are 6, not 5.2 rounded to 5.
If this occurs, you can solve the problem by setting codes ZFP40 or ZPF2 as 4 (or 6) and ZFP60 or ZFP3 as 6 (or 9). (see if a code beginning by a digit is accepted, it coud also be 2ZFP, 3ZFP). A formula used with Excel is kround(0.2starters;0), k being 2 for 2 ZFP and 3 for 3 ZFP, see if the syntax of SW accepts this.
In a twelve boat fleet, 20% is 2.4 which when rounded give a 2 point scoring penaly. However when a boat receives two ZFP, two 20% penalties is equal to 4 points, but if you use a 40% penalty instead, 40% is 4.8 which rounds to 5 points, which is wrong.
Hi Fred,
This is not something that Sailwave would know about, it is something that can be set-up in Sailwave though. You just need to create additional scoring codes ZFP40, ZFP60 etc as ZFP is already defined for an initial starting penalty under RRS 30.2 Z Flag Rule.
In case you are not aware of how to create the additional scoring codes:
click scoring button on toolbar
click scoring codes tab in window that pops up
click ZFP code at bottom of list to highlight then click New button on right hand side an dthis will create a copy of the ZFP code called New ZFP
double click New ZFP to edit
rename code ZFP40 in code field
change value to 40 in Value field
click OK to save
repeat steps 3 to 7 and in step 5 rename code to ZFP60 and change value to 60
click OK in Edit Scoring System window to exit and the save the file.
If you need you can also repeat steps to create a code for an 80% penalty in the same way etc.
Save the Sailwave file Note - these changes are only saved in the Sailwave file you have open unless you have edited a Sailwave you are using as a template for future events.
Hope t his helps.
Kind regards,
Huw
On 09/02/2011 15:43, Colin Jenkins wrote:
Pass on taht Fred - Huw may know - you';l; have to try it...
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
On 09/02/2011 13:14, Fred Welker wrote:
Colin,
Is Sailwave up to date on the Snipe 20% penalty for premature starters when a Z Flag has been raised? If they do it twice under a Z flag for the same race, it goes to 40%, etc…
Subject: Re: [sailwave] new publishing method - javascript
i think those days are over. in my experience most modern websites simply would not work w/o javascript.
afaik all browers implement it - including iphones etc.
however an alternative would be to fire up an adobe air app...
cj
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
On 08/02/2011 23:18, yahoo@wittongilbert.free-online.co.uk > > > wrote:
Have the days of js being considered evil gone?
Or do you still get browsers that cant play?
On Tue, 08 Feb 2011 13:56:08 +0000, Colin Jenkins <colin@sailwave.com> > > > > wrote:
I've been writing Javascript a lot recently and realised a useful publishing aaddition (doh). Publish to 'javascript' - what happens is that a browser fires up containing some Sailwave contributed javascript - essentially a load of object declarations representing the series/results - and some user contributed javascript spliced in from a file.
Your options are then endless - you can enumerate the objects to create HTML/XML/JSON or - more usefully - use Ajax (for example) to update something server-side - e.g. a mysql database.
In this way you have complete control of the results - and not only results - you can generate anything you like - from the sailwave data...
In progress.
This is also the way to go WRT scripting - use Javascript - it's a but trickier because Javascript can't write local files but there is a way around that.
–
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
the nCODE syntax is a possibility and in fact
the easiest solution for me.
the proper solution imo is to add a new field for penalty and/or
redress codes in addition to any retirement codes (existing field
which is overworked at present)
howener, nCODE would be an order of magnitude easier to implement.
is everybody happy with that?
e.g. "3ZFP" or "3 ZPF" means apply ZFP 3 times.
it doesn't stop you having ZFP2 codes for example if the SIs go
that way - which can them use used as nCODE in the same way.
20% is 2.6 rounded to 3 and 2 ZFP are 6, not 5.2 rounded to 5.
�
If this occurs, you can
solve the problem by setting codes ZFP40 or ZPF2 as 4 (or 6)
and ZFP60 or ZFP3 as 6 (or 9).� (see if a code beginning by a
digit is accepted, it coud also be 2ZFP, 3ZFP).� A formula
used with Excel is kround(0.2starters;0), k being 2 for 2
ZFP and 3 for 3 ZFP, see if the syntax of SW accepts this.
�
In a twelve boat fleet, 20% is 2.4 which when rounded give a 2
point scoring penaly. However when a boat receives two ZFP, two
20% penalties is equal to 4 points, but if you use a 40% penalty
instead, 40% is�4.8 which rounds to 5 points, which is wrong.
�
Mark Townsend
s_mark_townsend@hotmail.com
(562) 433-4366 - Home
(562) 533-5909 - Cell
�
To: From: Date: Wed, 9 Feb 2011 16:40:34 +0000
Subject: Re: [sailwave] new publishing method - javascript
No virus found in
this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3432 - Release Date:
02/09/11
This is not something that Sailwave would know about, it
is something that can be set-up in Sailwave though. You
just need to create additional scoring codes ZFP40, ZFP60 etc as ZFP is already defined for an initial
starting penalty under RRS 30.2 Z Flag Rule.
In case you are not aware of how to create the additional
scoring codes:
click scoring button on toolbar
click scoring codes tab in window that pops up
click ZFP code at bottom of list to highlight then
click New button on right hand side an dthis will
create a copy of the ZFP code called New ZFP
double click New ZFP to edit
rename code ZFP40 in code field
change value to 40 in Value field
click OK to save
repeat steps 3 to 7 and in step 5 rename code to
ZFP60 and change value to 60
click OK in Edit Scoring System window to exit and
the save the file.
If you need you can also repeat steps to create a code for
an 80% penalty in the same way etc.
Save the Sailwave file
**Note** -
these changes are only saved in the Sailwave file you have
open unless you have edited a Sailwave you are using as a
template for future events.
Hope t his helps.
Kind regards,
Huw
On 09/02/2011 15:43, Colin Jenkins wrote:
�
Pass on taht Fred - Huw may
know - you’;l; have to try it…
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
On 09/02/2011 13:14, Fred Welker wrote:
Colin,
Is Sailwave up to date on the Snipe 20% penalty for
premature starters when a Z Flag has been raised? If
they do it twice under a Z flag for the same race,
it goes to 40%, etc…
Fred Welker
fredwelker@aol.com
Sent via BlackBerry by AT&T
�
I’ve been writing
Javascript a lot recently and realised a
useful publishing aaddition (doh).�
Publish to ‘javascript’ - what happens
is that a browser fires up containing
some Sailwave contributed javascript -
essentially a load of object
declarations representing the
series/results - and some user
contributed javascript spliced in from a
file.�
Your options are then endless - you can
enumerate the objects to create
HTML/XML/JSON or - more usefully - use
Ajax (for example) to update something
server-side - e.g. a mysql database.
In this way you have complete control of
the results - and not only results - you
can generate anything you like - from
the sailwave data…
In progress.
This is also the way to go WRT scripting
use Javascript - it’s a but trickier
because Javascript can’t write local
files but there is a way around that.
--
Regards,
Colin J
[www.sailwave.com](http://www.sailwave.com/)
�
�
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3430
Release Date: 02/08/11
No virus found in
this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3431 -
Release Date: 02/08/11
I had a look around for possible candidate Joomla components for integration with SailWave. I'm lazy and would much rather leverage an existing component than try to learn how to build Joomla components from scratch.
It appears that this components supports plug-ins, so it might be worth contacting the developer and getting a better understanding of how the Sailwave and JPodium might be integrated.
Sailwave for recording, calculations, scoring and all that good stuff, JPodium for display under Joomla. Maybe it'll work!
I had a look around for possible candidate Joomla components for integration with SailWave. I'm lazy and would much rather leverage an existing component than try to learn how to build Joomla components from scratch.
I came up with JPodium (). I found a couple of examples of sailing clubs using this component, here's one: .
It appears that this components supports plug-ins, so it might be worth contacting the developer and getting a better understanding of how the Sailwave and JPodium might be integrated. Sailwave for recording, calculations, scoring and all that good stuff, JPodium for display under Joomla. Maybe it'll work!
------------------------------------
-!- -!- -!- -!- On-Line Sailwave help...http://sailwave.com/help/HTML ~ Mark Townsend's Sailwave User Guide is available from ~ Convert to daily digest of emails send blank email to ~ To unsubscribe from the SUG please send blank email to Yahoo! Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
-----
No virus found in this message.
Checked by AVG - Version: 10.0.1204 / Virus Database: 1435/3433 - Release Date: 02/09/11
)