Development/VCL/minweld

    From The Document Foundation Wiki

    LibreOffice uses VCL (Visual Class Library) as its internal widget toolkit to create the graphical user interface (GUI) of LibreOffice. Here we discuss how to use UI files designed with Glade interface designer to create LibreOffice user interfaces with a framework called weld, which is part of LibreOffice core source code. Creating a Minimal VCL Weld Application

    VCL Weld Mechanism

    Main article: VCL weld mechanism.

    In order to simplify user interface creation in LibreOffice, Caolán McNamara introduced a mechanism to load UI files created with Glade interface designer, and use them as if they are UI files for each and every GUI framework that LibreOffice supports: from GTK to Qt, Windows, macOS and even the so-called gen backend that only requires the X11 library on Linux.

    To illustrate how the VCL weld mechanism works, a minimal example, minweld, is provided as a test workbench. In the code, UI is created from a .ui file that is designed visually with Glade interface designer. The .ui file is an XML file which contains placement of widgets that should be displayed on the screen.

    The complete code for minweld is available in the LibreOffice core source code repository as vcl/workben/minweld.cxx, which can also be viewed online.

    Glade UI File

    In minweld, an existing Glade UI file, tipofthedaydialog.ui, has been used. This is the user interface for displaying a tip of the day in LibreOffice at startup. Here, we use it to create our own user interface in C++. You may use any other .ui file that you have created with almost the same code.

    This UI file is found in cui/uiconfig/ui/tipofthedaydialog.ui, and minweld loads it.

    Let’s look into the specifics of minweld.cxx.

    Header Includes

    We include vcl/weld.hxx:

    #include <vcl/weld.hxx>

    Then we have the C++ code for the application. The TipOfTheDayDialog class is defined with:

    class TipOfTheDayDialog : public weld::GenericDialogController
    {
    public:
        TipOfTheDayDialog(weld::Window* pParent = nullptr);
        DECL_LINK(OnNextClick, weld::Button&, void);
    
    private:
        std::unique_ptr<weld::Label> m_pTextLabel;
        std::unique_ptr<weld::Button> m_pNextButton;
        sal_Int32 m_nCounter = 0;
    };
    ...
    }

    As you can see, TipOfTheDayDialog inherits from weld::GenericDialogController. The TipOfTheDayDialog constructor receives a parent of type weld::Window*, which is nullptr now. The reason is that there is no parent window in this example. Using weld:: prefix is also done for other types of widgets that we use in LibreOffice. For example, we use weld::Button to denote a push button in LibreOffice, or in any application that is created with the vcl::weld mechanism.

    Class Constructor

    This is the code for the TipOfTheDayDialog constructor. Here, we initialize two member variables, m_pTextLabel and m_pNextButton which point to a label and a button, respectively. We will interact with these two in our code. There are string literals like lbText and btnNext, which are the IDs of those widgets in Glade. The IDs should be unique for linking to specific variables in the code.

    TipOfTheDayDialog::TipOfTheDayDialog(weld::Window* pParent)
    : weld::GenericDialogController(pParent, u"cui/ui/tipofthedaydialog.ui"_ustr,
    u"TipOfTheDayDialog"_ustr)
    , m_pTextLabel(m_xBuilder->weld_label(u"lbText"_ustr))
    , m_pNextButton(m_xBuilder->weld_button(u"btnNext"_ustr))
    {
        m_pNextButton->connect_clicked(LINK(this, TipOfTheDayDialog, OnNextClick));
    }

    One last step is linking the events with functions in the code. You may do that with the LINK macro. In the last line, connect_clicked activates OnNextClick from the class TipOfTheDayDialog, whenever m_pNextButton is clicked.

    Event Handler

    This is the implementation of the event handler. It should be started with IMPL_LINK macro, in the form of IMPL_LINK_NOARG(Class, Member, ArgType, RetType). The code is straightforward: It increases a counter which is initially zero, and displays it alongside a text:

    IMPL_LINK_NOARG(TipOfTheDayDialog, OnNextClick, weld::Button&, void)
    {
        ++m_nCounter;
        m_pTextLabel->set_label(u"Here you will see tip of the day #"_ustr
    + OUString::number(m_nCounter) + ".");
    }

    With a call to set_label function, m_pTextLabel is updated every time that you click on Next Tip.

    Running the Example

    You may run the example after you have built LibreOffice from sources. Then, you may simply invoke:

    ./bin/run minweld

    The result is a little bit different from the tipoftheday dialog in LibreOffice, as it does not use a picture. But, it has a nice feature: if you click on Next Tip, it will show a text and a counter that goes up whenever you click on it again.

    Final Notes

    You may look into the original “tip of the day” dialog box in cui/source/dialogs/tipofthedaydlg.cxx, which is more complex than the one that we created here, as it reads some data from the configuration and uses images. The idea is the same, though. Inherit a class from GenericDialogController, define and link variables to the widgets with their IDs, add event handlers. Now, the application with VCL graphical user interface is ready to use!

    This is somehow similar to the way one creates dialog boxes with Qt and other widget toolkits. On the other hand, the VCL weld mechanism is different in the way that it uses such a toolkit to create UI on the fly. Therefore, if you choose a desired VCL UI plugin, then it will use that specific library for creating user interface. For example, you can run minweld example with Qt this way:

    export SAL_USE_VCLPLUGIN=qt5
    
    ./bin/run minweld

    You may also run it with GTK3 UI this way:

    export SAL_USE_VCLPLUGIN=gtk3
    
    export GTK_THEME=Adwaita:light # For light/dark theme
    
    ./bin/run minweld