Am Dienstag, 13. Juli 2021, 18:46:35 CEST schrieb Frederik Schwarzer:
> On 7/12/21 8:43 PM, Friedrich W. H. Kossebau wrote:
> > IIRC main file of the generation is
> > https://invent.kde.org/websites/quality-kde-org/-/blob/master/apidox/src/
> > gendox.sh
> >
> > But I dropped out when there were
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?
(Just in case, Doxyg
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?
> > (Just in case, Doxygen usually itself already generated au
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" might not be enough
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" might not be enough for the "unknown
>users" in 3rd-party applications
Hi,
so there has been a bit more discussion in today's KF6 weekly meeting
about how to proceed with porting docs.
- Porting documentation needs an entry page pointing to the several
resources like C++ deprecations, Qt6 porting guides, KF6 porting
notes
- KF6 porting notes should follow a s
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? :)
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? :)
>
> It was discussed in the weekly BBB me
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 b
Am Samstag, 10. Juli 2021, 18:00:13 CEST schrieb Frederik Schwarzer:
> as mentioned earlier
Any pointers? :)
> I would like to document classes/methods/etc that
> are going to be deprecated during KF6 development.
Can you help confused-on-first-read people by explaining what "deprecated
during
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
edite
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
edited them to be more unified.
Good work, th
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
13 matches
Mail list logo