A Monday 12 January 2009 22:55:11, Aaron J. Seigo escreveu:
> On Monday 12 January 2009, Marco Martin wrote:
> > if the possible positions are not that much (lets say something like on
> > the 4 corners) maybe using a single pixmap for caching would still be
> > possible? or maybe just if the posit
On Monday 12 January 2009, Marco Martin wrote:
> if the possible positions are not that much (lets say something like on the
> 4 corners) maybe using a single pixmap for caching would still be possible?
> or maybe just if the position is consistent across instances the impact on
> cache would still
On Monday 12 January 2009, Aaron J. Seigo wrote:
> On Monday 12 January 2009, Marco Martin wrote:
> > On Monday 12 January 2009, Aaron J. Seigo wrote:
> > > * random position whenever a widget is created. this would result in
> > > every widget having a (potentially) unique position, and this posit
---
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.vidsolbach.de/r/325/
---
(Updated 2009-01-12 14:13:21.430508)
Review request for Plasma.
Summary
-
Thank you for help, it works right :)
On Mon, Jan 12, 2009 at 7:40 PM, Gökmen GÖKSEL wrote:
> > Hello,
> Hi !,
>
> > I'm trying to do a very simple python plasmoid in order to show a
> > Plasma.Label, but when I try to run it, I get an error:
> It will be done if you change your init method like
On Monday 12 January 2009, Nuno Pinheiro wrote:
> A Monday 12 January 2009 17:32:57, Aaron J. Seigo escreveu:
> > * random position whenever a widget is *first* created. this would result
> > in every widget having a (potentially) unique position, but the position
> > would remain constant between
On Monday 12 January 2009, Marco Martin wrote:
> On Monday 12 January 2009, Aaron J. Seigo wrote:
> > * random position whenever a widget is created. this would result in
> > every widget having a (potentially) unique position, and this position
> > would change between launches of plasma.
>
> hmm,
On Monday 12 January 2009, Marco Martin wrote:
> On Monday 12 January 2009, Aaron J. Seigo wrote:
> > On Monday 12 January 2009, Nuno Pinheiro wrote:
> > > > define "randomly"
> > >
> > > The idea for this case was that plasmoid A gets the same exact look
> > > every time but the bg of plasmoid A i
> Hello,
Hi !,
> I'm trying to do a very simple python plasmoid in order to show a
> Plasma.Label, but when I try to run it, I get an error:
It will be done if you change your init method like this;
def init(self):
# first of all we need a layout..
self.la
Hello,
I'm trying to do a very simple python plasmoid in order to show a
Plasma.Label, but when I try to run it, I get an error:
Traceback (most recent call last):
File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py",
line 54, in init
self.pyapplet.init()
File
"/usr/sh
On Monday 12 January 2009, Aaron J. Seigo wrote:
> On Monday 12 January 2009, Nuno Pinheiro wrote:
> > > define "randomly"
> >
> > The idea for this case was that plasmoid A gets the same exact look every
> > time but the bg of plasmoid A is diferent from plasmoid B.
>
> does it matter what the wid
Would it make sense to add another heading under the "Desktop" dialog?
Right now I see Deskopt Effects, Mulitiple Desktops, Screen Saver, and
Launch Feedback. How about adding something for the ZUI?
If not, what about adding a new section under the "Look & Feel" heading?
Just two thoughts off of
A Monday 12 January 2009 17:32:57, Aaron J. Seigo escreveu:
> On Monday 12 January 2009, Nuno Pinheiro wrote:
> > > define "randomly"
> >
> > The idea for this case was that plasmoid A gets the same exact look every
> > time but the bg of plasmoid A is diferent from plasmoid B.
>
> does it matter w
On Monday 12 January 2009, Nuno Pinheiro wrote:
> > define "randomly"
>
> The idea for this case was that plasmoid A gets the same exact look every
> time but the bg of plasmoid A is diferent from plasmoid B.
does it matter what the widget is (e.g. "digital-clock") or just that it's the
same for
A Monday 12 January 2009 17:10:44, Aaron J. Seigo escreveu:
> On Monday 12 January 2009, Nuno Pinheiro wrote:
> > A Monday 12 January 2009 16:47:30, Aaron J. Seigo escreveu:
> > > On Sunday 11 January 2009, Marco Martin wrote:
> > > > never scaled, position depending on applet name (eeeh, code for
On Monday 12 January 2009, Nuno Pinheiro wrote:
> A Monday 12 January 2009 16:47:30, Aaron J. Seigo escreveu:
> > On Sunday 11 January 2009, Marco Martin wrote:
> > > never scaled, position depending on applet name (eeeh, code for this is
> > > not overly pretty and probably can't be, i know :/) ti
A Monday 12 January 2009 16:47:30, Aaron J. Seigo escreveu:
> On Sunday 11 January 2009, Marco Martin wrote:
> > never scaled, position depending on applet name (eeeh, code for this is
> > not overly pretty and probably can't be, i know :/) tiled
>
> it can't be based on applet name. that will tie
On Sunday 11 January 2009, Marco Martin wrote:
> never scaled, position depending on applet name (eeeh, code for this is not
> overly pretty and probably can't be, i know :/) tiled
it can't be based on applet name. that will tie themes much, much too tightly
to a specific set of applets and will
On Saturday 10 January 2009, Virtual Sky Solutions wrote:
> that KDE has, but what does it matter if I want a black / grey checkerboard
> vs. a white / grey?
this brings us to the next set of questions:
Where do we put this configuration option, how do we label it, what do we let
the user set
19 matches
Mail list logo
