Jon,
Best wishes for your new `career' with Sailwave - trust you will be able to take it to new highs!
Echo thanks to Colin for this amazing programme.
I've just been able to run 2.5.5 beta - seems fine (but note that 2.5.6 is up already!)
Query - will you be able to tweak SW for RRS2013-2016 ? Not sure if its all, but RAF changes to RET and DPI must come in.
--
regards,
Malcolm Osborne
Sedgefield South Africa
Great work,
Will try run on my mac using WinOnX
Jon, when next update please change in Rating System from LYS to SRS (Svenskt Respitsystem)
//Anders
Skickat från min iPad
13 nov 2012 kl. 13:16 skrev Malcolm Osborne malcolmo@telkomsa.net:
Jon,
Best wishes for your new `career’ with Sailwave - trust you will be able
to take it to new highs!Echo thanks to Colin for this amazing programme.
I’ve just been able to run 2.5.5 beta - seems fine (but note that 2.5.6
is up already!)Query - will you be able to tweak SW for RRS2013-2016 ? Not sure if its
all, but RAF changes to RET and DPI must come in.–
regards,
Malcolm Osborne
Sedgefield South Africa
Hi Malcom,
Thanks - And I agree Colin has produced the nicest scoring program around.
In fact 2.5.7 is up now I actually replaced 2.5.6 with 2.5.7 as the compiler managed to remove a patch I had done in an earlier version (still getting used to the environment - learning the hard way) .
No problem tweaking it for RRS2013-2016. DPI is already in the current version there is a DPI1 and as the codes are all user changeable then anyone can change the RAF to RET at any time they wish.
I will change the RAF to RET for the default when you start a new File. Do you think this should happen now as in the next build?
As I’ve said its quite a big learning curve and I’m getting there slowly so doing the easier things first. As I’ve been a regular user for many years there are a few of my little niggles which I will try to see if I can improve on first before we make any bigger changes.
e.g.
When entering using the Sailno Wizard short Sail nos such as 1 you always have to press the down arrow to select it because there is another such as 1043. I feel as long as there is only one 1 then you should be able to press enter and it accept it. - The Sailno Wizard I wrote for the Grand-Prix finish did this.
I know you can press enter on any cell and edit it but when you double click a cell although it takes you to that competitor it doesn’t place the cursor in the right place.
Little things but things that make the difference between the Best and the Greatest
Jon
On 13 November 2012 12:16, Malcolm Osborne malcolmo@telkomsa.net wrote:
Jon,
Best wishes for your new `career’ with Sailwave - trust you will be able
to take it to new highs!Echo thanks to Colin for this amazing programme.
I’ve just been able to run 2.5.5 beta - seems fine (but note that 2.5.6
is up already!)Query - will you be able to tweak SW for RRS2013-2016 ? Not sure if its
all, but RAF changes to RET and DPI must come in.–
regards,
Malcolm Osborne
Sedgefield South Africa
–
Jon Eskdale
07976 709777
Skype “eskdale”
John,
When trying to delete multiple races or competitors could you make it so you can use shift and select to highlight a group together in one go please?
Chris
On 13 November 2012 12:16, Malcolm Osborne malcolmo@telkomsa.net wrote:
Jon,
Best wishes for your new `career’ with Sailwave - trust you will be able
to take it to new highs!Echo thanks to Colin for this amazing programme.
I’ve just been able to run 2.5.5 beta - seems fine (but note that 2.5.6
is up already!)Query - will you be able to tweak SW for RRS2013-2016 ? Not sure if its
all, but RAF changes to RET and DPI must come in.–
regards,
Malcolm Osborne
Sedgefield South Africa
–
Jon Eskdale
07976 709777
Skype “eskdale”
Thanks Anders,
I’ve change it now so the next build will have it in
Jon
On 13 November 2012 12:40, Anders Landenstad anders@landenstad.se wrote:
Great work,
Will try run on my mac using WinOnX
Jon, when next update please change in Rating System from LYS to SRS (Svenskt Respitsystem)
//Anders
Skickat från min iPad
13 nov 2012 kl. 13:16 skrev Malcolm Osborne malcolmo@telkomsa.net:
Jon,
Best wishes for your new `career’ with Sailwave - trust you will be able
to take it to new highs!Echo thanks to Colin for this amazing programme.
I’ve just been able to run 2.5.5 beta - seems fine (but note that 2.5.6
is up already!)Query - will you be able to tweak SW for RRS2013-2016 ? Not sure if its
all, but RAF changes to RET and DPI must come in.–
regards,
Malcolm Osborne
Sedgefield South Africa
–
Jon Eskdale
07976 709777
Skype “eskdale”
Hi Chris,
I understand what you are saying but in the current version you can click on and highlight multiple races/competitors and delete them all in one go. Or if it is most of them that you want to delete, you can select all and then deselect the ones that you want to keep, I thought it worked quite well although I agree it is a little different than the norm.
Jon
On 13 November 2012 12:53, Chris Gandy chrisgandy@me.com wrote:
John,
When trying to delete multiple races or competitors could you make it so you can use shift and select to highlight a group together in one go please?
Chris
On 13 Nov 2012, at 12:43, Jon Eskdale jon@eskdale.org wrote:
Hi Malcom,
Thanks - And I agree Colin has produced the nicest scoring program around.
In fact 2.5.7 is up now I actually replaced 2.5.6 with 2.5.7 as the compiler managed to remove a patch I had done in an earlier version (still getting used to the environment - learning the hard way) .
No problem tweaking it for RRS2013-2016. DPI is already in the current version there is a DPI1 and as the codes are all user changeable then anyone can change the RAF to RET at any time they wish.
I will change the RAF to RET for the default when you start a new File. Do you think this should happen now as in the next build?
As I’ve said its quite a big learning curve and I’m getting there slowly so doing the easier things first. As I’ve been a regular user for many years there are a few of my little niggles which I will try to see if I can improve on first before we make any bigger changes.
e.g.
When entering using the Sailno Wizard short Sail nos such as 1 you always have to press the down arrow to select it because there is another such as 1043. I feel as long as there is only one 1 then you should be able to press enter and it accept it. - The Sailno Wizard I wrote for the Grand-Prix finish did this.
I know you can press enter on any cell and edit it but when you double click a cell although it takes you to that competitor it doesn’t place the cursor in the right place.
Little things but things that make the difference between the Best and the Greatest
Jon
–
Jon Eskdale
07976 709777
Skype “eskdale”
On 13 November 2012 12:16, Malcolm Osborne malcolmo@telkomsa.net wrote:
Jon,
Best wishes for your new `career’ with Sailwave - trust you will be able
to take it to new highs!Echo thanks to Colin for this amazing programme.
I’ve just been able to run 2.5.5 beta - seems fine (but note that 2.5.6
is up already!)Query - will you be able to tweak SW for RRS2013-2016 ? Not sure if its
all, but RAF changes to RET and DPI must come in.–
regards,
Malcolm Osborne
Sedgefield South Africa
–
Jon Eskdale
07976 709777
Skype “eskdale”
Hi Jon,
You solved the problem with age-groups and gender of helm and crew very well in/with beta 2.5.7.
But this evening with some time to test Your beta-versions I dispaired on publishing. Since Version 2.5.3 and all following beta-versions my javascript template will not work. I utilised javascript to translate English terms to German. Now I get a lot of lines with code like "sw.ser = {}; sw.ser.version = "2.5.7"; ..." instead of the tables by publishing to my browser (Firefox) or MS Word.
I recognised that You changed something about the javascript abilities of sailwave from beta 2.5.4 and beta 2.5.5, because there was same javascript code displayed before the race tables by using normal templates without javascript features.
I suspect, that You will have a lot of work with our complaining ...
But Sailwave is and will be the best scoring software!
With kind regards
Christof
Hi Christof,
Glad the age groups and gender are working OK. The JavaScript problem is in the Code which Colin passed to me when I took over. Apparently he has made some changes to it to make it more flexible but he hadn’t finished it all and it’s broken the JavaScript output. He does tell me he is going to fix it. It’s almost impossible for me to change that bit of code without starting from scratch as I don’t know what his intention was with it. The change from 2.5.4 to 2.5.5 was only to stop any JavaScript code outputting during the standard publish.
Sorry about the JavaScript output but hopefully Colin is reading this.
Jon
Sent from my iPad
On 14 Nov 2012, at 00:09, “paulesgps” paulesgps@yahoo.com wrote:
Hi Jon,
You solved the problem with age-groups and gender of helm and crew very well in/with beta 2.5.7.
But this evening with some time to test Your beta-versions I dispaired on publishing. Since Version 2.5.3 and all following beta-versions my javascript template will not work. I utilised javascript to translate English terms to German. Now I get a lot of lines with code like “sw.ser = {}; sw.ser.version = “2.5.7”; …” instead of the tables by publishing to my browser (Firefox) or MS Word.
I recognised that You changed something about the javascript abilities of sailwave from beta 2.5.4 and beta 2.5.5, because there was same javascript code displayed before the race tables by using normal templates without javascript features.
I suspect, that You will have a lot of work with our complaining …
But Sailwave is and will be the best scoring software!
With kind regardsChristof
Jon,
I think maybe the Javascript stuff is not ideal. We already have "locales" for translation of control names and that general approach would seem a much better way to go for translation of column and other names in HTML output. The HTML files that include Javascript that I've generated for testing are approximately twice the size of straight HTML files for the same results. That seems like an awful lot of internet overhead just to change a few words.
If you look at the output Javascript files you will see a whole lot of definitions. Those could presumably be put into a config file that Sailwave would access when publishing, thus making the HTML output much cleaner and smaller.
Art
PS - I wanted to change some of the HTML output which is currently unchangeable. So, I have written an Excel macro which will do replacement on a specified file (it uses RegEx format, which you can Google for more info). The user picks an HTML file to "process" and the macro makes prettier HTML. I then have the user click a button to automatically upload the file via FTP with the correct name. I need to do a bit more work but would be happy to make a version of my Excel file available to anyone who might be interested.
As an example of the processing I do - I think it somewhat silly for the caption for races to repeat the name of the fleet/class which is just above in the title (as in: "Start: Laser" for the Laser fleet. That is redundant. So, in my processing I delete that from the HTML file. Samples of the standard and processed output here:
http://results.calyachtclub.com/sample_sailwave/
Note that the majority of the different "look" is undoubtedly due to differing CSS style but the text is different as well.
On 11/13/2012 4:30 PM, Jon Eskdale wrote:
Hi Christof,
Glad the age groups and gender are working OK. The JavaScript problem is in the Code which Colin passed to me when I took over. Apparently he has made some changes to it to make it more flexible but he hadn't finished it all and it's broken the JavaScript output. He does tell me he is going to fix it. It's almost impossible for me to change that bit of code without starting from scratch as I don't know what his intention was with it. The change from 2.5.4 to 2.5.5 was only to stop any JavaScript code outputting during the standard publish.
Sorry about the JavaScript output but hopefully Colin is reading this.
Jon
Sent from my iPad
On 14 Nov 2012, at 00:09, "paulesgps"<paulesgps@yahoo.com> wrote:
Hi Jon,
You solved the problem with age-groups and gender of helm and crew very well in/with beta 2.5.7.
But this evening with some time to test Your beta-versions I dispaired on publishing. Since Version 2.5.3 and all following beta-versions my javascript template will not work. I utilised javascript to translate English terms to German. Now I get a lot of lines with code like "sw.ser = {}; sw.ser.version = "2.5.7"; ..." instead of the tables by publishing to my browser (Firefox) or MS Word.
I recognised that You changed something about the javascript abilities of sailwave from beta 2.5.4 and beta 2.5.5, because there was same javascript code displayed before the race tables by using normal templates without javascript features.
I suspect, that You will have a lot of work with our complaining ...
But Sailwave is and will be the best scoring software!
With kind regardsChristof
Hi Art,
Just a quick thought and I’m no Python expert but I have seen what I think you are trying to do, done using Python and the “Beautifulsoup” Library. Beautifulsoup 4 is the latest version I believe. It made it look quite simple.
Perhaps a google would come up with some suggestions
Jon
On 14 November 2012 01:19, Art Engel artengel123@earthlink.net wrote:
Jon,
I think maybe the Javascript stuff is not ideal. We already have
“locales” for translation of control names and that general approach
would seem a much better way to go for translation of column and other
names in HTML output. The HTML files that include Javascript that I’ve
generated for testing are approximately twice the size of straight HTML
files for the same results. That seems like an awful lot of internet
overhead just to change a few words.If you look at the output Javascript files you will see a whole lot of
definitions. Those could presumably be put into a config file that
Sailwave would access when publishing, thus making the HTML output much
cleaner and smaller.Art
PS - I wanted to change some of the HTML output which is currently
unchangeable. So, I have written an Excel macro which will do
replacement on a specified file (it uses RegEx format, which you can
Google for more info). The user picks an HTML file to “process” and the
macro makes prettier HTML. I then have the user click a button to
automatically upload the file via FTP with the correct name. I need to
do a bit more work but would be happy to make a version of my Excel file
available to anyone who might be interested.As an example of the processing I do - I think it somewhat silly for the
caption for races to repeat the name of the fleet/class which is just
above in the title (as in: “Start: Laser” for the Laser fleet. That is
redundant. So, in my processing I delete that from the HTML file.
Samples of the standard and processed output here:
http://results.calyachtclub.com/sample_sailwave/Note that the majority of the different “look” is undoubtedly due to
differing CSS style but the text is different as well.
On 11/13/2012 4:30 PM, Jon Eskdale wrote:
Hi Christof,
Glad the age groups and gender are working OK. The JavaScript problem is in the Code which Colin passed to me when I took over. Apparently he has made some changes to it to make it more flexible but he hadn’t finished it all and it’s broken the JavaScript output. He does tell me he is going to fix it. It’s almost impossible for me to change that bit of code without starting from scratch as I don’t know what his intention was with it. The change from 2.5.4 to 2.5.5 was only to stop any JavaScript code outputting during the standard publish.
Sorry about the JavaScript output but hopefully Colin is reading this.
Jon
Sent from my iPad
On 14 Nov 2012, at 00:09, "paulesgps"paulesgps@yahoo.com wrote:
Hi Jon,
You solved the problem with age-groups and gender of helm and crew very well in/with beta 2.5.7.
But this evening with some time to test Your beta-versions I dispaired on publishing. Since Version 2.5.3 and all following beta-versions my javascript template will not work. I utilised javascript to translate English terms to German. Now I get a lot of lines with code like “sw.ser = {}; sw.ser.version = “2.5.7”; …” instead of the tables by publishing to my browser (Firefox) or MS Word.
I recognised that You changed something about the javascript abilities of sailwave from beta 2.5.4 and beta 2.5.5, because there was same javascript code displayed before the race tables by using normal templates without javascript features.
I suspect, that You will have a lot of work with our complaining …
But Sailwave is and will be the best scoring software!
With kind regards
Christof
–
Jon Eskdale
07976 709777
Skype “eskdale”
Thanks Jon. If I hadn't already done the Excel macro I might seriously look at Beautifulsoup, which looks interesting. Unfortunately, I have no Python experience at all (and am not a programmer, just a hobbyist). The part of the Excel macro I haven't finished with is the FTP upload, which I have done in other macros and just need to do the drudgery of copying and modifying existing code (I have some time as our next regatta is mid-February). The replacement (RegEx) stuff was pretty straight-forward and just required my learning some RegEx basics.
When I looked at "Beautifulsoup" it appears to use HTML "class" tags to "scrape" data from web pages. Unfortunately, there are very few "class" tags being output by Sailwave so it might not be all that helpful.
This is slightly off-topic but the I believe the convention is to put boat names in italics. I wanted to do that in the results webpages for my club but there are no class tags for the <td> codes in Sailwave. If I were designing HTML output from scratch (which I have done for our other scoring program) I would give each table cell in a table column a class tag. Then, you could italicize or bold an entire column of results with one style tag in your CSS file. There is a work-around but it is a real kludge and breaks if you add a column to your output (in your CSS file you can use "adjacent sibling selectors" on the <td>s). In my design work for 2013 I have implemented the kludge (it is in the sample I posted last time) but would much prefer it if Sailwave were to output class tags for each <td> cell in a <tr> row.
Art
On 11/14/2012 2:32 AM, Jon Eskdale wrote:
Hi Art,
Just a quick thought and I'm no Python expert but I have seen what I think
you are trying to do, done using Python and the "Beautifulsoup" Library.
Beautifulsoup 4 is the latest version I believe. It made it look quite
simple.Perhaps a google would come up with some suggestions
Jon
On 14 November 2012 01:19, Art Engel<artengel123@earthlink.net> wrote:
**
Jon,
I think maybe the Javascript stuff is not ideal. We already have
"locales" for translation of control names and that general approach
would seem a much better way to go for translation of column and other
names in HTML output. The HTML files that include Javascript that I've
generated for testing are approximately twice the size of straight HTML
files for the same results. That seems like an awful lot of internet
overhead just to change a few words.If you look at the output Javascript files you will see a whole lot of
definitions. Those could presumably be put into a config file that
Sailwave would access when publishing, thus making the HTML output much
cleaner and smaller.Art
PS - I wanted to change some of the HTML output which is currently
unchangeable. So, I have written an Excel macro which will do
replacement on a specified file (it uses RegEx format, which you can
Google for more info). The user picks an HTML file to "process" and the
macro makes prettier HTML. I then have the user click a button to
automatically upload the file via FTP with the correct name. I need to
do a bit more work but would be happy to make a version of my Excel file
available to anyone who might be interested.As an example of the processing I do - I think it somewhat silly for the
caption for races to repeat the name of the fleet/class which is just
above in the title (as in: "Start: Laser" for the Laser fleet. That is
redundant. So, in my processing I delete that from the HTML file.
Samples of the standard and processed output here:
http://results.calyachtclub.com/sample_sailwave/Note that the majority of the different "look" is undoubtedly due to
differing CSS style but the text is different as well.On 11/13/2012 4:30 PM, Jon Eskdale wrote:
Hi Christof,
Glad the age groups and gender are working OK. The JavaScript problem is
in the Code which Colin passed to me when I took over. Apparently he has
made some changes to it to make it more flexible but he hadn't finished it
all and it's broken the JavaScript output. He does tell me he is going to
fix it. It's almost impossible for me to change that bit of code without
starting from scratch as I don't know what his intention was with it. The
change from 2.5.4 to 2.5.5 was only to stop any JavaScript code outputting
during the standard publish.Sorry about the JavaScript output but hopefully Colin is reading this.
Jon
Sent from my iPad
On 14 Nov 2012, at 00:09, "paulesgps"<paulesgps@yahoo.com> wrote:
Hi Jon,
You solved the problem with age-groups and gender of helm and crew very
well in/with beta 2.5.7.
But this evening with some time to test Your beta-versions I dispaired
on publishing. Since Version 2.5.3 and all following beta-versions my
javascript template will not work. I utilised javascript to translate
English terms to German. Now I get a lot of lines with code like "sw.ser =
{}; sw.ser.version = "2.5.7"; ..." instead of the tables by publishing to
my browser (Firefox) or MS Word.I recognised that You changed something about the javascript abilities
of sailwave from beta 2.5.4 and beta 2.5.5, because there was same
javascript code displayed before the race tables by using normal templates
without javascript features.I suspect, that You will have a lot of work with our complaining ...
But Sailwave is and will be the best scoring software!
With kind regardsChristof
the problem is the
inability to target the columns of a colgroup with css -
something i didn’t realise when i did it - only 4 syles are
allowed - none of them involving font styling.
all the factory styles need redoing to they use class in the
td’s.
one could use "tr nth-child" but that depends on column number not
name, which is dodgy.
i'll speak to jon about it...
i agree that any one element should be addressable with css - i
think it’s only the golgroup limitation that is stopping that -
everything else is addressable.
On 14/11/2012 23:34, Art Engel wrote:
Cheers,
Colin J
Thanks Jon. If I hadn't already done the Excel macro Imight seriously
look at Beautifulsoup, which looks interesting.
Unfortunately, I have no
Python experience at all (and am not a programmer, just a
hobbyist). The
part of the Excel macro I haven’t finished with is the FTP
upload, which
I have done in other macros and just need to do the
drudgery of copying
and modifying existing code (I have some time as our next
regatta is
mid-February). The replacement (RegEx) stuff was pretty
straight-forward
and just required my learning some RegEx basics.When I looked at "Beautifulsoup" it appears to use HTML“class” tags to
“scrape” data from web pages. Unfortunately, there are
very few “class”
tags being output by Sailwave so it might not be all that
helpful.This is slightly off-topic but the I believe theconvention is to put
boat names in italics. I wanted to do that in the results
webpages for
my club but there are no class tags for the
codes in Sailwave. If I
were designing HTML output from scratch (which I have done
for our other
scoring program) I would give each table cell in a table
column a class
tag. Then, you could italicize or bold an entire column of
results with
one style tag in your CSS file. There is a work-around but
it is a real
kludge and breaks if you add a column to your output (in
your CSS file
you can use “adjacent sibling selectors” on thes). In my design work for 2013 I have implemented the kludge (it is in the sample I posted last time) but would much prefer it if Sailwave were to output class tags for each cell in a row. Art On 11/14/2012 2:32 AM, Jon Eskdale wrote: > Hi Art, > > Just a quick thought and I'm no Python expert but Ihave seen what I think
> you are trying to do, done using Python and the
“Beautifulsoup” Library.
> Beautifulsoup 4 is the latest version I believe. It
made it look quite
> simple.
>
> Perhaps a google would come up with some suggestions
>
> Jon
>
>
> On 14 November 2012 01:19, Art Engel<artengel123@earthlink.net >
wrote:
>
>> **
>>
>>
>> Jon,
>>
>> I think maybe the Javascript stuff is not ideal.
We already have
>> “locales” for translation of control names and
that general approach
>> would seem a much better way to go for
translation of column and other
>> names in HTML output. The HTML files that include
Javascript that I’ve
>> generated for testing are approximately twice the
size of straight HTML
>> files for the same results. That seems like an
awful lot of internet
>> overhead just to change a few words.
>>
>> If you look at the output Javascript files you
will see a whole lot of
>> definitions. Those could presumably be put into a
config file that
>> Sailwave would access when publishing, thus
making the HTML output much
>> cleaner and smaller.
>>
>> Art
>>
>> PS - I wanted to change some of the HTML output
which is currently
>> unchangeable. So, I have written an Excel macro
which will do
>> replacement on a specified file (it uses RegEx
format, which you can
>> Google for more info). The user picks an HTML
file to “process” and the
>> macro makes prettier HTML. I then have the user
click a button to
>> automatically upload the file via FTP with the
correct name. I need to
>> do a bit more work but would be happy to make a
version of my Excel file
>> available to anyone who might be interested.
>>
>> As an example of the processing I do - I think it
somewhat silly for the
>> caption for races to repeat the name of the
fleet/class which is just
>> above in the title (as in: “Start: Laser” for the
Laser fleet. That is
>> redundant. So, in my processing I delete that
from the HTML file.
>> Samples of the standard and processed output
here:
>> http://results.calyachtclub.com/sample_sailwave/
>>
>> Note that the majority of the different “look” is
undoubtedly due to
>> differing CSS style but the text is different as
well.
>>
>>
>> On 11/13/2012 4:30 PM, Jon Eskdale wrote:
>>> Hi Christof,
>>>
>>> Glad the age groups and gender are working
OK. The JavaScript problem is
>> in the Code which Colin passed to me when I took
over. Apparently he has
>> made some changes to it to make it more flexible
but he hadn’t finished it
>> all and it’s broken the JavaScript output. He
does tell me he is going to
>> fix it. It’s almost impossible for me to change
that bit of code without
>> starting from scratch as I don’t know what his
intention was with it. The
>> change from 2.5.4 to 2.5.5 was only to stop any
JavaScript code outputting
>> during the standard publish.
>>>
>>> Sorry about the JavaScript output but
hopefully Colin is reading this.
>>>
>>> Jon
>>>
>>> Sent from my iPad
>>>
>>> On 14 Nov 2012, at 00:09, “paulesgps”<paulesgps@yahoo.com >
wrote:
>>>
>>>> Hi Jon,
>>>>
>>>> You solved the problem with age-groups
and gender of helm and crew very
>> well in/with beta 2.5.7.
>>>> But this evening with some time to test
Your beta-versions I dispaired
>> on publishing. Since Version 2.5.3 and all
following beta-versions my
>> javascript template will not work. I utilised
javascript to translate
>> English terms to German. Now I get a lot of lines
with code like “sw.ser =
>> {}; sw.ser.version = “2.5.7”; …” instead of the
tables by publishing to
>> my browser (Firefox) or MS Word.
>>>> I recognised that You changed something
about the javascript abilities
>> of sailwave from beta 2.5.4 and beta 2.5.5,
because there was same
>> javascript code displayed before the race tables
by using normal templates
>> without javascript features.
>>>> I suspect, that You will have a lot of
work with our complaining …
>>>> But Sailwave is and will be the best
scoring software!
>>>> With kind regards
>>>>
>>>> Christof
>>>>
>>>>
>>>
>>
>>
>>
>
>
>No virusfound in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5395 - Release Date:
11/14/12
Colin’s comment just pre-empted mine, but I’ll make it anyway. Sailwave HTML did add a class to the columns to permit CSS formatting of each column, in particular to make some columns left aligned and others centred. But HTML/CSS in its wisdom allows very few attributes to be set in this way so it doesn’t work. My own result publishing tried the same trick, and I then tried adding a class to each
If anyone knows a workable way to reliably class a column I’d love to hear about it. Meanwhile if we all all complain to W3C about the poor implementation of … There’s a good reference here:
http://www.quirksmode.org/css/columns.html
On 15 November 2012 10:02, Colin Jenkins colin@sailwave.com wrote:
the problem is theinability to target the columns of a colgroup with css -
something i didn’t realise when i did it - only 4 syles are
allowed - none of them involving font styling.all the factory styles need redoing to they use class in thetd’s.
one could use "tr nth-child" but that depends on column number notname, which is dodgy.
i'll speak to jon about it... i agree that any one element should be addressable with css - ithink it’s only the golgroup limitation that is stopping that -
everything else is addressable.Cheers, Colin J [http://op12no2.me](http://op12no2.me)
On 14/11/2012 23:34, Art Engel wrote:
Thanks Jon. If I hadn't already done the Excel macro Imight seriously
look at Beautifulsoup, which looks interesting.
Unfortunately, I have no
Python experience at all (and am not a programmer, just a
hobbyist). The
part of the Excel macro I haven’t finished with is the FTP
upload, which
I have done in other macros and just need to do the
drudgery of copying
and modifying existing code (I have some time as our next
regatta is
mid-February). The replacement (RegEx) stuff was pretty
straight-forward
and just required my learning some RegEx basics.When I looked at "Beautifulsoup" it appears to use HTML“class” tags to
“scrape” data from web pages. Unfortunately, there are
very few “class”
tags being output by Sailwave so it might not be all that
helpful.This is slightly off-topic but the I believe theconvention is to put
boat names in italics. I wanted to do that in the results
webpages for
my club but there are no class tags for the
codes in Sailwave. If I
were designing HTML output from scratch (which I have done
for our other
scoring program) I would give each table cell in a table
column a class
tag. Then, you could italicize or bold an entire column of
results with
one style tag in your CSS file. There is a work-around but
it is a real
kludge and breaks if you add a column to your output (in
your CSS file
you can use “adjacent sibling selectors” on thes). In my design work for 2013 I have implemented the kludge (it is in the sample I posted last time) but would much prefer it if Sailwave were to output class tags for each cell in a row. Art On 11/14/2012 2:32 AM, Jon Eskdale wrote: > Hi Art, > > Just a quick thought and I'm no Python expert but Ihave seen what I think
> you are trying to do, done using Python and the
“Beautifulsoup” Library.
> Beautifulsoup 4 is the latest version I believe. It
made it look quite
> simple.
>
> Perhaps a google would come up with some suggestions
>
> Jon
>
>
> On 14 November 2012 01:19, Art Engel<artengel123@earthlink.net >
wrote:
>
>> **
>>
>>
>> Jon,
>>
>> I think maybe the Javascript stuff is not ideal.
We already have
>> “locales” for translation of control names and
that general approach
>> would seem a much better way to go for
translation of column and other
>> names in HTML output. The HTML files that include
Javascript that I’ve
>> generated for testing are approximately twice the
size of straight HTML
>> files for the same results. That seems like an
awful lot of internet
>> overhead just to change a few words.
>>
>> If you look at the output Javascript files you
will see a whole lot of
>> definitions. Those could presumably be put into a
config file that
>> Sailwave would access when publishing, thus
making the HTML output much
>> cleaner and smaller.
>>
>> Art
>>
>> PS - I wanted to change some of the HTML output
which is currently
>> unchangeable. So, I have written an Excel macro
which will do
>> replacement on a specified file (it uses RegEx
format, which you can
>> Google for more info). The user picks an HTML
file to “process” and the
>> macro makes prettier HTML. I then have the user
click a button to
>> automatically upload the file via FTP with the
correct name. I need to
>> do a bit more work but would be happy to make a
version of my Excel file
>> available to anyone who might be interested.
>>
>> As an example of the processing I do - I think it
somewhat silly for the
>> caption for races to repeat the name of the
fleet/class which is just
>> above in the title (as in: “Start: Laser” for the
Laser fleet. That is
>> redundant. So, in my processing I delete that
from the HTML file.
>> Samples of the standard and processed output
here:
>> http://results.calyachtclub.com/sample_sailwave/
>>
>> Note that the majority of the different “look” is
undoubtedly due to
>> differing CSS style but the text is different as
well.
>>
>>
>> On 11/13/2012 4:30 PM, Jon Eskdale wrote:
>>> Hi Christof,
>>>
>>> Glad the age groups and gender are working
OK. The JavaScript problem is
>> in the Code which Colin passed to me when I took
over. Apparently he has
>> made some changes to it to make it more flexible
but he hadn’t finished it
>> all and it’s broken the JavaScript output. He
does tell me he is going to
>> fix it. It’s almost impossible for me to change
that bit of code without
>> starting from scratch as I don’t know what his
intention was with it. The
>> change from 2.5.4 to 2.5.5 was only to stop any
JavaScript code outputting
>> during the standard publish.
>>>
>>> Sorry about the JavaScript output but
hopefully Colin is reading this.
>>>
>>> Jon
>>>
>>> Sent from my iPad
>>>
>>> On 14 Nov 2012, at 00:09, “paulesgps”<paulesgps@yahoo.com >
wrote:
>>>
>>>> Hi Jon,
>>>>
>>>> You solved the problem with age-groups
and gender of helm and crew very
>> well in/with beta 2.5.7.
>>>> But this evening with some time to test
Your beta-versions I dispaired
>> on publishing. Since Version 2.5.3 and all
following beta-versions my
>> javascript template will not work. I utilised
javascript to translate
>> English terms to German. Now I get a lot of lines
with code like “sw.ser =
>> {}; sw.ser.version = “2.5.7”; …” instead of the
tables by publishing to
>> my browser (Firefox) or MS Word.
>>>> I recognised that You changed something
about the javascript abilities
>> of sailwave from beta 2.5.4 and beta 2.5.5,
because there was same
>> javascript code displayed before the race tables
by using normal templates
>> without javascript features.
>>>> I suspect, that You will have a lot of
work with our complaining …
>>>> But Sailwave is and will be the best
scoring software!
>>>> With kind regards
>>>>
>>>> Christof
>>>>
>>>>
>>>
>>
>>
>>
>
>
>No virusfound in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5395 - Release Date:
11/14/12
this article says
it to do with the implementation - !!
On 15/11/2012 10:21, Ian Savell wrote:
http://ln.hixie.ch/?start=1070385285&count=1
Cheers,
Colin J
Colin's comment just pre-empted mine, but I'll make itanyway. Sailwave HTML did add a class to the columns to
permit CSS formatting of each column, in particular to
make some columns left aligned and others centred. But
HTML/CSS in its wisdom allows very few attributes to be
set in this way so it doesn’t work. My own result
publishing tried the same trick, and I then tried adding a
class to eachto achieve the same thing. Such a
proliferation of class tags makes the HTML much longer,
which can be an issue when publishing to, say, a phone,
and precedence between elements means theclass
formatting is easily lost, being overidden by higher level
elements such as. If anyone knows a workable way to reliably class a columnI’d love to hear about it. Meanwhile if we all all
... There's a good reference here:
complain to W3C about the poor implementation of[http://www.quirksmode.org/css/columns.html](http://www.quirksmode.org/css/columns.html)On 15 November 2012 10:02, ColinJenkins colin@sailwave.com
wrote:�
the problem is theinability to target the columns of a
colgroup with css - something i didn’t
realise when i did it - only 4 syles are
allowed - none of them involving font
styling.all the factory styles need redoing tothey use class in the td’s.
one could use "tr nth-child" but thatdepends on column number not name, which
is dodgy.i'll speak to jon about it... i agree that any one element should beaddressable with css - i think it’s only the
golgroup limitation that is stopping that -
everything else is addressable.Cheers, Colin J [http://op12no2.me](http://op12no2.me)On 14/11/2012 23:34, ArtEngel wrote:
�
Thanks Jon. If I hadn’t already
done the Excel macro I might
seriously
look at Beautifulsoup, which looks
interesting. Unfortunately, I have
no
Python experience at all (and am not
a programmer, just a hobbyist). Thepart of the Excel macro I haven'tfinished with is the FTP upload,
which
I have done in other macros and just
need to do the drudgery of copying
and modifying existing code (I have
some time as our next regatta is
mid-February). The replacement
(RegEx) stuff was pretty
straight-forward
and just required my learning some
RegEx basics.When I looked at "Beautifulsoup" itappears to use HTML “class” tags to
"scrape" data from web pages.Unfortunately, there are very few
“class”
tags being output by Sailwave so it
might not be all that helpful.This is slightly off-topic but the Ibelieve the convention is to put
boat names in italics. I wanted to
do that in the results webpages formy club but there are no class tagsfor the
codes in
Sailwave. If I
were designing HTML output from
scratch (which I have done for our
other
scoring program) I would give each
table cell in a table column a classtag. Then, you could italicize orbold an entire column of results
with
one style tag in your CSS file.
There is a work-around but it is a
real
kludge and breaks if you add a
column to your output (in your CSS
file
you can use “adjacent sibling
selectors” on thes). In
my design
work for 2013 I have implemented the
kludge (it is in the sample I
posted last time) but would much
prefer it if Sailwave were to outputclass tags for each <td> cellin a
row. Art On 11/14/2012 2:32 AM, Jon Eskdalewrote:
> Hi Art,
>
> Just a quick thought and I’m no
Python expert but I have seen what I
think
> you are trying to do, done
using Python and the “Beautifulsoup”
Library.
> Beautifulsoup 4 is the latest
version I believe. It made it look
quite
> simple.
>
> Perhaps a google would come up
with some suggestions
>
> Jon
>
>
> On 14 November 2012 01:19, Art
Engel<artengel123@earthlink.net
>
wrote:
>
>> **
>>
>>
>> Jon,
>>
>> I think maybe the
Javascript stuff is not ideal. We
already have
>> “locales” for translation
of control names and that general
approach
>> would seem a much better
way to go for translation of column
and other
>> names in HTML output. The
HTML files that include Javascript
that I’ve
>> generated for testing are
approximately twice the size of
straight HTML
>> files for the same results.
That seems like an awful lot of
internet
>> overhead just to change a
few words.
>>
>> If you look at the output
Javascript files you will see a
whole lot of
>> definitions. Those could
presumably be put into a config file
that
>> Sailwave would access when
publishing, thus making the HTML
output much
>> cleaner and smaller.
>>
>> Art
>>
>> PS - I wanted to change
some of the HTML output which is
currently
>> unchangeable. So, I have
written an Excel macro which will do
>> replacement on a specified
file (it uses RegEx format, which
you can
>> Google for more info). The
user picks an HTML file to “process”
and the
>> macro makes prettier HTML.
I then have the user click a button
to
>> automatically upload the
file via FTP with the correct name.
I need to
>> do a bit more work but
would be happy to make a version of
my Excel file
>> available to anyone who
might be interested.
>>
>> As an example of the
processing I do - I think it
somewhat silly for the
>> caption for races to repeat
the name of the fleet/class which is
just
>> above in the title (as in:
“Start: Laser” for the Laser fleet.
That is
>> redundant. So, in my
processing I delete that from the
HTML file.
>> Samples of the standard and
processed output here:
>> http://results.calyachtclub.com/sample_sailwave/
>>
>> Note that the majority of
the different “look” is undoubtedly
due to
>> differing CSS style but the
text is different as well.
>>
>>
>> On 11/13/2012 4:30 PM, Jon
Eskdale wrote:
>>> Hi Christof,
>>>
>>> Glad the age groups and
gender are working OK. The
JavaScript problem is
>> in the Code which Colin
passed to me when I took over.
Apparently he has
>> made some changes to it to
make it more flexible but he hadn’t
finished it
>> all and it’s broken the
JavaScript output. He does tell me
he is going to
>> fix it. It’s almost
impossible for me to change that bit
of code without
>> starting from scratch as I
don’t know what his intention was
with it. The
>> change from 2.5.4 to 2.5.5
was only to stop any JavaScript code
outputting
>> during the standard
publish.
>>>
>>> Sorry about the
JavaScript output but hopefully
Colin is reading this.
>>>
>>> Jon
>>>
>>> Sent from my iPad
>>>
>>> On 14 Nov 2012, at
00:09, “paulesgps”<paulesgps@yahoo.com
>
wrote:
>>>
>>>> Hi Jon,
>>>>
>>>> You solved the
problem with age-groups and gender
of helm and crew very
>> well in/with beta 2.5.7.
>>>> But this evening
with some time to test Your
beta-versions I dispaired
>> on publishing. Since
Version 2.5.3 and all following
beta-versions my
>> javascript template will
not work. I utilised javascript to
translate
>> English terms to German.
Now I get a lot of lines with code
like “sw.ser =
>> {}; sw.ser.version =
“2.5.7”; …” instead of the tables
by publishing to
>> my browser (Firefox) or MS
Word.
>>>> I recognised that
You changed something about the
javascript abilities
>> of sailwave from beta 2.5.4
and beta 2.5.5, because there was
same
>> javascript code displayed
before the race tables by using
normal templates
>> without javascript
features.
>>>> I suspect, that You
will have a lot of work with our
complaining …
>>>> But Sailwave is and
will be the best scoring software!
>>>> With kind regards
>>>>
>>>> Christof
>>>>
>>>>
>>>
>>
>>
>>
>
>
>No virusfound in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database:
2441/5395 - Release Date: 11/14/12No virusfound in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5395 - Release Date:
11/14/12
You can use "adjacent sibling selectors" in your CSS. BUT, this only works for a specified column (say, the 4th). So, if you add a new column things are thrown off. For the 4th column, you define your CSS for "TD + TD + TD + TD". This works but you need a different CSS file if the column location changes.
Art
On 11/15/2012 2:21 AM, Ian Savell wrote:
Colin's comment just pre-empted mine, but I'll make it anyway. Sailwave
HTML did add a class to the columns to permit CSS formatting of each
column, in particular to make some columns left aligned and others
centred. But HTML/CSS in its wisdom allows very few attributes to be set
in this way so it doesn't work. My own result publishing tried the same
trick, and I then tried adding a class to each <tr> to achieve the same
thing. Such a proliferation of class tags makes the HTML much longer,
which can be an issue when publishing to, say, a phone, and precedence
between elements means the <tr> class formatting is easily lost, being
overidden by higher level elements such as <tr>.If anyone knows a workable way to reliably class a column I'd love to
hear about it. Meanwhile if we all all complain to W3C about the poor
implementation of <colgroup>... There's a good reference here:http://www.quirksmode.org/css/columns.html
On 15 November 2012 10:02, Colin Jenkins <colin@sailwave.com > <mailto:colin@sailwave.com>> wrote:
the problem is the inability to target the columns of a colgroup
with css - something i didn't realise when i did it - only 4 syles
are allowed - none of them involving font styling.all the factory styles need redoing to they use class in the td's.
one could use "tr nth-child" but that depends on column number not
name, which is dodgy.i'll speak to jon about it...
i agree that any one element should be addressable with css - i
think it's only the golgroup limitation that is stopping that -
everything else is addressable.Cheers,
Colin J
http://op12no2.me
On 14/11/2012 23:34, Art Engel wrote:Thanks Jon. If I hadn't already done the Excel macro I might
seriously
look at Beautifulsoup, which looks interesting. Unfortunately, I
have no
Python experience at all (and am not a programmer, just a
hobbyist). The
part of the Excel macro I haven't finished with is the FTP upload,
which
I have done in other macros and just need to do the drudgery of
copying
and modifying existing code (I have some time as our next regatta is
mid-February). The replacement (RegEx) stuff was pretty
straight-forward
and just required my learning some RegEx basics.When I looked at "Beautifulsoup" it appears to use HTML "class"
tags to
"scrape" data from web pages. Unfortunately, there are very few
"class"
tags being output by Sailwave so it might not be all that helpful.This is slightly off-topic but the I believe the convention is to put
boat names in italics. I wanted to do that in the results webpages
for
my club but there are no class tags for the <td> codes in
Sailwave. If I
were designing HTML output from scratch (which I have done for our
other
scoring program) I would give each table cell in a table column a
class
tag. Then, you could italicize or bold an entire column of results
with
one style tag in your CSS file. There is a work-around but it is a
real
kludge and breaks if you add a column to your output (in your CSS
file
you can use "adjacent sibling selectors" on the <td>s). In my design
work for 2013 I have implemented the kludge (it is in the sample I
posted last time) but would much prefer it if Sailwave were to output
class tags for each <td> cell in a <tr> row.Art
On 11/14/2012 2:32 AM, Jon Eskdale wrote:
> Hi Art,
>
> Just a quick thought and I'm no Python expert but I have seen
what I think
> you are trying to do, done using Python and the "Beautifulsoup"
Library.
> Beautifulsoup 4 is the latest version I believe. It made it look
quite
> simple.
>
> Perhaps a google would come up with some suggestions
>
> Jon
>
> On 14 November 2012 01:19, Art Engel<artengel123@earthlink.net >> <mailto:artengel123%40earthlink.net>> wrote:
>
>> **
>>
>> Jon,
>>
>> I think maybe the Javascript stuff is not ideal. We already have
>> "locales" for translation of control names and that general
approach
>> would seem a much better way to go for translation of column
and other
>> names in HTML output. The HTML files that include Javascript
that I've
>> generated for testing are approximately twice the size of
straight HTML
>> files for the same results. That seems like an awful lot of
internet
>> overhead just to change a few words.
>>
>> If you look at the output Javascript files you will see a whole
lot of
>> definitions. Those could presumably be put into a config file that
>> Sailwave would access when publishing, thus making the HTML
output much
>> cleaner and smaller.
>>
>> Art
>>
>> PS - I wanted to change some of the HTML output which is currently
>> unchangeable. So, I have written an Excel macro which will do
>> replacement on a specified file (it uses RegEx format, which
you can
>> Google for more info). The user picks an HTML file to "process"
and the
>> macro makes prettier HTML. I then have the user click a button to
>> automatically upload the file via FTP with the correct name. I
need to
>> do a bit more work but would be happy to make a version of my
Excel file
>> available to anyone who might be interested.
>>
>> As an example of the processing I do - I think it somewhat
silly for the
>> caption for races to repeat the name of the fleet/class which
is just
>> above in the title (as in: "Start: Laser" for the Laser fleet.
That is
>> redundant. So, in my processing I delete that from the HTML file.
>> Samples of the standard and processed output here:
>> http://results.calyachtclub.com/sample_sailwave/
>>
>> Note that the majority of the different "look" is undoubtedly
due to
>> differing CSS style but the text is different as well.
>>
>> On 11/13/2012 4:30 PM, Jon Eskdale wrote:
>>> Hi Christof,
>>>
>>> Glad the age groups and gender are working OK. The JavaScript
problem is
>> in the Code which Colin passed to me when I took over.
Apparently he has
>> made some changes to it to make it more flexible but he hadn't
finished it
>> all and it's broken the JavaScript output. He does tell me he
is going to
>> fix it. It's almost impossible for me to change that bit of
code without
>> starting from scratch as I don't know what his intention was
with it. The
>> change from 2.5.4 to 2.5.5 was only to stop any JavaScript code
outputting
>> during the standard publish.
>>>
>>> Sorry about the JavaScript output but hopefully Colin is
reading this.
>>>
>>> Jon
>>>
>>> Sent from my iPad
>>>
>>> On 14 Nov 2012, at 00:09, "paulesgps"<paulesgps@yahoo.com >> <mailto:paulesgps%40yahoo.com>> wrote:
>>>
>>>> Hi Jon,
>>>>
>>>> You solved the problem with age-groups and gender of helm and
crew very
>> well in/with beta 2.5.7.
>>>> But this evening with some time to test Your beta-versions I
dispaired
>> on publishing. Since Version 2.5.3 and all following
beta-versions my
>> javascript template will not work. I utilised javascript to
translate
>> English terms to German. Now I get a lot of lines with code
like "sw.ser =
>> {}; sw.ser.version = "2.5.7"; ..." instead of the tables by
publishing to
>> my browser (Firefox) or MS Word.
>>>> I recognised that You changed something about the javascript
abilities
>> of sailwave from beta 2.5.4 and beta 2.5.5, because there was same
>> javascript code displayed before the race tables by using
normal templates
>> without javascript features.
>>>> I suspect, that You will have a lot of work with our
complaining ...
>>>> But Sailwave is and will be the best scoring software!
>>>> With kind regards
>>>>
>>>> Christof
>>>>
>>>
>>
>No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2012.0.2221 / Virus Database: 2441/5395 - Release Date:
11/14/12
Using CSS siblings, making the race scores normal text but the series score bold would depend on having the same number of races every time, so publishing during a regatta would require unsailed races to be published. Classes are the way to go, but how.
The html bloat issue could be minimised by allowing the race score cells to adopt the default format for the
Ian.
On 15 November 2012 10:39, Art Engel artengel123@earthlink.net wrote:
You can use “adjacent sibling selectors” in your CSS. BUT, this only
works for a specified column (say, the 4th). So, if you add a new column
things are thrown off. For the 4th column, you define your CSS for “TD +
TD + TD + TD”. This works but you need a different CSS file if the
column location changes.Art
On 11/15/2012 2:21 AM, Ian Savell wrote:
Colin’s comment just pre-empted mine, but I’ll make it anyway. Sailwave
HTML did add a class to the columns to permit CSS formatting of each
column, in particular to make some columns left aligned and others
centred. But HTML/CSS in its wisdom allows very few attributes to be set
in this way so it doesn’t work. My own result publishing tried the same
trick, and I then tried adding a class to each
to achieve the same thing. Such a proliferation of class tags makes the HTML much longer,
which can be an issue when publishing to, say, a phone, and precedence
between elements means the
class formatting is easily lost, being overidden by higher level elements such as
. If anyone knows a workable way to reliably class a column I’d love to
hear about it. Meanwhile if we all all complain to W3C about the poor
implementation of … There’s a good reference here:
On 15 November 2012 10:02, Colin Jenkins <colin@sailwave.com
mailto:colin@sailwave.com> wrote:
the problem is the inability to target the columns of a colgroup
with css - something i didn’t realise when i did it - only 4 syles
are allowed - none of them involving font styling.
all the factory styles need redoing to they use class in the td’s.
one could use “tr nth-child” but that depends on column number not
name, which is dodgy.
i’ll speak to jon about it…
i agree that any one element should be addressable with css - i
think it’s only the golgroup limitation that is stopping that -
everything else is addressable.
Cheers,
Colin J
On 14/11/2012 23:34, Art Engel wrote:
Thanks Jon. If I hadn’t already done the Excel macro I might
seriously
look at Beautifulsoup, which looks interesting. Unfortunately, I
have no
Python experience at all (and am not a programmer, just a
hobbyist). The
part of the Excel macro I haven’t finished with is the FTP upload,
which
I have done in other macros and just need to do the drudgery of
copying
and modifying existing code (I have some time as our next regatta is
mid-February). The replacement (RegEx) stuff was pretty
straight-forward
and just required my learning some RegEx basics.
When I looked at “Beautifulsoup” it appears to use HTML “class”
tags to
“scrape” data from web pages. Unfortunately, there are very few
“class”
tags being output by Sailwave so it might not be all that helpful.
This is slightly off-topic but the I believe the convention is to put
boat names in italics. I wanted to do that in the results webpages
for
my club but there are no class tags for the
codes in Sailwave. If I
were designing HTML output from scratch (which I have done for our
other
scoring program) I would give each table cell in a table column a
class
tag. Then, you could italicize or bold an entire column of results
with
one style tag in your CSS file. There is a work-around but it is a
real
kludge and breaks if you add a column to your output (in your CSS
file
you can use “adjacent sibling selectors” on the
s). In my design work for 2013 I have implemented the kludge (it is in the sample I
posted last time) but would much prefer it if Sailwave were to output
class tags for each
cell in a row. Art
On 11/14/2012 2:32 AM, Jon Eskdale wrote:
Hi Art,
Just a quick thought and I’m no Python expert but I have seen
what I think
you are trying to do, done using Python and the “Beautifulsoup”
Library.
Beautifulsoup 4 is the latest version I believe. It made it look
quite
simple.
Perhaps a google would come up with some suggestions
Jon
On 14 November 2012 01:19, Art Engel<artengel123@earthlink.net
**
Jon,
I think maybe the Javascript stuff is not ideal. We already have
“locales” for translation of control names and that general
approach
would seem a much better way to go for translation of column
and other
names in HTML output. The HTML files that include Javascript
that I’ve
generated for testing are approximately twice the size of
straight HTML
files for the same results. That seems like an awful lot of
internet
overhead just to change a few words.
If you look at the output Javascript files you will see a whole
lot of
definitions. Those could presumably be put into a config file that
Sailwave would access when publishing, thus making the HTML
output much
cleaner and smaller.
Art
PS - I wanted to change some of the HTML output which is currently
unchangeable. So, I have written an Excel macro which will do
replacement on a specified file (it uses RegEx format, which
you can
Google for more info). The user picks an HTML file to “process”
and the
macro makes prettier HTML. I then have the user click a button to
automatically upload the file via FTP with the correct name. I
need to
do a bit more work but would be happy to make a version of my
Excel file
available to anyone who might be interested.
As an example of the processing I do - I think it somewhat
silly for the
caption for races to repeat the name of the fleet/class which
is just
above in the title (as in: “Start: Laser” for the Laser fleet.
That is
redundant. So, in my processing I delete that from the HTML file.
Samples of the standard and processed output here:
Note that the majority of the different “look” is undoubtedly
due to
differing CSS style but the text is different as well.
On 11/13/2012 4:30 PM, Jon Eskdale wrote:
Hi Christof,
Glad the age groups and gender are working OK. The JavaScript
problem is
in the Code which Colin passed to me when I took over.
Apparently he has
made some changes to it to make it more flexible but he hadn’t
finished it
all and it’s broken the JavaScript output. He does tell me he
is going to
fix it. It’s almost impossible for me to change that bit of
code without
starting from scratch as I don’t know what his intention was
with it. The
change from 2.5.4 to 2.5.5 was only to stop any JavaScript code
outputting
during the standard publish.
Sorry about the JavaScript output but hopefully Colin is
reading this.
Jon
Sent from my iPad
On 14 Nov 2012, at 00:09, “paulesgps”<paulesgps@yahoo.com
mailto:paulesgps%40yahoo.com> wrote:
Hi Jon,
You solved the problem with age-groups and gender of helm and
crew very
well in/with beta 2.5.7.
But this evening with some time to test Your beta-versions I
dispaired
on publishing. Since Version 2.5.3 and all following
beta-versions my
javascript template will not work. I utilised javascript to
translate
English terms to German. Now I get a lot of lines with code
like "sw.ser =
{}; sw.ser.version = “2.5.7”; …" instead of the tables by
publishing to
my browser (Firefox) or MS Word.
I recognised that You changed something about the javascript
abilities
of sailwave from beta 2.5.4 and beta 2.5.5, because there was same
javascript code displayed before the race tables by using
normal templates
without javascript features.
I suspect, that You will have a lot of work with our
complaining …
But Sailwave is and will be the best scoring software!
With kind regards
Christof
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2012.0.2221 / Virus Database: 2441/5395 - Release Date:
11/14/12
one way is to add
a class field to the column record in sailwave and use that for
those td cells if specified.� its a shame it has to come to
that but it is trivially easy to do and would minimise html.
On 15/11/2012 11:38, Ian Savell wrote:
Cheers,
Colin J
Using CSS siblings, making the race scores normal textbut the series score bold would depend on having the same
number of races every time, so publishing during a regatta
would require unsailed races to be published. Classes are
the way to go, but how.The html bloat issue could be minimised by allowing therace score cells to adopt the default format for the
element while classing all other cells. There is generally a preponderance of race score cells which are typically very short, and a limited number of entry and series score cells. Ian.On 15 November 2012 10:39, ArtEngel artengel123@earthlink.net
wrote:�
You can use “adjacent sibling selectors” in
your CSS. BUT, this only
works for a specified column (say, the 4th).
So, if you add a new column
things are thrown off. For the 4th column,
you define your CSS for “TD +
TD + TD + TD”. This works but you need a
different CSS file if the
column location changes.ArtOn 11/15/2012 2:21 AM, Ian Savell wrote: > > > Colin's comment just pre-empted mine,but I’ll make it anyway. Sailwave
> HTML did add a class to the columns topermit CSS formatting of each
> column, in particular to make somecolumns left aligned and others
> centred. But HTML/CSS in its wisdomallows very few attributes to be set
> in this way so it doesn't work. My ownresult publishing tried the same
> trick, and I then tried adding a classto each
to achieve the same > thing. Such a proliferation of classtags makes the HTML much longer,
> which can be an issue when publishingto, say, a phone, and precedence
> between elements means the <tr>class formatting is easily lost, being
> overidden by higher level elements suchas
. > > If anyone knows a workable way toreliably class a column I’d love to
> hear about it. Meanwhile if we all allcomplain to W3C about the poor
> implementation of <colgroup>...There’s a good reference here:
> > [http://www.quirksmode.org/css/columns.html](http://www.quirksmode.org/css/columns.html) > > > On 15 November 2012 10:02, ColinJenkins <colin@sailwave.com
<mailto:colin@sailwave.com >>
wrote:> > the problem is the inability totarget the columns of a colgroup
> with css - something i didn't realisewhen i did it - only 4 syles
> are allowed - none of them involvingfont styling.
> > all the factory styles need redoingto they use class in the td’s.
> > one could use "tr nth-child" but thatdepends on column number not
> name, which is dodgy. > > i'll speak to jon about it... > > i agree that any one element shouldbe addressable with css - i
> think it's only the golgrouplimitation that is stopping that -
> everything else is addressable. > > > Cheers, > Colin J > [http://op12no2.me](http://op12no2.me) > On 14/11/2012 23:34, Art Engel wrote: >> >> Thanks Jon. If I hadn't alreadydone the Excel macro I might
>> seriously >> look at Beautifulsoup, whichlooks interesting. Unfortunately, I
>> have no >> Python experience at all (and amnot a programmer, just a
>> hobbyist). The >> part of the Excel macro I haven'tfinished with is the FTP upload,
>> which >> I have done in other macros andjust need to do the drudgery of
>> copying >> and modifying existing code (Ihave some time as our next regatta is
>> mid-February). The replacement(RegEx) stuff was pretty
>> straight-forward >> and just required my learningsome RegEx basics.
>> >> When I looked at "Beautifulsoup"it appears to use HTML “class”
>> tags to >> "scrape" data from web pages.Unfortunately, there are very few
>> "class" >> tags being output by Sailwave soit might not be all that helpful.
>> >> This is slightly off-topic butthe I believe the convention is to put
>> boat names in italics. I wantedto do that in the results webpages
>> for >> my club but there are no classtags for the
codes in >> Sailwave. If I >> were designing HTML output fromscratch (which I have done for our
>> other >> scoring program) I would giveeach table cell in a table column a
>> class >> tag. Then, you could italicize orbold an entire column of results
>> with >> one style tag in your CSS file.There is a work-around but it is a
>> real >> kludge and breaks if you add acolumn to your output (in your CSS
>> file >> you can use "adjacent siblingselectors" on the
s). In my
design>> work for 2013 I have implementedthe kludge (it is in the sample I
>> posted last time) but would muchprefer it if Sailwave were to output
>> class tags for each <td>cell in a
row. >> >> Art >> >> On 11/14/2012 2:32 AM, JonEskdale wrote:
>> > Hi Art, >> > >> > Just a quick thought and I'mno Python expert but I have seen
>> what I think >> > you are trying to do, doneusing Python and the “Beautifulsoup”
>> Library. >> > Beautifulsoup 4 is thelatest version I believe. It made it look
>> quite >> > simple. >> > >> > Perhaps a google would comeup with some suggestions
>> > >> > Jon >> > >> > >> > On 14 November 2012 01:19,Art Engel<artengel123@earthlink.net
<mailto:artengel123%40earthlink.net >>
wrote:>> > >> >> ** >> >> >> >> >> >> Jon, >> >> >> >> I think maybe theJavascript stuff is not ideal. We already
have>> >> "locales" fortranslation of control names and that
general>> approach >> >> would seem a much betterway to go for translation of column
>> and other >> >> names in HTML output.The HTML files that include Javascript
>> that I've >> >> generated for testingare approximately twice the size of
>> straight HTML >> >> files for the sameresults. That seems like an awful lot of
>> internet >> >> overhead just to changea few words.
>> >> >> >> If you look at theoutput Javascript files you will see a
whole>> lot of >> >> definitions. Those couldpresumably be put into a config file that
>> >> Sailwave would accesswhen publishing, thus making the HTML
>> output much >> >> cleaner and smaller. >> >> >> >> Art >> >> >> >> PS - I wanted to changesome of the HTML output which is currently
>> >> unchangeable. So, I havewritten an Excel macro which will do
>> >> replacement on aspecified file (it uses RegEx format,
which>> you can >> >> Google for more info).The user picks an HTML file to “process”
>> and the >> >> macro makes prettierHTML. I then have the user click a button
to>> >> automatically upload thefile via FTP with the correct name. I
>> need to >> >> do a bit more work butwould be happy to make a version of my
>> Excel file >> >> available to anyone whomight be interested.
>> >> >> >> As an example of theprocessing I do - I think it somewhat
>> silly for the >> >> caption for races torepeat the name of the fleet/class which
>> is just >> >> above in the title (asin: “Start: Laser” for the Laser fleet.
>> That is >> >> redundant. So, in myprocessing I delete that from the HTML
file.>> >> Samples of the standardand processed output here:
>> >> [http://results.calyachtclub.com/sample_sailwave/](http://results.calyachtclub.com/sample_sailwave/) >> >> >> >> Note that the majorityof the different “look” is undoubtedly
>> due to >> >> differing CSS style butthe text is different as well.
>> >> >> >> >> >> On 11/13/2012 4:30 PM,Jon Eskdale wrote:
>> >>> Hi Christof, >> >>> >> >>> Glad the age groupsand gender are working OK. The JavaScript
>> problem is >> >> in the Code which Colinpassed to me when I took over.
>> Apparently he has >> >> made some changes to itto make it more flexible but he hadn’t
>> finished it >> >> all and it's broken theJavaScript output. He does tell me he
>> is going to >> >> fix it. It's almostimpossible for me to change that bit of
>> code without >> >> starting from scratch asI don’t know what his intention was
>> with it. The >> >> change from 2.5.4 to2.5.5 was only to stop any JavaScript code
>> outputting >> >> during the standardpublish.
>> >>> >> >>> Sorry about theJavaScript output but hopefully Colin is
>> reading this. >> >>> >> >>> Jon >> >>> >> >>> Sent from my iPad >> >>> >> >>> On 14 Nov 2012, at00:09, “paulesgps”<paulesgps@yahoo.com
<mailto:paulesgps%40yahoo.com >>
wrote:>> >>> >> >>>> Hi Jon, >> >>>> >> >>>> You solved theproblem with age-groups and gender of helm
and>> crew very >> >> well in/with beta 2.5.7. >> >>>> But this eveningwith some time to test Your beta-versions
I>> dispaired >> >> on publishing. SinceVersion 2.5.3 and all following
>> beta-versions my >> >> javascript template willnot work. I utilised javascript to
>> translate >> >> English terms to German.Now I get a lot of lines with code
>> like "sw.ser = >> >> {}; sw.ser.version =“2.5.7”; …" instead of the tables by
>> publishing to >> >> my browser (Firefox) orMS Word.
>> >>>> I recognisedthat You changed something about the
javascript>> abilities >> >> of sailwave from beta2.5.4 and beta 2.5.5, because there was
same>> >> javascript codedisplayed before the race tables by using
>> normal templates >> >> without javascriptfeatures.
>> >>>> I suspect, thatYou will have a lot of work with our
>> complaining ... >> >>>> But Sailwave isand will be the best scoring software!
>> >>>> With kindregards
>> >>>> >> >>>> Christof >> >>>> >> >>>> >> >>> >> >> >> >> >> >> >> > >> > >> > >> >> No virus found in this message.Checked by AVG - www.avg.com
<http://www.avg.com>>> Version: 2012.0.2221 / VirusDatabase: 2441/5395 - Release Date:
>> 11/14/12 >> > > > > >No virusfound in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5395 - Release Date:
11/14/12
Colin’s comment just pre-empted mine, but I’ll make it anyway. Sailwave HTML did add a class to the columns to permit CSS formatting of each column, in particular to make some columns left aligned and others centred. But HTML/CSS in its wisdom allows very few attributes to be set in this way so it doesn’t work.
Must be missing something! Just apply the style to the
That allocation of classes needs to happen in the code. Naming by header name makes sense…
My own result publishing tried the same trick, and I then tried adding a class to each
to achieve the same thing. Such a proliferation of class tags makes the HTML much longer, Its not exactly the end of the world in coding world - we should be worrying about getting the right output then reducing the file size. But in my example above class names could be shortened if need be to rL, rO, rE, p if you wanted…
which can be an issue when publishing to, say, a phone,
Getting a results page that views/navigates well on a phone would be a priority over speed of download.
···
On 2012-11-15 10:21, Ian Savell wrote:
The point is that attributes on tags are limited. Of course you can add a class to every TD but a big result page with class attributes on every TD can be of considerable size, and users have to live with that whether their CSS uses the class attributes or not (and most users use the default CSS). Not everyone has huge bandwidth, and GSM is frequently the only comms medium in remote locations like sailing clubs.
Ian…
On 15 November 2012 20:29, yahoo@wittongilbert.free-online.co.uk wrote:
On 2012-11-15 10:21, Ian Savell wrote:
Colin’s comment just pre-empted mine, but I’ll make it anyway. Sailwave HTML did add a class to the columns to permit CSS formatting of each column, in particular to make some columns left aligned and others centred. But HTML/CSS in its wisdom allows very few attributes to be set in this way so it doesn’t work.
Must be missing something! Just apply the style to the
using classes // allows you to add vertical stripes That allocation of classes needs to happen in the code. Naming by header name makes sense…
My own result publishing tried the same trick, and I then tried adding a class to each
to achieve the same thing. Such a proliferation of class tags makes the HTML much longer, Its not exactly the end of the world in coding world - we should be worrying about getting the right output then reducing the file size. But in my example above class names could be shortened if need be to rL, rO, rE, p if you wanted…
which can be an issue when publishing to, say, a phone,
Getting a results page that views/navigates well on a phone would be a priority over speed of download.
Ian,
Not sure I completely understand your comment. If you link a CSS stylesheet to a webpage it is always used - end of story. There is no opting in or opting out (actually, there is an add-on for Firefox that allows ignoring a CSS stylesheet but my point is that the ability to do that is not native and I would guess less than 1/10 of 1% of users can do it; I know I cannot). So, class attributes will ALWAYS be used to the extent that the CSS stylesheet for a webpage uses them. They should be there for every <td> tag so that webpage designers can use them when they want to.
Your comment about "most users use the default CSS" is, I believe, about stuff like whether links and visited links are highlighted in a certain color - none of which is changed by your typical CSS stylesheet but if it were then I believe the stylesheet would take precedence anyway.
The trick is to make your HTML files as small as possible AND NO SMALLER. I would rate having a class id for each <td> tag in a table as necessary for modern web browsers to implement HTML styles correctly. Thus, I wouldn't advocate leaving out important functionality just to make the files 10% smaller.
I agree with your comment about making HTML files as small as possible. So, I would advocate using an external CSS stylesheet rather than embedded styles (the latter is the default for Sailwave but can be changed). That has two advantages - (1) since you are using the stylesheet for multiple pages I believe your browser only needs to download the file once (unless the stylesheet has changed) and (2) that makes it easy to implement the same style across multiple webpages and change the style for all those pages by changing a single stylesheet.
For the same reason (smaller files) I would shy away from using Javascript to simply change a few column headings from English to some other language. Better to do that right in Sailwave so the output HTML is minimized in size.
Art
PS - You are 100% right about the <col> tags having limited functionality. But, that is life and we are stuck with it.
On 11/15/2012 2:13 PM, Ian Savell wrote:
The point is that attributes on<col> tags are limited. Of course you can
add a class to every TD but a big result page with class attributes on
every TD can be of considerable size, and users have to live with that
whether their CSS uses the class attributes or not (and most users use the
default CSS). Not everyone has huge bandwidth, and GSM is frequently the
only comms medium in remote locations like sailing clubs.Ian..
On 15 November 2012 20:29,<yahoo@wittongilbert.free-online.co.uk> wrote:
**
**
On 2012-11-15 10:21, Ian Savell wrote:
Colin's comment just pre-empted mine, but I'll make it anyway. Sailwave
HTML did add a class to the columns to permit CSS formatting of each
column, in particular to make some columns left aligned and others centred.
But HTML/CSS in its wisdom allows very few attributes to be set in this way
so it doesn't work.Must be missing something! Just apply the style to the<td> using
classes<td class='row_label'>
<td class='result_odd'>
<td class='result_even'> // allows you to add vertical stripes
<td class='points'>
That allocation of classes needs to happen in the code. Naming by header
name makes sense...My own result publishing tried the same trick, and I then tried adding
a class to each<tr> to achieve the same thing. Such a proliferation of
class tags makes the HTML much longer,Its not exactly the end of the world in coding world - we should be
worrying about getting the right output then reducing the file size. But
in my example above class names could be shortened if need be to rL, rO,
rE, p if you wanted...which can be an issue when publishing to, say, a phone,
Getting a results page that views/navigates well on a phone would be a
priority over speed of download.