1. 08 Nov, 2016 2 commits
  2. 26 Oct, 2016 1 commit
  3. 25 Oct, 2016 2 commits
  4. 20 Oct, 2016 1 commit
    • Martin Flöser's avatar
      [tools/generator] Improve resource destruction on server side · efbd11b8
      Martin Flöser authored
      The generator misdetected the destructor Requests by looking at the
      arguments instead of the type of the request.
      In addition the destructor handling changed in KWayland::Server since
      the generator got created. There is now a shared implementation for the
      Resource destruction. The generator is adjusted to generate the code for
      that and implements the destruction for the Global resource destruction.
  5. 05 May, 2016 1 commit
  6. 10 Sep, 2015 1 commit
  7. 09 Sep, 2015 2 commits
    • Sebastian Kügler's avatar
      small fixes for kwaylandScanner · 7d2f54a4
      Sebastian Kügler authored
      * fix initializer type -- was hardcoded, seems like an oversight
      * add semicolons after class declarations -- one less thing to fix in the
        resulting code
    • Martin Flöser's avatar
      Fix doxygen generation · 502e1c5d
      Martin Flöser authored
      Doxygen doesn't like our callback listener at all. We need to hide
      it from doxygen, otherwise docu doesn't get generated.
  8. 08 Sep, 2015 1 commit
  9. 07 Sep, 2015 3 commits
  10. 04 Sep, 2015 1 commit
  11. 03 Sep, 2015 1 commit
    • Martin Flöser's avatar
      Add a small tool to generate the boilerplate for Wayland interfaces · 11c9fc0b
      Martin Flöser authored
      The small tool added here allows to automate the process of generating
      the boiler plate for an interface. Currently it's able to generate the
      Client side code representing a wl_global.
      The tool does not get installed, so run it from build directory:
      Example usage:
      ./kwaylandScanner -c Foo -f foo -g wl_foo
      This will generate a wrapper for the wl_foo interface in files:
      foo.h and foo.cpp
      The class is called KWayland::Client::Foo.
      The tool will be extended. Following things are on the TODO list:
      * parse xml to get the Wayland names
      * add listener (if needed)
      * generate code for Wayland interfaces representing Resources
      * generate the Server boiler plate
      CCMAIL: mart@kde.org
      CCMAIL: sebas@kde.org