On Sunday, 2011-09-11, Duncan wrote: > Anne Wilson posted on Sun, 11 Sep 2011 18:35:32 +0100 as excerpted: > > I take your point, but in truth, any well-written piece of code should > > be able to exit gracefully if something fails. If it can't, I'd rather > > not run it at all. > > You're absolutely correct. But the point is, one of the big selling- > point features of plasma has been its extensibility... by coders who may > in fact be rather bad at it, beginners or whatever. In that sort of > environment, you have to COUNT on some of the code being bad, because it > is GOING to happen. An app designed for that can't simply crash when one > of the extensions goes bad, because it WILL heppen, and it WILL look bad > for the main app as a result. It MUST be designed to be robust and have > the rest keep running in spite of whatever badly coded barf-code someone > throws at it, or it wasn't so properly designed for that extensibility as > it might seem to be after all. That's what Plasma's Javascript API is for. The extension points which allow external code to be part of the applet, e.g. C++, Python, can't be isolated against bad behavior very well. Hence the need and existance of a save extension point. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
Attachment:
signature.asc
Description: This is a digitally signed message part.
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
