[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: To much QML options in KDE!
From: Mark <markg85 () gmail ! com>
Date: 2011-10-30 13:41:51
Message-ID: CAPd6JnH3tKSOOn_oh9_PNn7ZCxHC34UmFKY5ykjvM=Sw7dz-Mw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Sun, Oct 30, 2011 at 1:43 PM, Marco Martin <notmart@gmail.com> wrote:
> On Saturday 29 October 2011, Mark wrote:
> > Hi plasma people,
> >
> > I was expecting some components to be available for KDE and indeed there
> > are. Sadly there is to much with roughly similar names which makes it
> > really inconvenient to find out which one i should or should not use..
> >
> > You have (in kde-runtime/plasma/declarativeimports/):
> > - core (what is in there besides the background stuff?)
>
> svg, dataengines and service access, directly and tough models, access to
> theme colors/fonts, dialogs, tooltips
>
> > - draganddrop (uhh.. ?)
>
> does what it says, drag and you know, drop :p
>
> > - graphicslayouts (what is this supposed to be?)
>
> bindings for qgraphicsLinear/grid layout, and yes, quite deprecated
>
> > - graphicswidgets (So these are the Plasma:: widgets right? Sadly they
> are
> > currently broken and give me this error: "Type dump of C++ plugin failed.
> > Parse error: 7:5: Component defenition is missing a name binding" .. I
> > would like to use this one but it's not working. Could someone
> > knowledgable about that one fix it please?)
>
> seems an installation issue on your side. btw those should be really,
> really
> really avoided at this point, unless a very valid reason to use an element
> from them exist (every time those gets used, makes harder for porting to
> plasma2)
>
> > - plasmacomponents (These are the new components from GSoC right? But why
> > do they look so.. different then the Plasma:: components? These do work
> > btw.)
>
> api wise they at least try to follow the standard used in symbian and meego
> look/behaviour they try to look similar, is not 100% possible to have a
> complete carbon copy, some other visual differences are instead wanted as
> in
> "the way things are supposed to look in the future"
> from now on those are *the* elements to use for graphical widgets
>
> > - qtextracomponents (What is this?)
>
> elements low in the stack in qt that don't have bindings directly, like
> icons,
> pixmaps, qimages useful when the c++ part needs to directly have one of
> those
> visualized
>
> > So we have - at the very least - 2 "component" plugins. graphicswidgets
> > and plasmacomponents, but which one am i supposed to use when re-creating
> > the plasma panel tool box? Right now i go for plasmacomponents since it's
> > working..
>
> bits of Components and bits of Core.. ignore graphicswidgets.
>
> actually, the plasma toolbox menu api/behaviour wise is very similar to the
> "menu" component now that i think about it...
> i have now implemented it as a standard QMenu, thinking about it there are
> both usecases for having it done like that and use cases to have a themed
> on
> scene one like the toolbox menu.
>
> do you have already code for this?
> i think we can try to do a component that depending from some factor (type
> of
> the menu item? extra api?) can behave both as a qmenu or as a styled thing.
>
> I'm losing you.. What do you mean with QMenu?
Well, i have "some" code but that's very basic and not even functioning the
way i want.. It's basically just showing a QML file and that QML file is
just a plain QML example that pops up when i press the plasma tool box
button. So nothing worth sharing yet ;p
> > But can't we clean this stuff up a bit, remove what we don't need and
> just
>
> everything that's there is here for a reason :p
> (there is so much stuff, because qml is missing that much stuff and even
> more
> to be actually useful :p)
> now, i would love to remove graphicslayouts and graphicswidgets, but it's
> released api, so we can't just yank it from the kde4 series, besides
> unfortunately graphicswidgets are still needed for some corner cases
>
Sounds like some nice cleanups will get done here with KDE 5.0.
>
> > have "components" for the rest? Then a nice wiki page that explains
> what's
> > all in the components.
>
> a wiki pages does exist, explains only core right now, expansions are
> appreciated of course ;)
>
Yeah, expansions are needed there and it would be nice if the people that
know about it could edit it (you ^_-)
>
> Cheers,
> Marco Martin
>
Cheers,
Mark
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
[Attachment #5 (text/html)]
<div class="gmail_quote">On Sun, Oct 30, 2011 at 1:43 PM, Marco Martin <span \
dir="ltr"><<a href="mailto:notmart@gmail.com">notmart@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">
<div class="im">On Saturday 29 October 2011, Mark wrote:<br>
> Hi plasma people,<br>
><br>
> I was expecting some components to be available for KDE and indeed there<br>
> are. Sadly there is to much with roughly similar names which makes it<br>
> really inconvenient to find out which one i should or should not use..<br>
><br>
> You have (in kde-runtime/plasma/declarativeimports/):<br>
> - core (what is in there besides the background stuff?)<br>
<br>
</div>svg, dataengines and service access, directly and tough models, access to<br>
theme colors/fonts, dialogs, tooltips<br>
<br>
> - draganddrop (uhh.. ?)<br>
<br>
does what it says, drag and you know, drop :p<br>
<div class="im"><br>
> - graphicslayouts (what is this supposed to be?)<br>
<br>
</div>bindings for qgraphicsLinear/grid layout, and yes, quite deprecated<br>
<div class="im"><br>
> - graphicswidgets (So these are the Plasma:: widgets right? Sadly they are<br>
> currently broken and give me this error: "Type dump of C++ plugin \
failed.<br> > Parse error: 7:5: Component defenition is missing a name \
binding" .. I<br> > would like to use this one but it's not working. \
Could someone<br> > knowledgable about that one fix it please?)<br>
<br>
</div>seems an installation issue on your side. btw those should be really, \
really<br> really avoided at this point, unless a very valid reason to use an \
element<br> from them exist (every time those gets used, makes harder for porting \
to<br> plasma2)<br>
<div class="im"><br>
> - plasmacomponents (These are the new components from GSoC right? But why<br>
> do they look so.. different then the Plasma:: components? These do work<br>
> btw.)<br>
<br>
</div>api wise they at least try to follow the standard used in symbian and meego<br>
look/behaviour they try to look similar, is not 100% possible to have a<br>
complete carbon copy, some other visual differences are instead wanted as in<br>
"the way things are supposed to look in the future"<br>
from now on those are *the* elements to use for graphical widgets<br>
<div class="im"><br>
> - qtextracomponents (What is this?)<br>
<br>
</div>elements low in the stack in qt that don't have bindings directly, like \
icons,<br> pixmaps, qimages useful when the c++ part needs to directly have one of \
those<br> visualized<br>
<div class="im"><br>
> So we have - at the very least - 2 "component" plugins. \
graphicswidgets<br> > and plasmacomponents, but which one am i supposed to use \
when re-creating<br> > the plasma panel tool box? Right now i go for \
plasmacomponents since it's<br> > working..<br>
<br>
</div>bits of Components and bits of Core.. ignore graphicswidgets.<br>
<br>
actually, the plasma toolbox menu api/behaviour wise is very similar to the<br>
"menu" component now that i think about it...<br>
i have now implemented it as a standard QMenu, thinking about it there are<br>
both usecases for having it done like that and use cases to have a themed on<br>
scene one like the toolbox menu.<br>
<br>
do you have already code for this?<br>
i think we can try to do a component that depending from some factor (type of<br>
the menu item? extra api?) can behave both as a qmenu or as a styled thing.<br>
<div class="im"><br></div></blockquote><div>I'm losing you.. What do you mean \
with QMenu?</div><div>Well, i have "some" code but that's very basic \
and not even functioning the way i want.. It's basically just showing a QML file \
and that QML file is just a plain QML example that pops up when i press the plasma \
tool box button. So nothing worth sharing yet ;p</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"><div class="im"> > But can't we clean this stuff \
up a bit, remove what we don't need and just<br> <br>
</div>everything that's there is here for a reason :p<br>
(there is so much stuff, because qml is missing that much stuff and even more<br>
to be actually useful :p)<br>
now, i would love to remove graphicslayouts and graphicswidgets, but it's<br>
released api, so we can't just yank it from the kde4 series, besides<br>
unfortunately graphicswidgets are still needed for some corner \
cases<br></blockquote><div><br></div><div>Sounds like some nice cleanups will get \
done here with KDE 5.0. </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> have "components" for the rest? Then a nice wiki page that explains \
what's<br> > all in the components.<br>
<br>
</div>a wiki pages does exist, explains only core right now, expansions are<br>
appreciated of course ;)<br></blockquote><div><br></div><div>Yeah, expansions are \
needed there and it would be nice if the people that know about it could edit it (you \
^_-)</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">
<br>
Cheers,<br>
<font color="#888888">Marco \
Martin<br></font></blockquote><div><br></div><div>Cheers,</div><div>Mark \
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;"><font color="#888888"> \
_______________________________________________<br> Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</font></blockquote></div><br>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic