Plasma Media Center and state machines

[Christophe Olinger]

I'll just have to try and see how far I get with a single state machine. I
think that Shan's idea could work but also think that extending things would
mean writing new states for all applets. For me it seems easier to write a
top level state which can direct infromation to all applets. The applets
wouldn't need to know any states, they would just do what they are told.

Could any new future states simply be added to the State enum in the
library? Would extending it be some form of binary incompatibilty or
something?

Chris

On Fri, Apr 2, 2010 at 10:34 AM, Alessandro Diaferia
<alediaferia at gmail.com>wrote:

>
>
> 2010/4/2 Marco Martin <notmart at gmail.com>
>
> On Friday 02 April 2010, Shantanu Tushar Jha wrote:
>> > (My ideas, be free to kick ;)
>> >
>> > Hi Christophe, now I'm able to understand most of what you've
>> > proposed. Somehow, I don't like having just one state machine for the
>> > whole MC, the main reason being that we're going to support
>> > extensibility through custom plugins, so the MC can no longer assume
>> > that it knows exactly how many states are present.
>> > What I propose is not altering the libraries, but to have a state
>> > machine for each component (component as in the containment,
>> > controller applet etc). Though I don't have code to show that right
>> > now (i'm writing a small Qt app to demo it), I'll try to explain a
>> > sample working-
>>
>> While i share the concern over extesibility (and wouldn't know how to do
>> it
>> with a single global state machine) how a state machine for each component
>> would fix that?
>> a part every plugin being a omplete set of new applets...
>>
>> Cheers,
>> Marco Martin
>> _______________________________________________
>> Plasma-devel mailing list
>> Plasma-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/plasma-devel
>>
>
> I like the extensibility idea too but i think that we are bound to the
> definition of a set of possible states. We can try to look forward as much
> as we can and define such states. Plugins will just specify which of those
> states they'll refer to. In the future, probably, we'll update our libraries
> with the states that we could have never imagined in the past :-).
>
> So we can now have:
> Pictures,
> Videos,
> Audio tracks,
> Games,
> Olographic films :-)
> ...
>
> That's probably enough for now :-P
>
> Cheers
>
> --
> Alessandro Diaferia
> KDE Developer
> KDE e.V. member
>
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/plasma-devel/attachments/20100402/a3b96fa3/attachment.htm