GSoC 18 work report - 23rd May


The coding period of GSoC started 10 days ago. I'm working with LibreOffice's UI logger. The aim of first two weeks is to support logging for UNO commands, dialogs, radiobuttons, checkboxes, and buttons.
To get a summary of what has been done so far, let's perform a couple of steps and look at the generated log file.

Steps:
1) Click on "Writer Document" button
2) Go to Format -> Character to open the Character Properties Dialog.
3) Check the radiobutton 90 degrees and check the checkbox "Fit to line".
4) Click ok
5) Type "hi" in the main wrier_edit window

libreoffice_steps

The generated log file contains the following -
  1. ButtonUIObject Action:CLICK Id:writer_all Parent:
  2. CommandSent Name:.uno:FontDialog
  3. ModalDialogExecuted Id:CharacterPropertiesDialog
  4. RadioButtonUIObject Action:CLICK Id:90deg Parent:CharacterPropertiesDialog
  5. Action on element: 90deg with action : CLICK
  6. CheckBoxUIObject Action:CLICK Id:fittoline Parent:CharacterPropertiesDialog
  7. Action on element: fittoline with action : CLICK
  8. ButtonUIObject Action:CLICK Id:ok Parent:CharacterPropertiesDialog
  9. DialogClosed
  10. SwEditWinUIObject Action:TYPE Id:writer_edit Parent:UNKNOWN {"TEXT": "h"}
  11. SwEditWinUIObject Action:TYPE Id:writer_edit Parent:UNKNOWN {"TEXT": "i"}

As evident, the log file logs about-
1) Opening and closing of dialogs
2) UNO commands
3) Radiobuttion, checkbox and button click
4) Keys pressed

I'm stuck with printing the top parent of a generic UI element (so that the Parent:UNKOWN in the log file in lines 10 and 11 start giving some useful information)

The code of my work can be found here: https://gerrit.libreoffice.org/54745

Suggestions for what I have done so far, or what I should be working on next are welcome!

Comments

  1. NathanialDecember 24, 2018 at 2:11 AM

    Hello. If you want to know about all the companies. My company knows about 170 worple road freehold limited. If you want to know about 170 worple road freehold limited please contact with my company. You can also know more about companies.
    Thank you.

    ReplyDelete
  2. sandeep saxenaFebruary 27, 2019 at 10:02 PM

    This is very nice post im very like it and i appreciate you for good work keep it up it is very useful for me.
    Struts Training in Chennai
    Struts Training
    Wordpress course in Chennai
    Wordpress Training Chennai
    Wordpress Training in Adyar
    Wordpress Training in OMR
    Struts Training
    Struts Training in Chennai

    ReplyDelete
  3. ManipriyanJune 15, 2019 at 11:21 PM

    This comment has been removed by the author.

    ReplyDelete
  4. UnknownJuly 12, 2021 at 9:39 PM

    You should be a piece of a challenge for probably the best website on the web. I will suggest this site!

    best interiors

    ReplyDelete

Post a Comment

Popular posts from this blog

An overview of how UI logging works in LibreOffice

Logging in LibreOffice is mainly handled by a class called UITestLogger, defined here . The logger class logs the user actions only if the member flag mbValid is set to true. The flag can be turned on by setting the environment variable LO_COLLECT_UIINFO to a file name where the logs should be collected (see the constructor of UITestLogger, defined here ). We maintain a pointer to an instance of UITestLogger class here . To use the logger object, the static function getInstance can be used to get access to the pointer. The function logAction, defined in the same class, is used to log events from the classes which extend the class vcl::Control. The log statements corresponding to a particular class can be found in the function get_action of the UI wrapper classes. Most of the wrapper classes can be found with this OpenGrok search. The log statements get generated when VCL events get broadcasted. A list of the VCL events can be found in the enum class VclEventId here . ...
Read more

Things to know if you are a new contributor to LibreOffice code

When I began contributing code to LibreOffice, I faced some issues because I didn't know several facts that the other active contributors knew. This blog post summarizes some of those facts, and I hope it will be useful for other new contributors! 1) The data types LibreOffice code uses - If you have already browsed through the codebase of LibreOffice, you might have realized that the code doesn't generally use data types like int, float, double, et cetera like we use in small C++ programs. LibreOffice has its own classes, typedefs and structs defined and most of the code use them instead of the trivial data types. Some of those are OUString (instead of string), sal_uInt32 (instead of unsigned int), etc.
Read more

GSoC final report - UI logger

Overview The idea of this GSoC project was to implement a feature which logs the interaction of users with the UI elements in an interpretable Domain Specific Language (DSL), and an interpreter which converts the log into a file into something which will help in replaying the user actions. The project involved working with the UI elements and the UI testing framework of LibreOffice. Achievements The logger - The logging for the following is currently supported - The UI elements of Visual Component Library like Buttons, Checkboxes, Radio-buttons, Listboxes, Comboboxes, Spinbuttons, etc. Keys pressed in different UI elements UNO commands sent with parameters Selection of Objects Opening of Sidebar/Deck Some application-specific events can also be logged - Writer - Goto Page, Set Zoom, Text Selection Calc - Autofilter Launch, Selection of cells/range of cells, Switching of Sheet Math - Selection of elements from the element selector panel Impress - Set Zoom Addi...
Read more