I want to make the published stuff (results, alt. dec. forms etc) more
customisable. There are a few fundamental approaches; feedback about which
is best is welcome.
Possibilities.
� Each report is a HTML page containing 'meta' references to Sailwave
data - flexible but would need JavaScript for control flow of dimensioned
objects. Limited to HTML which is OK in my book.
� Implement a COM or DDE interface to Sailwave and let Word/Excel (etc)
macros do the work - flexible and ultimate formatting capabilities because
of or Word/Excel. Can print to paper from Word/Excel.
� Provide options for font size etc etc using the existing HTML -
inflexible but simple.
� Just add more hard-wired examples... ug.
� A middle-ground - keep the basic publishing as now but allow users to
tweak the style sheet part of each page and add libraries of style-sets.
Probably more flexible than it sounds as long as all the hard-wired HTML has
a class=x.
Colin,
I think allowing the users to adjust the font size etc and edit the style sheets or make their own is the best option. I would strongly suggest to keep Javascript, DDE and all that other fancy stuff out of it as things like that tend to crash browsers and sometimes Windows too.
That way users could share the layouts they like best by just sending the style sheet.
I'm sorry for repeating myself, but is there any way I can bring races from one Sailwave to another one? I tried just copying and pasting with notepad but this screwed up the orders and everything. It still wasn't quite right when I changed the "racerank" values to the right numbers either.
I want to make the published stuff (results, alt. dec. forms etc) more
customisable. There are a few fundamental approaches; feedback about which
is best is welcome.
Possibilities.
¤ Each report is a HTML page containing 'meta' references to Sailwave
data - flexible but would need JavaScript for control flow of dimensioned
objects. Limited to HTML which is OK in my book.
¤ Implement a COM or DDE interface to Sailwave and let Word/Excel (etc)
macros do the work - flexible and ultimate formatting capabilities because
of or Word/Excel. Can print to paper from Word/Excel.
¤ Provide options for font size etc etc using the existing HTML -
inflexible but simple.
¤ Just add more hard-wired examples... ug.
¤ A middle-ground - keep the basic publishing as now but allow users to
tweak the style sheet part of each page and add libraries of style-sets.
Probably more flexible than it sounds as long as all the hard-wired HTML has
a class=x.
Keep it as simple as possible. The beauty at the moment is that you can get the main print outs you require without having to do anything special to the program.
I want to make the published stuff (results, alt. dec. forms etc) more
customisable. There are a few fundamental approaches; feedback about which
is best is welcome.
Possibilities.
¤ Each report is a HTML page containing 'meta' references to Sailwave
data - flexible but would need JavaScript for control flow of dimensioned
objects. Limited to HTML which is OK in my book.
¤ Implement a COM or DDE interface to Sailwave and let Word/Excel (etc)
macros do the work - flexible and ultimate formatting capabilities because
of or Word/Excel. Can print to paper from Word/Excel.
¤ Provide options for font size etc etc using the existing HTML -
inflexible but simple.
¤ Just add more hard-wired examples... ug.
¤ A middle-ground - keep the basic publishing as now but allow users to
tweak the style sheet part of each page and add libraries of style-sets.
Probably more flexible than it sounds as long as all the hard-wired HTML has
a class=x.
I feel having a COM or DDE interface to Sailwave would be a good idea
but I think it should be available as an add-on. This way the program
can remain small and if people want the feature it can be added easily.
I believe the main download should not exceed 1.2Mb so it can be placed
on a single disk.
I want to make the published stuff (results, alt. dec. forms etc) more
customisable. There are a few fundamental approaches; feedback about
which
is best is welcome.
Possibilities.
¤ Each report is a HTML page containing 'meta' references to Sailwave
data - flexible but would need JavaScript for control flow of
dimensioned
objects. Limited to HTML which is OK in my book.
¤ Implement a COM or DDE interface to Sailwave and let Word/Excel
(etc)
macros do the work - flexible and ultimate formatting capabilities
because
of or Word/Excel. Can print to paper from Word/Excel.
¤ Provide options for font size etc etc using the existing HTML -
inflexible but simple.
¤ Just add more hard-wired examples... ug.
¤ A middle-ground - keep the basic publishing as now but allow users
to
tweak the style sheet part of each page and add libraries of style-sets.
Probably more flexible than it sounds as long as all the hard-wired HTML
has
a class=x.
I want to make the published stuff (results, alt. dec. forms etc) more
customisable. There are a few fundamental approaches; feedback about which
is best is welcome.
Possibilities.
� Each report is a HTML page containing 'meta' references to Sailwave
data - flexible but would need JavaScript for control flow of dimensioned
objects. Limited to HTML which is OK in my book.
� Implement a COM or DDE interface to Sailwave and let Word/Excel (etc)
macros do the work - flexible and ultimate formatting capabilities because
of or Word/Excel. Can print to paper from Word/Excel.
� Provide options for font size etc etc using the existing HTML -
inflexible but simple.
� Just add more hard-wired examples... ug.
� A middle-ground - keep the basic publishing as now but allow users to
tweak the style sheet part of each page and add libraries of style-sets.
Probably more flexible than it sounds as long as all the hard-wired HTML
I think it should be kept as simple as possible like it is now. The only
thing I would suggest is the option to make the HTML just a minimal table
without all the styles.
If I want to change the look and feel I import the SailWave generated page
into an HTML editing tool, e.g. DreamWeaver, Microsoft Word, HotDog or in my
case in to Microsoft Frontpage, and make the changes to match the look and
feel of my web site, see http://www.dwsc.co.uk/clubsailing/series/wedeve/series-alt.htm
I want to make the published stuff (results, alt. dec. forms etc) more
customisable. There are a few fundamental approaches; feedback about which
is best is welcome.
Possibilities.
� Each report is a HTML page containing 'meta' references to Sailwave
data - flexible but would need JavaScript for control flow of dimensioned
objects. Limited to HTML which is OK in my book.
� Implement a COM or DDE interface to Sailwave and let Word/Excel (etc)
macros do the work - flexible and ultimate formatting capabilities because
of or Word/Excel. Can print to paper from Word/Excel.
� Provide options for font size etc etc using the existing HTML -
inflexible but simple.
� Just add more hard-wired examples... ug.
� A middle-ground - keep the basic publishing as now but allow users to
tweak the style sheet part of each page and add libraries of style-sets.
Probably more flexible than it sounds as long as all the hard-wired HTML has
a class=x.