Re: [RFC] Plasma mobile components -> Plasma controls
On Monday, February 8, 2016 1:21:01 PM CET Marco Martin wrote: > Hi all, > > It's almost time to make the plasma mobile components a framework/repository > by itself, and with that I'm wondering of "plasma mobile components" it's > even the proper name after all. > > Following the Qt naming conventions i was going for "Plasma Controls" where > "Plasma" is there purely for branding, but not as "dependency" (at least can > be disabled at build time) and that is not reall "mobile" specific. There > are things that aren't really "mobile" , like colors and listviews.. one > could use pieces of them in desktop apps and plasmoids as well, as long as > doesn't use the really mobile specific parts. > > so a name should be: > * Exprime that it's something "extra", it's not the "buttons and textboxes" > of QQC1/2 > * Exprime that is ours (would go for Plasma instead of KDE for the usual KDE > is people) > * I wouldn't stress too much on it being "mobile" > > Opinions? comments? Plasma is the brand for the "Desktop Shell". Why use Plasma as the name for the components, then? Isn't that going to be confusing for devs. Like the assumption that you need Plasma or it's only for Plasma? Kind of introducing the same problems as we used to have with the generic KDE name? 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
[RFC] Plasma mobile components -> Plasma controls
Hi all, It's almost time to make the plasma mobile components a framework/repository by itself, and with that I'm wondering of "plasma mobile components" it's even the proper name after all. Following the Qt naming conventions i was going for "Plasma Controls" where "Plasma" is there purely for branding, but not as "dependency" (at least can be disabled at build time) and that is not reall "mobile" specific. There are things that aren't really "mobile" , like colors and listviews.. one could use pieces of them in desktop apps and plasmoids as well, as long as doesn't use the really mobile specific parts. so a name should be: * Exprime that it's something "extra", it's not the "buttons and textboxes" of QQC1/2 * Exprime that is ours (would go for Plasma instead of KDE for the usual KDE is people) * I wouldn't stress too much on it being "mobile" Opinions? comments? -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [RFC] Plasma mobile components -> Plasma controls
On Monday, February 8, 2016 4:07:35 PM CET Marco Martin wrote: > On Monday 08 February 2016, Martin Graesslin wrote: > > Plasma is the brand for the "Desktop Shell". Why use Plasma as the name > > for > > the components, then? Isn't that going to be confusing for devs. Like the > > assumption that you need Plasma or it's only for Plasma? Kind of > > introducing the same problems as we used to have with the generic KDE > > name? > > perhaps... > what i was thinking about is that we have this work tightly coupled together > the HIG work. > That's pretty much the pack of things that google calls "Material design" > (blackberry had cascades, microsoft could have metro but fucked up, apple > doesn't seem to have a name) > > "Breeze Design" wouldn't go i think, because is more just a theme, we > probably need an hip name for the components, and general design/hig of > applications. > > We could call it something high brow like "Flow" or some bs like that maybe something for the VDG to come up with a good name, otherwise I vote for "Bikeshed Controls" :-P But yeah, if it goes into a tier 1 framework it makes sense to do a generic "hip" name. 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: [RFC] Plasma mobile components -> Plasma controls
On Monday 08 February 2016, Martin Graesslin wrote: > > Plasma is the brand for the "Desktop Shell". Why use Plasma as the name for > the components, then? Isn't that going to be confusing for devs. Like the > assumption that you need Plasma or it's only for Plasma? Kind of > introducing the same problems as we used to have with the generic KDE > name? perhaps... what i was thinking about is that we have this work tightly coupled together the HIG work. That's pretty much the pack of things that google calls "Material design" (blackberry had cascades, microsoft could have metro but fucked up, apple doesn't seem to have a name) "Breeze Design" wouldn't go i think, because is more just a theme, we probably need an hip name for the components, and general design/hig of applications. We could call it something high brow like "Flow" or some bs like that -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
