[
Lists Home |
Date Index |
Thread Index
]
At 22:17 23/07/2006, Didier PH Martin wrote:
<snip/>
>Didier replies:
>Dam Jeff you're fast.
>
>This raises a new point: update of the transformation document to get in
>tune with new versions. This is what people are doing anyway to stay in
>phase with Java. More than one time I encountered problems of
>incompatibility brought by new java run times or new JDKs. This is why most
>of the install programs have a java run-time check before installation. Why
>not having same thing for datument or more specifically for their transform
>script/template? We expect too much from browsers it seems.
This is an excellent idea and should be included in our services.
There are too many variations in apparently standard formats and it
would be extremely useful to have a checker. Not much fun to write,
but really valuable. We should be able to convince the publishers to use them.
<snip/>
>OK everybody,
>
>More seriously, what about a small environment to check the platform (i.e.
>the browser version, manufacturer) and either ask for what is required,
>download it (after the user's approval) and run it?
Another very good idea.
>Anyway, the alternative
>based on IBM's version of Java (yes, this is another hypnotic trance here,
>the java world is not standardized and homogeneous) will ask for the same
>things doesn't it? OK I'll count from 1 to three and.... :-)
>
>You know what? This small run-time can be made in ECMAScript/Javascript...
Again this looks feasible. I am happy for ECMAScript to be used for
small things like this but suspect it doesn't scale.
>P.
Peter Murray-Rust
Unilever Centre for Molecular Sciences Informatics
University of Cambridge,
Lensfield Road, Cambridge CB2 1EW, UK
+44-1223-763069
|
