--===============3016226297747006929== Content-Type: multipart/alternative; boundary=00148536ed86b7937f04b0742fe6 --00148536ed86b7937f04b0742fe6 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Oct 29, 2011 at 11:58 AM, Marco Martin wrote: > On Saturday 29 October 2011, Aaron J. Seigo wrote: > > On Friday, October 28, 2011 22:10:07 Mark wrote: > > > On Thu, Oct 27, 2011 at 2:24 PM, Aaron J. Seigo > wrote: > > > > On Thursday, October 27, 2011 14:05:42 Mark wrote: > > > > > Ah men i hate this.. This is a typical "it's right under your nose" > > > > > case > > > > : > > > > :p > > > > > > > > usually only after it's been pointed out is it right under your now; > > > > before > > > > that it may as well be very well hidden behind your back ;) > > > > > > > > don't worry, with time you'll get to learn the source tree and where > > > > you can > > > > expect to look for different kinds of things. it's just a learning > > > > curve, though hopefully one we've made as level as possible. > > > > > > > > > Thanx for helping :) > > > > > > > > np :) > > > > > > Oke, i finally have the darn QML file working in the position where i > > > want it. Quite irritating since apparently i need to set the base > > > position of QDeclarativeView in C++ where i'd expect it to be set from > > > XML with just X and Y position.. Also the line to set some flags > doesn't > > > seem to be working on QDeclerativeView: > KWindowSystem::setState(winId(), > > > NET::SkipTaskbar | NET::SkipPager | NET::Sticky | NET::KeepAbove); ... > > > Or i did something wrong. > > > > > > Anyway, i'm gonna try to fill up the QML file with elements so it looks > > > like the current tool box we all know but for that i need to get some > > > things working.. > > > > > > 1. How do i get the PlasmaCore import working: > > > > http://techbase.kde.org/Development/Tutorials/Plasma/QML/GettingStarted#P > > > las ma_Widgets_in_QML My > > > > you just include PlasmaCore like: > > > > import org.kde.plasma.core 0.1 as PlasmaCore > > > > assumng you have a sufficiently new kde-runtime installed, this should > > "just work" > > make sure the proper import path is set in the qml runtime. > ie if you are using this from plasma you ***M U S T*** use > Plasma::DeclarativeWidget > > if you are doing tests with qmlviewer, add the command line parameter > -I /usr/lib/kde4/imports > > (or whatever prefix kde is installed instead of /usr) > > > > > 2. Which options are possible for plasmacore backgrounds.. Right now i > > > have "widgets/frame" but what else is there? > > > > these come from the SVG theme... in this case you probably want to use > > dialogs/background > > > http://techbase.kde.org/Development/Tutorials/Plasma/ThemeDetails#Current_Theme_Elements > > > > 3. Where are the plasma QML files hidden for a button and such and how > do > > > i use them (imports.. same as question 1 only with different files) > > > > until the MobileComponents and Plasma::Components become available to you > > (will be in kde-runtime, and eventually a separate KDE QML repository), > you > > can use Plasma widgdets like PlasmaWidgets.PushButton > > plasma components are now in runtime master (whether leavng them in for 4.8 > is > another question, but i would) > > Cheers, > Marco Martin > Apparently it isn't "just" working. I was missing a "QML_IMPORT_PATH" environment variable. Once i set that to the imports it worked. However, if i run it through QtCreator (just a QML file with no project behind it) then QtCreator still doesn't see it.. Right now i "work around" this by making a project and setting the "importPaths" variable in the .qmlproject, but does anyone know the environment variable i need to edit for the default import paths? Odly enough QtCreator doesn't seem to look at QML_IMPORT_PATH ... Thanx. --00148536ed86b7937f04b0742fe6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sat, Oct 29, 2011 at 11:58 AM, Marco Martin <= span dir=3D"ltr"><notmart@gmail.com= > wrote:
On Saturday 29 October 2011, Aaron J. Sei= go wrote:
> On Friday, October 28, 2011 22:10:07 Mark wrote:
> > On Thu, Oct 27, 2011 at 2:24 PM, Aaron J. Seigo <aseigo@kde.org> wrote:
> > > On Thursday, October 27, 2011 14:05:42 Mark wrote:
> > > > Ah men i hate this.. This is a typical "it's r= ight under your nose"
> > > > case
> > > :
> > > :p
> > >
> > > usually only after it's been pointed out is it right und= er your now;
> > > before
> > > that it may as well be very well hidden behind your back ;)<= br> > > >
> > > don't worry, with time you'll get to learn the sourc= e tree and where
> > > you can
> > > expect to look for different kinds of things. it's just = a learning
> > > curve, though hopefully one we've made as level as possi= ble.
> > >
> > > > Thanx for helping :)
> > >
> > > np :)
> >
> > Oke, i finally have the darn QML file working in the position whe= re i
> > want it. Quite irritating since apparently i need to set the base=
> > position of QDeclarativeView in C++ where i'd expect it to be= set from
> > XML with just X and Y position.. Also the line to set some flags = doesn't
> > seem to be working on QDeclerativeView: KWindowSystem::setState(w= inId(),
> > NET::SkipTaskbar | NET::SkipPager | NET::Sticky | NET::KeepAbove)= ; ...
> > Or i did something wrong.
> >
> > Anyway, i'm gonna try to fill up the QML file with elements s= o it looks
> > like the current tool box we all know but for that i need to get = some
> > things working..
> >
> > 1. How do i get the PlasmaCore import working:
> > http://techbase.kde.org/Development/= Tutorials/Plasma/QML/GettingStarted#P
> > las ma_Widgets_in_QML My
>
> you just include PlasmaCore like:
>
> import org.kde.plasma.core 0.1 as PlasmaCore
>
> assumng you have a sufficiently new kde-runtime installed, this should=
> "just work"

make sure the proper import path is set in the qml runtime.
ie if you are using this from plasma you <blink>***M U S T***</bli= nk> use
Plasma::DeclarativeWidget

if you are doing tests with qmlviewer, add the command line parameter
-I /usr/lib/kde4/imports

(or whatever prefix kde is installed instead of /usr)


> > 2. Which options are possible for plasmacore backgrounds.. Right = now i
> > have "widgets/frame" but what else is there?
>
> these come from the SVG theme... in this case you probably want to use=
> dialogs/background

http://techbase.kde.org/D= evelopment/Tutorials/Plasma/ThemeDetails#Current_Theme_Elements

> > 3. Where are the plasma QML files hidden for a button and such an= d how do
> > i use them (imports.. same as question 1 only with different file= s)
>
> until the MobileComponents and Plasma::Components become available to = you
> (will be in kde-runtime, and eventually a separate KDE QML repository)= , you
> can use Plasma widgdets like PlasmaWidgets.PushButton

plasma components are now in runtime master (whether leavng them in f= or 4.8 is
another question, but i would)

Cheers,
Marco Martin
Apparently it isn't "just" working. I was missing a &qu= ot;QML_IMPORT_PATH" environment variable. Once i set that to the impor= ts it worked.
However, if i run it through QtCreator (just a QML file with no projec= t behind it) then QtCreator still doesn't see it.. Right now i "wo= rk around" this by making a project and setting the "importPaths&= quot; variable in the <project>.qmlproject, but does anyone know the = environment variable i need to edit for the default import paths? Odly enou= gh QtCreator doesn't seem to look at QML_IMPORT_PATH ...

Thanx.
--00148536ed86b7937f04b0742fe6-- --===============3016226297747006929== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel --===============3016226297747006929==--