Re: Notes from "Async and representation"

Code comment: Make sure you default m_minimumWidth and the others to something in the ctor and check your usage of width when you mean height :) It might be a good idea to have a default property of type QmlListProperty so that Applets can have child objects in the QML for all their models/shared

Re: [kde-promo] Plasma Next Naming

On Tuesday, January 14, 2014 15:41:27 Carl Symons wrote: > I like the marine animal/fish metaphor. Prolly don't need much promo > domain expertise to come up with the name. I was thinking about domain expertise in the underwater department, and I'm offering my help. :) -- sebas http://www.kde.

Re: [kde-promo] Plasma Next Naming

On 01/14/2014 11:18 AM, Sebastian Kügler wrote: Hey, Until now, we've been using "Plasma 2" as a working title for the next version of Plasma. We never formalized this, and the last discussion we had about this died out without producing a clear result. We've gone over these points during the sp

Re: Notes from "Async and representation"

On Wednesday 15 January 2014 00:01:35 Mark Gaiser wrote: > Hi Marco, First, to be clear is not *my* proposal per se, is the proposal we came up at the sprint. > So if i get it right you propose that every plasmoid - in QML - will > at the very least have this: > > Item { > > Applet { > m

Re: QML Calendar stuff

On Wed, Jan 15, 2014 at 12:09 AM, Mark Gaiser wrote: > > Just events? No todo, journal and holiday? > Or is "everything" a "event"? > Yes, everything is an event which has a type property, which can be todo, journal or holiday (or whatever). Cheers -- Martin Klapetek | KDE Developer __

Re: Notes from session "Community Health"

On Wed, Jan 15, 2014 at 12:07 AM, Mark Gaiser wrote: > > Solid and not set in stone. Weird kind of solid plan ;) > Solid as in "good and as much complete as possible" and not set in stone as in "open for changes/input" ;) Cheers -- Martin Klapetek | KDE Developer __

Re: QML Calendar stuff

On Mon, Jan 13, 2014 at 11:40 AM, Martin Klapetek wrote: > Hi, > > at the Plasma sprint we discussed the next-gen calendar plasmoid, we had > Mitch from Digia here, who is working on QtQuickControls calendar stuff. > > The idea is to share as much code as possible between our plasmoid and > upstre

Re: Notes from session "Community Health"

On Tue, Jan 14, 2014 at 8:30 PM, David Edmundson wrote: > There was a nice phrase that someone used during the sprint which I > think is very relevant. > > The goal of each discussion is to come up with 'finished blueprints' > for each topic. > A solid plan, but not set in stone. Solid and not se

Re: Notes from "Async and representation"

On Tue, Jan 14, 2014 at 8:14 PM, Marco Martin wrote: > Hi all, > those are some notes in a probable API change that will probably happen (let's > discuss!) on how QML plasmoids are written. > > The problem: > * plasmoids needs some properties in the root object, such as minimumWidth, > maximumWidt

Re: Notes from "Async and representation"

On Tuesday 14 January 2014 20:14:55 you wrote: > * everything that needs to always exist is stuff like model and dataengines > (therefore not graphical) this will have to be child of the root Applet > item. (another proposal was to make another property that contains it) > * another thing i was th

Re: System Tray

On Monday, January 13, 2014 14:01:52 DmitriyBoyko . wrote: > I can't install systemtray2 (the one generated by Plasmate) widget on my > system, it simply says that it failed (where to look for log?) One more thing: Right now, it doesn't make much sense to do any patches without talking to me firs

Re: [kde-promo] Plasma Next Naming

> "KDE releases the January Update to the October 2014 release of Plasma" > "October 2014, january update" This is a mouthful, and even more, quite confusing. While I like the month/year idea (duh:)), this is kinda breaking the aims we previously defined. Cheerio, Ivan __

Re: Review Request 115004: use KDeclarative namespace for kdeclarative framework classes

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/115004/#review47415 --- This review has been submitted with commit 96e4a9705b51e129d7

Re: Review Request 115004: use KDeclarative namespace for kdeclarative framework classes

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/115004/ --- (Updated Jan. 14, 2014, 10:31 p.m.) Status -- This change has been m

Re: [kde-promo] Plasma Next Naming

On Tuesday 14 January 2014 21:07:57 Martin Graesslin wrote: > > I.e. as a user may want to see if the new release i'm going to install is > > a > > bugfix release (i.e. i'm going from 4.12.0 to 4.12.1) or if it is a new > > feature release (i.e. i'm going from 4.12.0 to 4.13.0). > > "KDE releases

Re: System Tray

Hello, On 13 January 2014 14:01, DmitriyBoyko . wrote: > > I am using vertial task bar and I think that it would look better if icons > were not so big (please see attahed file). > if you have a patch please submit it to git.reviewboard.kde.org > I can't install systemtray2 (the one generated

Re: System Tray

Hi, You are really working on it :) I can see that in the 4.12 version of KDE that triangle became much smaller :) So no need for picture now... 2014/1/14 Martin Klapetek > Hey, > > On Mon, Jan 13, 2014 at 1:01 PM, DmitriyBoyko . > wrote: > >> Hi all, >> Writing here as Sebastian Kugler asked

Re: [kde-promo] Plasma Next Naming

On Tuesday 14 January 2014 20:34:15 Albert Astals Cid wrote: > El Dimarts, 14 de gener de 2014, a les 20:18:17, Sebastian Kügler va escriure: > > Hey, > > > > Until now, we've been using "Plasma 2" as a working title for the next > > version of Plasma. We never formalized this, and the last discu

Re: System Tray

Hey, On Mon, Jan 13, 2014 at 1:01 PM, DmitriyBoyko . wrote: > Hi all, > Writing here as Sebastian Kugler asked to do so. > I am using vertial task bar and I think that it would look better if icons > were not so big (please see attahed file). > You seem to forget the file :) > I also want to m

Re: [kde-promo] Plasma Next Naming

El Dimarts, 14 de gener de 2014, a les 20:18:17, Sebastian Kügler va escriure: > Hey, > > Until now, we've been using "Plasma 2" as a working title for the next > version of Plasma. We never formalized this, and the last discussion we had > about this died out without producing a clear result. We'

Re: Notes from session "Community Health"

There was a nice phrase that someone used during the sprint which I think is very relevant. The goal of each discussion is to come up with 'finished blueprints' for each topic. A solid plan, but not set in stone. David ___ Plasma-devel mailing list Plas

Re: System Tray

Hi all, Writing here as Sebastian Kugler asked to do so. I am using vertial task bar and I think that it would look better if icons were not so big (please see attahed file). I also want to move triangle (that shows all programs running) in the row with programs if there is enough space on the pane

Re: Notes from session "Community Health"

On Tuesday 14 January 2014 11:46:11 David Edmundson wrote: > Right now we have a situation that some people are afraid of posting > to the list, every discussion escalates into an argument, and this > stops us working effectively. I just want to note one thing: most of the threads "notes from..."

Plasma Next Naming

Hey, Until now, we've been using "Plasma 2" as a working title for the next version of Plasma. We never formalized this, and the last discussion we had about this died out without producing a clear result. We've gone over these points during the sprint, and discussed some details about it. Som

Notes from "Async and representation"

Hi all, those are some notes in a probable API change that will probably happen (let's discuss!) on how QML plasmoids are written. The problem: * plasmoids needs some properties in the root object, such as minimumWidth, maximumWidth, compactRepresentation.. * the user has to declare *and* implem

Re: Review Request 114932: Use QExplicitlySharedDataPointer as the replacement of KSharedPtr

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/114932/ --- (Updated Jan. 14, 2014, 6:41 p.m.) Status -- This change has been ma

Re: Review Request 114932: Use QExplicitlySharedDataPointer as the replacement of KSharedPtr

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/114932/#review47389 --- This review has been submitted with commit afe17f1dca77ac6afd

Re: Error(Cmake) while building PMC

On Tue, Jan 14, 2014 at 7:57 PM, R.Harish Navnit wrote: > omg! You got some stuff messed up. It is weird why you have Qt5 >> development headers installed, do you remember installing it? >> > > Yes , it sure looks messed up ! I remember installing a lot of packages > while building digikam(which a

Re: Error(Cmake) while building PMC

> If its not too much pain, can you create a new VM for 13.10 and try > building PMC before doing anything else? > Right now the only trouble is in getting the ISO and then running the installations . Will 2-3 hours I guess :P But I'll do it nevertheless . Infact I think I'll remove the Ubuntu 13.

Re: Error(Cmake) while building PMC

On Tue, Jan 14, 2014 at 7:57 PM, R.Harish Navnit wrote: > omg! You got some stuff messed up. It is weird why you have Qt5 >> development headers installed, do you remember installing it? >> > > Yes , it sure looks messed up ! I remember installing a lot of packages > while building digikam(which a

Re: Error(Cmake) while building PMC

> > omg! You got some stuff messed up. It is weird why you have Qt5 > development headers installed, do you remember installing it? > Yes , it sure looks messed up ! I remember installing a lot of packages while building digikam(which also failed :( ) I think that could be the reason behind this.

Re: Error(Cmake) while building PMC

omg! You got some stuff messed up. It is weird why you have Qt5 development headers installed, do you remember installing it? I'm asking this because compiling PMC from source is a piece of cake and unless there is something screwed up, you shouldn't me having so many issues. To make sure I just c

Re: Review Request 114932: Use QExplicitlySharedDataPointer as the replacement of KSharedPtr

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/114932/#review47363 --- Ship it! OK, go for it then. - Aurélien Gâteau On Jan. 9,

Re: Error(Cmake) while building PMC

This is the output log when I don't add what was mentioned to the cmake command : http://pastebin.kde.org/px9ek7w4q Regards. R.Harish Navnit The Enigma On Tue, Jan 14, 2014 at 6:53 PM, R.Harish Navnit wrote: > I tried removing Qt 5.1 and then running the com

Re: Error(Cmake) while building PMC

I tried removing Qt 5.1 and then running the command again , and again I get an error ! This is the output log : http://pastebin.kde.org/pe9gqepue Moreover did I type the command correctly ? Regards. R.Harish Navnit The Enigma On Tue, Jan 14, 2014 at 6:26 PM

Re: Error(Cmake) while building PMC

On Tue, Jan 14, 2014 at 4:06 PM, R.Harish Navnit wrote: > Okay now I've been trying the build on my Ubuntu 13.04 with KDE plasma > Workspace(It now shows Kubuntu on boot) . > This is the error log that I get : http://pastebin.kde.org/pee7kzjwx > By looking into error message, issue is most proba

Re: Error(Cmake) while building PMC

I tried running the cmake adding what you mentioned to your reply . I tried more than one permutations of the same command . Here are the output logs of each of those [1] http://pastebin.kde.org/puwvvc97e [2] http://pastebin.kde.org/pooahzown [3] http://pastebin.kde.org/p1dztqlc9 Am I doing it ri

Re: Error(Cmake) while building PMC

Try adding this to your cmake command line- -DQT_QT_INCLUDE_DIR=/usr/include/qt4/Qt Usually cmake should autodetect that, but lets see if this works. On Tue, Jan 14, 2014 at 5:07 PM, R.Harish Navnit wrote: > Yes , I just checked again using "dpkg -s" each of the package names > mentioned in th

Re: Error(Cmake) while building PMC

Yes , I just checked again using "dpkg -s" each of the package names mentioned in the blog . I believe I have installed all the packages listed under the ubuntu section in the blog . I still keep getting these error-messages . R.Harish Navnit The Enigma On T

Re: Error(Cmake) while building PMC

Are you following all the steps as listed at http://sinny.in/node/25 (Under ubuntu section) ? This error means that you probably missed installing one of those packages. On Tue, Jan 14, 2014 at 4:06 PM, R.Harish Navnit wrote: > Okay now I've been trying the build on my Ubuntu 13.04 with KDE plas

Notes from session "Community Health"

Right now we have a situation that some people are afraid of posting to the list, every discussion escalates into an argument, and this stops us working effectively. All the issues come down to a lack of trust. ==Actions== We must all: - assume everyone means well with their involvement - read

Re: Error(Cmake) while building PMC

Okay now I've been trying the build on my Ubuntu 13.04 with KDE plasma Workspace(It now shows Kubuntu on boot) . This is the error log that I get : http://pastebin.kde.org/pee7kzjwx I've tried googling for the error and I even got a lot of answers , but I couldn't really understand much of what wa

Re: Error(Cmake) while building PMC

There's one more issue on which I'd like some clarification. I have Ubuntu 13.04 installed on my laptop . I later on installed KDE plasma workspace on my system using some terminal commands . I then again ran updates/security updates using the package manager . Now ofcourse , I can select the sessi

Re: Error(Cmake) while building PMC

The easy solution is, upgrade to/install Kubuntu 13.10 (recommended). From > what I see, you are using a VM so you could just create another one with a > newer version. > Isn't there anything else that can be done with the current O.S ? I don't have the ISO image and then installation will take eve