Hi.

The moonshot-ui package is now available in the
repository.project-moonshot.org repository.
If you boot the dvd image you can do
sudo aptitude update &&sudo aptitude install moonshot-ui

You'll probably have to reject the first alternatives and instead accept
upgrading a lot of GTK to unstable/experimental.  I can build against an
older GTK, but I didn't have the build environment for stable i386
handy.

Kevin Wasserman, who is doing the windows port, and I walked through the
UI to see where it is.


The best performance  can be seen  if you start by running dbus-client
from the terminal.
Dbus-client is a test program. If you run it, the UI will pop up.

We noticed a few usability problems off the bat:

1) It's not obvious that you are being requested to choose an ID card
for an application

2) You don't know what service you are authenticating to

3) In our configuration, the ID card was issued by "local": we're using
the steve@local account described on the wiki.  It was not obvious to
Kevin that local was an issuer nor that the Id card was an ID card.


If you select the identity card  and hit send,  the UI disappears and
dbus-client exits with an error that the selected identity card had the
wrong NAI, service or password.

Now, that behavior doesn't make sense; I've described that in the thread
about RPC documentation.  If the NAI doesn't match, the user never
should have been offered the Id card.  If the password doesn't match,
I'm not entirely sure what we do, but it shouldn't be fail. Probably
return the password the application provided.  If the user selects an Id
card that ID card should be enabled for the service in question.
Remember a service is something like [log in to unmask] specific
instance of a protocol running on a well defined host.

We then began to play around with things.

The following work flow did not behave as expected.

* Start with no UI running and the steve@local identity configured

* start moonshot
* Select file->add ID card
* enter  information and click save

* The application crashed with a glib error trying to allocate close to
  maxint storage. So some sort of integer overflow


Other flows:

* Start Moonshot

* start dbus-client. Notice that the moonshot UI doesn't change at
 all. You cannot  distinguish using moonshot-ui for things like viewing
 details and adding/removing a card and using it called by an
 application.



* Start moonshot

* Hit send; you get an assertion failure that is non-fatal

* Send should not appear if there is no one to send to



* Start several dbus-clients

* Kill some of them

* Some of your sends will not cause any effect because their clients are
  dead

* Requests probably need to be removed if the client goes away. Also,
  knowing which service is involved will help



* We viewed the details of the steve@local identity. Even though  the
  password field was filled in, the remember password checkbox was
  unchecked.



* What's the point of being able to type in a password on the add an
  identity screen if remember password is not checked?




* The search box on the first screen is non-intuitive. At first Kevin
  thought it was some sort of command line.

In conclusion, we were able to get none of the expected functionality to
work, although we did come reasonably close selecting the local identity
and sending it.