On Thursday 03 February 2011 19:28:44 Marco Martin wrote:
Hi all,
thi probably isn't going to be a good workflow for the future, but now that
kdelibs and base are just being converted i think would be a pretty common
problem.
basically, what i have is some repositories (one born as git,
On Friday 04 February 2011 17:05:07 Tom Albers wrote:
- Original Message -
It
is when I have to unnecessarily type more than I have to. Seriously
this is getting to be annoying and I do not mean you personally. These
rigid and brittle coding styles. One project says no braces
On March 8, 2011, 2:12 p.m., Hans Meine wrote:
kcontrol/colors/colorsettings.ui, line 615
http://git.reviewboard.kde.org/r/100821/diff/1/?file=10768#file10768line615
I believe to recall that blend was the term used in the past as well,
but given that not all styles actually use
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/100921/#review2349
---
Ship it!
Btw a window implementation should be possible,
On Monday 09 May 2011 12:27:14 Maksim Orlovich wrote:
I am probably being a bit selfish here, but I don't see how we can
ever build on a toolkit that requires OpenGL ES2.0 level hardware.
I think it would make sense to have at least optionally the legacy code
(QWidget + X11)
without an OpenGL
On Monday 09 May 2011 18:03:18 Olivier Goffart wrote:
Hi,
With Qt5 around the corner[1], I think it is time to start thinking about KDE5
Raw summary:
- Qt5 is planed to be released in about one year from now if everything goes
well.
- It should be mostly source compatible with Qt4,
On Monday 06 June 2011 23:05:52 Ben Cooksley wrote:
Hi all,
I am requesting that a moratorium on dependency bumps for dependencies
which are hard to build be enacted. This would affect system wide
components which rely on root access and are heavily integrated into
the system. This would
On Monday 13 June 2011 21:10:36 Alex Fiestas wrote:
Hi there
Today something happened to me again, I turn on my laptop at the begining of
a
meeting and when I needed it the battery was over because the laptop didn't
went to suspension (as I'm used).
That makes me wonder what are the
On Mon, 13 Jun 2011 16:29:45 -0400, Shaun Reich predator...@gmail.com
wrote:
lightDM is also headed by my dear friend Canonical, as is clearly
seen.
Serious question: does anyone know if it requires Canonical's copyright
assignment to contribute to lightDM? If yes we can stop any further
On Tuesday 14 June 2011 10:35:49 Harald Sitter wrote:
On Tue, Jun 14, 2011 at 8:16 AM, Martin Gräßlin mgraess...@kde.org wrote:
On Mon, 13 Jun 2011 16:29:45 -0400, Shaun Reich predator...@gmail.com
wrote:
lightDM is also headed by my dear friend Canonical, as is clearly seen.
Serious
On Tuesday 14 June 2011 20:26:45 Harald Sitter wrote:
snip
Agreed.
Yet despite having complete control we did not manage to come up with a truly
good workspace experience that starts at the DM (power management, good
looks,
I for one have yet to see a sane UI-wise integration of stuff
On Wednesday 15 June 2011 12:22:10 Alex Fiestas wrote:
But right now: (Once again this is what I see from outside:)
-KDM developers have no plans
This seems incorrect, given Shaun's work on Plasma - and after the discussion
in this thread
this should be known by now.
-KDM maintainer has no
On Wednesday 15 June 2011 17:46:08 Alex Fiestas wrote:
On Wednesday, June 15, 2011 05:37:14 PM todd rme wrote:
There are apparently people willing to implement KDE support in
LightDM, so why don't they instead improve KDM? Why should they be
putting their effort into an immature project
On Wednesday 20 July 2011 11:52:31 Alex Fiestas wrote:
Hi there
Last few days I have been patching some pieces of our workspace here and
there, the first set of patches I did them directly into master which if
I remember correctly was against the policy.
So, the second round of fixes I
On Saturday 23 July 2011 01:42:16 David Jarvie wrote:
On Saturday 23 July 2011 00:00:16 Nicolas Alvarez wrote:
There is no active policy saying you're supposed to merge. Almost everybody
in KDE is still doing cherry-picks. KDevelop is the only KDE project I know
that consistently uses
On Saturday 23 July 2011 19:28:53 Ben Cooksley wrote:
During the stable branch freeze before a minor version release (such as
currently
before
the 4.7 release), it isn't possible to commit bug fixes to stable first and
then merge to
master.
Only master can be committed to, so
On Monday 18 July 2011 22:43:20 Alexander Neundorf wrote:
Hi,
I'm currently comparing our FindX11.cmake with the one in current cmake.
Our copy is in kdelibs/cmake/modules/, CMake's is in its Module/ directory.
There are some things our version checks for, which the one from cmake
On Sunday 31 July 2011 12:58:05 Michael Jansen wrote:
Hi @all
I am currently trying to setup a compiled from sources master on opensuse in
a
vm. I first tried kvm and then virtualbox.
In both cases i got the same problem. The vms work as expected with the
opensuse 11.4 provided kde
On Saturday 20 August 2011 12:20:55 Thiago Macieira wrote:
That I agree: klauncher is systemd for KDE only, so we should see about
getting the same benefits from systemd instead.
There are two drawbacks with that, though:
1) systemd will not likely ever run on non-Linux systems, not even
On Friday 02 September 2011 19:23:52 Guy Maurel wrote:
Hello Martin!
First: Thanks!
On Friday, September 02, 2011 06:45:58 PM Martin Gräßlin wrote:
On Friday 02 September 2011 18:16:05 Guy Maurel wrote:
Hello!
It might be trivial:
I got many kde-xx software from git, compile
On Tuesday 27 September 2011 16:57:20 Lydia Pintscher wrote:
Heya folks :)
I've got an eager SoK student who needs a mentor for a bit of
hand-holding in the coding part of his project. He's already done
extensive research but is stuck on the implementation part because his
initial mentor
On Sunday 02 October 2011 21:09:00 Andras Mantia wrote:
On Sunday, October 02, 2011 14:45:58 Dario Freddi wrote:
That was one example. Another example brought up is e.g switching of
strigi or nepomuk indexing when switching to a power saving profile.
These two are something that usually
On Sunday 02 October 2011 18:36:14 Allen Winter wrote:
Howdy,
A lot of CMakeLists.txt use the ${GENERIC_LIB_VERSION} to set the so
versioning of their libraries.
That variable is hard-coded in kdelibs/cmake/modules/KDE4Defaults.cmake
If we rely on kdelibs-4.7 for the KDE SC 4.8 release,
On Oct. 3, 2011, 1:15 p.m., David Faure wrote:
Couldn't this be done higher in the stack, e.g. in KTabWidget or in Qt?
Kevin Kofler wrote:
Indeed, I think there should be some interface for this stuff in kdelibs,
so that 1. applications don't have to add such platform-specific code
Hi all,
as you might know we have been working on moving the screenlocker from KRunner
to KWin and passed the control to the compositor (iff compositing is active)
to ensure that nothing which should not be shown gets visible.
I want to request a security audit for the changes to ensure that
On Tuesday 11 October 2011 15:33:39 Torgny Nyblom wrote:
On Tuesday 11 October 2011 14.55.29 Martin Gräßlin wrote:
On Monday 10 October 2011 20:02:07 Parker Coates wrote:
On Sun, Oct 9, 2011 at 14:02, Martin Gräßlin wrote:
I want to request a security audit for the changes to ensure
On Tuesday 11 October 2011 16:06:11 Andras Mantia wrote:
From here:
If KWin crashes without restarting privacy is leaked but the system is
hardly useable due to missing window manager. This situation can savely
be ignored as a corner case as KWin normaly restart.
This is not true, the
On Tuesday 11 October 2011 16:33:39 you wrote:
Once the screen locker crashes, security must be assumed
broken (if only by visual access).
Therefore the locker must not crash
full ack, we have to be at 0 crashes in KWin (which has to be our goal for
Wayland anyway ;-)
and if it does,
On Tuesday 11 October 2011 17:47:13 you wrote:
Am Tue, 11 Oct 2011 17:00:46 +0200
schrieb Martin Gräßlin mgraess...@kde.org:
that is a good suggestion. I will think about how I can add that.
Though if someone breaks by crashing kwin he is also able to remove
any log. So this could be just
the screen locking.
On Tue, Oct 11, 2011 at 04:00:17PM +0200, Martin Gräßlin wrote:
yes if you have a terminal open and if it is the top most of stacking
order it is possible to start another window manager.
[in fact ... oh, scratch that, thomas already answered]
I think there is hardly
On Tuesday 11 October 2011 18:02:32 Torgny Nyblom wrote:
On Tuesday 11 October 2011 15.55.15 you wrote:
Am Tue, 11 Oct 2011 15:33:39 +0200
schrieb Torgny Nyblom nyb...@kde.org:
Does this mean that I will be focred to use a screensaver with
password unlock? If so why is that not a
On Tuesday 11 October 2011 21:06:13 Alexander Neundorf wrote:
On Tuesday 11 October 2011, Martin Gräßlin wrote:
On Tuesday 11 October 2011 16:06:11 Andras Mantia wrote:
From here:
If KWin crashes without restarting privacy is leaked but the system is
hardly useable due to missing
On Wednesday 12 October 2011 08:26:20 Torgny Nyblom wrote:
On Tuesday 11 October 2011 20.54.42 Thomas Lübking wrote:
Am Tue, 11 Oct 2011 18:02:32 +0200
schrieb Torgny Nyblom nyb...@kde.org:
Screensaver is bling only
No, screensaver hacks are bling only, a screensaver is a
software
On Wednesday 12 October 2011 09:10:40 Oswald Buddenhagen wrote:
Of course KWin is a more complex application than others, but given
what we need in a screen locker the difference becomes marginal IMHO.
yes. one should consider decoupling the greeter from the core engine.
I myself have
On Wednesday 12 October 2011 19:38:11 Oswald Buddenhagen wrote:
On Wed, Oct 12, 2011 at 04:47:54PM +0200, Dario Freddi wrote:
2011/10/12 Martin Gräßlin mgraess...@kde.org:
ok I have been thinking about it and have a new proposal:
* writing a kded module to only handle the screen locking
On Thursday 13 October 2011 17:29:16 Martin Koller wrote:
On Tuesday, 11. October 2011 21:11:03 Martin Gräßlin wrote:
I consider most effects being bling yes, with that said I like it and
appreciate it but still most effects add no real productive value.
offtopicI have to disagree
On Thursday 13 October 2011 20:49:29 Matthias Fuchs wrote:
I understand and agree to the technical reasons against keeping the
current architecture but that does not mean that I agree to all the
other arguments.
I just want to point out once more that we will not remove anything which is
change and should
be fine for 4.7 as well. But I don't know what's the state for additions to
kdelibs currently...
- Martin Gräßlin
On Nov. 9, 2011, 10:15 p.m., Anton Kreuzkamp wrote:
---
This is an automatically generated e-mail
On Saturday 12 November 2011 08:12:27 Kevin Kofler wrote:
We definitely do want your ksecretsservice work ASAP and I don't see why it
can't be in kdelibs where it belongs.
*sigh* could we please stop adding this whining about the frozen kdelibs in
each thread on kde-core-devel.
Yes we got that
On Wednesday 11 January 2012 17:38:11 Allen Winter wrote:
On Wednesday 11 January 2012 11:47:00 AM Shaun Reich wrote:
Prompting motion for making Qt 4.8 a hard dependency for KDE
4.9/master. Currently kde-baseapps/plasma/folderview does not build
against 4.7 due to an (albeit minor) api
On Wednesday 18 January 2012 10:26:13 Thomas Zander wrote:
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
On Wednesday 18 January 2012 12:53:25 Dario Freddi wrote:
Let's try to move the issue another way
round: can we think of a way in which we can safely make master depend
on new stuff without the risk of hurting these categories?
Yes of course. First of all we have to think whether we introduce
On Thursday 19 January 2012 08:52:48 Thomas Zander wrote:
On Thursday 19 January 2012 08.15.39 Martin Gräßlin wrote:
As far as I know there are no forward incompatible behavior changes
between Qt4.7 and Qt 4.8 I.e. AFAIK programming for 4.8 using 4.7 APIs
but 4.8 behavior will give
On Jan. 22, 2012, 9:06 a.m., Erik Sigra wrote:
Ship It!
giving yourself a ship it kind of destroys the idea behind review board.
From my side there is a clear NO for everything KWin related. So why? Let's
consider for example atoms.h. I just used git blame and well the includes were
last
Am 22.02.2012 18:13, schrieb Laszlo Papp:
The suggestion remains: to allow everyone to edit and close bugs, as
is
apparently the case in some other bug trackers.
+1.
Worked fine on the MeeGo bugzilla for instance, I previously used.
Personally I'm not sure whether the MeeGo bugzilla can be
Am 22.02.2012 20:01, schrieb Kai-Uwe Behrmann:
Am 22.02.12, 09:38 -0800 schrieb Daniel Nicoletti:
As Richard said Oyranos is doing all this by it self on the CPU so
it
would act like a proxy between your application,
and the window manager which sounds like killing performance.
( I might have
On Friday 24 February 2012 02:15:54 Sven Burmeister wrote:
Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin:
Personally I'm not sure whether the MeeGo bugzilla can be compared to
the KDE one (technical oriented vs. user oriented). From my personal
experience (KWin bugtracker
On Friday 24 February 2012 21:03:42 Ben Cooksley wrote:
On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Friday 24 February 2012 02:15:54 Sven Burmeister wrote:
Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin:
Personally I'm not sure whether
On Friday 24 February 2012 19:32:10 Andras Mantia wrote:
On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote:
Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia aman...@kde.org:
Bugzilla is not a to-do list, it is for what else... a bug (and
wishlist)
reporting tool for users.
On Friday 24 February 2012 19:11:12 Sven Burmeister wrote:
Am Freitag, 24. Februar 2012, 08:06:41 schrieb Martin Gräßlin:
My claim is that most of that user support only ends-up in bugzilla
because people did not get help somewhere else, e.g. because only
developers are familiar enough
On Friday 24 February 2012 19:27:09 Sven Burmeister wrote:
yes, of course, we have to help the users. But they need to get a tool for
user support, not a tool for developer communication. We need a
first-level- support to help the users. Developers are the
third-level-support.
I doubt
On Friday 24 February 2012 20:31:46 Andras Mantia wrote:
On Friday, February 24, 2012 06:51:11 PM Martin Gräßlin wrote:
- first level support
issues are not opened on the bug tracker but in a user support management
system - e.g. forums.kde.org. Only if the supporters figure out
On Monday 12 March 2012 19:39:12 Niko Sams wrote:
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
Good ideas, if anyone actually implements
what you want to tell me with this last sentence. To me it's
totally irrelevant what people want if I have to do a technical decision. I
also want many things but don't get them :-)
Kind Regards
Martin Gräßlin
KWin Maintainer
signature.asc
Description: This is a digitally signed message part.
On Wednesday 21 March 2012 19:14:51 Kai-Uwe Behrmann wrote:
Am 21.03.12, 18:20 +0100 schrieb Martin Gräßlin:
On Wednesday 21 March 2012 08:23:39 Kai-Uwe Behrmann wrote:
There is more into it: first of all KWin currently does not distinguish
between screens during rendering. To properly have
On Thursday 22 March 2012 19:20:11 Kai-Uwe Behrmann wrote:
Something like that is technical possible. But let me repeat, you get then
a mixture of colour managed and non colour managed apps with the same
toolkit, which is completely non understandable for users.
First of all: users don't know
On Monday 09 April 2012 13:15:26 Andreas Pakulat wrote:
There is not only Jenkins, but also CDash, which integrates nicely with
our
cmake-based build system.
I was trying to set up nightly builds for the KDE modules two years ago or
so (hosted on http://my.cdash.org, some of our
On Tuesday 10 April 2012 06:45:17 Laszlo Papp wrote:
all I care about is that its easy to get a project set up to
be build continously (and the unit-tests executed) and wether it
provides more than just build errors/warnings and test-results. Since
some of these things are handy -
://git.reviewboard.kde.org/r/104593/diff/
Testing
---
Thanks,
Martin Gräßlin
---
On April 13, 2012, 8:07 p.m., Martin Gräßlin wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104593
On Monday 16 April 2012 15:00:39 Rick Stockton wrote:
I know that such a request is only an optional suggestion to the WM.
Now, looking ahead: Do we want KWin (and maybe PLasma, as well) to
continue skip layers, going directly to xcb or wayland (or ??) in the
same way we currently do a lot of
On Sunday 29 April 2012 13:11:19 Alexander Neundorf wrote:
Can somebody please take care of the sorry state of our git documentation ?
There were so many people supporting it, can please somebody document it ?
On techbase.kde.org, not in some blog or wherever.
For the record:
On Friday 04 May 2012 22:36:25 Mark wrote:
Hi,
So all things considered, why don't we pull the plug for taskmanager and
start using icon tasks by default?
And would this still be on time for KDE 4.9?
this discussion does not belong on core-devel, but on plasma-devel as it is
only workspace
On Wednesday, May 23, 2012 22:08:08 Milian Wolff wrote:
We have port Kate away from QtScript.
I want to remind that today is beta tagging for 4.9 and we are already in
feature and dependency freeze.
No matter how we turn it: switching the scripting engine cannot count as a
bugfix and might
On Wednesday 06 June 2012 20:32:49 Albert Astals Cid wrote:
But I'm expecting more people to have an opinion on this. David? Sebas?
Someone from plasma?
in the initial thread I was in favor of going for Qt 4.8, but I accepted the
opinion of the majority. I would consider it as a bad incident if
On Monday 18 June 2012 00:26:13 Albert Astals Cid wrote:
My concerns:
* Need more people to do the tarball packaging/releasing (since if you
propose to release that often you can't expect the same person to be doing
packages almost weekly or byweekly given the release dates won't probably
On Monday 18 June 2012 19:08:33 Albert Astals Cid wrote:
El Dilluns, 18 de juny de 2012, a les 06:36:33, Martin Gräßlin va escriure:
On Monday 18 June 2012 00:26:13 Albert Astals Cid wrote:
My concerns:
* Need more people to do the tarball packaging/releasing (since if you
propose
On Wednesday 27 June 2012 23:28:30 Ivan Čukić wrote:
Hi all,
I've tested the waters some time ago [1] what would people say if we
started asking for more modern compilers. I've stated there I'll start
the discussion on k-c-d once we branch out 4.9, so I'm doing as
promised. The post was only
On Thursday 28 June 2012 00:27:08 Ivan Cukic wrote:
Can you explain why you need a more modern version, I see a good analysis
of what the current situation regarding compiler availability but i fail
to see why we need a newer compiler.
For me, the main reasons for this request are:
-
if it would mean that we have to restrict ourself to an outdated gcc
version. Reasons why in general I would find it acceptable to drop support for
non-linux in KWin are outlined in a recent discussion on plasma mailing list
[1].
@Raphael any idea about that?
Cheers
Martin Gräßlin
[1] http
Am 30.06.2012 17:31, schrieb Heinz Wiesinger:
However, the point of dropping platforms in general remains, I
suppose.
From what I understood the compilers are available in FreeBSD and I
think there was no other system having problems with it.
Regards
Martin Gräßlin
that it's docbook (tried it once, decided again that xml is just a form
of binary and I don't write binary).
Using Wiki markup is much more natural and with future MediaWiki
releases we will even have WYSIWYG editors.
Cheers
Martin Gräßlin
to
update to gcc 4.6.
Cheers
Martin Gräßlin
On Tuesday 10 July 2012 18:12:03 Thomas Lübking wrote:
Am 10.07.2012, 17:38 Uhr, schrieb guy-kde guy-...@maurel.de:
Hello Thomas!
Hi Guy and everyone else =)
There's iirc somewhere a config key to build kwin w/o activity
support - try ccmake
I found in CMakeCache.txt:
//Enable
but not beeing a mouse.
So I would say that it would be a waste to not make use of what's possible.
Kind Regards
Martin Gräßlin
signature.asc
Description: This is a digitally signed message part.
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105522/#review15724
---
Ship it!
Ship It!
- Martin Gräßlin
On July 12, 2012, 7:57
bad idea to ask for passwords in a nag window way as long as
we have kded asks for password. Yeah right, what's kded again?
- Martin Gräßlin
On July 20, 2012, 1:41 p.m., Allen Winter wrote:
---
This is an automatically generated e
On July 20, 2012, 2:15 p.m., Martin Gräßlin wrote:
Allen Winter wrote:
So I don't know much about window managers and stuff.. what I want is to
make sure that no matter what the prompt dialog is in the user's face and
can't be dismissed.
The worst case I've found
On Friday 20 July 2012 18:48:47 Thomas Lübking wrote:
Like into the plasma-desktop process which shares memory with random
plasmoids of questionable source?
No. And I mean no way. The wallet password dialog isn't very secure
anyway, but passing the password through plasma means to open it
On Friday 20 July 2012 19:37:00 Thomas Lübking wrote:
no, see above. the password dialog is snake-oil. (given kwallet acts like
this)
no it's not complete snake-oil. It does not protect against an attacker
already on the system (to my knowledge hardly anything not running as root can
be
On Friday 20 July 2012 18:25:15 David Edmundson wrote:
On Fri, Jul 20, 2012 at 4:58 PM, Martin Gräßlin mgraess...@kde.org wrote:
Hi all,
the problems around review request #105628 and getting KWallet's Password
dialog properly raised above the window it is asking the password for just
On Tuesday 24 July 2012 14:20:48 Aurélien Gâteau wrote:
Le vendredi 20 juillet 2012 17:58:04 Martin Gräßlin a écrit :
Providing a password safe and asking for the master password is also a
system service and should belong into the workspace.
So here my idea: let's move the password dialog
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105628/#review17478
---
this approach seems fine to me.
- Martin Gräßlin
On Aug. 4
On Wednesday 22 August 2012 20:44:00 Sune Vuorela wrote:
From my personal view and as a packager, I would say we only need *one*
display manager in the workspace. So, if lightdm comes, then KDM must
go in my opinion.
No, LightDM-KDE and KDM solve different problems. KDM is a full-blown display
On Tuesday 11 September 2012 15:24:44 Cedric Bellegarde wrote:
Hello,
since last mail, many changes.
Kded-appmenu:
https://projects.kde.org/projects/kdereview/kded-appmenu
- DBus interface allowing KWin to ask for applications menu to popup
- New Top menubar:
*
to
the line edit by default in this mode.
Overall it's good stuff from a user perspective (I haven't looked at the
code at all unfortunately), just need to make sure it's possible to lock
screen and unlock without using the mouse. :)
Martin Gräßlin wrote:
The only issues I've
On Saturday 29 September 2012 11:48:03 Alexander Neundorf wrote:
On Saturday 29 September 2012, André Wöbbeking wrote:
Hi Alex,
On Saturday 29 September 2012 10:36:55 Alexander Neundorf wrote:
I know this will cause some effort, because I guess only few
distributions already come with
On Saturday 29 September 2012 13:19:30 you wrote:
But how does that differ from requiring other very recent packages,
including Qt ?
we don't do that. We still require only Qt 4.7 and there is one difference in
build system vs. some depending library. Depending library is nicely handled
by
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/106124/#review19834
---
It's submitted, isn't it?
- Martin Gräßlin
On Sept. 19
On Monday 08 October 2012 22:40:55 Albert Astals Cid wrote:
Hi fellow kde-core-develers, i was thinking that from time to time someone
commits some code that breaks the building of the tests.
This happens because people is not aware that those parts are unit tested.
I think that by
On Saturday 29 December 2012 16:25:54 Albert Astals Cid wrote:
Would there be any chance to have the style check done by a pre-commit hook?
Or at least have a command-line tool that checks it for me?
yeah that should be possible. At my old day-job I created a pre-commit hook to
basically grep
On Sunday 06 January 2013 16:37:47 Aaron J. Seigo wrote:
btw, these changes were made in mid-November of 2012. i'm a little surprised
people are only noticing now.
maybe because the hard feature freeze was on November 8th and nobody expects
that they need to adjust their applications after the
On Monday 07 January 2013 10:51:11 Aaron J. Seigo wrote:
On Sunday, January 6, 2013 17:40:42 Thomas Lübking wrote:
1. it will make kwin link generic-shell what is sematically the
gnome/unity
shell approach.
it is a library. that does not rely on the desktop (or other) shell. it
provides
On Monday 07 January 2013 11:03:24 Aaron J. Seigo wrote:
a reversion is not going to happen at this point. it is the proper way to do
the shadows (one that relies on window manager functionality which kwin has
thankfully provided for quite some time now; i'm a bit surprised that of
all
Am 07.01.2013 14:18, schrieb Aaron J. Seigo:
On Monday, January 7, 2013 11:14:49 Martin Gräßlin wrote:
The shadow system has been designed to work around the problem which
occurs
if we try to have the shadow in the panel. That is for any window
where the
shadow should not be part of the window
(in case you use any Kate-based editor: there's an option to only remove
whitespaces on changed lines)
- Martin Gräßlin
On Jan. 7, 2013, 3:11 p.m., Xuetian Weng wrote:
---
This is an automatically generated e-mail. To reply
X :-) For 4.10 it
shall be Plasma.Dialog there of course.
kwin/tabbox/qml/qmldir
http://git.reviewboard.kde.org/r/108243/#comment19118
please don't include the IconTabBox in the qmldir. I consider it private
API :-)
- Martin Gräßlin
On Jan. 7, 2013, 4:07 p.m., Xuetian Weng wrote
On Jan. 7, 2013, 4:39 p.m., Martin Gräßlin wrote:
kwin/tabbox/qml/qmldir, line 2
http://git.reviewboard.kde.org/r/108243/diff/2/?file=105557#file105557line2
please don't include the IconTabBox in the qmldir. I consider it
private API :-)
Xuetian Weng wrote:
I saw
On Wednesday 09 January 2013 18:35:49 Martin Sandsmark wrote:
On Tuesday 08 January 2013 19:30:45 Allen Winter wrote:
No docbook manual
I guess I'll to contact the doc team for this?
Do you want apidox generated? if so you also need a Mainpage.dox
No need for that (yet, at least, we
we could add a KDE hint. We
see the problem with _NET_WM_STATE_HIDDEN in the comment section of the code:
shaded windows use it, too.
- Martin Gräßlin
On Jan. 10, 2013, 12:12 a.m., Yichao Yu wrote:
---
This is an automatically generated
1 - 100 of 349 matches
Mail list logo
