Hi,
On 9/10/21 21:17, Ben Cooksley wrote:
On Sat, Sep 11, 2021 at 5:40 AM Carl Schwan wrote:
We also are losing the krita/kmymoney/other app private api generation,
but that maybe can be generated in another ci pipeline later. Not sure how
much thses apps' developers are using it.
This ca
Hi,
On 9/10/21 19:39, Carl Schwan wrote:
I see on an issue that I would qualify as blocking and it's the lack of the
ECM generated doc: https://api-dev.kde.org/ecm. We are also losing the
kube/sink doc (located at api.kde.org/doc/sink) but it's also available
in readthedocs and ihmo it should b
Hi,
On 9/11/21 00:30, Ben Cooksley wrote:
I've now completed transferring a copy of all of the Older API
Documentation to https://api-dev.kde.org/legacy/
This is aliased in from elsewhere on the server, so it's contents won't be
disturbed by the automatic generation process we have for new KApi
Hi,
we have been working on getting KApiDox to run on Jenkins. This work has
been taken way longer than I expected but has now reached a state close
to finished. :)
So I would like to invite you to check https://api-dev.kde.org/ for any
show stoppers.
Known issues (not show stoppers):
- F
On 7/19/21 5:52 PM, David Faure wrote:
On dimanche 18 juillet 2021 02:34:24 CEST Frederik Schwarzer wrote:
So the question is: did you notice things that have been removed from
the C++ standard since C++11 that were used in our applications?
I found a list of things that were removed from
Hi,
Thanks for the links. I know about those papers but I do not think we
should point KF6 application porters there because the vast majority of
the stuff mentioned is very unlikely to affect them.
For now I will go with some general remarks here.
Cheers,
Frederik
On 7/18/21 10:22 AM, Davi
Hi,
since we are increasing the C++ standard requirement from 11 to 17 with
KF6 and there were a few deprecations/removals in between, I wonder if
any of those are noteworthy for people developing applications based on
KDE Frameworks.
What I mean by "noteworthy" is features that are commonly
On 7/12/21 8:43 PM, Friedrich W. H. Kossebau wrote:
Am Montag, 12. Juli 2021, 20:22:30 CEST schrieb Frederik Schwarzer:
On 7/12/21 7:38 PM, Friedrich W. H. Kossebau wrote:
Now what is meant by "clickable links to replacements" exactly? Any
example
for what you have in mind?
(Ju
On 7/12/21 7:38 PM, Friedrich W. H. Kossebau wrote:
Some hopefully helpful quick comments from couch:
Am Montag, 12. Juli 2021, 19:14:17 CEST schrieb Frederik Schwarzer:
- If not documented separately, should existing deprecation messages
be improved? "no known users" mi
who get that message
- Is it possible/desirable to keep the latest KF5 API docs as it is
generated on api.k.o to have deprecation messages with clickable links
to replacements?
Opinions/additions?
Cheers,
Frederik
On 7/11/21 2:24 PM, Frederik Schwarzer wrote:
Hi,
On 7/10/21 11:54 PM, Fried
Hi,
On 7/10/21 11:54 PM, Friedrich W. H. Kossebau wrote:
Am Samstag, 10. Juli 2021, 22:47:58 CEST schrieb Frederik Schwarzer:
Hi,
On 7/10/21 7:38 PM, Friedrich W. H. Kossebau wrote:
Am Samstag, 10. Juli 2021, 18:00:13 CEST schrieb Frederik Schwarzer:
as mentioned earlier
Any pointers
Hi,
On 7/10/21 7:38 PM, Friedrich W. H. Kossebau wrote:
Am Samstag, 10. Juli 2021, 18:00:13 CEST schrieb Frederik Schwarzer:
as mentioned earlier
Any pointers? :)
It was discussed in the weekly BBB meetings a few weeks ago.
I would like to document classes/methods/etc that
are going to
On 7/10/21 6:17 PM, Ahmad Samir wrote:
On 10/07/2021 18:00, Frederik Schwarzer wrote:
Hi,
as mentioned earlier, I would like to document classes/methods/etc that
are going to be deprecated during KF6 development.
For that I scraped up all the deprecation macros from the frameworks and
Hi,
as mentioned earlier, I would like to document classes/methods/etc that
are going to be deprecated during KF6 development.
For that I scraped up all the deprecation macros from the frameworks and
edited them to be more unified.
Now I need some opinions.
For once, there is still some st
14 matches
Mail list logo
