Am 2013-05-27 04:02, schrieb David Edmundson:
On Sun, May 26, 2013 at 11:05 AM, Martin Graesslin
wrote:
Hi all,
this is probably a controversial proposal: Let's disable bug
reporting for
Plasma until the current situation is improved.
Reason: the bugtracker in it's current state gets floode
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110633/
---
(Updated May 27, 2013, 7:59 a.m.)
Status
--
This change has been disc
On Sun, May 26, 2013 at 11:05 AM, Martin Graesslin wrote:
> Hi all,
>
> this is probably a controversial proposal: Let's disable bug reporting for
> Plasma until the current situation is improved.
>
> Reason: the bugtracker in it's current state gets flooded by new incoming
> reports and we are no
On Sunday 26 May 2013 18:53:24 Kai Uwe Broulik wrote:
> > very nice; one thing that Marco noted was that it should only be animating
> > when the popup is open
>
> Fixed. Although I couldnt just do
> running: plasmoid.popupShowing
> but had to fetch the property on the root item and pass it thro
On Sunday 26 May 2013 18:35:20 Martin Graesslin wrote:
> > So if ambiguity is the only reason against using switches on Desktop, we
> > should use them.
>
> At least for me there is another reason: given the way how the switch
> component is designed (again no matter which one) I am inclined to dr
So I pushed a few patches:
Am Samstag, 25. Mai 2013, 13:10:14 schrieb Aaron J. Seigo:
> see these screenshots for some layouting issues:
Fixed.
> also, after expanding a battery to see detailed information, collapsing it
> leaves an empty space. that should re-collapse, similar to thow the
> not
On Monday, May 27, 2013 00:41:31 Jekyll Wu wrote:
> "let's acknowledge the mess, close all existing bugs and restart from zero".
afaik, that is not being suggested.
the plan is close OLD crash reports so we only have crash reports against
moderately new versions.
--
Aaron J. Seigo
signature
于 2013年05月26日 18:05, Martin Graesslin 写道:
> Hi all,
>
> this is probably a controversial proposal: Let's disable bug
> reporting for Plasma until the current situation is improved.
>
> Reason: the bugtracker in it's current state gets flooded by new
> incoming reports and we are not able to get t
On Sunday 26 May 2013 18:07:14 Thomas Pfeiffer wrote:
> On Sunday 26 May 2013 00:05:56 Marco Martin wrote:
> > On Saturday 25 May 2013 14:32:29 Martin Graesslin wrote:
> > > > And this is clearly the case let's work around something we don't want
> > > > to
> > > > fix. Switches are a clear improve
On Sunday 26 May 2013 00:05:56 Marco Martin wrote:
> On Saturday 25 May 2013 14:32:29 Martin Graesslin wrote:
> > > And this is clearly the case let's work around something we don't want
> > > to
> > > fix. Switches are a clear improvement over checkboxes depending on the
> > > context even my 60yo
> On May 26, 2013, 9:42 a.m., Marco Martin wrote:
> > The libtaskmanager part is nice.
> >
> > However the applet is about t be replaced, so the display part would have
> > to be redone
I am aware that the tasks applet is going to be replaced soon, but most changes
of this patch are in the li
On Sunday 26 May 2013 13:26:45 Aaron J. Seigo wrote:
> On Sunday, May 26, 2013 12:05:25 Martin Graesslin wrote:
> > this is probably a controversial proposal: Let's disable bug reporting for
> > Plasma until the current situation is improved.
>
> ..
>
> > Opinions?
>
> I would expect this to pis
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107983/#review33146
---
Ship it!
Ship It!
- Aaron J. Seigo
On March 23, 2013, 8:06
On Sunday, May 26, 2013 12:05:25 Martin Graesslin wrote:
> this is probably a controversial proposal: Let's disable bug reporting for
> Plasma until the current situation is improved.
..
> Opinions?
I would expect this to piss off users even more than the current situation.
Saying "we don't even
Hi all,
this is probably a controversial proposal: Let's disable bug reporting for
Plasma until the current situation is improved.
Reason: the bugtracker in it's current state gets flooded by new incoming
reports and we are not able to get the water out of our cellar as long as new
water is co
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110504/#review33145
---
The libtaskmanager part is nice.
However the applet is about t
> On May 26, 2013, 9:39 a.m., Marco Martin wrote:
> > Ship It!
At least for the plasma part, some feedback by solid people would be
appreciated as well ;)
- Marco
---
This is an automatically generated e-mail. To reply, visit:
http://g
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110608/#review33143
---
Ship it!
Ship It!
- Marco Martin
On May 23, 2013, 9:13 a.m.
> overriding the implementation of QApplication::saveState() or by using
> KSessionManager)
Ah, ok then. You have the green light for the change, as long as it doesn't
changes the workflow for the non-manually-saved-session-restoration mode.
Cheerio,
Ivan
--
A program that has not been teste
On Sunday 26 May 2013 14:30:05 Simon Persson wrote:
> The needed change for this to work would be for kamd to _not_ save the
> running state to file every time it changes, but instead only when asked by
> the session manager to save state. (For applications that is done by
> overriding the impleme
On Sunday, May 26, 2013 1:23:20 PM ICT, Ivan Čukić wrote:
I would say that the right thing (what I as a user would expect to happen)
is that clicking "save session" in the kickoff menu would save which
I might be missing the point - kamd loads the last used
activity on login (if
it doesn't, i
21 matches
Mail list logo
