Fwd: Re: [icedtea-web] xml output for junit, transformation sheets for daily report

Dr Andrew John Hughes ahughes at redhat.com
Thu May 12 09:57:04 PDT 2011

On 13:20 Thu 12 May     , Jiri Vanek wrote:


> My intention is really not to provide final html. It is to provide data, 
> and some simple possibility to view them. Javascript have evolved into 
> quite sufficient language, quite perfect for this usage. I see no reason 
> why use xsltproc instead of it. I'm pretty sure that this solution is 
> working in all common gui-based linux browser. In case somebody  still 
> prefer  commandline browser then the xml is more suitable for him.

What contradicts this is the fact you had to have two cases in the Javascript
to handle different browsers.  I presume, now you removed the ActiveX solution,
it doesn't work on Internet Explorer any more.

I don't like making assumptions about end users.  Not only may it not work on
some browsers, people do perfectly legitimately disable Javascript or restrict
it to certain sites.

Processing the XML post-test using xsltproc has the advantage that there is
only a requirement on the machine producing the test results, rather than
every client viewing it.

> >> As mentioned at the top, index.html is overview after make check and
> >> make distcheck - especially for the one who made the build.
> >>
> >
> > I still think something like xsltproc to generate the final HTML
> > would be preferable.  Doing things in web pages tends to be horrible
> > to support across multiple browsers.
> Except M$IE javascript is moreover united IMHO.
> >

Which browsers did you test?

As I said, even if it works on a browser, it doesn't mean it's enabled.

On a side note, can we please not have all this "M$" nonsense?  It
seems a little childish.


> >
> > I didn't see this post.  My mailer shows the thread as started May 9th.
> > Maybe it got buried during the time I was away with all the UK bank holidays.
> That is  why I have threads turned off and  rely more to my (full of 
> holes) memory :)
> >

Having threads on works well for most mail, as it allows me to recap
the context of a discussion.  You seem to have broken the thread with
one of your mails, which is what caused the problem.

> >>
> >> Regards J.
> >>
> >>
> >

Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and IcedTea
PGP Key: F5862A37 (https://keys.indymedia.org/)
Fingerprint = EA30 D855 D50F 90CD F54D  0698 0713 C3ED F586 2A37

More information about the distro-pkg-dev mailing list