Re: Notes from "Async and representation"

On Saturday 18 January 2014 01:11:54 Mark Gaiser wrote: > > I guess my arguments for going with the "Plasmoid" name rather then > "Applet" are just ignored then? > Sebas did gave "some" (few lines) explanation before my bunch of > arguments. Yet i still think "Plasmoid" would suit it better. I th

Re: Notes from "Async and representation"

On Saturday 18 January 2014 01:11:54 Mark Gaiser wrote: > I guess my arguments for going with the "Plasmoid" name rather then > "Applet" are just ignored then? Mark, I doubt Marco meant any disrespect; discussing the name just isn't really a priority while we're trying to work out the semantics. K

Re: Notes from "Async and representation"

On Fri, Jan 17, 2014 at 9:25 PM, Marco Martin wrote: > On Friday 17 January 2014, Marco Martin wrote: >> Applet { >> >> compactRepresentation: Component { >> PlasmaComponents.Button { >> text: i18n("Click me") >> onClicked: plasmoid.expanded = !plasmoid.expanded

Re: [kde-promo] Plasma Next Naming

On Fri, Jan 17, 2014 at 11:24 PM, Martin Klapetek wrote: > On Fri, Jan 17, 2014 at 10:18 PM, Martin Graesslin wrote: > >> >> It looks like the discussion split. There is no mail by Aaron on the >> plasma >> mailing list. Could someone please forward the mails so that it is >> possible to >> follo

Re: [kde-promo] Plasma Next Naming

I would just like to respond to one point (and related) as the rest was pretty covered by Ivan. On Fri, Jan 17, 2014 at 5:32 PM, Aaron J. Seigo wrote: > > Then again - you have Ubuntu (changing every 6 months), OS X and I > don’t > > > > know what elseand using an animal (weird ones in Ubu

Re: [kde-promo] Plasma Next Naming

On Fri, Jan 17, 2014 at 10:18 PM, Martin Graesslin wrote: > > It looks like the discussion split. There is no mail by Aaron on the plasma > mailing list. Could someone please forward the mails so that it is > possible to > follow the discussion and to add value to the discussion. > > Especially I'

Re: [kde-promo] Plasma Next Naming

On Friday 17 January 2014 22:08:36 Jos Poortvliet wrote: > On Tuesday 14 January 2014 20:18:17 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 t

Re: Systemtray breakout notes

On Friday 17 January 2014 22:02:35 Marco Martin wrote: > On Friday 17 January 2014, Martin Graesslin wrote: > > > icon, and window icons can further contain their own stateful in- > > > formation of their own (e.g. some drawing apps put a thumbnail of > > > the current document in there

Re: [kde-promo] Plasma Next Naming

On Tuesday 14 January 2014 20:18:17 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 > thes

Re: Systemtray breakout notes

On Friday 17 January 2014, Martin Graesslin wrote: > > icon, and window icons can further contain their own stateful in- > > formation of their own (e.g. some drawing apps put a thumbnail of > > the current document in there), so there can be contention between > > the two. > > We

Re: Systemtray breakout notes

On Friday 17 January 2014 16:22:34 Eike Hein wrote: > On Friday 17 January 2014 10:23:48 Martin Klapetek wrote: > > On Thu, Jan 16, 2014 at 6:01 PM, Sebastian Kügler wrote: > > > Some applications nest in the systemtray, and appear in both taskbar and > > > systemtray. We'd like to merge their ent

Re: Notes from "Async and representation"

On Friday 17 January 2014, Marco Martin wrote: > Applet { > > compactRepresentation: Component { > PlasmaComponents.Button { > text: i18n("Click me") > onClicked: plasmoid.expanded = !plasmoid.expanded > } > } > > fullRepresentation: Component {

Re: Notes from "Async and representation"

On Friday 17 January 2014, Eike Hein wrote: > General comment: Please note that these size hints aren't only > there so the shell can decide which representation to pick, but > at times also do things like: > > * Set useful default sizes (e.g. for popups from panels) *before* > appearance. > * A

Re: Notes from "KRunner Breakout"

On Friday 17 January 2014 18:47:09 Vishesh Handa wrote: > The only big change that I can see coming is the conversion of RunnerManager > into a model. For Homerun, it needs to be able to either: * Get individual runner's results as a model with low overhead. or * Be able to filter a single glob

Re: Notes from "KRunner Breakout"

On Friday 17 January 2014 16:32:18 Eike Hein wrote: > On Thursday 16 January 2014 21:15:02 Vishesh Handa wrote: > > * Runner Library needs a certain amount of work > > - Add item type capabilities to the results > > - Add preview capabilities > > - Refactor so that async runners do not need to spaw

Re: Notes from "Async and representation"

General comment: Please note that these size hints aren't only there so the shell can decide which representation to pick, but at times also do things like: * Set useful default sizes (e.g. for popups from panels) *before* appearance. * Affect interaction behavior (e.g. lock down resizing in on

Re: Systemtray breakout notes

On Friday 17 January 2014, Mark Gaiser wrote: > On Fri, Jan 17, 2014 at 11:51 AM, Marco Martin wrote: > > On Friday 17 January 2014, Martin Klapetek wrote: > >> I think this raises another question though - if you add any applet on > >> the panel, will it also share the systray popup? And if not,

Re: [Development] Qt Quick Controls Calendar

On 12/06/2013 02:02 PM, Mitch Curtis wrote: Hello. At the beginning of this year I started work on a Calendar for Qt Quick Controls as a sort of side project. After removing the "WIP" from the commit message, I got some feedback from developers who either a) had also wrote a Calendar for KDE stu

Re: Error(Cmake) while building PMC

Run these two commands and you should be ok- sudo apt-get install libdeclarative-multimedia kbuildsycoca4 Also, I'm surprised that it compiled on 12.04, can you tell me the output of the command "lsb_release -a" on that machine? On Fri, Jan 17, 2014 at 8:39 PM, R.Harish Navnit wrote: > Here is

Re: Notes from "KRunner Breakout"

On Thursday 16 January 2014 21:15:02 Vishesh Handa wrote: > * Runner Library needs a certain amount of work > - Add item type capabilities to the results > - Add preview capabilities > - Refactor so that async runners do not need to spawn an event loop and > block Do you expect the API will stay i

Re: Error(Cmake) while building PMC

Wow ! It works . I never thought it would be possible too . It's been a week or two now since I started building this . The "lsb_release-a" gives the output log : http://pastebin.kde.org/p4v5s1srq #FeelingGreat now :) R.Harish Navnit The Enigma On Fri, Jan 1

Re: Systemtray breakout notes

On Friday, January 17, 2014 11:02:14 Kevin Krammer wrote: > On Friday, 2014-01-17, 10:27:13, Djuro Drljaca wrote: > > what about a separate component just for XEmbed? This would solve the > > modern systray dependency problems and the users that really need XEmbed > > could just add XEmbed systray

Re: Systemtray breakout notes

On Friday 17 January 2014 10:23:48 Martin Klapetek wrote: > On Thu, Jan 16, 2014 at 6:01 PM, Sebastian Kügler wrote: > > Some applications nest in the systemtray, and appear in both taskbar and > > systemtray. We'd like to merge their entries. Example: Kmail's taskbar > > item > > could show the n

Need new Plasma monochrome icons

Hi Jens, I'm working on the new OSD for Plasma and I need some new, currently non-existing monochrome icons, would you have some time to draft some? These should be just two icons - one depicting the screen brightness and one depicting a keyboard or keyboard layout. These will be used when the re

Re: Error(Cmake) while building PMC

Here is the output log : http://pastebin.kde.org/pynlrphur when I run 'plasma-mediacenter' . Sorry for the random and unorganized emails . Regards. R.Harish Navnit The Enigma On Fri, Jan 17, 2014 at 8:33 PM, R.Harish Navnit wrote: > > > R.Harish Navnit > Th

Re: Error(Cmake) while building PMC

R.Harish Navnit The Enigma On Fri, Jan 17, 2014 at 8:29 PM, R.Harish Navnit wrote: > I ran make and make install , and I think it went okay . I couldn't spot > any errors , as output log was just too lengthy(sorry about being careless > here :P). > So , assumi

Re: Error(Cmake) while building PMC

I ran make and make install , and I think it went okay . I couldn't spot any errors , as output log was just too lengthy(sorry about being careless here :P). So , assuming the build was successful , how do I now run this ? Regards. ___ Plasma-devel maili

Re: Error(Cmake) while building PMC

Most probably you will encounter errors when you run make (but give it a try anyway? It doesn't cost anything :P) because we use some newer Nepomuk API that was not present in the KDE that Ubuntu 12.04 ships. You will have to use 13.04 or later. On Fri, Jan 17, 2014 at 7:29 PM, R.Harish Navnit wr

Re: Error(Cmake) while building PMC

Hi again , Since I was doing a fresh install of kubuntu 13.10 on Vbox and it's taking a long while , I thought of running cmake on my Ubuntu 12.04 LTS lab systems . I think the cmake is almost done , I had a few warnings however . Should I ignore it and proceed with make ? Here's th

Re: Systemtray breakout notes

> That's just fine. We can try making the default perfect and provide the best > possible default experience. Users do not have to use the default, but they > don't need to expect the same experience when moving away from the > defaults. I really think this can't be said enough - as long as the

Re: Re: Systemtray breakout notes

On Friday 17 January 2014 14:31:56 Mark Gaiser wrote: > On Fri, Jan 17, 2014 at 11:51 AM, Marco Martin wrote: > > On Friday 17 January 2014, Martin Klapetek wrote: > >> I think this raises another question though - if you add any applet on > >> the > >> panel, will it also share the systray popup?

Re: Systemtray breakout notes

On Fri, Jan 17, 2014 at 11:51 AM, Marco Martin wrote: > On Friday 17 January 2014, Martin Klapetek wrote: > >> I think this raises another question though - if you add any applet on the >> panel, will it also share the systray popup? And if not, which I really >> think it should not, then the cale

Re: Error(Cmake) while building PMC

And here's what "cat .xsession-errors" shows me : "Script for cjkv started at run_im Script for default started at default at run_im" I have no idea what it means . I also fiddled with my lightdm.conf , I changed the greeter-session to "unity-greeter". I think I can afford a fresh install since

Re: Error(Cmake) while building PMC

On Thu, Jan 16, 2014 at 9:43 PM, Shantanu Tushar Jha wrote: > Ah, I'm not talking about RAM, I'm asking about how much virtual hard disk > space you allocated to the VM. > Virtual Hard disk space : 21.38GB Actual Size : 6.35GB > > (Also, with just 4 gigs of RAM, development on a VM might be prett

Re: Systemtray breakout notes

On Friday 17 January 2014, Martin Klapetek wrote: > I think this raises another question though - if you add any applet on the > panel, will it also share the systray popup? And if not, which I really > think it should not, then the calendar should stay its own popup because > it's not part of the

Re: Notes from "KRunner Breakout"

On Thursday 16 January 2014, Àlex Fiestas wrote: > One missing point, it will be possible to change the interface of Milou, so > if somebody wants to write a task oriented GUI (old katapoult was > mentioned) it will a matter of throwing some QMl files :p would be nice if it has the package structu

Re: Systemtray breakout notes

On Thursday 16 January 2014, Sebastian Kügler wrote: > Hey, > > During the sprint here in Barcelona, we've talked about the rework of the > notification area / systemtray and had a critical look at its concept and > direction. I've extracted some notes from it, which I plan to address in > the com

Re: Systemtray breakout notes

On Friday, 2014-01-17, 10:27:13, Djuro Drljaca wrote: > Hello, > > what about a separate component just for XEmbed? This would solve the > modern systray dependency problems and the users that really need XEmbed > could just add XEmbed systray component next to the modern systray > component. > >

Re: Systemtray breakout notes

Hello, what about a separate component just for XEmbed? This would solve the modern systray dependency problems and the users that really need XEmbed could just add XEmbed systray component next to the modern systray component. I know this would be ugly, but it might be a good compromise... Rega

Re: Re: Systemtray breakout notes

On Friday 17 January 2014 10:20:24 Martin Klapetek wrote: > I think this is also a way to send a message to those apps still using > XEmbed - "your [systray] stuff is old and crap, use some 21st century tech, > if you're not willing to, we're not willing to keep supporting your old > stuff" (hello

Re: Systemtray breakout notes

On Thu, Jan 16, 2014 at 6:01 PM, Sebastian Kügler wrote: > > Some applications nest in the systemtray, and appear in both taskbar and > systemtray. We'd like to merge their entries. Example: Kmail's taskbar item > could show the number of unread emails as an overlay, instead of having a > separat

Re: Systemtray breakout notes

On Thu, Jan 16, 2014 at 8:33 PM, Mark Gaiser wrote: > > > Seriously, have you looked at the protocol? Have you looked at the > > implementations that would be possible? It's easy to say "I want that", > but > > that ignores the whole decision space for this. It's impossible to > integrate > > it,

Re: Systemtray breakout notes

On Thu, Jan 16, 2014 at 8:09 PM, Sebastian Kügler wrote: > On Thursday, January 16, 2014 19:38:30 Mark Gaiser wrote: > > On Thu, Jan 16, 2014 at 6:01 PM, Sebastian Kügler wrote: > > > - the calendar should move into the systray popup > > > > Why? > > Same reason for moving all the others into th

Re: Notes from "KRunner Breakout"

On Thu, Jan 16, 2014 at 9:15 PM, Vishesh Handa wrote: > - Session Switching - Move to KSMServer > Isn't KSMServer going away? In which case it can be moved anywhere of course, just checking ;) Cheers -- Martin Klapetek | KDE Developer ___ Plasma-deve