On 2023-03-07 13:12, Friedrich W. H. Kossebau wrote:
Am Dienstag, 7. März 2023, 02:51:06 CET schrieb Aleix Pol:
Having ninja/make do this dependency generation can end up being more
work than worth it because then we need to have a static list
Such static list could be generated by scripty whe
On 2022-07-13 06:03, Luca Beltrame wrote:
In data martedì 12 luglio 2022 16:52:21 CEST, Nate Graham ha scritto:
Hello Nate,
+Fabian Vogt and Luca Beltrame specifically
Thanks, that's a relief! Does this looks legit enough for openSUSE to
stop patching out the KUSerFeedback integration?
In p
On 2022-05-16 19:38, Alexander Neundorf wrote:
On Dienstag, 3. Mai 2022 18:43:48 CEST Méven wrote:
Le mar. 3 mai 2022 à 18:25, Thomas Friedrichsmeier <
thomas.friedrichsme...@kdemail.net> a écrit :
> On Tue, 3 May 2022 10:35:20 +0200
>
> Méven wrote:
> > I am guessing you are using cmake >= 3.
On 2022-05-10 15:33, Nate Graham wrote:
On 5/10/22 04:15, Ingo Klöcker wrote:
https://manifesto.kde.org/commitments/
I don't see anything in there that would force the same merge workflow
on all
KDE projects. In my view the merge workflow is comparable to the
coding style.
Regards,
Ingo
Hi,
we will change KWrite to re-use the Kate codebase.
As side-effect, KWrite will like Kate now support opt-in telemetry via
KUserFeedback (can be even deactivated fully during compile time, purely
optional dependency).
The code is the same as used in Kate, the relevant merge request for th
On 2021-09-06 11:48, Ben Cooksley wrote:
On Mon, Sep 6, 2021 at 9:00 PM Tom Zander wrote:
On zondag 5 september 2021 08:13:09 CEST Ben Cooksley wrote:
In terms of the format of the 'Dependencies' section,
Playing with kde-build script and noticing the fast growing
dependency trees we have t
On 2021-03-02 22:11, Albert Astals Cid wrote:
El dimarts, 2 de març de 2021, a les 19:39:57 CET, Christoph Cullmann
va escriure:
Hi,
for the KDE Gear release service releases, what is actually an
acceptable Frameworks release requirement for the upcoming 21.04?
e.g. at the moment, Kate
Hi,
for the KDE Gear release service releases, what is actually an
acceptable Frameworks release requirement for the upcoming 21.04?
e.g. at the moment, Kate requires Frameworks 5.79 in master, we needed
some new API to avoid ugly hacks.
Would it be acceptable to move this to the latest ver
On 2021-01-30 12:14, Volker Krause wrote:
On Freitag, 29. Januar 2021 15:57:59 CET Adam Szopa wrote:
Hello,
I've been talking with David Faure about setting up a Sprint focused
on KF6
work. Some of the topics would include:
- Reviewing the KF6 board
(https://phabricator.kde.org/project/board/3
On 2021-01-13 23:05, Milian Wolff wrote:
On Mittwoch, 13. Januar 2021 21:57:13 CET Christoph Feck wrote:
Hello developers,
my personal situation allows for much less time for KDE
related work, at least during the Corona times.
I would like to retire as soon as possible from these
responsibilit
On 2020-12-04 20:12, Jason Christie wrote:
Hello, all!
I *really* feel I'm intruding here, so I will try and be brief and
succinct.
When you have text buffered/in the clipboard, and need to replace
other text while at the same time keeping it as well, there's no easy
and fast way to do this.
S
On 2020-10-29 21:46, Elvis Angelaccio wrote:
Hi everyone,
I was planning to add KUserFeedback in Dolphin for the upcoming 20.12
release, but then I realized that our telemetry policy [1] says we
should go through a public review on kde-core-devel first.
So here I am, this is the MR:
https://inv
On 2020-09-15 01:06, Albert Astals Cid wrote:
El dimecres, 12 d’agost de 2020, a les 22:42:37 CEST, Albert Astals
Cid va escriure:
Would it make sense to do an Akademy BoF about this to try to get more
than 3 people to decide on it?
So we didn't have an Akademy BoF.
I need clear messaging on
On 2020-02-02 12:27, Christoph Cullmann wrote:
Hi,
I created some initial merge request for basic user feedback
integration into Kate:
https://invent.kde.org/kde/kate/merge_requests/60
To do this properly like described in
https://community.kde.org/Policies/Telemetry_Policy
I would like to
Hi,
I created some initial merge request for basic user feedback integration
into Kate:
https://invent.kde.org/kde/kate/merge_requests/60
To do this properly like described in
https://community.kde.org/Policies/Telemetry_Policy
I would like to have people review this change and raise issues
Hi,
I created some initial merge request for basic user feedback integration
into Kate:
https://invent.kde.org/kde/kate/merge_requests/60
To do this properly like described in
https://community.kde.org/Policies/Telemetry_Policy
I would like to have people review this change and raise issues
Hi,
I created some initial merge request for basic user feedback integration
into Kate:
https://invent.kde.org/kde/kate/merge_requests/60
To do this properly like described in
https://community.kde.org/Policies/Telemetry_Policy
I would like to have people review this change and raise issues
Hi,
With my KTextEditor hat on: KF6:TextDocument implies somehow a link
to QTextDocument or KF6:TextEditor, which both is incorrect, right?
QTextDocument is exactly what it's about, which makes the name
KF6::TextDocument fully appropriate and correct.
Before starting this work, let's clarify
, testing there would be appreciated.
I can only tell, that without the below change, already on one screen
it looks horrible :=)
Greetings
Christoph
On Sat, Sep 28, 2019, 11:05 AM Christoph Cullmann
wrote:
Hi,
I just checked again the HIDPI support of Kate/KWrite on Windows and
it
"s
On 2019-09-28 17:37, Christoph Cullmann wrote:
On 2019-09-28 17:34, Albert Vaca Cintora wrote:
If this has to be done for all apps, why isn't it done at Qt level?
Because in some cases, that breaks the application, e.g. if it expects
pixel to be real physical pixel 1:1.
Therefore,
on if it
behaves OK.
(I did that for KWrite/Kate)
Greetings
Christoph
On Sat, Sep 28, 2019 at 5:05 PM Christoph Cullmann
wrote:
Hi,
I just checked again the HIDPI support of Kate/KWrite on Windows and
it
"sucked".
It seems we never properly did setup the stuff to auto-
Hi,
I just checked again the HIDPI support of Kate/KWrite on Windows and it
"sucked".
It seems we never properly did setup the stuff to auto-scale, e.g. the
QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true);
call was missing, we only had the
QCoreApplication::setAttribute(
Hi,
perhaps this would be some good BoF at Akademy:
What is needed to move frameworks development to invent.kde.org.
(I assume we want to do that some when in the future anyways)
At this point my planning expected that Frameworks would move when the
rest of KDE moves (which will likely be a
Hi,
> Unfortunately the problem isn't with Frameworks, Applications and
> Plasma - they're easy to handle and their naming can be scripted
> without too much trouble.
> The problem lies with Extragear, which has a large number of projects,
> all of which have different rules for what a stable br
On 2019-08-11 16:53, Albert Astals Cid wrote:
El diumenge, 11 d’agost de 2019, a les 12:33:19 CEST, Christoph
Cullmann va escriure:
Hi,
is it possible to move individual framework modules over to
invent.kde.org or will that be
done at once somewhen in the future?
Seems kde-frameworks-devel
Hi,
is it possible to move individual framework modules over to
invent.kde.org or will that be
done at once somewhen in the future?
Would be interested to move syntax-highlighting and ktexteditor if that
is possible.
But if that shall be done as bulk in the future I can wait ;=)
Greetings
C
or features you not use
yourself at all),
any meaningful review is a full-time job. e.g. in our company you would let
some student
test the changed behavior some days. This is just not feasible for me, and yes,
for some of these changes, rather than abandoning them (and trashing precious
work
Hi,
> On Sun, Mar 25, 2018 at 11:08 PM, David Rosca wrote:
>> On Sat, Mar 24, 2018 at 7:58 PM, Dr.-Ing. Christoph Cullmann
>> wrote:
>>> Hi,
>>>
>>> no objections from my side,
>>>
>>> just a note that we need to take care of th
;>
>
> All issues that were pointed out are now fixed.
>
> It's been in kdereview for over two weeks now, so if there are no
> objections I will request move to extragear by the end of this week.
>
> David
--
- Dr.-Ing. Christoph Cullma
no porting guidelines exist, have not tried it again. (attached the
state of the port,
if somebody wants to give it a try) But as the above mail indicates, such a
guide should come up.
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Inf
>
> Sometimes, that even works, sometimes, not.
>
> Is there anything special to do? Does KIconThemes play around with that, too?
>
> Greetings
> Christoph
>
> --
> - Dr.-Ing. Christoph Cullmann -
> AbsInt Angewandte Informa
with breeze dir inside the "icons" path with the index.theme inside.
Sometimes, that even works, sometimes, not.
Is there anything special to do? Does KIconThemes play around with that, too?
Greetings
Christoph
--
----- Dr.-Ing. Christoph Cullmann ---
ould be much simpler with a single diff.
>
> Gerrit gives you a git command to copy'n'paste and you can pull the changeset
> and test it. That's much better than manually applying some plaintext diff.
>
> Bye
> --
> Milian Wolff | milian.wo...@kdab.com | Softw
ust reopen it again.
I think this would make a lot of time consuming bug triaging much easier.
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel:
gt; Cheers,
> > Andreas
>
>
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax:
> - -
> >
> > If it is OK this way, I can add it later today to the wiki page.
I somehow missed that mail ;=)
I am all for adding that paragraph and then moving the wiki page to the right
place.
Greetings
Christoph
--
---
- Ursprüngliche Mail -
> El Dissabte, 11 de juliol de 2015, a les 16:59:13, Christoph Cullmann va
> escriure:
> > - Ursprüngliche Mail -
> >
> > > El Dissabte, 11 de juliol de 2015, a les 15:52:44, Christoph Cullmann va
> > >
> > &
- Ursprüngliche Mail -
> El Dissabte, 11 de juliol de 2015, a les 15:52:44, Christoph Cullmann va
> escriure:
> > Hi, something like that?
> >
> > https://userbase.kde.org/KDE_Applications_Versioning
>
> I'd like to make it clearer that this is option
gt; > Yes, that's why Albert was asking for a blog/wiki documentation.
> >
>
> ...on a release-team mailing list to which I guess most of us are not
> subscribed ;)
>
> Cheers
> --
> Martin Klapetek | KDE Developer
>
--
---
E_APPLICATIONS_ variables around for people wanting to use them.
And I think it makes sense to use them for a lot apps, given not many apps have
any
real version number updates it seems ;=) (it makes bug reports much nicer, if
you can actually
track the bug to some released version)
nsuse packages seems to
have patched release numbers, at least for Konsole).
Greetings
Christoph
--
----- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681-38360-
> On Saturday, 2014-08-09, 18:04:18, Christoph Cullmann wrote:
> >
> > for the JS scripting in KatePart I would be interested in a BoF, for the
> > Python stuff I have actually no clue how it works :P
>
> Neither do I but we can certainly discuss multi language support
t
to the the
Qml/JSEngine stuff, but that was to buggy in 5.2, perhaps in 5.3 and later it
is usable.
Act
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1
alled, Kate still works, thought the
poor console window stays empty)
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken
itable is anyway problematic,
guess users will have to live with "less safe" saving in such settings.
Will KSaveFile get some of that patches, too?
Greetings
Christoph
--
- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email: c
; modules in
> question? (And if so, I'd appreciate ideas for better ways to fix).
Hi,
I would have no problem with moving kate.git around, splitting is IMHO
a pain for later developing on it, as all parts are tightly coupled anyway.
Greetings
Christoph
--
----
ean, I have nothing against allowing people to login with their Google
account or whatever
if that is possible, but I would not like to see bug reports by
.
Greetings
Christoph
--
-- Christoph Cullmann -
AbsInt Angewandte Informatik GmbH Email
t; we have something like on the Wikis, e.g. OpenID, or something
> comment
> sections of websites used, e.g. "login via Facebook"?
>
> --
> Kevin Krammer, KDE developer, xdg-utils developer
> KDE user support, developer mentoring
>
--
---
- [supported by GCC since] 4.3
>
> I too would be interested in variadic templates, would this be
> acceptable in
> a tier 2 KF component (i18n)?
Then there is no longer Windows support.
MSVC (even the upcoming one) doesn't support that.
Greetings
Christoph
--
-
ne please explain to me
> > why
> > distros ship with docbook help pages that were written years ago
> > and
> > not updated since?
>
> Maybe they don't need to be updated?
> http://techbase.kde.org/Projects/Documentation/KDE4_%28health_table%29
> looks quite green to me
Yeah, and, just as
that are available for the application.
There can be cool stuff, useful FAQ, howtos, video guides, whatever, but I
think that
should be in the normal case an extension of the local manual.
Greetings
Christoph
--
-- Christoph Cullman
is anyway "deprecated"
in favour
of the V8 based new variant?
But does the new engine provide the same nice features to easily wrap your
objects and expose a custom API?
That was the major reason we switched over from KJS to QtScript.
Greetings
Christoph
--
-
- Original Message -
> On Tuesday, 24 de January de 2012 19.26.01, Christoph Cullmann wrote:
> > Hi,
> >
> > just out of curiosity: Why is Intel blocking this to get into Qt?
>
> The Qt Contribution License Agreement has not been approved
> internally yet.
cases, there is no reason for KUrl::protocol to
> exist.
>
> Less difference between Qt and KDE API for no lasting reason is a
> good
> thing.
Hi,
just out of curiosity: Why is Intel blocking this to get into Qt?
Greetings
Christoph
--
-- Christo
CMake to build only the kate parts, if you want only to have katepart and
co. fresh and not all libs, ...)
I can understand that new dependencies are work, but I don't see the problem
in comparison to other dependencies which change the whole time.
To get new contributors for Kate, it is
55 matches
Mail list logo
