<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">aha! ok .. so imho this belongs more in kactivitymanagerd (kamd) itself.<br>
<br>
i was considering whether or not it makes sense to have different orders of<br>
activities .. and i don't think it does. activities should probably be<br>
globally consistent.<br>
<br>
where we coordinate all activity related information in kamd. it would<br>
probably be best if kamd would store the order and coordinate the keyboard<br>
shortcuts for jumping between those ordered items.<br>
<br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
would that work with the design you had in mind as well, or are there other<br>
needs / requirements that would not cover?<br>
<br>
and perhaps Ivan can weigh in here as well ...<br>
<span class="HOEnZb"></span><br>
</blockquote>That would definetely solve the situation but the problem is that I dont have enough experience to touch a very important piece of code as kamd (I havent touched library code before). At the same time I believe this is a very big task for kamd and many things must change, so except manpower that needs also time.<br>
<br></div><div class="gmail_quote">The development road I chose was to implement most of the new features for kde through plasmoids, data engines (and kwin effects soon) in order not to touch the core. After the users and programmers had tested and critisized the new features I was thinking to try to help implementing them with guidance in the plasma shell.<br>
</div></div></div>