UserManager: test possibility to remove an user

[GoogleCodeExporter]

Create X user,  go to UserManager try to remove users.

Original issue reported on code.google.com by eric.mae...@gmail.com on 19 Nov 2012 at 7:32

[GoogleCodeExporter]

The usermanager has some weird behaviours.
When deleting a user (according to your question), the user gets deleted, but 
after restart of FMF an empty line is there in the list. So it's somehow still 
there.

What bothers me as well is that the workflow is VERY broken.
* there is no way to show if a user was modified (* sign etc., button enable 
state changed, ask user when another user is clicked if he wants to save)
* if no user is selected (at beginning) the viewer still shows some data?!?
* if one or more users are deleted the user is asked to save, and if he presses 
discard, the users are deleted anyway (but stay empty in the database, see 
above)
* only after adding/removing a user the Admin user gets red

...

Original comment by christian.a.reiter@gmail.com on 19 Nov 2012 at 9:56

[GoogleCodeExporter]

You're right the UM needs a nice refactoring.
Something fresher, easier and cleaner. 
Let's start to find a way to present the UM first, define the workflow for any 
modification and start coding...
UM is an old code ~ 4 years

Original comment by eric.mae...@gmail.com on 19 Nov 2012 at 10:37

[GoogleCodeExporter]

Yes, I'm just digging in the UM code and it's really not the cleanest...

What disturbs too is that there is a separate view of user properties (Agenda, 
Documents, etc) that is a second row when viewed in the Options page.

So this should be done with the options page reworking as well - ther MUST not 
be two rows of treeviews!

Original comment by christian.a.reiter@gmail.com on 19 Nov 2012 at 10:42

[GoogleCodeExporter]

UI could be (gnomish'd)
+-----------------------------------+
+ Actions                             Search             +
+-----------------------------------+
+ User      |     Something like the control    +
+ List        |  center in gnome                      +
+ View      |                                                 +
+              |                                                 +
+              |                                                 +
+              |                                                 +
+-----------------------------------+

Secondly, may be we don't need to include the full user manager directly inside 
FMF, but better as a standalone app. And inside FMF just keep a "personal 
widget".

This is many work, time and code/debug...

Original comment by eric.mae...@gmail.com on 19 Nov 2012 at 10:43

[GoogleCodeExporter]

Ok, I second that there should be no user manager directly in the FMF main app.
But what to do with the part applications like FreeAccount - there is a user 
manager needed if it is run as standalone app.
Hm, and I am not sure about having a second app just for user management?

Maybe we create an app for general Management of FMF - isn't FreeToolBox 
something that would serve that purpose? We could include the user management 
there?

But keep it in e.g. FreeAccount as plugin?

Original comment by christian.a.reiter@gmail.com on 19 Nov 2012 at 11:00

[GoogleCodeExporter]

Original comment by eric.mae...@gmail.com on 11 May 2013 at 10:16

• Changed state: Fixed