BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks%20ktexteditor%20kf5-qt5%20FreeBSDQt5.7/69/
Project:
Frameworks ktexteditor kf5-qt5 FreeBSDQt5.7
Date of build:
Fri, 08 Sep 2017 02:32:24 +
Build duration:
9 min 50 sec and counting
JUnit
Thanks for keeping on top of this, Julian. Here are my findings:
On Thursday 07 September 2017, Julian Wolff wrote:
> The "dirty" signal of the corresponding directory is not emitted when files
> are moved
That's not what I see when testing with kdirwatchtest_gui. I get dirty signals
for all
maxrd2 added a comment.
In https://phabricator.kde.org/D7648#142638, @davidedmundson wrote:
> Thanks, but do you know why the apps datasource doesn't have that entry
after a while?
I've managed to get some more insight into original problem.
It seems that after some system
apol accepted this revision.
apol added a comment.
This revision is now accepted and ready to land.
LGTM
REPOSITORY
R263 KXmlGui
BRANCH
master
REVISION DETAIL
https://phabricator.kde.org/D7729
To: elvisangelaccio, #frameworks, dfaure, apol
Cc: apol
elvisangelaccio created this revision.
Restricted Application added a project: Frameworks.
REPOSITORY
R263 KXmlGui
BRANCH
master
REVISION DETAIL
https://phabricator.kde.org/D7729
AFFECTED FILES
src/kgesture_p.h
src/kkeysequencewidget.h
src/kmainwindowiface_p.h
cullmann added a comment.
> Btw, if qrcs overlay, then you can already now overlay
org.kde.syntaxhighlighting/syntax and /theme :-)
That true, but for /syntax that doesn't help as the generated index will not
allow to find the additional files ;=)
REPOSITORY
R216 Syntax Highlighting
dhaumann added a comment.
In any case, even if we use this patch, adding files are resource is the
preferred way.
Btw, if qrcs overlay, then you can already now overlay
org.kde.syntaxhighlighting/syntax and /theme :-)
REPOSITORY
R216 Syntax Highlighting
REVISION DETAIL
cullmann added a comment.
> QRC support is definitely preferred, but that should work with the original
proposal indeed. Having just one fixed QRC extension path baked in would be
problematic for PIM with its hundreds of libs/components for example, AFAIK
QRCs don't overlay on the same
We are pleased to announce that CMake 3.9.2 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.9.2 since 3.9.1:
Brad
On Thu Aug 31 21:00:06 UTC 2017 Albert Astals Cid wrote:
>
>Okular is watching the file
> "/home/kdeunstable/breeze-icons/README.md"
>and its parent folder
> "/home/kdeunstable/breeze-icons"
>that is being edited by kate, when you save in kate, this is what Okular sees
>coming from
Hm this looks indeed like we need to fix ecm.
Here is what we did for Windows
> https://github.com/KDE/extra-cmake-modules/blob/master/kde-modules/KDEInstallDirs.cmake#L520
I'll include the mac mailing list and the frameworks maling list.
Hannah
On 07/09/2017 08:11, Kåre Särs wrote:
> Hi,
vkrause added a comment.
QRC support is definitely preferred, but that should work with the original
proposal indeed. Having just one fixed QRC extension path baked in would be
problematic for PIM with its hundreds of libs/components for example, AFAIK
QRCs don't overlay on the same path,
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks%20ktexteditor%20kf5-qt5%20FreeBSDQt5.7/68/
Project:
Frameworks ktexteditor kf5-qt5 FreeBSDQt5.7
Date of build:
Thu, 07 Sep 2017 14:52:03 +
Build duration:
25 min and counting
JUnit Tests
On Thursday September 07 2017 14:37:56 Hannah von Reth wrote:
What ECM really ought to have is a link to QStandardPaths which is the source
of all the evil mentioned below. In the simplest approach it could be set up
when being configured, querying the qtpaths utility for the writable standard
This revision was automatically updated to reflect the committed changes.
Closed by commit R858:8907e5c51d08: Add missing imports for attached properties
(authored by apol).
REPOSITORY
R858 Qt Quick Controls 2: Desktop Style
CHANGES SINCE LAST UPDATE
[ Copying in kde-frameworks-devel as suggested ]
On 5 September 2017 at 22:12, Shaheed Haque wrote:
> A lot of progress has been made in the last 18 months or so:
>
> THE TOOLING
> ===
>
> We have:
>
> - A pretty powerful KDE-independent automatic binding generation
[ Copying in kde-frameworks-devel as suggested ]
On 5 September 2017 at 22:12, Shaheed Haque wrote:
> A lot of progress has been made in the last 18 months or so:
>
> THE TOOLING
> ===
>
> We have:
>
> - A pretty powerful KDE-independent automatic binding generation
dhaumann added a comment.
Btw, just in case we go for the files-in-a-resource way, maybe we should
install the katehighlightindexer for this so everyone can use this. This way,
we also could ensure our strict policies we now have (correct RegExps, trimmed
keyword lists, possibly other
18 matches
Mail list logo