Thank you Alex for your thoughtful answers. I have one follow-up question. You wrote:
> We want Do to become a first class part of your desktop. To implicitly > integrate with your system. We want the applications themselves to have more > control over what Do does. This should increase the coherence between Do > and your desktop. This sounds great, but it is pretty abstract. Can you give me an example of this tight integration? What application could benefit from having more control over Do? > Another great engineering point is that it lets us also move the plugins > into their own processes. Plugins will never again be able to crash Do. If a > plugin crashes you won't get its items- but everything else will still work, > as if nothing happened. [...] Sounds good, even though Do never crashes on my computer. Thank you for taking a look at my "wishlist". Being able to write plugins in any language is very nice! I won't comment a lot more, but if I understand correctly, you will look into some of these issues, which is great :) > Happy to answer all of your questions, I hope I did a sufficient job. If you > have any questions about blueprints, or if you can identify parts that are > unclear to you I'd like to know so I can clear the up. I'll look more into them, and see if I can give you a better feedback. -- You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en.
