[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: User Resources
From:       Johan De Messemaeker <johan.demessemaeker () telenet ! be>
Date:       2005-08-22 14:44:37
Message-ID: 200508221644.37845.johan.demessemaeker () telenet ! be
[Download RAW message or body]

On Monday 22 August 2005 16:22, Zak Jensen wrote:

> It could do that, but there are other arguments for making all of the
> data available elsewhere:
> 1) Better integration among desktops (e.g. reading Kopete logs in gaim)

I have to admit, I haven't thought about this on previous posts since I don't 
care about other desktops. But it is a interesting point that could be 
usefull for a range of users.

> 2) Easier for "power users" to figure out where everything is. (For
> those who want/need to know).

The only difference I see between our two points is that I propose default 
values through automatic registrations. Power users can still have access to 
proper tools to adjust these settings.

> 3) It removes complexity from the system. (seems like a cleaner system)

Not from a usability viewpoint. If the app registers itself as a program that 
has backupable data, the user doesn't need to know about _ANY_ directories or 
locations or whatever.

> Note that "application created data" does not include config data... I
> was going off of the definitions that you stated in a previous post.

I know. I made those definitions like that because I think it would be 
beneficial to be able to easily backup/clone all three kinds of user data 
seperatly.

I haven't seen any stuff on FreeDesktop yet but I'll read some later.

The way I saw it was kinda daemon-like. A 'backup' daemon runs and listens to 
actions:

- programs that want to register themselves
- programs that just created application created user data (eg, Quanta created 
a new project 'SampleWebsite')
- programs that want to use the daemon information to read the information for 
mutiple purposes (can be backup, cloning or even documentation generation if 
defined for that type of data)

Since it's a daemon, it's already desktop independent. Application developers 
could easily define the rules of the application in eg a XML description 
file.

Just thinking out loud here :P

Regards, Johan
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

[prev in list] [next in list] [prev in thread] [next in thread]