be good
to avoid spending resources on this.
--
Thomas Zander
to
those already.
--
Thomas Zander
Quoting Chusslove Illich caslav.i...@gmx.net:
[: Thomas Zander :]
I like that idea in general, not sure how to implement it properly,
though. Simplest idea is to make cmake generate a klocale-{module}.h
file and make everyone include that. But that sounds like a lot of work.
Actually I have
rather well, but I could definitely be missing details
here.
--
Thomas Zander
will never resolve to a string in any framework.
--
Thomas Zander
failed before
that this is actually worth stopping the innovations that Chusslove is working
on?
Read those numbers again; its kinda depressing really;
Only 5 out of
24 KUIT tags were used more than 100 times (filename being the most used
with 333 appearances).
--
Thomas Zander
renders the whole
screen.
Sounds good to me.
--
Thomas Zander
://www.oyranos.org/doc_alpha/index.html
--
Thomas Zander
if there is currently no KDE gui for it.
--
Thomas Zander
to give an opinion on a (technical) idea, the above is
not acceptable.
Please respect these values we hold dear here in KDE :)
--
Thomas Zander
I disagree.
Could you explain what you mean with the
since other KDE already works with it
part?
AFAIK there is no KDE software that would function better with oyranos than
with colord. Which means there is no clear advantage on that basis. Am I
missing some piece of software?
--
Thomas
a bigger impact than
the gnome components that pull it in.
--
Thomas Zander
On Wednesday 14 March 2012 18.12.13 Kai-Uwe Behrmann wrote:
Am 14.03.12, 17:46 +0100 schrieb Thomas Zander:
On Wednesday 14 March 2012 16.39.00 Boudewijn Rempt wrote:
Colord - just to mention that - is also not a GNOME project, it's a
FreeDesktop project. (Doesn't mean it's standard
and OSX ?
Matthias answered your question very well, and I agree with him.
Let me ask you a return question; with the heavy dependency on X11 in oyranos
but with colord already starting work on wayland, how will we support wayland
soon?
--
Thomas Zander
into bugzilla tasks which are
handled as normal.
So, I'm interested (and active) in solving this in a way that is only
a little related to bugzilla and get free from the thinking imposed by
bugzilla.
--
Thomas Zander
Quoting Niko Sams niko.s...@gmail.com:
On Mon, Mar 12, 2012 at 17:32, Thomas Zander zan...@kde.org wrote:
On Monday 12 March 2012 16.20.00 David Jarvie wrote:
There would be an advantage in giving instant feedback to the user if
possible, but if that turns out to be impractical, Thomas's
(and
needed) project so I could help out.
Cheers
--
Thomas Zander
--rebase
The 'no branching work' is what 90% of the contributors will do, they just
work on one branch all the time.
--
Thomas Zander
community.
Kind of a postscript I just wanted to reply on your argument for a branch. It
doesn't in practice apply to the guys coming in with a simple bugfix. Their
starting point will very likely be the current main branch.
--
Thomas Zander
On Wednesday 18 January 2012 10.11.58 todd rme wrote:
But according to Martin, this isn't just about API changes, it is also about
behavior changes. How do you expect people to know if they are relying on a
Qt 4.8-specific behavior?
As far as I know there are no forward incompatible behavior
.
--
Thomas Zander
community members that may not have the computer power or
computer savy or just the time you have.
thanks :)
--
Thomas Zander
torsdagen den 12 januari 2012 22.50.24 skrev Ingo Klöcker:
If you want developers to switch to Qt 4.8 to get the KDE code better
tested with this version of Qt then simply ask developers to do so. I
see no good reason to force developers to do so.
+1
--
Thomas Zander
On Wednesday 04 January 2012 20.54.27 Alexander Neundorf wrote:
It would mean that simply using kdeclarative means that cmake
interprets this as name of a library and simply adds -lkdeclarative to the
command
line, without checking whether it actually exists nor in which directory.
I can
On Wednesday 04 January 2012 21.55.36 Lamarque V. Souza wrote:
My question is: since you know how to send patches to Qt's
repository wouldn't be better just send my patch upstream (it is
here https://bugs.kde.org/show_bug.cgi?id=182672)
Contributing to Qt is a simple matter; after a
to be tricky since the feature-freeze in Qt is
coming very very quickly. (mere weeks)
So unless this can be done binary-compatible this change will likely have to
wait for Qt6 ;)
--
Thomas Zander
!
--
Thomas Zander
helper,
unrelated to libmm-qt (though the name suggests otherwise). mm and nm
really don't say much about what these libraries do. the names are
ambiguous and stand a high chance of collision with other libraries.
+1
--
Thomas Zander
between the lowercase and the mixed-case ones.
Lets start with a descriptive and clear name, to raise the bar.
Cheers!
--
Thomas Zander
for me is that we move the responsibility of defending decisions
and documenting them and gathering them up etc from the people that made
those decisions to the community at large.
--
Thomas Zander
sense from your perspective.
It also makes sense from the long term, the medium term and the KDE community
perspectives.
The short term you have to talk to the maintainer of the application you are
targetting; but thats obviously off topic for this list.
--
Thomas Zander
a natural evolution.
--
Thomas Zander
a good usecase which they did not
think about yet.
Cheers!
--
Thomas Zander
disturbing at night.
My usecases could now be solved by having an activity like watching TV,
another thats Music centre for usage at parties and a 3rd for idle state
which turns off the screen after 2 min.
Thanks!
--
Thomas Zander
On Tuesday 13 September 2011 02.52.53 Giorgos Tsiapaliwkas wrote:
Does anyone can point me to the qt docs system and how it works(any link?)?
http://doc.qt.nokia.com/latest/qthelp-framework.html
--
Thomas Zander
://www.stack.nl/~dimitri/doxygen/faq.html
Here is a version that claims to do this trick for cmake modules;
https://github.com/saschazelzer/CMakeDoxygenFilter/
--
Thomas Zander
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102519/#review6263
---
Showing less text even when you have the space for it sounds
subsequent release so you can avoid accidental breakages.
I've been doing C++ for years, and I still accidentally make breakages when I
change something I didn't expect to cause issues, its much easier to break
than you might expect ;)
Cheers!
--
Thomas Zander
mirrors of many open source git repositories from lots of different
sources, there this would get lost too.
I would be happier with the KDE/x.y solution, personally.
--
Thomas Zander
On Wednesday 17 August 2011 09.24.31 Alexander Potashev wrote:
If I'll add just a forward declaration like class NoteInfoPrivate;
and a NoteInfoPrivate *p; into the NoteInfo class, will it be OK?
I guess you mean using a d-pointer, yes, that's the suggested way of
dealing with this kind of
On Sunday 14 August 2011 23.05.41 Albert Astals Cid wrote:
#2 Your patch has several issues i mentioned there
I noticed those too, and I wanted to just say that I'd trust David and Thiago
on these concepts any day. Maybe we can just use the structure they suggested
(and Albert coded) and move
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102267/#review5598
---
kioslave/ftp/speedController.h
:00 2001
From: Thomas Zander zan...@kde.org
Date: Tue, 9 Aug 2011 12:32:55 +0200
Subject: [PATCH 1/2] fix typos
---
kio/kio/kurifilter.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kio/kio/kurifilter.h b/kio/kio/kurifilter.h
index 289b910..c773f2d 100644
--- a/kio
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102246/#review5517
---
This change could alter the behaviour of some windows, if they
like this?
const int id = QHostInfo::lookupHost ( hostname, receiver, slot);
QTimer::singleshot(timeout, QHostInfo::abortHostLookup (id );
And do we really want a public API doing that?
I would guess a private (or non exported) method in kio and/or khtml can do
that.
--
Thomas Zander
On Monday 08 August 2011 21.02.02 Dawit A wrote:
On Mon, Aug 8, 2011 at 2:31 PM, Thomas Zander zan...@kde.org wrote:
On Monday 08 August 2011 18.35.13 Dawit A wrote:
#2. The original functions in this class were non-blocking. It is only
the new function I added that is a blocking call
On Monday 08 August 2011 21.28.45 Dawit A wrote:
On Mon, Aug 8, 2011 at 3:20 PM, Thomas Zander zan...@kde.org wrote:
On Monday 08 August 2011 21.02.02 Dawit A wrote:
On Mon, Aug 8, 2011 at 2:31 PM, Thomas Zander zan...@kde.org wrote:
On Monday 08 August 2011 18.35.13 Dawit A wrote:
#2
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102149/#review5482
---
Hmm, did this get committed already?
visually the change looks
with the assumption that a piece of
software is only usable on one desktop won't have problems if you call a
similar piece of software the same on your desktop.
In general; please stop assuming ;) (ask politely first)
--
Thomas Zander
49 matches
Mail list logo
