Re: HTML export of profiler data

[Daniel Kraft]

Hi John!

On 2016-02-25 19:28, John W. Eaton wrote:
> On 02/25/2016 01:18 PM, Daniel Kraft wrote:
>> On 2016-02-25 09:07, Julien Bect wrote:
>>> Le 24/02/2016 19:24, Daniel Kraft a écrit :
>>>> We could create a standalone CSS file that contains our rules (might be
>>>> more in the future, or we might also add JS files to enhance the report
>>>> even more).  This file could be installed in a /usr/share location, and
>>>> then referenced (at this location) from the generated HTML files.  This
>>>> seems like a cleaner way, although it means that HTML files may not be
>>>> portable to other machines -- not sure if that should be a design goal
>>>> or not.
>>
>>> a) going for the "separate CSS file" approach,
>>>
>>> b) but copying the CSS file(s) from /usr/share/... to the directory
>>> containing the report.
> 
> I agree that it would be good to have a single shared CSS file for
> temporary reports viewed from within Octave.
> 
> For files that are exported, is it unreasonable to insert the CSS in the
> HTML file itself?  How large is the CSS data?  I expect that people will
> forget that they need to transfer two files if they want to share the
> files with others.

This was my first thought as well, but the patch actually already
creates a whole directory of HTML files (for each function, roughly
speaking) linked to each other.  So if there is a directory to send
anyway, adding the CSS file seems like a small additional price to pay
and is probably easier than fiddling the CSS into the HTML file
(although that is not too hard as well).

Yours,
Daniel

-- 
http://www.domob.eu/
OpenPGP: 1142 850E 6DFF 65BA 63D6  88A8 B249 2AC4 A733 0737
Namecoin: id/domob -> https://nameid.org/?name=domob
--
Done:  Arc-Bar-Cav-Hea-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Mon-Pri

signature.asc
Description: OpenPGP digital signature