KScreenGenie 1.9.95 release

[Boudhayan Gupta]

Hi,

Earlier today I tagged the 1.9.95 release of KScreenGenie. This is the
first release (I haven't generated any tarballs), and the 1.x.xx
numbering is because this is supposed to become KSnapshot 2.0.

There are no *known* bugs, but probably a few I've missed. There's no
docs or a handbook yet, or I would have applied to move into kdereview
now. I hope to have a basic handbook up in one or two days.

As for platform support, right now there's only X11 and a dummy
backend. The dummy backend is correctly loaded when started as a
Wayland application, but the X11 backend is loaded when started under
XWayland, which crashes the app with a core-dump. Standard X11 works
fine.

Comments, bug reports and patches welcome. There's no Bugzilla product
yet (again, because this will become KSnapshot-Next on release).

-- Boudhayan Gupta

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[ANNOUNCE] CMake 3.3.0-rc2 is now ready!

[Robert Maynard]

I am proud to announce the second CMake 3.3 release candidate.

Sources and binaries are available at:
  http://www.cmake.org/download/

Documentation is available at:
  http://www.cmake.org/cmake/help/v3.3

Release notes appear below and are also published at
  http://www.cmake.org/cmake/help/v3.3/release/3.3.html

Some of the more significant features of CMake 3.3 are:

* The "if()" command learned a new "IN_LIST" operator that evaluates
  to true if a given element is contained in a named list.

* The "add_dependencies()" command learned to allow dependencies to
  be added to *interface libraries*. Dependencies added to an
  interface library are followed transitively in its place since the
  target itself does not build.

* The "find_library()", "find_path()", and "find_file()" commands
  now search in installation prefixes derived from the "PATH"
  environment variable.

* The "_VISIBILITY_PRESET" and "VISIBILITY_INLINES_HIDDEN"
  target properties now affect compilation in sources of all target
  types.  See policy "CMP0063".

* A "_INCLUDE_WHAT_YOU_USE" target property and supporting
  "CMAKE__INCLUDE_WHAT_YOU_USE" variable were introduced to tell
  the *Makefile Generators* and the "Ninja" generator to run "include-
  what-you-use" along with the compiler for "C" and "CXX" languages.

Deprecated and Removed Features:

* The "ctest_build()" and "build_command()" commands no longer tell
  "make" tools to ignore errors with the "-i" option. Previously this
  was done for *Makefile Generators* but not others. See policy
  "CMP0061".

* The "Visual Studio 7" generator (.NET 2002) is now deprecated and
  will be removed in a future version of CMake.

* The "Visual Studio 6" generator is now deprecated and will be
  removed in a future version of CMake.

* The "add_definitions()" command no longer causes a "DEFINITIONS"
  directory property to be populated. See policy "CMP0059".


CMake 3.3 Release Notes
***

Changes made since CMake 3.2 include the following.


New Features



Generators
--

* The *Makefile Generators* now add ".DELETE_ON_ERROR" to the
  makefiles that contain the actual build rules for files on disk.
  This tells GNU make to remove rule outputs when their recipe
  modifies an output but fails.

* The *Visual Studio Generators* learned to support ".xaml" source
  files and automatically associate them with corresponding ".h" and
  ".cpp" sources.

* A new experimental "Green Hills MULTI" generator was added on
  Windows.  Green Hills MULTI is an IDE for embedded real-time
  systems.


Commands


* The "add_dependencies()" command learned to allow dependencies to
  be added to *interface libraries*. Dependencies added to an
  interface library are followed transitively in its place since the
  target itself does not build.

* The "execute_process()" command learned to support specifying the
  same file for "OUTPUT_FILE" and "ERROR_FILE".

* The "file(GLOB)" and "file(GLOB_RECURSE)" commands learned a new
  "LIST_DIRECTORIES " option to specify whether the glob result
  should include directories.

* The "find_library()", "find_path()", and "find_file()" commands
  now search in installation prefixes derived from the "PATH"
  environment variable.

* The "if()" command learned a new "IN_LIST" operator that evaluates
  to true if a given element is contained in a named list.

* The "install(EXPORT)" and "export()" commands learned to export
  targets that populate the "INTERFACE_SOURCES" target property.

* The "install(TARGETS)" command learned to support generator
  expressions in the "DESTINATION" value.


Variables
-

* The version of some Fortran compilers is now detected and stored
  in the "CMAKE_Fortran_COMPILER_VERSION" variable.

* The *Visual Studio Generators* learned a new
  "CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD" option to put the
  "INSTALL" target in the default build of a solution (".sln") file.


Properties
--

* A "CROSSCOMPILING_EMULATOR" target property and supporting
  "CMAKE_CROSSCOMPILING_EMULATOR" variable were introduced to allow
  target platform binaries to run on the host during cross compiling.

* A "_INCLUDE_WHAT_YOU_USE" target property and supporting
  "CMAKE__INCLUDE_WHAT_YOU_USE" variable were introduced to tell
  the *Makefile Generators* and the "Ninja" generator to run "include-
  what-you-use" along with the compiler for "C" and "CXX" languages.

* The "_VISIBILITY_PRESET" and "VISIBILITY_INLINES_HIDDEN"
  target properties now affect compilation in sources of all target
  types.  See policy "CMP0063".

* The "XCODE_ATTRIBUTE_" target property learned to
  support generator expressions.


Modules
---

* The "CheckFortranCompilerFlag" module was introduced to check
  "Fortran" compiler flags, much like the "CheckCCompilerFlag" module
  already does for "C".

* The "ExternalData" module learned a new "ExternalData_NO_SYMLINKS"
  option to disable use of symbolic links to populate the

Re: Review Request 124063: Add docSize(id) to transaction

[Vishesh Handa]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124063/#review81388
---


The method of calculation of the document size isn't very accurate.

* It's quite hard to approximate the size used by the postingDB + positionDB.
  * For the PostingDB you are using 64 bytes. I'm not sure how that translates.
  * For the PositionDB it's even more complex. Also, when/if the PositionCodec 
implementation changes, the current code breaks.

* For the other databases, we actually need to take the pagesize of the db and 
the header size into consideration, since they also consume space. Also there 
is a concept of overflow pages. All of this is generally taken care of by the 
MDB_stat method. But doing it per document will be hard.

Maybe you could drop this for now and focus on other stuff?

- Vishesh Handa


On June 10, 2015, 4:44 p.m., Pinak Ahuja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/124063/
> ---
> 
> (Updated June 10, 2015, 4:44 p.m.)
> 
> 
> Review request for Baloo and Vishesh Handa.
> 
> 
> Repository: baloo
> 
> 
> Description
> ---
> 
> This method tries to approximate the space a file's data is taking in the 
> index.
> balooctl status [file..] now also shows this information.
> 
> 
> Diffs
> -
> 
>   src/engine/transaction.h d7f0715 
>   src/engine/transaction.cpp f343f53 
>   src/tools/balooctl/main.cpp 8413621 
> 
> Diff: https://git.reviewboard.kde.org/r/124063/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Pinak Ahuja
> 
>


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: HTML systray tooltips under KF5

[Sebastian Kügler]

On Monday, June 08, 2015 14:38:42 Jason L Tibbitts III wrote:
> > "SK" == Sebastian Kügler  writes:
> SK> You can port it to QML, make it a plasmoid and use a custom QML item
> SK> to display the tooltip.
> 
> I don't really think "rewrite the entire application" qualifies as a
> workaround.  Can I take it that the documented functionality of tooltips
> has changed to no longer allow the HTML subset it previously allowed?
> If so I'll just have to drop the rich tooltips.  Not a huge deal, but
> unfortunate.

It's not a workaround, it's the proper way of doing it. KStatusNotifier is a 
very high-level API, which doesn't support HTML tooltips on Plasma. For more 
complex usecases, such as the custom tooltip layout you're trying, QML is the 
tool of choice in Plasma, not HTML.

The workaround here is that you're using HTML, not the other way around. :)

Cheers,
-- 
sebas

Sebastian Kügler|http://vizZzion.org| http://kde.org


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Review Request 124075: Export file being indexed by FileContentIndexer

[Pinak Ahuja]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124075/
---

Review request for Baloo and Vishesh Handa.


Repository: baloo


Description
---

The batchStart signal gives us the urls of files we are about to index. We will 
assume the indexing the of the first file has started as soon as this signal is 
caught and the fileDone() signal tells us that the file is done.


Diffs
-

  src/file/CMakeLists.txt 16bc6dd 
  src/file/extractorprocess.h 3106a71 
  src/file/extractorprocess.cpp 38c2493 
  src/file/filecontentindexer.cpp df218a7 
  src/file/filecontentindexerprovider.h e5f8d2a 
  src/file/org.kde.baloo.file.contentindexer.xml PRE-CREATION 

Diff: https://git.reviewboard.kde.org/r/124075/diff/


Testing
---

Not tested yet as the filecontentindexer is not hooked up to the main code.


Thanks,

Pinak Ahuja


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Review Request 124076: autotests: Use QTEST_GUILESS_MAIN

[Heiko Becker]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124076/
---

Review request for Baloo.


Repository: baloo


Description
---

... to allow running the tests without a display server.


Diffs
-

  autotests/unit/file/basicindexingjobtest.cpp ab003b6 
  autotests/unit/file/fileindexerconfigtest.cpp ae88ea1 
  autotests/unit/file/filtereddiriteratortest.cpp 4447990 
  autotests/unit/file/kinotifytest.cpp 2261824 
  autotests/unit/file/metadatamovertest.cpp 18697b6 
  autotests/unit/file/pendingfilequeuetest.cpp 8f23fc3 
  autotests/unit/file/regularexpcachebenchmark.cpp 211faa5 
  autotests/unit/file/unindexedfileiteratortest.cpp f3b3f3f 
  autotests/unit/lib/filemonitortest.cpp 57ed264 

Diff: https://git.reviewboard.kde.org/r/124076/diff/


Testing
---

All changed tests still ran successfully.


Thanks,

Heiko Becker


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Review Request 124076: autotests: Use QTEST_GUILESS_MAIN

[Vishesh Handa]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124076/#review81398
---

Ship it!


Good stuff!

- Vishesh Handa


On June 11, 2015, 9:31 p.m., Heiko Becker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/124076/
> ---
> 
> (Updated June 11, 2015, 9:31 p.m.)
> 
> 
> Review request for Baloo.
> 
> 
> Repository: baloo
> 
> 
> Description
> ---
> 
> ... to allow running the tests without a display server.
> 
> 
> Diffs
> -
> 
>   autotests/unit/file/basicindexingjobtest.cpp ab003b6 
>   autotests/unit/file/fileindexerconfigtest.cpp ae88ea1 
>   autotests/unit/file/filtereddiriteratortest.cpp 4447990 
>   autotests/unit/file/kinotifytest.cpp 2261824 
>   autotests/unit/file/metadatamovertest.cpp 18697b6 
>   autotests/unit/file/pendingfilequeuetest.cpp 8f23fc3 
>   autotests/unit/file/regularexpcachebenchmark.cpp 211faa5 
>   autotests/unit/file/unindexedfileiteratortest.cpp f3b3f3f 
>   autotests/unit/lib/filemonitortest.cpp 57ed264 
> 
> Diff: https://git.reviewboard.kde.org/r/124076/diff/
> 
> 
> Testing
> ---
> 
> All changed tests still ran successfully.
> 
> 
> Thanks,
> 
> Heiko Becker
> 
>


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Review Request 124075: Export file being indexed by FileContentIndexer

[Vishesh Handa]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124075/#review81399
---



src/file/extractorprocess.h (line 46)






src/file/extractorprocess.cpp (line 71)


The ids are already being converts to urls in the extractor. We should do 
all of this over there.


- Vishesh Handa


On June 11, 2015, 8:25 p.m., Pinak Ahuja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/124075/
> ---
> 
> (Updated June 11, 2015, 8:25 p.m.)
> 
> 
> Review request for Baloo and Vishesh Handa.
> 
> 
> Repository: baloo
> 
> 
> Description
> ---
> 
> The batchStart signal gives us the urls of files we are about to index. We 
> will assume the indexing the of the first file has started as soon as this 
> signal is caught and the fileDone() signal tells us that the file is done.
> 
> 
> Diffs
> -
> 
>   src/file/CMakeLists.txt 16bc6dd 
>   src/file/extractorprocess.h 3106a71 
>   src/file/extractorprocess.cpp 38c2493 
>   src/file/filecontentindexer.cpp df218a7 
>   src/file/filecontentindexerprovider.h e5f8d2a 
>   src/file/org.kde.baloo.file.contentindexer.xml PRE-CREATION 
> 
> Diff: https://git.reviewboard.kde.org/r/124075/diff/
> 
> 
> Testing
> ---
> 
> Not tested yet as the filecontentindexer is not hooked up to the main code.
> 
> 
> Thanks,
> 
> Pinak Ahuja
> 
>


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Review Request 124076: autotests: Use QTEST_GUILESS_MAIN

[Heiko Becker]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124076/
---

(Updated June 11, 2015, 11:22 p.m.)


Status
--

This change has been marked as submitted.


Review request for Baloo.


Changes
---

Submitted with commit e2be53ea79be4598760be0596ad474abd03d0b73 by Heiko Becker 
to branch master.


Repository: baloo


Description
---

... to allow running the tests without a display server.


Diffs
-

  autotests/unit/file/basicindexingjobtest.cpp ab003b6 
  autotests/unit/file/fileindexerconfigtest.cpp ae88ea1 
  autotests/unit/file/filtereddiriteratortest.cpp 4447990 
  autotests/unit/file/kinotifytest.cpp 2261824 
  autotests/unit/file/metadatamovertest.cpp 18697b6 
  autotests/unit/file/pendingfilequeuetest.cpp 8f23fc3 
  autotests/unit/file/regularexpcachebenchmark.cpp 211faa5 
  autotests/unit/file/unindexedfileiteratortest.cpp f3b3f3f 
  autotests/unit/lib/filemonitortest.cpp 57ed264 

Diff: https://git.reviewboard.kde.org/r/124076/diff/


Testing
---

All changed tests still ran successfully.


Thanks,

Heiko Becker


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: HTML systray tooltips under KF5

[Sebastian Kügler]

[adding kde-devel back in]

On Thursday, June 11, 2015 13:31:13 Jason L Tibbitts III wrote:
> > "SK" == Sebastian Kügler  writes:
> SK> It's not a workaround, it's the proper way of doing it.
> 
> In a way that works on other desktops as well?  I may have written it
> using the KDE libraries but it still needs to work elsewhere.
> 
> SK> KStatusNotifier is a very high-level API, which doesn't support
> SK> HTML tooltips on Plasma.
> 
> Wouldn't it have been simpler to just have said at the outset that HTML
> is no longer supported in tooltips?
> 
> SK> The workaround here is that you're using HTML, not the other way
> SK> around.
> 
> Well, OK.  I mean, it wasn't available when I wrote this stuff.  I just
> want to format a tooltip to look nice, not rewrite the application in
> javascript.  It used to work fine.  It's fine to deprecate things but
> it's at least polite to document the fact.

Understandable. I've started a discussion to reconsider this change on the 
Plasma devel list.

Cheers,
-- 
sebas

Sebastian Kügler|http://vizZzion.org| http://kde.org


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<