Publishing to Web Site

Colin,

I’ve an example under 1.93 Build 3

Were the changes introcuced after this version?

Just an example of very light files using javascript on http://www.microclass.org/results/platetaille06.html (1.93 kB)

The file is very small, the results are in a separate file http://www.microclass.org/results/MEH06.js
(3.65 kB) as the same results are also published on other places with different lay-outs, see http://www.microclass.be/results/MEH06.html (0.9 kB),nd there is also a file functions.js in both results directories of the web sites (14 and 17 kB), but they could be included in the as a function, and the style sheets .css are common to many other pages… but the relevant part is very limited.

There is no significant gain with such a limited number of boats, but the variable part does not exceed 0,18 kB per boat… son a full package for 100 boats should be approx 35 kB…

Philippe

···

----- Original Message -----

From:
Colin Jenkins

To: sailwave@yahoogroups.com

Sent: Monday, January 08, 2007 6:26 PM

Subject: RE: [sailwave] Re: Publishing to Web Site

Hi Philippe,

Can you take a set of results from the latest Sailwave version and show me what you mean with a small before and after example. Or do you mean link to the style sheets rather than incorporating them inline…? Currenty the style section is tiny - much smnaller than earlier versions of Sailwave… What did you have in mind WRT javascript. To date I’ve tried to balance simplicity with size so that there are not any browser dependent issues…

Regards,
Colin
www.sailwave.com

-----Original Message-----
From:
sailwave@yahoogroup s.com [mailto:sailwave@yahoogroups.com]On Behalf Of FFYB Web Manager
Sent: 08 January 2007 17:01
To:
sailwave@yahoogroups.com
Subject: Re: [sailwave] Re: Publishing to Web Site

Broadband ma be slow for upload, sometimes not faster than a standard ISDN.
For upload, you could use the free FTP software Filezilla ([http://filezilla.sourceforge.net/](http://filezilla.sourceforge.net/)    ), and compare the upload times...
For me, a weak point of sailwave is that there is a poor use of cascading style sheets, so the same style could be defined deveral times with the same description and different (long) names...
This could be an improvement, even if download is not really affected, at least for those who are no longer unsing a conventional modem connection. 
There was a similar problem in the Frenche software FReg, and I made a propsal to organise the use of the style sheets, reducing the file size by 40 to 60%, a another proposal using javascript reduced the size by a further 50%, but was never developed. 

Philippe De Troy

----- Original Message -----

From: Alan Jones

To: sailwave@yahoogroups.com

Sent: Monday, January 08, 2007 5:29 PM

Subject: [sailwave] Re: Publishing to Web Site

  Why not just use the built-in FTP functionality. The way you are
  doing it seems to be using a sledgehammer to crack a walnut if you

are simply uploading the results pages only.

— In sailwave@yahoogroups.com , “Mike Croker” <mdcroker@…> wrote:

— In sailwave@yahoogroups.com , “fiona689389” <fchicks@> wrote:

Our Club publishes Sailwave results to a web site using
Contribute.

The site is made with Dreamweaver. With only two small logos at
the

head of the page the results seem to take a very long time to
upload.

A typical class would be up to fifteen boats on a PY handicap
system

and I upload that evening’s race together with the cumulative
results

table. At a regatta type event I would be publishing 3 or 4
races with

the overall table.

Is this likely to be a problem with our system locally, we are on
broadband, or do these software programmes not handle Sailwave
results

well?

Any sensible suggestions welcomed.

Fiona

I just publish our results direct from Sailwave. Works fine (and
fast) for us.
Mike Croker
Lancing SC (www.lancingsc.org.uk)