A Publishing Script

Imported from Yahoo
1

For Fed Week publishing all fleets with individual race tables and summary tables produced an html page of close to 1Mb. I judged this to be too big for the web so reluctantly split it into six more manageable chunks and provided navigation via a page on the event website.

This was fine except generating 6 html files with different ‘What to publish’ settings plus printed versions for the noticeboard proved time consuming and error prone.

“It would be nice” if the whole operation could be scripted ahead of time so all that is needed is just the proverbial one click to publish on the day. Is it possible?

2

For one design classes there is not really much point in publishing the individual race tables.
For handicap racing the individual races will contain more and important information but these wont change after the race has been scored unless some historic results are changed.

So if you always publish the series summary and then have individual pages for the individual races this makes it quite efficient. At the end of the race publish the individual race to its specific page and publish the series summary to its page. This makes the publishing of results much more efficient.

One tip that you might find useful is, if you publish to a file there is a preview button which will also publish to the local browser. So in one publish operation you get a file for publishing to the web and a browser displaying the results from which you can print.

If you use the add page breaks - so that each fleet is on a new sheet of paper you can print only the fleets that have changed making the printing more efficient.

Jon

···

Jon Eskdale
07976 709777

Skype “eskdale”

On 30 August 2014 17:27, richard@radixsoftware.co.uk [sailwave] sailwave@yahoogroups.com wrote:

For Fed Week publishing all fleets with individual race tables and summary tables produced an html page of close to 1Mb. I judged this to be too big for the web so reluctantly split it into six more manageable chunks and provided navigation via a page on the event website.

This was fine except generating 6 html files with different ‘What to publish’ settings plus printed versions for the noticeboard proved time consuming and error prone.

“It would be nice” if the whole operation could be scripted ahead of time so all that is needed is just the proverbial one click to publish on the day. Is it possible?

3

Jon

Regarding individual race tables, we regularly use a single file for different fleets, some of which are raced on a position basis, and others on a timed handicap basis. Would it be easy to exclude race tables for the fleets racing on a position basis as we presently publish a single file to the web which is unnecessarily cluttered when we include the individual race tables for handicap races

Thanks

William Carruthers

···

Jon Eskdale
07976 709777

Skype “eskdale”

On 30 August 2014 17:27, richard@radixsoftware.co.uk [sailwave] sailwave@yahoogroups.com wrote:

For Fed Week publishing all fleets with individual race tables and summary tables produced an html page of close to 1Mb. I judged this to be too big for the web so reluctantly split it into six more manageable chunks and provided navigation via a page on the event website.

This was fine except generating 6 html files with different ‘What to publish’ settings plus printed versions for the noticeboard proved time consuming and error prone.

“It would be nice” if the whole operation could be scripted ahead of time so all that is needed is just the proverbial one click to publish on the day. Is it possible?

4

Jon,

We publish a webpage for each race, regardless of whether it is OD or
handicap since all our finishes include times and race results show the
time out of first for all boats (OD or handicap). And, of course, we
also publish series results. Putting everything on one page makes things
much too cluttered in our opinion and also breaks a basic web design
rule to avoid pages where it takes more than one (or possibly two)
clicks to scroll from top to bottom.

We have to have different settings depending on whether we are
publishing series or race results. A script that we could preset would
be very helpful in this regard. This idea was floated here some time
back and a fair number of people seemed to like the idea.

The script could also include file names. We are uncomfortable having
the Sailwave user need to remember what names to give files when
uploading via FTP. So, we don't use the FTP function in Sailwave but
instead have a separate program that automatically names files correctly
when uploading to the web. This could be part of the script with a slot
to pre-define file names according to some pattern (for example, series
= 2014FunRace.html; races = 2014FunRace_r0X.html).

We are doing just fine without scripts but they could be a BIG help to
the entry clerks.

Art

···

On 9/1/2014 3:01 PM, Jon Eskdale jon@sailwave.com [sailwave] wrote:

For one design classes there is not really much point in publishing the
individual race tables.
For handicap racing the individual races will contain more and important
information but these wont change after the race has been scored unless
some historic results are changed.

So if you always publish the series summary and then have individual pages
for the individual races this makes it quite efficient. At the end of the
race publish the individual race to its specific page and publish the
series summary to its page. This makes the publishing of results much more
efficient.

One tip that you might find useful is, if you publish to a file there is a
preview button which will also publish to the local browser. So in one
publish operation you get a file for publishing to the web and a browser
displaying the results from which you can print.

If you use the add page breaks - so that each fleet is on a new sheet of
paper you can print only the fleets that have changed making the printing
more efficient.

Jon

Jon Eskdale
07976 709777
Skype "eskdale"

On 30 August 2014 17:27, richard@radixsoftware.co.uk [sailwave] < > sailwave@yahoogroups.com> wrote:

For Fed Week publishing all fleets with individual race tables and summary
tables produced an html page of close to 1Mb. I judged this to be too big
for the web so reluctantly split it into six more manageable chunks and
provided navigation via a page on the event website.

This was fine except generating 6 html files with different �What to
publish� settings plus printed versions for the noticeboard proved time
consuming and error prone.

�It would be nice� if the whole operation could be scripted ahead of time
so all that is needed is just the proverbial one click to publish on the
day. Is it possible?

5

Hi Art,

You are correct - I did start looking at having presets for publishing some time ago but everyones requirements, although they all seem logical to them were all different which made the implementation messy. Then start adding where do you store these - in the sailwave file or elsewhere because users say they don’t want to enter them for each series etc. I can see the advantages for some users - may be I’ll look at what can be done with the Messaging interface. This weekend I have scoring at the NWF (National Watersports Festival) followed by next weekend scoring at the NWC (National Windsurfing Championship) both big events to score so I’m going to be busy for next couple of weekends

···

Jon Eskdale
07976 709777

Skype “eskdale”

On 2 September 2014 21:49, Art Engel artengel123@earthlink.net [sailwave] sailwave@yahoogroups.com wrote:

Jon,

We publish a webpage for each race, regardless of whether it is OD or

handicap since all our finishes include times and race results show the

time out of first for all boats (OD or handicap). And, of course, we

also publish series results. Putting everything on one page makes things

much too cluttered in our opinion and also breaks a basic web design

rule to avoid pages where it takes more than one (or possibly two)

clicks to scroll from top to bottom.

We have to have different settings depending on whether we are

publishing series or race results. A script that we could preset would

be very helpful in this regard. This idea was floated here some time

back and a fair number of people seemed to like the idea.

The script could also include file names. We are uncomfortable having

the Sailwave user need to remember what names to give files when

uploading via FTP. So, we don’t use the FTP function in Sailwave but

instead have a separate program that automatically names files correctly

when uploading to the web. This could be part of the script with a slot

to pre-define file names according to some pattern (for example, series

= 2014FunRace.html; races = 2014FunRace_r0X.html).

We are doing just fine without scripts but they could be a BIG help to

the entry clerks.

Art

On 9/1/2014 3:01 PM, Jon Eskdale jon@sailwave.com [sailwave] wrote:

For one design classes there is not really much point in publishing the

individual race tables.

For handicap racing the individual races will contain more and important

information but these wont change after the race has been scored unless

some historic results are changed.

So if you always publish the series summary and then have individual pages

for the individual races this makes it quite efficient. At the end of the

race publish the individual race to its specific page and publish the

series summary to its page. This makes the publishing of results much more

efficient.

One tip that you might find useful is, if you publish to a file there is a

preview button which will also publish to the local browser. So in one

publish operation you get a file for publishing to the web and a browser

displaying the results from which you can print.

If you use the add page breaks - so that each fleet is on a new sheet of

paper you can print only the fleets that have changed making the printing

more efficient.

Jon

Jon Eskdale

07976 709777

Skype “eskdale”

On 30 August 2014 17:27, richard@radixsoftware.co.uk [sailwave] <

sailwave@yahoogroups.com> wrote:

For Fed Week publishing all fleets with individual race tables and summary

tables produced an html page of close to 1Mb. I judged this to be too big

for the web so reluctantly split it into six more manageable chunks and

provided navigation via a page on the event website.

This was fine except generating 6 html files with different ‘What to

publish’ settings plus printed versions for the noticeboard proved time

consuming and error prone.

“It would be nice” if the whole operation could be scripted ahead of time

so all that is needed is just the proverbial one click to publish on the

day. Is it possible?

-!- http://www.yachtsandyachting.com/ -!- http://www.sailing.org/ -!- http://www.sailwave.com/ -!- On-Line Sailwave help…http://sailwave.com/help/HTML ~ Mark Townsend’s Sailwave User Guide is available from http://www.abyc.org/upload/Sailwave_ABYC_User_Guide.pdf ~ Convert to daily digest of emails send blank email to sailwave-digest@yahoogroups.com ~ To unsubscribe from the SUG please send blank email to sailwave-unsubscribe@yahoogroups.com

Yahoo Groups Links

<*> To visit your group on the web, go to:

[http://groups.yahoo.com/group/sailwave/](http://groups.yahoo.com/group/sailwave/)

<*> Your email settings:

Individual Email | Traditional

<*> To change settings online go to:

[http://groups.yahoo.com/group/sailwave/join](http://groups.yahoo.com/group/sailwave/join)

(Yahoo! ID required)

<*> To change settings via email:

sailwave-digest@yahoogroups.com

sailwave-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:

sailwave-unsubscribe@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:

[https://info.yahoo.com/legal/us/yahoo/utos/terms/](https://info.yahoo.com/legal/us/yahoo/utos/terms/)
6

Regattas that I score frequently have one-design and handicapped fleets. It often happens that fleets have a different number of races. At the end of each day I publish each fleet separately in order to have summary tables with only the races sailed by the fleet and to have individual race tables only for handicap fleets. This can be a bit complex, takes time, and is subject to error. And the racers are usually anxious to see the results posted. A script or a set of options that enables the publishing options all to be set up once, edited as needed, and then executed with one command would be very helpful.

For publishing to the website, we often publish all fleets together. It would be nice to have the option of selecting to publish (or not) Individual race tables for each fleet when publishing all results together.

I find that the Summary table option “All sailed races” does omit the races not sailed by a fleet but the same option for Individual race tables DOES NOT omit races not sailed by a fleet: headings only are output for those races. Is this a bug? Because it works that way, I use the option “Just these races” and have to select the all the races that were sailed for each fleet, which takes time and care.

I would like to take this opportunity to thank Colin for this excellent program and Jon for joining in to continue with improvements and support.

Gordon

7

It would be possible to automate it using “AutoIt 3” https://www.autoitscript.com/site/autoit/ (It’s free)

You could do it now using this although with some customisation of Sailwave it could be made easier. - I’ll add it to my list but this weekend and next I’m tied up scoring 2 large events.

But don’t expect scripting to be a very straight forward job. All the scripting tools take time to learn - once you have done a few things it will get easier but unless the job is very repetitive or the time window to get it done is critical, then doing it manually will probably use less overall time. There is the advantage that it can reduce errors but will take some time testing.

Jon

···

Jon Eskdale
07976 709777

Skype “eskdale”

On 3 September 2014 20:07, wilkinson.gordon@gmail.com [sailwave] sailwave@yahoogroups.com wrote:

Regattas that I score frequently have one-design and handicapped fleets. It often happens that fleets have a different number of races. At the end of each day I publish each fleet separately in order to have summary tables with only the races sailed by the fleet and to have individual race tables only for handicap fleets. This can be a bit complex, takes time, and is subject to error. And the racers are usually anxious to see the results posted. A script or a set of options that enables the publishing options all to be set up once, edited as needed, and then executed with one command would be very helpful.

For publishing to the website, we often publish all fleets together. It would be nice to have the option of selecting to publish (or not) Individual race tables for each fleet when publishing all results together.

I find that the Summary table option “All sailed races” does omit the races not sailed by a fleet but the same option for Individual race tables DOES NOT omit races not sailed by a fleet: headings only are output for those races. Is this a bug? Because it works that way, I use the option “Just these races” and have to select the all the races that were sailed for each fleet, which takes time and care.

I would like to take this opportunity to thank Colin for this excellent program and Jon for joining in to continue with improvements and support.

Gordon

8

Another way is to use scripting on the server. upload the published results as one glob (once) but treat it as a data file - in fact click the opion to publish as javascript - it’s all in data structures then. run a server script (php,asp,node.js, whatever) (once) to read that file and bust it up into lots of small files that are linked to and served by the website. it’s not hard to parse the sailwave html tables or javascript data structures.

nb: once == once per results changing and need to be published kind of once.

···

Cheers,

Colin J

http://sailwave.com

On Wed, Sep 3, 2014 at 11:28 PM, Jon Eskdale jon@sailwave.com [sailwave] sailwave@yahoogroups.com wrote:

It would be possible to automate it using “AutoIt 3” https://www.autoitscript.com/site/autoit/ (It’s free)

You could do it now using this although with some customisation of Sailwave it could be made easier. - I’ll add it to my list but this weekend and next I’m tied up scoring 2 large events.

But don’t expect scripting to be a very straight forward job. All the scripting tools take time to learn - once you have done a few things it will get easier but unless the job is very repetitive or the time window to get it done is critical, then doing it manually will probably use less overall time. There is the advantage that it can reduce errors but will take some time testing.

Jon

Jon Eskdale
07976 709777

Skype “eskdale”

On 3 September 2014 20:07, wilkinson.gordon@gmail.com [sailwave] sailwave@yahoogroups.com wrote:

Regattas that I score frequently have one-design and handicapped fleets. It often happens that fleets have a different number of races. At the end of each day I publish each fleet separately in order to have summary tables with only the races sailed by the fleet and to have individual race tables only for handicap fleets. This can be a bit complex, takes time, and is subject to error. And the racers are usually anxious to see the results posted. A script or a set of options that enables the publishing options all to be set up once, edited as needed, and then executed with one command would be very helpful.

For publishing to the website, we often publish all fleets together. It would be nice to have the option of selecting to publish (or not) Individual race tables for each fleet when publishing all results together.

I find that the Summary table option “All sailed races” does omit the races not sailed by a fleet but the same option for Individual race tables DOES NOT omit races not sailed by a fleet: headings only are output for those races. Is this a bug? Because it works that way, I use the option “Just these races” and have to select the all the races that were sailed for each fleet, which takes time and care.

I would like to take this opportunity to thank Colin for this excellent program and Jon for joining in to continue with improvements and support.

Gordon