Writing a LibreOffice extension that logs user (and other) events in real-time

[Chide]

Hi Andrew,
Thank you so much for your quick reply. We will take your advice. In
the end - you think it is possible to realise what I said with an
extension? Or do you have doubts about it? Another, much less desirable
option, is that we dive right into the source code of LibreOffice and
add "hooks"...  I do not know how doable that is. Or are there even
other options?
If you would  gain more insight into the problems and tricky things you
mention below, then don't hesitate to let us know!
- C
On Thu, 2019-11-28 at 21:26 -0500, Andrew Pitonyak wrote:
> Take a look at event listeners to see what they can do
> 
> the biggest problems will probably be related to things such as
> understanding which event listeners get called in which orders and
> also things like what will cause an event listener to disappear such
> as changing from a print view to a regular view
> 
> and finally some of that information could be really tricky such as
> understanding that they have selected a particular region when what
> you really have access to is things like mouse clicks and down and up
> and that sort of thing.
> 
> 
> 
> Sent from BlueMail
> On Nov 28, 2019, at 7:20 PM, Chide Groenouwe <cg at xs4all.nl> wrote:
> > Hi,
> > 
> > I'm new to LibreOffice extension development. To prevent my team
> > and I investing too much time in studying how to write LibreOffice
> > extensions, I want to pose a question:
> > 
> > Is it possible to capture/intercept all - or at least most - user
> > events that occur within LibreOffice by means of an extension, in
> > real-time? For example, suppose that someone
> > 
> > 0) opens a new document in Writer by using the drop-down menu item
> > "New -> Text Document",
> > 1) types a text,
> > 2) selects a region using the mouse,
> > 3) presses the Italic button (so that the region becomes Italic),
> > and
> > 4) saves the text by pressing Ctrl-s.
> > 
> > Can you log all this information in real-time? Could you even log
> > each keypress of the user when this user is writing the text? And
> > can you also differentiate between the different methods that have
> > been used to accomplish a certain task? For example, can one
> > distinquish between saving a file by selecting a drop-down menu
> > item, or saving a file by using the short-cut key Ctrl-s?
> > 
> > Can this also be done for *other* extensions? Can you also log
> > events that occur within these?
> > 
> > Or should we use another approach to accomplish this all?
> > 
> > (Although not needed for answering the question: If you wonder -
> > the context has something to do with process mining (
> > https://en.wikipedia.org/wiki/Process_mining) -- in this case to
> > optimise software usage...)
> > 
> > Thank you so much in advance,
> > 
> > Chide Groenouwe
> > 
> > LibreOffice mailing list
> > LibreOffice at lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/libreoffice
> 
> _______________________________________________LibreOffice mailing
> listLibreOffice at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libreoffice
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20191129/72f86ecc/attachment.html>