Re: KDE architecture diagram

2012-06-07 Thread Dario Freddi
Hey, first of all thanks for caring :)

Well it looks quite close to the status quo imho, but it occurred to
me we have indeed a serious naming problem (which I believe was the
main source of misunderstanding over the last days) on all of this. In
my opinion the diagram makes more sense when s/Workspace/Desktop. I
see more the concept of workspaces, aka desktop, mobile, tablet
etc...

Another thing is that we have way too many names: software
compilation, active, workspace, etc... I mean if we, the people
working on that, are confused, how could a user feel?

I guess a goal for the next sprint should indeed be starting from
something like this and drawing a scenario, also in a marketing
perspective.

2012/6/7 Aurélien Gâteau agat...@kde.org:
 Hi,

 Spent some time yesterday evening on drawing a diagram of KDE architecture, as
 I proposed in an other thread. Please have a look and tell me what's wrong in
 it.

 Aurélien
 ___
 Plasma-devel mailing list
 Plasma-devel@kde.org
 https://mail.kde.org/mailman/listinfo/plasma-devel

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: KDE architecture diagram

2012-06-07 Thread Aaron J. Seigo
On Thursday, June 7, 2012 13:47:06 Dario Freddi wrote:
 Well it looks quite close to the status quo imho,

i think it reflects the understanding many have, yes.

 but it occurred to
 me we have indeed a serious naming problem (which I believe was the
 main source of misunderstanding over the last days) on all of this. In
 my opinion the diagram makes more sense when s/Workspace/Desktop. I
 see more the concept of workspaces, aka desktop, mobile, tablet
 etc...

calling it desktop fails for various reasons (all of which have been 
discussed extensively elsewhere in past years):

* we have the legacy of desktop both in KDE and the KDE Desktop
* a t.v. recorder is not a desktop. we might be able to grin and say that 
tablet is running a desktop system, but that is even a bit of a stretch.

that said .. there are certainly bigger issues than this we have to in front 
of us to tackle to bring our efforts into sync.

 I guess a goal for the next sprint should indeed be starting from
 something like this and drawing a scenario, also in a marketing
 perspective.

there will be enough on the agenda without adding marketing to it, and there 
are many people not there who ought to be if marketing was part of the mix.

-1

-- 
Aaron J. Seigo

signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: KDE architecture diagram

2012-06-07 Thread Aaron J. Seigo
On Thursday, June 7, 2012 09:31:08 Aurélien Gâteau wrote:
 Spent some time yesterday evening on drawing a diagram of KDE architecture,
 as I proposed in an other thread. Please have a look and tell me what's
 wrong in it.

thanks for taking the time to do this.

it certainly helps me understand some of the confusion. the diagram is a set
of interlocking, overlapping boxes with no apparent structure. there's no
thematic nature in the boxes or their intersections. it looks confused and
muddled. it looks nothing like the thing i know, however :)

there's an artificial spliting between kde workspace and plasma active that
does not exist. those of us working on these things keep saying that but
nobody seems to either be listening to or believing us :)

in the diagram, plasma active contains an operating system and intersects
(some) applications. i'm happy on the one hand because that means that the
user message has come across clear - it's an attempt to bring a coherent
approach to this area. and so the OS and the UX and the apps all need
harmonize with each other.

it also reflects the people structure in many ways. in fact, i'd say this is a
more accurate documentation of who has worked on what than what the technical
design is :)

these are all not bad things. but they are not overly useful when we are
trying to have technical discussions about the technical design of the
software.

i will try to come up with something that reflects my knowledge of the system
in time for the sprint. i can probably start with a diagram that sebas and i
did up a couple years ago 

--
Aaron J. Seigo

signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Re: KDE architecture diagram

2012-06-07 Thread Martin Gräßlin
On Thursday 07 June 2012 21:11:09 Aaron J. Seigo wrote:
 there's an artificial spliting between kde workspace and plasma active
 that does not exist. those of us working on these things keep saying that
 but nobody seems to either be listening to or believing us :)
and I think here we have found the root cause of the discussions the last 
days: there seems to be a misconception in what active is from the view of the 
developers and from how it is seen from outside. Personally I have to put 
myself to the outside as I also see active as something not belonging to the 
other desktops box. I would even split kwin in the diagram in a kwin desktop 
and a kwin active.

Given that it's great that we have the sprint the next week to discuss that. 
Something went wrong over the last year. We need to figure out what, why and 
how to fix it.

Cheers
Martin

signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: KDE architecture diagram

2012-06-07 Thread Aurélien Gâteau
Le jeudi 7 juin 2012 21:11:09 Aaron J. Seigo a écrit :
 there's an artificial spliting between kde workspace and plasma active
 that does not exist. those of us working on these things keep saying that
 but nobody seems to either be listening to or believing us :)

If I am not mistaken, kde workspace and plasma active are developed in 
different repositories, have different release schedules and target different 
devices. That was enough for me to split them.

 i will try to come up with something that reflects my knowledge of the
 system in time for the sprint. i can probably start with a diagram that
 sebas and i did up a couple years ago 

That would be great.

Aurélien
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Mouse wheel on Slider QML component

2012-06-07 Thread Viranch Mehta
Hi,

I wanted to know if the Slider (from QML components) can be moved
using the mouse wheels. If not, is it possible to implement it atm?

Thanks,
Viranch
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Mouse wheel on Slider QML component

2012-06-07 Thread David Edmundson
On Thu, Jun 7, 2012 at 9:51 PM, Viranch Mehta viranch.me...@gmail.com wrote:
 Hi,

 I wanted to know if the Slider (from QML components) can be moved
 using the mouse wheels. If not, is it possible to implement it atm?

Qt 4.x does not have a wheel event on MouseArea therefore it's not
possible to fix Slider in Components.

Qt5 does.
We could make our own Plasma.Extras.MouseArea which is just a subclass
of qdeclarativemousearea with the new code.. it's quite an important
feature to match QWidgets parity, but I don't know if it's worth it.

Dave

 Thanks,
 Viranch

 ___
 Plasma-devel mailing list
 Plasma-devel@kde.org
 https://mail.kde.org/mailman/listinfo/plasma-devel

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Review Request: Fix text colors on TabButton and ToolButton

2012-06-07 Thread David Edmundson

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105163/#review14504
---

Ship it!


Ship It!

- David Edmundson


On June 6, 2012, 2:28 p.m., Aurélien Gâteau wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 http://git.reviewboard.kde.org/r/105163/
 ---
 
 (Updated June 6, 2012, 2:28 p.m.)
 
 
 Review request for Plasma.
 
 
 Description
 ---
 
 When the widgets use the button background frame, use buttonTextColor. When 
 they do not use any background frame, use textColor.
 This avoids unreadable text with Oxygen, as visible on screenshots.
 
 
 Diffs
 -
 
   
 plasma/declarativeimports/plasmacomponents/platformcomponents/touch/ToolButton.qml
  71629fc 
   plasma/declarativeimports/plasmacomponents/qml/TabButton.qml 0131b12 
   plasma/declarativeimports/plasmacomponents/qml/ToolButton.qml a10e0bf 
 
 Diff: http://git.reviewboard.kde.org/r/105163/diff/
 
 
 Testing
 ---
 
 Run Plasma widget gallery, before and after the patch.
 
 
 Screenshots
 ---
 
 before
   http://git.reviewboard.kde.org/r/105163/s/598/
 after
   http://git.reviewboard.kde.org/r/105163/s/599/
 
 
 Thanks,
 
 Aurélien Gâteau
 


___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel