alecs/plasma-framework
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
14,423 Commits 1 Branch 0 Tags
Commit Graph

8 Commits

Author SHA1 Message Date
Marco Martin
a629fe4d8f migrate to KPackage 
Plasma::Package internally uses KPackage, being a pure wrapper.
old client code and old packagestructures still work using the wrapper.
old workspace code that is not directly using kpackage continues to work correctly

Change-Id: I05f95e8d05e3b67759973c4009e3753c61b1dcce
 2014-12-29 13:56:52 +01:00
Marco Martin
21cf68dbd2 set directly the fallback package not its path 2014-09-01 14:54:10 +02:00
Marco Martin
aba4dcb915 introduce setFallbackPackagePath 
the fallback package would then be decided by the packagestructure
 2014-09-01 14:00:06 +02:00
Aaron Seigo
928d5e63a5 bool Package::hasValidStructure() const 
needed to differentiate between packages with structures and without
before path is set
 2014-08-08 14:12:22 +02:00
Kevin Ottens
72ba7b4146 Apply the astyle-kdelibs script 2014-04-26 01:48:37 +02:00
Aurélien Gâteau
43e2b0f670 Unbreak build of code using plasma-framework 
plasma_export.h is now installed in include/plasma/, not in include/.
Code using plasma-framework does not have include/plasma in its include
directory list, so plasma-framework headers must refer to others using
</plasma/foo.h>, not "foo.h".

CCMAIL: aleixpol@kde.org
 2014-03-18 12:01:36 +01:00
Aleix Pol
2ef12f1ee8 More headers tweaking 
Don't install the camel-case headers twice
Look for the plasma_export.h in the current directory instead of jumping
around in the project.
 2014-03-17 16:48:49 +01:00
Sebastian Kügler
7dfe957e66 The Big Move 
All cpp code moves into the src/ subdirectory, as the Frameworks policy
suggests.

Directory structure should now be in line with other, future frameworks.
 2013-02-14 17:17:12 +01:00