Chusslove Illich wrote:
[: Stephen Kelly :]
If such calls are generated by uic, then that is a bug in Qt (which
should have been reported years ago), and should be fixed in Qt, right?
Maybe, I'm not sure of the conventions of Qt Linguist.
I created a .ui file with a QLabel with an empty
On Sunday 17 November 2013 18:53:36 Stephen Kelly wrote:
Kevin Ottens wrote:
On Friday 15 November 2013 16:28:10 Stephen Kelly wrote:
Aleix Pol wrote:
I see that Stephen Kelly has been doing some work on Qt and cmake to
make it possible to integrate these properly, but also those
Stephen Kelly wrote:
It'd need to be released quite a bit before us to
be something we can consider as a dependency. At that point I'm
considering having 2.8.12 as dependency for the release (so that it got
time to spread, sounds less likely with CMake 3).
I don't understand. Why is CMake
Kevin Ottens wrote:
10% chance? 50%? 80%?
Basically what's the time frame for CMake 3.
I'll be 90% surprised if it is not released in January, or maybe February.
Thanks,
Steve.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
On Mon, Nov 18, 2013 at 12:50 PM, Stephen Kelly steve...@gmail.com wrote:
Kevin Ottens wrote:
10% chance? 50%? 80%?
Basically what's the time frame for CMake 3.
I'll be 90% surprised if it is not released in January, or maybe February.
Thanks,
Steve.
On Monday 18 November 2013 12:49:39 Stephen Kelly wrote:
Stephen Kelly wrote:
It'd need to be released quite a bit before us to
be something we can consider as a dependency. At that point I'm
considering having 2.8.12 as dependency for the release (so that it got
time to spread, sounds
Kevin Ottens wrote:
You have enough credibility that people would believe it and spread it,
but it is not true. That's not how backward compatibility works in CMake.
I know, I was more thinking about the natural spreading of new version in
distros. The time they package stuff and that ends
On Mon, Nov 18, 2013 at 4:17 PM, Kevin Ottens er...@kde.org wrote:
On Monday 18 November 2013 13:27:19 Aleix Pol wrote:
So would it be that bad to have a macro of ours that ends up being just a
wrapper to qt5_wrap_ui?
Otherwise, this delays the possibility to help the ongoing porting
On Monday 18 November 2013 17:41:49 Aleix Pol wrote:
On Mon, Nov 18, 2013 at 4:17 PM, Kevin Ottens er...@kde.org wrote:
Right, we need to cater to that need too. Since that's tied to ki18n use,
what about putting that wrapper macro in ki18n for the time being?
Of course it should be
Chusslove Illich wrote:
[: Stephen Kelly :]
This depends on Qt 5.3 and CMake master plus some trivial new generator
expressions. Aside from bikeshedding names of things and defaults, can
you see any problem with this?
Other than bikeshedding about the defaults (which I will do a bit
On Mon, Nov 18, 2013 at 9:10 PM, Chusslove Illich caslav.i...@gmx.netwrote:
[: Kevin Ottens :]
Of course it should be removed when we get a proper fix via CMake 3
around. But in the meantime it'll do the trick and allow removing
dependencies on KDE4Support just for that.
[: Aleix Pol
Chusslove Illich wrote:
[: Aleix Pol :]
I have been going through the list looking for what we should we do when
it comes to .ui file generation and i18n.
I am confused by that too. Stephen's projected solution seems to me more
elegant in principle, but I couldn't quite get if (when) it
Kevin Ottens wrote:
On Friday 15 November 2013 16:28:10 Stephen Kelly wrote:
Aleix Pol wrote:
I see that Stephen Kelly has been doing some work on Qt and cmake to
make it possible to integrate these properly, but also those changes
will get in cmake 3 and Qt 5.3 which are not among our
[: Stephen Kelly :]
If such calls are generated by uic, then that is a bug in Qt (which should
have been reported years ago), and should be fixed in Qt, right?
Maybe, I'm not sure of the conventions of Qt Linguist. For Gettext-based
system, empty string will not result in empty translation,
Hi,
I have been going through the list looking for what we should we do when it
comes to .ui file generation and i18n.
I see that Stephen Kelly has been doing some work on Qt and cmake to make
it possible to integrate these properly, but also those changes will get in
cmake 3 and Qt 5.3 which are
Aleix Pol wrote:
I see that Stephen Kelly has been doing some work on Qt and cmake to make
it possible to integrate these properly, but also those changes will get
in cmake 3 and Qt 5.3 which are not among our dependencies.
CMake 3 will probably be out when releasing KI18n. Only KArchive
On Friday 15 November 2013 16:28:10 Stephen Kelly wrote:
Aleix Pol wrote:
I see that Stephen Kelly has been doing some work on Qt and cmake to make
it possible to integrate these properly, but also those changes will get
in cmake 3 and Qt 5.3 which are not among our dependencies.
CMake 3
[: Aleix Pol :]
I have been going through the list looking for what we should we do when
it comes to .ui file generation and i18n.
I am confused by that too. Stephen's projected solution seems to me more
elegant in principle, but I couldn't quite get if (when) it would be able to
do all that
18 matches
Mail list logo
