Re: [Bug-gnubg] HTML export

[Nardy Pillards]

[snip]

>> A few problems:
>>
>> (a) it's impossible to print the entire game, match, or session
>>     within the browser
>> (b) we have to implement this with JavaScript or ECMA script, which
>>      (1) is probably browser dependent
>>      (2) won't work in older browsers
>>      (3) won't work if the user has disabled javascript
>> (c) we use frames which won't work in older browsers
>>     (in general, frames suck, but they may be have a usual purpose here)
>>
>> Of course, it's possible to make it an option to export in the current
>> one-game-per-page format so people still can use that.
>>
>> ad (a): we can't do anything about that
>> ad (b): it's possible to make some work-arounds for missing or disabled
>> JavaScript. For example, instead of the game dropdown we can display a
>> series of links, and the user must live with the fact that the right
>> hand move list does not automatically scrolls when she clicks on the
>> "next move" and "prev move" links.
>> ad (c): we can't do anything about that
>>
>> Jørn
>
> As to a), I think the idea of opening a separate window for a
> printer-friendly version fine. In fact, it could simply be an option to
> view it in a plain HTML version. This would immediately solve the
> problem for those using older browsers. The thing is that I think it
> would be a big improvement over the current way of viewing. I don't ant
> to isolate the users of older browsers, but think that one mustn't limit
> the possibilties according to 1990 technology just because 2% of users
> are still stuck with it. A plain HTML version link would let them still
> enjoy the games. Plus this would be the solution for printing.
>

[snip]
> Albert

Win32 here, and only 500 visitors since Dec 20th, but stats so far:

Javascript: all enabled (91% JS 1.3, 5% JS 1.4, 3% JS 1.1 and  1% JS 1.2)

Browsers: 72% IE 6.x, 18% IE 5.x, 5% NS 5.x, 3% NS 3.x and 2% NS 4.x

oh... and:
PNG Graphics: 95% yes, 5% no.

Nardy