On Monday 24 November 2008, Sebastian Sauer wrote:
> Hi *
>
> sorry for not using http://reviewboard.vidsolbach.de but seems it's not
> possible to use it with konqi at KDE3. Anyway...
the autostart change looks unecesary or even wrong, but the change to krunner
itself looks fine.
--
Aaron J. S
Hi *
sorry for not using http://reviewboard.vidsolbach.de but seems it's not
possible to use it with konqi at KDE3. Anyway...
Attached patch does;
1. let krunner start after plasma (X-KDE-autostart-after=panel - don't ask me
why it's named panel and not plasma. It's the same in e.g. kmix and se
On Monday 24 November 2008, Jud Craft wrote:
> I didn't realize this. Does it work with any style? Could I have,
> for example, a midnight-blue Oxygen, like in the early preview-shots
> of KDE4?
no, but you can have a midnight blue Aya. it follows your desktop colour
scheme, if the theme says i
I didn't realize this. Does it work with any style? Could I have,
for example, a midnight-blue Oxygen, like in the early preview-shots
of KDE4?
I hate to be so ignorant, but I'm actually running GNOME at the
moment, and I didn't notice that feature in my KDE 4.1 setup
elsewhere. But I may have
On Monday 24 November 2008, Fabrizio Montesi wrote:
> On Monday 24 November 2008 20:24:59 Aaron J. Seigo wrote:
> > On Monday 24 November 2008, Fabrizio Montesi wrote:
> > > We would need to support the loading of Jolie scripts anyway (for more
> > > complex cases or coding distributed behaviour as
On Monday 24 November 2008, Davide Bettio wrote:
> I'm not saying that we shouldn't use composite, I'm just saying that we
> need something nice just in case we can't use composite.
the plasma policy is no hacking around the lack of composite. it'll result in
hard to maintain hacks that often hav
On Monday 24 November 2008 20:24:59 Aaron J. Seigo wrote:
> On Monday 24 November 2008, Fabrizio Montesi wrote:
> > We would need to support the loading of Jolie scripts anyway (for more
> > complex cases or coding distributed behaviour as backend to a plasmoid),
> > so while this option (the XML o
Hi,
Il Monday 24 November 2008 23:52:48 Aaron J. Seigo ha scritto:
> Yes, my opinion is that this is so wrong in so many ways.
>
> If we copy the desktop background it will:
>
> * end up looking stupid because with compositing it will be "wallaper over
> windows over wallpaper"
we could disable i
On Monday 24 November 2008, Davide Bettio wrote:
> Any opinion?
Yes, my opinion is that this is so wrong in so many ways.
If we copy the desktop background it will:
* end up looking stupid because with compositing it will be "wallaper over
windows over wallpaper"
* be even less performant than
On Monday 24 November 2008, Jud Craft wrote:
> I do wish that there were non-composited ways to add a touch of flare
> to your KDE desktop, however; for example, the ability to color-tint
> the current plasma theme (similar to what Vista does for the Aero
> interface's taskbar) would be nice, as op
Hi,
Il Monday 24 November 2008 23:30:52 Jud Craft ha scritto:
> I believe it has been expressed that the overall philosophy with
> Plasma is that if you have 3d-compositing capability, you get
> compositing features. If you do not, then you don't. There will be
> no clever hacks to enable such e
I believe it has been expressed that the overall philosophy with
Plasma is that if you have 3d-compositing capability, you get
compositing features. If you do not, then you don't. There will be
no clever hacks to enable such effects in a non-composited
environment.
I remember that there is a pos
Hi,
Actualy If you don't have composite enabled panel doesn't looks very well with
some wallpapers, so I thought that we should use a simple workaround: we can
get the current background from the desktop view and then we can do
compositing on it.
(Kicker used a similiar workaround for a lot of
On Saturday 22 November 2008 02:49:57 Aaron J. Seigo wrote:
> use case: widget wants to publish it's own service onto the network
>
> * it takes a Plasma::Service and, again with a one liner and no jargon it
> pushes the service by a name passed in; this would get automatically set up
> using SODEP
On Monday 24 November 2008, Fabrizio Montesi wrote:
> We would need to support the loading of Jolie scripts anyway (for more
> complex cases or coding distributed behaviour as backend to a plasmoid), so
> while this option (the XML one) could be nice I'm wondering if we would end
> up with too many
On Monday 24 November 2008 18:10:06 Aaron J. Seigo wrote:
> On Sunday 23 November 2008, Fabrizio Montesi wrote:
> > On Saturday 22 November 2008 02:49:57 Aaron J. Seigo wrote:
> > > something else i just remembered:
> > >
> > > we're going to want to think about the full round trip "experience":
>
On Sunday 23 November 2008 23:16:44 Alex Merry wrote:
> On Sunday 23 November 2008 22:59:32 Nicolas Lécureuil wrote:
> > If you right click, keep the mouse pressed, mouse it on the menu, and
> > unclick the mouse, kde4 consider that you have clicked on the menu.
> I'm guessing Windows does the sam
On Sunday 23 November 2008, Fabrizio Montesi wrote:
> On Saturday 22 November 2008 02:49:57 Aaron J. Seigo wrote:
> > something else i just remembered:
> >
> > we're going to want to think about the full round trip "experience":
> >
> > use case: widget wants to use a web service
> >
> > * it says
18 matches
Mail list logo
