Re: Plasma Addons
On Saturday 24 May 2014 16:51:49 David Edmundson wrote: > KDE 3.x had a clock with 5 pages of config tabs. It was not a great system. > > I don't think there's much wrong with doing one thing and doing it > well. Swappable small parts iis what plasma does well. Exactly! That's why I suggested (and Marco said it was doable, although not for the first release) to provide an easy way to switch between different Plasmoids for the same tasks (e.g. the clock). See here for details: http://sessellift.wordpress.com/2014/02/06/leveraging-the-power-of-choice/ I won't stop bugging the Plasma team until that feature is implemented ;) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Plasma Package -> Application Extension Framework?
Hi folks, first please apologize if this is already under way or done and I am just not up to date enough :-) Basically I was thinking about application scripting, allowing power users, sysadmins, etc. to control or extend applications through built-in scripting capabilities. A couple of KDE applications do that already, e.g. Kate, but it is not a very common features. So my base line of thinking was that maybe we can help application developers by having common code and tools available as a framework. One of the features that would likely be interesting to most application developers is how to handle installation and runtime detection of available scripts. Since I remembered reading about some form of packaging being developed for Plasma years ago I went to TechBase and read up a bit on Plasma Package. What are your opinions on having that in a generic "app extension" framework? Are there any Plasma specific dependencies in the current code? Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring 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: Plasma Addons
On Saturday 24 May 2014, Tomaz Canabrava wrote: > From my just user perspective since I don't write any plasmoids nor > plasma tech for a long thile, there are a few 'clocks' that should > just disappear. Fuzzy, Binary, Digital and Analog should be merged > together and plasma should have just one clock, the normal instalation > has what, 5 clocks? especially when the thing is small, having different plasmoids is waaay more maintainable (not to mention less ui hell) than a single one littered with options, most of which are pretty much untested code paths -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Next visual polish feedback from VDG core folks
Great, thanks. Bug reports it is. :-) Andrew On Sat, May 24, 2014 at 8:33 AM, Eike Hein wrote: > > Feedback on visual glitches bugs is as useful as any other bug report. >> > > What's more, poor visual polish is a critical barrier to > adoption. Assuming we're of the opinion that people using > our stuff is a swell idea, we should treat the problems > as important. > > Developers tend not to because it doesn't match their own > experience of the system, or their value system, but that > doesn't mean that "I'm not using it because it looks fugly" > isn't very _real_, and often less subjective than one > might think. > > > Cheers, > Eike > > ___ > 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: Plasma Next visual polish feedback from VDG core folks
Feedback on visual glitches bugs is as useful as any other bug report. What's more, poor visual polish is a critical barrier to adoption. Assuming we're of the opinion that people using our stuff is a swell idea, we should treat the problems as important. Developers tend not to because it doesn't match their own experience of the system, or their value system, but that doesn't mean that "I'm not using it because it looks fugly" isn't very _real_, and often less subjective than one might think. Cheers, Eike ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Next visual polish feedback from VDG core folks
On Sat, May 24, 2014 at 2:21 AM, Andrew Lake wrote: > Hello all, > > I just had a quick question. If I have some feedback on areas to visually > polish up for the Plasma Next release, should I file a bug or just share > them via the email list? > Bugs. Emails get lost. Bugs don't. I think most of us are treating bugzilla as a TODO list ATM. Please help comment on any existing bugs which affect design too. > I honestly would rather just pitch in and submit review requests for patches > but, unfortunately, I just don't have the bandwidth to do that. And *really* > I hate being that guy in the peanut gallery yapping on about visuals and not > pitching in to try to fix them. But I also didn't want to just be silent if > the feedback would be useful. Feedback on visual glitches bugs is as useful as any other bug report. David ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
On Sat, May 24, 2014 at 3:32 PM, Marco Martin wrote: > On Saturday, May 24, 2014, Martin Graesslin wrote: >> I support David on this one. I think we have better ways to spend our >> development resources than to pick up some dead code and port it to QML. > > I think the best thing is to list the plasmoids there and prioritize, from > the user perspective, what is important, what is not, what should be > continued, what should be dropped ++ We'll quickly see after the first release which ones are most missed. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
On Sat, May 24, 2014 at 3:43 PM, Tomaz Canabrava wrote: > On Sat, May 24, 2014 at 10:32 AM, Marco Martin wrote: >> On Saturday, May 24, 2014, Martin Graesslin wrote: >>> I support David on this one. I think we have better ways to spend our >>> development resources than to pick up some dead code and port it to QML. >> >> I think the best thing is to list the plasmoids there and prioritize, from >> the user perspective, what is important, what is not, what should be >> continued, what should be dropped > > From my just user perspective since I don't write any plasmoids nor > plasma tech for a long thile, there are a few 'clocks' that should > just disappear. Fuzzy, Binary, Digital and Analog should be merged > together and plasma should have just one clock, the normal instalation > has what, 5 clocks? KDE 3.x had a clock with 5 pages of config tabs. It was not a great system. I don't think there's much wrong with doing one thing and doing it well. Swappable small parts iis what plasma does well. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
On Sat, May 24, 2014 at 10:32 AM, Marco Martin wrote: > On Saturday, May 24, 2014, Martin Graesslin wrote: >> I support David on this one. I think we have better ways to spend our >> development resources than to pick up some dead code and port it to QML. > > I think the best thing is to list the plasmoids there and prioritize, from > the user perspective, what is important, what is not, what should be > continued, what should be dropped >From my just user perspective since I don't write any plasmoids nor plasma tech for a long thile, there are a few 'clocks' that should just disappear. Fuzzy, Binary, Digital and Analog should be merged together and plasma should have just one clock, the normal instalation has what, 5 clocks? > > ___ > 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: Plasma Addons
On Saturday, May 24, 2014, Martin Graesslin wrote: > I support David on this one. I think we have better ways to spend our > development resources than to pick up some dead code and port it to QML. I think the best thing is to list the plasmoids there and prioritize, from the user perspective, what is important, what is not, what should be continued, what should be dropped ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
In data sabato 24 maggio 2014 14:54:02, Sebastian Kügler ha scritto: > +1 on all of the above. kdeplasma-addons is outside of our scope. Should distros tell reporters not to report bugs against kdeplasma-addons for the moment? For openSUSE I can take care of that if it is deisred. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 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: Plasma Next visual polish feedback from VDG core folks
On Saturday, May 24, 2014 12:23:54 Marco Martin wrote: > On Friday 23 May 2014 17:21:16 Andrew Lake wrote: > > I just had a quick question. If I have some feedback on areas to visually > > polish up for the Plasma Next release, should I file a bug or just share > > them via the email list? > > > > I honestly would rather just pitch in and submit review requests for > > patches but, unfortunately, I just don't have the bandwidth to do that. > > And > > *really* I hate being that guy in the peanut gallery yapping on about > > visuals and not pitching in to try to fix them. But I also didn't want to > > just be silent if the feedback would be useful. > > > > Anyway, let me know your preference. > > > > Thanks for your help and patience, > > Andrew Lake > > bugs sound good to me, maybe in a separate area? (to me it sounds to me > that "graphics issue" should be as "severity", but i don't think is > possible to add categories there in bugzilla? For now, bugs are OK. If that doesn't work, process-wise, we'll think further. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
On Saturday, May 24, 2014 08:22:24 Martin Gräßlin wrote: > On Saturday 24 May 2014 00:23:45 David Edmundson wrote: > > we've started to get bug reports on plasma-addons. It appears they're > > distributed as part of OpenSuse RPMs. > > > > Can I confirm our position on what we're doing here, based on our > > conversation last sprint. > > > > 1) They will not be released with the plasma release next month > > I think to do so would undermine the quality of anything we currently > > have. > > +1 > > > Plasma Next + 1 should be ok for any plasmoid that someone steps up to > > maintain (not just port). > > +1 > > > 2) They should have somewhere else in bugzilla than plasmashell > > +1 > > > I clean through plasma-shell every other evening, I know others do > > too, if we include everything under the sun it'll be plasma1 all over > > again. Stretched too thin. > > it will be a hard time to filter anyway. But maybe we get volunteers to pre- > filter... +1 on all of the above. kdeplasma-addons is outside of our scope. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
On Saturday 24 May 2014 12:31:26 David Edmundson wrote: > On Sat, May 24, 2014 at 12:22 PM, Marco Martin wrote: > > On Saturday 24 May 2014 00:23:45 David Edmundson wrote: > >> Hey, > >> > >> we've started to get bug reports on plasma-addons. It appears they're > >> distributed as part of OpenSuse RPMs. > >> > >> Can I confirm our position on what we're doing here, based on our > >> conversation last sprint. > >> > >> 1) They will not be released with the plasma release next month > >> I think to do so would undermine the quality of anything we currently > >> have. > >> > >> Plasma Next + 1 should be ok for any plasmoid that someone steps up to > >> maintain (not just port). > >> > >> 2) They should have somewhere else in bugzilla than plasmashell > >> > >> I clean through plasma-shell every other evening, I know others do > >> too, if we include everything under the sun it'll be plasma1 all over > >> again. Stretched too thin. > > > > yep, should be somewhere. > > > > btw,porting the complete set is kdeplasma-addons is not optional for > > future > > release, because everything that's missing will be perceived as a > > regression, no matter what we feel about it :p > > I really don't agree here. > Some of them, KDE Observatory for example, don't even work in KDE4. > > Just because someone wrote some code once 5 years ago and then > abandoned it does not make it our duty to support it. I support David on this one. I think we have better ways to spend our development resources than to pick up some dead code and port it to QML. My favorite example is IconTasks which is a huge framework on how to build a tasks applet. It copies Unity way too much that it should be something we provide and I think our development resources are better spent making the default tasks applet work kick ass (note with that I do not mean that we should merge the bazillion of options from icon tasks.). 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: Plasma Addons
On Saturday 24 May 2014 12:31:26 David Edmundson wrote: > > btw,porting the complete set is kdeplasma-addons is not optional for > > future > > release, because everything that's missing will be perceived as a > > regression, no matter what we feel about it :p > > I really don't agree here. > Some of them, KDE Observatory for example, don't even work in KDE4. > > Just because someone wrote some code once 5 years ago and then > abandoned it does not make it our duty to support it. well, yeah, the kde observatory is a bit an extreme example indeed -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
On Sat, May 24, 2014 at 12:22 PM, Marco Martin wrote: > On Saturday 24 May 2014 00:23:45 David Edmundson wrote: >> Hey, >> >> we've started to get bug reports on plasma-addons. It appears they're >> distributed as part of OpenSuse RPMs. >> >> Can I confirm our position on what we're doing here, based on our >> conversation last sprint. >> >> 1) They will not be released with the plasma release next month >> I think to do so would undermine the quality of anything we currently have. >> >> Plasma Next + 1 should be ok for any plasmoid that someone steps up to >> maintain (not just port). >> >> 2) They should have somewhere else in bugzilla than plasmashell >> >> I clean through plasma-shell every other evening, I know others do >> too, if we include everything under the sun it'll be plasma1 all over >> again. Stretched too thin. >> > > yep, should be somewhere. > > btw,porting the complete set is kdeplasma-addons is not optional for future > release, because everything that's missing will be perceived as a regression, > no matter what we feel about it :p I really don't agree here. Some of them, KDE Observatory for example, don't even work in KDE4. Just because someone wrote some code once 5 years ago and then abandoned it does not make it our duty to support it. David ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Next visual polish feedback from VDG core folks
On Friday 23 May 2014 17:21:16 Andrew Lake wrote: > Hello all, > > I just had a quick question. If I have some feedback on areas to visually > polish up for the Plasma Next release, should I file a bug or just share > them via the email list? > > I honestly would rather just pitch in and submit review requests for > patches but, unfortunately, I just don't have the bandwidth to do that. And > *really* I hate being that guy in the peanut gallery yapping on about > visuals and not pitching in to try to fix them. But I also didn't want to > just be silent if the feedback would be useful. > > Anyway, let me know your preference. > > Thanks for your help and patience, > Andrew Lake bugs sound good to me, maybe in a separate area? (to me it sounds to me that "graphics issue" should be as "severity", but i don't think is possible to add categories there in bugzilla? -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Addons
On Saturday 24 May 2014 00:23:45 David Edmundson wrote: > Hey, > > we've started to get bug reports on plasma-addons. It appears they're > distributed as part of OpenSuse RPMs. > > Can I confirm our position on what we're doing here, based on our > conversation last sprint. > > 1) They will not be released with the plasma release next month > I think to do so would undermine the quality of anything we currently have. > > Plasma Next + 1 should be ok for any plasmoid that someone steps up to > maintain (not just port). > > 2) They should have somewhere else in bugzilla than plasmashell > > I clean through plasma-shell every other evening, I know others do > too, if we include everything under the sun it'll be plasma1 all over > again. Stretched too thin. > yep, should be somewhere. btw,porting the complete set is kdeplasma-addons is not optional for future release, because everything that's missing will be perceived as a regression, no matter what we feel about it :p -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
