This revision was automatically updated to reflect the committed changes.
Closed by commit R119:fd1f77d5dbff: KCMSplashScreen fix warning, use
KPackage::Package instead of Plasma::Package (authored by crossi).
Herald added a project: Plasma.
Herald added a subscriber: plasma-devel.
REPOSITORY
This revision was automatically updated to reflect the committed changes.
Closed by commit R119:550a9a25d628: KCM LookAndFeel : fix warnings, use
KPackage instead of Plasma::Package (authored by crossi).
Herald added a project: Plasma.
Herald added a subscriber: plasma-devel.
REPOSITORY
R119
This revision was automatically updated to reflect the committed changes.
Closed by commit R242:563011436d5f: Port a bunch of classes away from
Plasma::Package (authored by apol).
REPOSITORY
R242 Plasma Framework (Library)
CHANGES SINCE LAST UPDATE
https://phabricator.kde.org/D6041?vs=15015
apol added a comment.
Yes sure.
REPOSITORY
R242 Plasma Framework (Library)
BRANCH
master
REVISION DETAIL
https://phabricator.kde.org/D6041
To: apol, #frameworks, #plasma, mart
Cc: davidedmundson, mart, plasma-devel, ZrenBot, spstarr, progwolff,
lesliezhai, ali-mohamed, jensreuterberg
davidedmundson added a comment.
Can we wait till after the next release is tagged as that's super soon and
this isn't that important.
We've had major bugs porting stuff in this area before.
REPOSITORY
R242 Plasma Framework (Library)
BRANCH
master
REVISION DETAIL
https://phabricator.
mart accepted this revision.
This revision is now accepted and ready to land.
REPOSITORY
R242 Plasma Framework (Library)
BRANCH
master
REVISION DETAIL
https://phabricator.kde.org/D6041
To: apol, #frameworks, #plasma, mart
Cc: mart, plasma-devel, ZrenBot, spstarr, progwolff, lesliezhai, al
apol marked 2 inline comments as done.
apol added inline comments.
INLINE COMMENTS
> mart wrote in appletquickitem.h:105
> despite the warning in the header, this ended up being an exported symbol, so
> binary compatibility rules apply here too.
> Plasma::Package appletPackage() c
apol updated this revision to Diff 15015.
apol marked an inline comment as done.
apol added a comment.
Address Marco's comments
REPOSITORY
R242 Plasma Framework (Library)
CHANGES SINCE LAST UPDATE
https://phabricator.kde.org/D6041?vs=15003&id=15015
BRANCH
master
REVISION DETAIL
http
ab isn't that smart in the diff it makes checking for binary
compatibility quite tricky ;)
> appletquickitem.h:105
>
> -Plasma::Package appletPackage() const;
> - void setAppletPackage(const Plasma::Package &package);
> +KPackage::Package appletPackage() const;
apol created this revision.
Restricted Application added projects: Plasma, Frameworks.
Restricted Application added a subscriber: plasma-devel.
REVISION SUMMARY
Ported away some classes, removes many unneeded casts that happen when
starting.
TEST PLAN
Tests still pass, plasma starts properly
This revision was automatically updated to reflect the committed changes.
Closed by commit R242:4798310ed788: Deprecate Plasma::Package API in
PluginLoader (authored by graesslin).
REPOSITORY
R242 Plasma Frameworks
CHANGES SINCE LAST UPDATE
https://phabricator.kde.org/D3812?vs=9366&id=
mart accepted this revision.
mart added a reviewer: mart.
This revision is now accepted and ready to land.
REPOSITORY
R242 Plasma Frameworks
BRANCH
deprecate-package-in-pluginloader
REVISION DETAIL
https://phabricator.kde.org/D3812
EMAIL PREFERENCES
https://phabricator.kde.org/settings/
graesslin created this revision.
graesslin added reviewers: Plasma, Frameworks.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.
REVISION SUMMARY
As Plasma::Package is deprecated API using Plasma::Package should also
be deprecated
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122595/
---
(Updated Feb. 25, 2015, 3:28 p.m.)
Status
--
This change has been ma
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122595/#review76398
---
Ship it!
Ship It!
- Marco Martin
On Feb. 21, 2015, 12:56 p
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122595/
---
(Updated Feb. 21, 2015, 1:56 p.m.)
Review request for Plasma.
Changes
-
> On Feb. 16, 2015, 6:38 p.m., Kai Uwe Broulik wrote:
> > Can't we resurrect, for instance, the X-Plasma-RequiredExtensions thing or
> > so? I don't want to end up with dozens of X-Plasma-Requires-Internet,
> > X-Plasma-Requires-This-and-that
+1,
it can be X-Plasma-RequiredExtensions=ExternalS
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122595/#review76152
---
Can't we resurrect, for instance, the X-Plasma-RequiredExtensi
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122595/#review76149
---
Ship it!
+1, could you just add a short paragraph about this
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122595/
---
Review request for Plasma.
Repository: plasma-framework
Description
---
On Tue, Sep 16, 2014 at 2:19 PM, Marco Martin wrote:
> right now all the classes are still under the Plasma namespace, and should
> probably be renamed and cmakes to be cleaned up (especially because it
> would
> be used by plasma too to the two identically named classes, new and
> deprecated
> w
On Wednesday, September 17, 2014 11:20:10 Marco Martin wrote:
> On Wednesday 17 September 2014 11:06:50 Martin Gräßlin wrote:
> > > Is the name ok for everybody? potential name clashes?
> >
> > as it used to be namespaces before, what about using a namespace KPackage
> > and just call the classes:
On Wednesday 17 September 2014 11:06:50 Martin Gräßlin wrote:
> > Is the name ok for everybody? potential name clashes?
>
> as it used to be namespaces before, what about using a namespace KPackage
> and just call the classes:
> KPackage::Package
> KPackage::PackageStructure
> KPackage::PackageTra
On Wednesday 17 September 2014 10:40:35 Marco Martin wrote:
> On Tuesday 16 September 2014 14:19:44 Marco Martin wrote:
> > right now all the classes are still under the Plasma namespace, and should
> > probably be renamed and cmakes to be cleaned up (especially because it
> > would be used by plas
On Tuesday 16 September 2014 14:19:44 Marco Martin wrote:
> right now all the classes are still under the Plasma namespace, and should
> probably be renamed and cmakes to be cleaned up (especially because it would
> be used by plasma too to the two identically named classes, new and
> deprecated wo
Hi all,
first, brief introductionon what this is:
during a Bof about scripting in applications at Akademy it occurred that some
applications may be interested by the functionality provided by
Plasma::Package, provided it was on a lower tier.
Since I already had kindof the idea of making Package
On Monday, 2014-05-26, 10:58:06, Marco Martin wrote:
> On Saturday 24 May 2014, Kevin Krammer wrote:
> > 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.
> >
&g
ailable 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
> Pla
> Are there any Plasma specific dependencies in the current code?
Not really.
In terms of dependencies, it's pretty much:
KArchive
KService
KI8n (could be dropped)
David
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/li
ing 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,
>
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 exte
On Thursday, July 25, 2013 16:02:53 Michael Bohlender wrote:
> On Thu, Jul 25, 2013 at 4:00 PM, Michael Bohlender
wrote:
> > I am using plasma components outside of a plasma package in kmail-mobile
> > and some components don't get displayed / themed correctly.
> >
&g
On Thu, Jul 25, 2013 at 4:00 PM, Michael Bohlender <
michael.bohlen...@gmail.com> wrote:
>
> > I am using plasma components outside of a plasma package in kmail-mobile
>> and
>> > some components don't get displayed / themed correctly.
>> &g
Hi Michael,
On Thursday, July 25, 2013 14:22:09 Michael Bohlender wrote:
> I am using plasma components outside of a plasma package in kmail-mobile and
> some components don't get displayed / themed correctly.
>
> # PageRow: bordershadows not visible
>
> "
> fi
I am using plasma components outside of a plasma package in kmail-mobile
and some components don't get displayed / themed correctly.
# PageRow: bordershadows not visible
"
file:///opt/kde4/lib/kde4/imports/org/kde/plasma/extras/PageRow.qml:316:13:
QML QDeclarativeImage_QML_25: Fai
Hey Giorgos,
On Saturday, December 24, 2011 16:05:31 Giorgos Tsiapaliwkas wrote:
> here some questions about the plasma package
>
> 1.every plasmoid has these 3 dirs code,data,animations.
> What kind of files should exist in those 3?
> Does those 3 have any "special"
Hello,
here some questions about the plasma package
1.every plasmoid has these 3 dirs code,data,animations.
What kind of files should exist in those 3?
Does those 3 have any "special" effects to the plasmoids like the ui/config.ui?
2.in the declarative-plasmoids repository there i
wboard.kde.org/r/101302/#review3150
---
On May 6, 2011, 5:17 a.m., Raphael Kubo da Costa wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> ht
On May 6, 2011, 5:17 a.m., Raphael Kubo da Costa wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/101302/
> ---
>
> (Updated May 6
tomatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/101302/
> ---
>
> (Updated May 6, 2011, 5:17 a.m.)
>
>
> Review request for Plasma.
>
>
> Summary
> ---
>
> Do not check if the created Plasma::Package is valid.
>
Plasma::Package is valid.
Wallpapers consisting of a single image (without a .desktop metadata or
anything else), usually obtained via GHNS, are not valid packages, but are
valid wallpapers.
Commit b60136e, besides moving the loading code to a separate thread, also
started checking if a
2009/7/25 Aaron J. Seigo
> On Friday 24 July 2009, Dong Tiger wrote:
> > After removing the line of "X-KDE-ParentApp=", it appears in the dialog.
>
> aha! and looking at the code in libplasma, the reason for that is fairly
> obvious. i'll be committing (and backporting) a fix for this shortly.
>
On Friday 24 July 2009, Dong Tiger wrote:
> After removing the line of "X-KDE-ParentApp=", it appears in the dialog.
aha! and looking at the code in libplasma, the reason for that is fairly
obvious. i'll be committing (and backporting) a fix for this shortly. thanks
for tracking down the exact i
Aaron J. Seigo
>> >
>> > > On Wednesday 22 July 2009, Dong Tiger wrote:
>> > > > I found I can't add Google Gadget into plasma any more. Google
>> Gadget
>> > > > in plasma uses Plasma::Package::registerPackage to add gadgets into
>>
On Wednesday 22 July 2009, Dong Tiger wrote:
> > 2009/7/23 Aaron J. Seigo
> >
> > > On Wednesday 22 July 2009, Dong Tiger wrote:
> > > > I found I can't add Google Gadget into plasma any more. Google
> Gadget
> > > > in plasma uses Plasma::Pac
On Wednesday 22 July 2009, Dong Tiger wrote:
> 2009/7/23 Aaron J. Seigo
>
> > On Wednesday 22 July 2009, Dong Tiger wrote:
> > > I found I can't add Google Gadget into plasma any more. Google Gadget
> > > in plasma uses Plasma::Package::registerPacka
2009/7/23 Aaron J. Seigo
> On Wednesday 22 July 2009, Dong Tiger wrote:
> > I found I can't add Google Gadget into plasma any more. Google Gadget in
> > plasma uses Plasma::Package::registerPackage to add gadgets into plasma.
> It
> > used to work.
>
> * is
On Wednesday 22 July 2009, Dong Tiger wrote:
> I found I can't add Google Gadget into plasma any more. Google Gadget in
> plasma uses Plasma::Package::registerPackage to add gadgets into plasma. It
> used to work.
* is the pluginName() set in the Plasma::PackageMetadata obje
> >
> > I found I can't add Google Gadget into plasma any more. Google Gadget in
> > plasma uses Plasma::Package::registerPackage to add gadgets into plasma.
> It
> > used to work.
> >
> > I saw there is another method installPackage in Plasma::Package. Sho
In data mercoledì 22 luglio 2009 08:29:59, Dong Tiger ha scritto:
: > Hi,
>
> I found I can't add Google Gadget into plasma any more. Google Gadget in
> plasma uses Plasma::Package::registerPackage to add gadgets into plasma. It
> used to work.
>
> I saw there is anothe
On Wednesday 22 July 2009, Dong Tiger wrote:
> Hi,
>
> I found I can't add Google Gadget into plasma any more. Google Gadget in
> plasma uses Plasma::Package::registerPackage to add gadgets into plasma. It
> used to work.
>
> I saw there is another method installPackage
Hi,
I found I can't add Google Gadget into plasma any more. Google Gadget in
plasma uses Plasma::Package::registerPackage to add gadgets into plasma. It
used to work.
I saw there is another method installPackage in Plasma::Package. Should it
be used instead of registerPackage? One more th
On Friday 26 September 2008, Petri Damstén wrote:
> hi,
>
> This patch enables custom packages to use default install function by
> adding defaultPackageRoot and servicePrefix to package handling.
nice.. something i've been wanting to get to for quite a while =)
--
Aaron J. Seigo
humru othro a k
hi,
This patch enables custom packages to use default install function by adding
defaultPackageRoot and servicePrefix to package handling.
Petri
Index: libs/plasma/package.h
===
--- libs/plasma/package.h (revision 865053)
+++ libs/
54 matches
Mail list logo
