Hello,
Damien Nozay wrote:
> Well we do not use something fancy, just firefox. Http supports compression.
> see http://en.wikipedia.org/wiki/HTTP_compression,
> see "network.http.accept-encoding" key in firefox about:config.
The documentation you are referring to describes on-the-fly compression of HTML pages to reduce bandwidth usage, not storing HTML files in compressed form. I'm not sure how a web browser would decide when to serve the gzip file as binary and when to render the uncompressed html file.
>> On the other hand it shouldn't be too difficult for you to write
>> a small script that compresses all files in the html directory created by
>> genhtml in the way you described, which is then run right
>> after genhtml.
>
> That is what there is now, but doing that as a 2nd pass is time consuming,
> plus
> some people just will not run the script.
A wrapper script might help.
>> > it would also be nice to have function details (gcov
>> > --function-summaries) in generated html (maybe keep same option
>> > name?).
>>
>> This has been on the wish-list for some time already and will
>> be considered when more development is being done on lcov.
>
> Where could I find this wish-list?
There's no dedicated wish-list/feature request tracking instance for lcov. Whenever there is time for more advanced lcov changes, I search for previous postings on this mailing list to find out about commonly requested features.
> I do have some more ideas for development
> but maybe
> they are already in that wish-list.
Posting them on ltp-coverage would be the prefered way (at least for me).
Regards,
Peter

Hello Peter,=20
> I don't think this kind of compressed html is part of a=20
> published standard and I'm rather reluctant to add support=20
> for special browsers in a generic tool.
Well we do not use something fancy, just firefox. Http supports =
compression.
see http://en.wikipedia.org/wiki/HTTP_compression,
see "network.http.accept-encoding" key in firefox about:config.
> On the other hand it shouldn't be too difficult for you to write=20
> a small script that compresses all files in the html directory created =
by=20
> genhtml in the way you described, which is then run right=20
> after genhtml.
That is what there is now, but doing that as a 2nd pass is time =
consuming,
plus
some people just will not run the script.
> > it would also be nice to have function details (gcov=20
> > --function-summaries) in generated html (maybe keep same option=20
> > name?).
>=20
> This has been on the wish-list for some time already and will=20
> be considered when more development is being done on lcov.
Where could I find this wish-list? I did not see that neither in the ltp
bug/feature tracker
nor on the LTP>Coverage>lcov page. I do have some more ideas for =
development
but maybe
they are already in that wish-list.
thank you,
damien
> -----Original Message-----
> From: Peter Oberparleiter [mailto:oberparleiter@...]=20
> Sent: Friday, February 01, 2008 2:08 AM
> To: Damien Nozay
> Cc: ltp-coverage@...
> Subject: Re: [Ltp-coverage] some more options in lcov
>=20
> Hello,
>=20
> Damien Nozay wrote:
> > we are using browsers with
> > htmlz support, so
> > it would be nice to have support for that in genhtml,=20
> relying on 'gzip -S z'
> > to do the
> > job. That would be useful.
>=20
> I don't think this kind of compressed html is part of a=20
> published standard and I'm rather reluctant to add support=20
> for special browsers in a generic tool. On the other hand it=20
> shouldn't be too difficult for you to write a small script=20
> that compresses all files in the html directory created by=20
> genhtml in the way you described, which is then run right=20
> after genhtml.
>=20
> > it would also be nice to have function details (gcov=20
> > --function-summaries) in generated html (maybe keep same option=20
> > name?).
>=20
> This has been on the wish-list for some time already and will=20
> be considered when more development is being done on lcov.
>=20
>=20
> Regards,
> Peter Oberparleiter
>=20

Hello,
Damien Nozay wrote:
> we are using browsers with
> htmlz support, so
> it would be nice to have support for that in genhtml, relying on 'gzip -S z'
> to do the
> job. That would be useful.
I don't think this kind of compressed html is part of a published standard and I'm rather reluctant to add support for special browsers in a generic tool. On the other hand it shouldn't be too difficult for you to write a small script that compresses all files in the html directory created by genhtml in the way you described, which is then run right after genhtml.
> it would also be nice to have function details (gcov --function-summaries) in
> generated html
> (maybe keep same option name?).
This has been on the wish-list for some time already and will be considered when more development is being done on lcov.
Regards,
Peter Oberparleiter