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?
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?
The Sailwave results (in html) just contain a link to the event and venue logos.
If these are already on your website, it is not necessary to upload the picture files each time. Just set the link to the file locations on the website.
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?
how long is this piece of string?
1. Dreamweaver isn't part of the upload process (although you can
transfer to your website via Dreamweaver) -- at least that's what
Adobe's 'advert' for Contribute implies;
2. Contribute is presumably handling the upload & has some sort of
native ftp facility.
3. so why is it slow? slow is how fast? e.g. is it as slow to upload
other similar files to the same website (presumably you have built
other stuff with Dreamweaver & Contribute for the same website).
Sailwave files tend to be a bit big because of all the embedded CSS
(it would be nice to separate out the HTML/XHTML/XML and the CSS...,
or haven't I been paying attention?) but they are only simple text
files & text whizzes along. even the graphics should be small (you are
using a web friendly format I assume), though there is no need to
duplicate them. Broadband isn't the same thing to all people. remember
you likely share it with quite a few other people & that 'up to 8 Mb'
only means 'and you'll never get as much as 8 Mb, and often a whole
lot less'. I find my main limiting factor is my local wireless
network. Do you get timed out? I'm wondering if there is some local
configuration feature for Contribute's transfers. Any Contribute users
out there?
what's the website? maybe something obvious there (to the geeks).
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?
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.
>
> 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
--- In sailwave@yahoogroups.com, "fiona689389" <fchicks@> wrote:
> 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)
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.
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.
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…
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.
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…