We have some unusual collections, like Scripts and Certificate Store, that behave somewhat differently than your typical collection of events, tasks and so forth.
This leads to interesting situations I am not sure how to solve, so some design decisions are called for. Here are some examples. You have Certificate Store selected in the sidebar. Arguably you should not be able to create/move non-certificates into this collection. I don't think we have any support for that (I am pretty sure you will get exceptions raised if you try). And you need different type of feedback to the user so that they won't even try or if they manage to try give some useful feedback that it is not supported (create event from menu, copy/paste, drag & drop, double click, ...). You have Scripts selected in the sidebar. You click on Calendar toolbar button. Currently what happens is that the toolbar buttons seems to be selected but you get an empty summary table view. While at first glance it would seem it would be ok to disable the toolbar buttons that don't make sense, this will lead to a situation where the user does not understand why they can't switch to the calendar, for example. You can actually stamp a certificate to an event, for example. For some reason this does not show up on the calendar - seems like a bug. At first glance you might say it is stupid to stamp certificate and stamping should be disabled for certs, but if you think of the case where you are buying certificates (which expire yearly) you'd like to have a calendar reminder to renew the certificate before it expires. And come to think of scripts, why not make it possible to stamp scripts too - a script event could run at the specified time etc. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
