On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/114283/#review60536
---
This patch doesn't include Plasma's SectionScroller, so it
On June 19, 2014, 4:26 p.m., David Edmundson wrote:
This patch doesn't include Plasma's SectionScroller, so it would be a
regression.
However I'm not entirely sure what SectionScroller actually does, so
possibly not an important one.
Shouldn't we either commit to the review request
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
On June 19, 2014, 4:26 p.m., David Edmundson wrote:
This patch doesn't include Plasma's SectionScroller, so it would be a
regression.
However I'm not entirely sure what SectionScroller actually does, so
possibly not an important one.
Aleix Pol Gonzalez wrote:
Shouldn't we
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/114283/
---
(Updated June 19, 2014, 6 p.m.)
Review request for KDE Frameworks and
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/114283/#review60553
---
Ship it!
Ship It!
- Marco Martin
On June 19, 2014, 6
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/114283/#review60554
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/114283/
---
(Updated June 19, 2014, 6:09 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/114283/#review60561
---
Note: The property names don't line up 100% in the merge.
On June 19, 2014, 8:42 p.m., David Edmundson wrote:
Note: The property names don't line up 100% in the merge.
flickableItem has now become contentItem (which is a default property)
All instances in plasma-workspace/plasma-desktop are now updated.
That doesn't matter: flickableItem:
On June 19, 2014, 8:42 p.m., David Edmundson wrote:
Note: The property names don't line up 100% in the merge.
flickableItem has now become contentItem (which is a default property)
All instances in plasma-workspace/plasma-desktop are now updated.
Kai Uwe Broulik wrote:
That
On June 19, 2014, 8:42 p.m., David Edmundson wrote:
Note: The property names don't line up 100% in the merge.
flickableItem has now become contentItem (which is a default property)
All instances in plasma-workspace/plasma-desktop are now updated.
Kai Uwe Broulik wrote:
That
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/114283/#review45057
---
I really like the idea. I think we should keep our Scroll*
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in to
ease porting, but move away from using it for our own stuff first, and
then, before a first API promise, revisit if we can remove our own
implementation
On Tuesday, December 03, 2013 20:55:19 Mark Gaiser wrote:
On Dec. 3, 2013, 8:49 p.m., Sebastian Kügler wrote:
I really like the idea. I think we should keep our Scroll* components in
to ease porting, but move away from using it for our own stuff first,
and then, before a first API
23 matches
Mail list logo
