Hi all,
There are currently two control modules for Solid: one for choosing
backends, and one for managing actions. At the end of the review of
the managing actions module it was suggested that I start a discussion
about how to merge these two modules, since they belong together.
Currently I prop
On Tuesday 24 March 2009 08:14:20 Ben Cooksley wrote:
> There are currently two control modules for Solid: one for choosing
> backends, and one for managing actions. At the end of the review of
> the managing actions module it was suggested that I start a discussion
> about how to merge these two m
On Wednesday 25 March 2009 09:10:25 Kevin Ottens wrote:
> On Tuesday 24 March 2009 08:14:20 Ben Cooksley wrote:
> > There are currently two control modules for Solid: one for choosing
> > backends, and one for managing actions. At the end of the review of
> > the managing actions module it was sugg
On Wednesday 25 March 2009 10:30:10 Will Stephenson wrote:
> where I doubt that Platform Backends belongs on any end user system, since
> they should have exactly 1 backend installed by default. Perhaps we can
> urge that it is packages separately (eg as
> kdebase4-workspace-hardware-expert) and n
On Wed, Mar 25, 2009 at 10:30 PM, Will Stephenson wrote:
> On Wednesday 25 March 2009 09:10:25 Kevin Ottens wrote:
>> On Tuesday 24 March 2009 08:14:20 Ben Cooksley wrote:
>> > There are currently two control modules for Solid: one for choosing
>> > backends, and one for managing actions. At the e
On Thursday 26 March 2009 08:14:03 Ben Cooksley wrote:
> Definitely agree here. I will begin work on a new Platform backends
> control module, creating a new display widget to configure the
> platform specific backends in the process so that this functionality
> can be moved to the appropriate modu
