Tails

#2 Updated by intrigeri 2014-06-22 00:55:19

What would be the usecase(s) satisfied by this “main window”?

#5 Updated by sajolida 2014-06-22 08:21:58

> What would be the usecase(s) satisfied by this “main window”?

I’m not sure to understand to scope of your question.

I’m not thinking about any use case that would be different than the
applet itself for this window but if we want to add it the the menus,
then this launcher has to start something. That’s what I call main window.

According to the report from the UX testing, someone had to fallback on
using gpg from the terminal because he didn’t find our applet.

I admit he probably didn’t read our doc. But currently you can’t really
know that this applet does GPG stuff unless you read the doc, or check
its About page. The interface of the applet itself doesn’t mention OpenPGP.

So having a menu would be a good step towards making it easier to
discover that there is a dedicated application to do OpenPGP in Tails.

#6 Updated by intrigeri 2014-06-22 09:01:35

> I’m not thinking about any use case that would be different than the
> applet itself for this window but if we want to add it the the menus,
> then this launcher has to start something. That’s what I call main window.

So, the “main window” should expose the same set of features as the applet?

#7 Updated by sajolida 2014-06-22 10:19:24

> So, the “main window” should expose the same set of features as the applet?

I’d say so…

#9 Updated by alant 2014-06-28 12:29:25

This is actually a good step towards replacing this our OpenPGP systray icon (it’s actually not an applet) by an actual application with a dbus interface that could be triggered e.g. by a gnome-shelle addon. This will anyway be necessary if we drop gnome-panel for tails jessie.