Video of the California 4 bypass

Jon Morse wrote:
> Andrew Tompkins wrote:
>> Jon Morse wrote:
>>> Further, one should not "force" people into a format which really
>>> does depend on either using a specific OS (and its built-in memory
>>> hog viewing application which uses way too many resources on crap you
>>> don't need), paying for a decent substitute viewing application, or
>>> settling for really crappy freeware which doesn't always handle it
>>> properly.
>>>
>>
>> So, you're saying that, if I put up a website, it should be compatible
>> with all platforms, despite the incompatibilities between all of them?
>> I'm having enough trouble getting my stripchart website to work on
>> both IE and Mozilla stuff (which would allow most non-Windows
>> platforms to view the stripchart pages) from one set of pages. And
>> I'm not about to put up 2 complete sets of pages to satisfy that.
>
> "All"? No. Primarily because "all" includes "crappy **** that doesn't
> follow standards" anyway. Windows, Mac, Linux; IE, Firefox, Safari.
>
> Now, see... your strip chart stuff... I've been out of the community for
> a couple-three years, but I recall seeing some really cool XML strip
> chart stuff back before I got distracted with life. Were those yours?
> If not, my following argument is still relevant anyway, just not
> directly applicable to you personally. (And if they were, hey, those
> were really awesome.)
>

From the sounds of it, those were mine. They are still available at
http://home.comcast.net/~andytom/Highways/index.html
Coverage is now 8 states: WA, OR, CA, ME, NH, VT, MA and RI.

>
> The two things are quite a bit different; the different browsers
> approached XML strangely and are just starting to get back into sync,
> and the XML strip charts I recall couldn't have been done another way
> (at least not sensibly). It was worth jumping through some hoops, *as a
> user*, to check them out for that reason. (And ironically, Mac users
> had fewer hoops to jump through; in fact, at first I HAD to use my Mac
> to check them out.)
>

Do you remember any of the details for viewing on Mac? I'd like to put
them on the requirements page.

>
> BIG difference between that and deciding whether to
> use WMV or some other non-annoying, non-proprietary movie format; no
> relevant browser has any problem displaying an AVI file for example, and
> the only difference in the code for the webmaster is the filename.
>

He also produces the videos. Are you certain that he has the capability
to produce in AVI? Have you asked? Non-confrontationally?

--
--Andy

Andrew Tompkins wrote:

> Jon Morse wrote:
>> Andrew Tompkins wrote:
>>> Jon Morse wrote:
>>>> Further, one should not "force" people into a format which really
>>>> does depend on either using a specific OS (and its built-in memory
>>>> hog viewing application which uses way too many resources on crap you
>>>> don't need), paying for a decent substitute viewing application, or
>>>> settling for really crappy freeware which doesn't always handle it
>>>> properly.
>>>>
>>>
>>> So, you're saying that, if I put up a website, it should be compatible
>>> with all platforms, despite the incompatibilities between all of them?
>>> I'm having enough trouble getting my stripchart website to work on
>>> both IE and Mozilla stuff (which would allow most non-Windows
>>> platforms to view the stripchart pages) from one set of pages. And
>>> I'm not about to put up 2 complete sets of pages to satisfy that.
>>
>> "All"? No. Primarily because "all" includes "crappy **** that doesn't
>> follow standards" anyway. Windows, Mac, Linux; IE, Firefox, Safari.
>>
>> Now, see... your strip chart stuff... I've been out of the community for
>> a couple-three years, but I recall seeing some really cool XML strip
>> chart stuff back before I got distracted with life. Were those yours?
>> If not, my following argument is still relevant anyway, just not
>> directly applicable to you personally. (And if they were, hey, those
>> were really awesome.)
>>
>
> From the sounds of it, those were mine. They are still available at
> http://home.comcast.net/~andytom/Highways/index.html
> Coverage is now 8 states: WA, OR, CA, ME, NH, VT, MA and RI.
>
>>
>> The two things are quite a bit different; the different browsers
>> approached XML strangely and are just starting to get back into sync,
>> and the XML strip charts I recall couldn't have been done another way
>> (at least not sensibly). It was worth jumping through some hoops, *as a
>> user*, to check them out for that reason. (And ironically, Mac users
>> had fewer hoops to jump through; in fact, at first I HAD to use my Mac
>> to check them out.)
>>
>
> Do you remember any of the details for viewing on Mac? I'd like to put
> them on the requirements page.
>
>>
>> BIG difference between that and deciding whether to
>> use WMV or some other non-annoying, non-proprietary movie format; no
>> relevant browser has any problem displaying an AVI file for example, and
>> the only difference in the code for the webmaster is the filename.
>>
>
> He also produces the videos. Are you certain that he has the capability
> to produce in AVI? Have you asked? Non-confrontationally?
>

There are any number of handy-dandy file conversion programmes out there for
all platforms.

--
Comrade Otto The Duke Of Yamamoto
http://mryamamoto.50megs.com

Andrew Tompkins wrote:
> Jon Morse wrote:
>> The two things are quite a bit different; the different browsers
>> approached XML strangely and are just starting to get back into sync,
>> and the XML strip charts I recall couldn't have been done another way
>> (at least not sensibly). It was worth jumping through some hoops, *as
>> a user*, to check them out for that reason. (And ironically, Mac
>> users had fewer hoops to jump through; in fact, at first I HAD to use
>> my Mac to check them out.)
>>
>
> Do you remember any of the details for viewing on Mac? I'd like to put
> them on the requirements page.

Gah, this was at least two years ago, I think. IIRC, it was "open
safari, go to link, profit!", meaning that version of Safari already had
an XSLT translator (which really should be the only "requirement" as far
as I can tell).

At the time, it did not work for Firefox on a Windows machine, and I
assiduously avoid using IE, although I would have attempted it had it
not worked on the Mac.

By the way, works fine now in Firefox 2.0.0.12 on Vista (with no
plug-ins or add-ons), so Mozilla's obviously added translation as well.

--
Jon Morse
Herndon, VA

Jon Morse wrote:
> Andrew Tompkins wrote:
>> Jon Morse wrote:
>>> The two things are quite a bit different; the different browsers
>>> approached XML strangely and are just starting to get back into sync,
>>> and the XML strip charts I recall couldn't have been done another way
>>> (at least not sensibly). It was worth jumping through some hoops,
>>> *as a user*, to check them out for that reason. (And ironically, Mac
>>> users had fewer hoops to jump through; in fact, at first I HAD to use
>>> my Mac to check them out.)
>>>
>>
>> Do you remember any of the details for viewing on Mac? I'd like to
>> put them on the requirements page.
>
> Gah, this was at least two years ago, I think. IIRC, it was "open
> safari, go to link, profit!", meaning that version of Safari already had
> an XSLT translator (which really should be the only "requirement" as far
> as I can tell).
>
> At the time, it did not work for Firefox on a Windows machine, and I
> assiduously avoid using IE, although I would have attempted it had it
> not worked on the Mac.
>
> By the way, works fine now in Firefox 2.0.0.12 on Vista (with no
> plug-ins or add-ons), so Mozilla's obviously added translation as well.
>

Thanks for the info.

I think they all have had the translator available for quite some time.
The problem has always been that all of them except IE required that
the applicable mime type be sent also, which Comcast doesn't do (and for
whatever reason, won't add to the list unless they recently have done
so). Looks like things are changing. I need to make some adjustments
(the shield doesn't come out right and the stripchart isn't centered in
my Firefox display).

--
--Andy