Hi all, I'm not going to be able to come to the hangout (noons are becoming difficult for me).
I've finished the structure that will be needed for supporting templates (the generic properties for plugins thing). There are a few questions thgouh. 0. How / where do we want the plugins to be located - kamd doesn't care much apart from listing them. So, I need only to know where the template dirs will be at. 1. The activities api do not allow setting the props while creating an activity at this moment. This is good and clean as far as kactivities are concerned, but would be difficult for the client app - you get a signal that an activity has been created, but you need to wait until it gets a template assigned. The alternative would be to have an addActivity(name, proplist) method that would delay the activity added signal until the properties are set. This would be cool for the user, but would potentially introduce service blocks if some plugin starts misbehaving. Still don't know which way to go. 2. Any objections to adding boost.range (stl algorithm on steroids library) to the list of deps? It is a header-only library, so it doesn't have any effects on runtime deps. Ch -- Acting is merely the art of keeping a large group of people from coughing. -- Sir Ralph Richardson _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
