[prev in list] [next in list] [prev in thread] [next in thread]
List: gtk-devel
Subject: Re: Interface analyzer for GTK+
From: Matthias Clasen <matthias.clasen () gmail ! com>
Date: 2015-10-01 12:49:54
Message-ID: CAFwd_vAzPz-Zd0EMjVj7fx0O0Qf8-g03TWh_TYfJxAhn9FK-mQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Sep 28, 2015 at 1:58 PM, Daniel Milewski <
danmilew1@student.pg.gda.pl> wrote:
> As a part of my engineer's thesis I'm developing a interface analysis
> tool for GTK+. The tool's purpose is to let one judge how good the
> interface design is based on task execution and learning time. It'll
> employ a theoretical framework known as the GOMS method[1]. As I hope
> to get my code accepted into GTK+, I have a few questions.
>
> I need to make GTK+ create an event log in runtime. I skimmed through
> documentation and the source code and I've found the --gtk-debug
> option. My idea was to add a one more debug flag named "goms" to make
> analysis conditional. Is it ok?
> It'd also be nice to have a way to specify a filename of the event log.
> Since it's not possible to squeeze the filename into the debug string,
> is it ok to introduce a second command line for this?
>
> I also wonder if there is a preferred format for dumps of this kind in
> GNOME. I think of going with XML since a lot of other things in GNOME
> like interface descriptions also make use of XML. Do you have better
> ideas or suggestions on this?
>
> If XML is ok, then what is the recommended way to generate XML output
> in GNOME? I saw that some parts of GTK+ are generating XML from inline
> strings and using convenience functions provided by GMarkup, which is
> rather not clean. Is it fine to generate dumps this way? I wonder if
> introducing a dependency on e.g. libxml would be better.
>
> [1] https://en.wikipedia.org/wiki/GOMS
>
I don't think putting such specialized logging directly into GTK+ is going
to be acceptable. I would suggest to either investigate if you can get what
you need through the accessibility framework, or look at creating a
loadable module that connects signal handlers to catch the necessary events
(you can eg look at libcanberra for how that works in practice).
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra">On Mon, Sep 28, 2015 at 1:58 PM, Daniel \
Milewski <span dir="ltr"><<a href="mailto:danmilew1@student.pg.gda.pl" \
target="_blank">danmilew1@student.pg.gda.pl</a>></span> wrote:<br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">As a part of my engineer's \
thesis I'm developing a interface analysis<br> tool for GTK+. The tool's \
purpose is to let one judge how good the<br> interface design is based on task \
execution and learning time. It'll<br> employ a theoretical framework known as \
the GOMS method[1]. As I hope<br> to get my code accepted into GTK+, I have a few \
questions.<br> <br>
I need to make GTK+ create an event log in runtime. I skimmed through<br>
documentation and the source code and I've found the --gtk-debug<br>
option. My idea was to add a one more debug flag named "goms" to make<br>
analysis conditional. Is it ok?<br>
It'd also be nice to have a way to specify a filename of the event log.<br>
Since it's not possible to squeeze the filename into the debug string,<br>
is it ok to introduce a second command line for this?<br>
<br>
I also wonder if there is a preferred format for dumps of this kind in<br>
GNOME. I think of going with XML since a lot of other things in GNOME<br>
like interface descriptions also make use of XML. Do you have better<br>
ideas or suggestions on this?<br>
<br>
If XML is ok, then what is the recommended way to generate XML output<br>
in GNOME? I saw that some parts of GTK+ are generating XML from inline<br>
strings and using convenience functions provided by GMarkup, which is<br>
rather not clean. Is it fine to generate dumps this way? I wonder if<br>
introducing a dependency on e.g. libxml would be better.<br>
<br>
[1] <a href="https://en.wikipedia.org/wiki/GOMS" rel="noreferrer" \
target="_blank">https://en.wikipedia.org/wiki/GOMS</a><br></blockquote><div><br></div><div>I \
don't think putting such specialized logging directly into GTK+ is going to be \
acceptable. I would suggest to either investigate if you can get what you need \
through the accessibility framework, or look at creating a loadable module that \
connects signal handlers to catch the necessary events (you can eg look at \
libcanberra for how that works in practice). <br></div></div></div></div>
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic