Discussion:
Question about "kate/ktexteditor" highlighting implementation in QtCreator
(too old to reply)
Dr.-Ing. Christoph Cullmann
2018-08-12 22:21:13 UTC
Permalink
Hi,

at the moment, the KTextEditor team ports away from its old syntax highlighting
engine (which was reimplemented some years ago in QtCreator) to the new
KSyntaxHighlighting framework (a Qt only KF5 framework).

https://api.kde.org/frameworks/syntax-highlighting/html/index.html
https://cgit.kde.org/syntax-highlighting.git/about/

After this is done, we will do some incompatible changes to the xml files (that
are reused by QtCreator at the moment).

I know that in the past there was no chance to reuse the KTextEditor/Kate implementation
due to licensing/dependencies issues.

Would it be possible to reuse the framework above to stay compatible and share code/maintenance
effort?

At the moment the framework is LGPLv2+, but even relicensing to something
more liberal is at the moment still possible, if that would allow better collaboration.

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Eike Ziller
2018-08-14 09:01:08 UTC
Permalink
Post by Dr.-Ing. Christoph Cullmann
Hi,
at the moment, the KTextEditor team ports away from its old syntax highlighting
engine (which was reimplemented some years ago in QtCreator) to the new
KSyntaxHighlighting framework (a Qt only KF5 framework).
https://api.kde.org/frameworks/syntax-highlighting/html/index.html
https://cgit.kde.org/syntax-highlighting.git/about/
After this is done, we will do some incompatible changes to the xml files (that
are reused by QtCreator at the moment).
I know that in the past there was no chance to reuse the KTextEditor/Kate implementation
due to licensing/dependencies issues.
Would it be possible to reuse the framework above to stay compatible and share code/maintenance
effort?
That would be desirable goal :)
Post by Dr.-Ing. Christoph Cullmann
At the moment the framework is LGPLv2+, but even relicensing to something
more liberal is at the moment still possible, if that would allow better collaboration.
Thanks for contacting us on that question! I’ve added Lars as our Chief Maintainer to CC.

Our 3rd-party license policy is documented here:
https://quips-qt-io.herokuapp.com/quip-0004.html#acceptable-licenses

It boils down to:
* MIT or BSD or anything that is basically the same is no problem to include for us
* L(GPL) might be ok in some cases, but usually not for “core” parts

(That last part about “core” parts is written in the policy with the Qt hat on as “part of Qt Essentials", but for Qt Creator I’d interpret that in a similar manner.)

I’d say that the generic text highlighting is a “core” part in Qt Creator, so it would be good if a 3rd-party library for that would be MIT/BSD-style, otherwise we probably cannot use it.

Best regards, Eike
Post by Dr.-Ing. Christoph Cullmann
Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
--
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
***@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
Dr.-Ing. Christoph Cullmann
2018-08-14 09:07:29 UTC
Permalink
Hi,
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
Hi,
at the moment, the KTextEditor team ports away from its old syntax highlighting
engine (which was reimplemented some years ago in QtCreator) to the new
KSyntaxHighlighting framework (a Qt only KF5 framework).
https://api.kde.org/frameworks/syntax-highlighting/html/index.html
https://cgit.kde.org/syntax-highlighting.git/about/
After this is done, we will do some incompatible changes to the xml files (that
are reused by QtCreator at the moment).
I know that in the past there was no chance to reuse the KTextEditor/Kate implementation
due to licensing/dependencies issues.
Would it be possible to reuse the framework above to stay compatible and share
code/maintenance
effort?
That would be desirable goal :)
I hoped some, too.
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
At the moment the framework is LGPLv2+, but even relicensing to something
more liberal is at the moment still possible, if that would allow better collaboration.
Thanks for contacting us on that question! I’ve added Lars as our Chief Maintainer to CC.
I added the maintainer of syntax-highlighting Volker Krause in CC.
Actually both are at akademy at the moment and perhaps can just talk
about the thing in person if wanted.
Post by Eike Ziller
https://quips-qt-io.herokuapp.com/quip-0004.html#acceptable-licenses
* MIT or BSD or anything that is basically the same is no problem to include for us
* L(GPL) might be ok in some cases, but usually not for “core” parts
(That last part about “core” parts is written in the policy with the Qt hat on
as “part of Qt Essentials", but for Qt Creator I’d interpret that in a similar
manner.)
I’d say that the generic text highlighting is a “core” part in Qt Creator, so it
would be good if a 3rd-party library for that would be MIT/BSD-style, otherwise
we probably cannot use it.
I think if the license would be the last issue, we can try to find some common ground
for that.

Thanks already for the quick response.
Post by Eike Ziller
Best regards, Eike
Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Lars Knoll
2018-08-14 16:12:53 UTC
Permalink
Hi,
Post by Dr.-Ing. Christoph Cullmann
Hi,
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
Hi,
at the moment, the KTextEditor team ports away from its old syntax highlighting
engine (which was reimplemented some years ago in QtCreator) to the new
KSyntaxHighlighting framework (a Qt only KF5 framework).
https://api.kde.org/frameworks/syntax-highlighting/html/index.html
https://cgit.kde.org/syntax-highlighting.git/about/
After this is done, we will do some incompatible changes to the xml files (that
are reused by QtCreator at the moment).
I know that in the past there was no chance to reuse the KTextEditor/Kate
implementation
due to licensing/dependencies issues.
Would it be possible to reuse the framework above to stay compatible and share
code/maintenance
effort?
That would be desirable goal :)
I hoped some, too.
Sharing that code would IMO be great. I don't see why we should maintain our own code for parsing those syntax highlighter definitions :)
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
At the moment the framework is LGPLv2+, but even relicensing to something
more liberal is at the moment still possible, if that would allow better collaboration.
Thanks for contacting us on that question! I’ve added Lars as our Chief
Maintainer to CC.
I added the maintainer of syntax-highlighting Volker Krause in CC.
Actually both are at akademy at the moment and perhaps can just talk
about the thing in person if wanted.
We had a good talk at Academy today, and both agreed that it would be good if we could re-use the same component in all places (including Qt Creator).
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
https://quips-qt-io.herokuapp.com/quip-0004.html#acceptable-licenses
* MIT or BSD or anything that is basically the same is no problem to include for us
* L(GPL) might be ok in some cases, but usually not for “core” parts
(That last part about “core” parts is written in the policy with the Qt hat on
as “part of Qt Essentials", but for Qt Creator I’d interpret that in a similar
manner.)
MIT or BSD is easiest. For various reasons I would very much prefer not to add L(GPL) dependencies to any parts of Qt.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
I’d say that the generic text highlighting is a “core” part in Qt Creator, so it
would be good if a 3rd-party library for that would be MIT/BSD-style, otherwise
we probably cannot use it.
I think if the license would be the last issue, we can try to find some common ground
for that.
That would be great. Then the remaining issue for us would be to find the time to do the porting to the new engine.

Cheers,
Lars
Post by Dr.-Ing. Christoph Cullmann
Thanks already for the quick response.
Post by Eike Ziller
Best regards, Eike
Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Dr.-Ing. Christoph Cullmann
2018-08-14 16:56:56 UTC
Permalink
Hi,
Post by Lars Knoll
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
Would it be possible to reuse the framework above to stay compatible and share
code/maintenance
effort?
That would be desirable goal :)
I hoped some, too.
Sharing that code would IMO be great. I don't see why we should maintain our own
code for parsing those syntax highlighter definitions :)
Nice that we share that point of view, as during the discussion today here at Akademy.
Post by Lars Knoll
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
At the moment the framework is LGPLv2+, but even relicensing to something
more liberal is at the moment still possible, if that would allow better
collaboration.
Thanks for contacting us on that question! I’ve added Lars as our Chief
Maintainer to CC.
I added the maintainer of syntax-highlighting Volker Krause in CC.
Actually both are at akademy at the moment and perhaps can just talk
about the thing in person if wanted.
We had a good talk at Academy today, and both agreed that it would be good if we
could re-use the same component in all places (including Qt Creator).
It would be great if some QtCreator developer could take a short look at what
the framework provides and if it is usable for their purpose.

The KTextEditor port is now done, for us it did work more or less out-of-the-box
with only minor extensions to extract a bit more meta-data from the XML.
Post by Lars Knoll
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
https://quips-qt-io.herokuapp.com/quip-0004.html#acceptable-licenses
* MIT or BSD or anything that is basically the same is no problem to include for us
* L(GPL) might be ok in some cases, but usually not for “core” parts
(That last part about “core” parts is written in the policy with the Qt hat on
as “part of Qt Essentials", but for Qt Creator I’d interpret that in a similar
manner.)
MIT or BSD is easiest. For various reasons I would very much prefer not to add
L(GPL) dependencies to any parts of Qt.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
I’d say that the generic text highlighting is a “core” part in Qt Creator, so it
would be good if a 3rd-party library for that would be MIT/BSD-style, otherwise
we probably cannot use it.
I think if the license would be the last issue, we can try to find some common ground
for that.
That would be great. Then the remaining issue for us would be to find the time
to do the porting to the new engine.
If we get positive feedback from the QtCreator team that

1) it is usable for them
2) they are willing to port their stuff in the future

we can start the relicensing work to MIT to get all things ready for
use by you.

Thanks for the fruitful discussion today, lets see how that all works out.

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
David Schulz
2018-08-17 11:25:10 UTC
Permalink
It would be great if some QtCreator developer could take a short look at what the framework provides and if it is usable for their purpose.
I'll check the new engine soonish 😉

Greetings
David

-----Original Message-----
From: Qt-creator <qt-creator-bounces+david.schulz=***@qt-project.org> On Behalf Of Dr.-Ing. Christoph Cullmann
Sent: Tuesday, August 14, 2018 18:57
To: Lars Knoll <***@qt.io>
Cc: Volker Krause <***@kde.org>; qt-creator <qt-***@qt-project.org>
Subject: Re: [Qt-creator] Question about "kate/ktexteditor" highlighting implementation in QtCreator

Hi,
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
Would it be possible to reuse the framework above to stay
compatible and share code/maintenance effort?
That would be desirable goal :)
I hoped some, too.
Sharing that code would IMO be great. I don't see why we should
maintain our own code for parsing those syntax highlighter definitions
:)
Nice that we share that point of view, as during the discussion today here at Akademy.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
At the moment the framework is LGPLv2+, but even relicensing to
something more liberal is at the moment still possible, if that
would allow better collaboration.
Thanks for contacting us on that question! I’ve added Lars as our
Chief Maintainer to CC.
I added the maintainer of syntax-highlighting Volker Krause in CC.
Actually both are at akademy at the moment and perhaps can just talk
about the thing in person if wanted.
We had a good talk at Academy today, and both agreed that it would be
good if we could re-use the same component in all places (including Qt Creator).
It would be great if some QtCreator developer could take a short look at what the framework provides and if it is usable for their purpose.

The KTextEditor port is now done, for us it did work more or less out-of-the-box with only minor extensions to extract a bit more meta-data from the XML.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
https://quips-qt-io.herokuapp.com/quip-0004.html#acceptable-licenses
* MIT or BSD or anything that is basically the same is no problem to include for us
* L(GPL) might be ok in some cases, but usually not for “core” parts
(That last part about “core” parts is written in the policy with the
Qt hat on as “part of Qt Essentials", but for Qt Creator I’d
interpret that in a similar
manner.)
MIT or BSD is easiest. For various reasons I would very much prefer not to add
L(GPL) dependencies to any parts of Qt.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
I’d say that the generic text highlighting is a “core” part in Qt
Creator, so it would be good if a 3rd-party library for that would
be MIT/BSD-style, otherwise we probably cannot use it.
I think if the license would be the last issue, we can try to find
some common ground for that.
That would be great. Then the remaining issue for us would be to find
the time to do the porting to the new engine.
If we get positive feedback from the QtCreator team that

1) it is usable for them
2) they are willing to port their stuff in the future

we can start the relicensing work to MIT to get all things ready for use by you.

Thanks for the fruitful discussion today, lets see how that all works out.

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 _______________________________________________
Qt-creator mailing list
Qt-***@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
David Schulz
2018-08-20 11:38:49 UTC
Permalink
Hi,

After a first look it seems that the transition to the KSyntaxHighlighter should be pretty straight forward, just some minor adjustments to the state handling. So let's wait for any kind of licensing decision and we are good to go.

Greetings
David

-----Original Message-----
From: Qt-creator <qt-creator-bounces+david.schulz=***@qt-project.org> On Behalf Of David Schulz
Sent: Friday, August 17, 2018 13:25
To: qt-creator <qt-***@qt-project.org>
Subject: Re: [Qt-creator] Question about "kate/ktexteditor" highlighting implementation in QtCreator
It would be great if some QtCreator developer could take a short look at what the framework provides and if it is usable for their purpose.
I'll check the new engine soonish 😉

Greetings
David

-----Original Message-----
From: Qt-creator <qt-creator-bounces+david.schulz=***@qt-project.org> On Behalf Of Dr.-Ing. Christoph Cullmann
Sent: Tuesday, August 14, 2018 18:57
To: Lars Knoll <***@qt.io>
Cc: Volker Krause <***@kde.org>; qt-creator <qt-***@qt-project.org>
Subject: Re: [Qt-creator] Question about "kate/ktexteditor" highlighting implementation in QtCreator

Hi,
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
Would it be possible to reuse the framework above to stay
compatible and share code/maintenance effort?
That would be desirable goal :)
I hoped some, too.
Sharing that code would IMO be great. I don't see why we should
maintain our own code for parsing those syntax highlighter definitions
:)
Nice that we share that point of view, as during the discussion today here at Akademy.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
Post by Dr.-Ing. Christoph Cullmann
At the moment the framework is LGPLv2+, but even relicensing to
something more liberal is at the moment still possible, if that
would allow better collaboration.
Thanks for contacting us on that question! I’ve added Lars as our
Chief Maintainer to CC.
I added the maintainer of syntax-highlighting Volker Krause in CC.
Actually both are at akademy at the moment and perhaps can just talk
about the thing in person if wanted.
We had a good talk at Academy today, and both agreed that it would be
good if we could re-use the same component in all places (including Qt Creator).
It would be great if some QtCreator developer could take a short look at what the framework provides and if it is usable for their purpose.

The KTextEditor port is now done, for us it did work more or less out-of-the-box with only minor extensions to extract a bit more meta-data from the XML.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
https://quips-qt-io.herokuapp.com/quip-0004.html#acceptable-licenses
* MIT or BSD or anything that is basically the same is no problem to include for us
* L(GPL) might be ok in some cases, but usually not for “core” parts
(That last part about “core” parts is written in the policy with the
Qt hat on as “part of Qt Essentials", but for Qt Creator I’d
interpret that in a similar
manner.)
MIT or BSD is easiest. For various reasons I would very much prefer not to add
L(GPL) dependencies to any parts of Qt.
Post by Dr.-Ing. Christoph Cullmann
Post by Eike Ziller
I’d say that the generic text highlighting is a “core” part in Qt
Creator, so it would be good if a 3rd-party library for that would
be MIT/BSD-style, otherwise we probably cannot use it.
I think if the license would be the last issue, we can try to find
some common ground for that.
That would be great. Then the remaining issue for us would be to find
the time to do the porting to the new engine.
If we get positive feedback from the QtCreator team that

1) it is usable for them
2) they are willing to port their stuff in the future

we can start the relicensing work to MIT to get all things ready for use by you.

Thanks for the fruitful discussion today, lets see how that all works out.

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 _______________________________________________
Qt-creator mailing list
Qt-***@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-***@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
Dr.-Ing. Christoph Cullmann
2018-08-20 11:41:32 UTC
Permalink
Hi,
Post by David Schulz
Hi,
After a first look it seems that the transition to the KSyntaxHighlighter should
be pretty straight forward, just some minor adjustments to the state handling.
So let's wait for any kind of licensing decision and we are good to go.
Great to hear that.

I CC'd Volker, we will take care of the license and inform you after that is done.

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Dr.-Ing. Christoph Cullmann
2018-08-25 17:01:42 UTC
Permalink
Hi,
Post by David Schulz
Hi,
After a first look it seems that the transition to the KSyntaxHighlighter should
be pretty straight forward, just some minor adjustments to the state handling.
So let's wait for any kind of licensing decision and we are good to go.
the relicensing is done in master of

https://cgit.kde.org/syntax-highlighting.git/

The next released frameworks 5.50 will include this change, too.

The Code is now MIT, the syntax definition files are still licensed as before.

I introduced some defines/cmake switches to disable bundling of the files or lookup
in QStandardPaths to easy bundling of the framework as e.g. static library in QtCreator
or for others.

see

https://cgit.kde.org/syntax-highlighting.git/commit/?id=59ddf56f98d95f2562da338cea935ea9bcbcb175
https://cgit.kde.org/syntax-highlighting.git/commit/?id=ee0aa575255b98d8ba2eaf033e9e5228bcf12968

If there are any integration questions, API wishs, ..., please contact us ;=)

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Dr.-Ing. Christoph Cullmann
2018-09-22 14:25:30 UTC
Permalink
Hi,
Post by Dr.-Ing. Christoph Cullmann
Post by David Schulz
After a first look it seems that the transition to the KSyntaxHighlighter should
be pretty straight forward, just some minor adjustments to the state handling.
So let's wait for any kind of licensing decision and we are good to go.
the relicensing is done in master of
https://cgit.kde.org/syntax-highlighting.git/
The next released frameworks 5.50 will include this change, too.
The Code is now MIT, the syntax definition files are still licensed as before.
I introduced some defines/cmake switches to disable bundling of the files or lookup
in QStandardPaths to easy bundling of the framework as e.g. static library in QtCreator
or for others.
see
https://cgit.kde.org/syntax-highlighting.git/commit/?id=59ddf56f98d95f2562da338cea935ea9bcbcb175
https://cgit.kde.org/syntax-highlighting.git/commit/?id=ee0aa575255b98d8ba2eaf033e9e5228bcf12968
If there are any integration questions, API wishs, ..., please contact us ;=)
the initial 5.50 release with all library code under MIT is done.

https://download.kde.org/stable/frameworks/5.50/

KTextEditor (aka KatePart) uses the framework now, too, as is.

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Dr.-Ing. Christoph Cullmann
2018-08-17 12:36:13 UTC
Permalink
Hi,
Post by David Schulz
Post by Dr.-Ing. Christoph Cullmann
It would be great if some QtCreator developer could take a short look at what
the framework provides and if it is usable for their purpose.
I'll check the new engine soonish 😉
Great ;=)

If any questions show up, don't hesitate to ask me
or the maintainer of the framework Volker (Volker Krause <***@kde.org>).

Greetings
Christoph
--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH Email: ***@AbsInt.com
Science Park 1 Tel: +49-681-38360-22
66123 Saarbrücken Fax: +49-681-38360-20
GERMANY WWW: http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Loading...