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

List:       kde-devel
Subject:    Re: KDE rough edges - file-types in KDE 3
From:       Christian Loose <christian.loose () hamburg ! de>
Date:       2007-09-20 16:35:52
Message-ID: 200709201835.52689.christian.loose () hamburg ! de
[Download RAW message or body]

On Thursday 20 September 2007 13:06, Aaron J. Seigo wrote:
> On Tuesday 18 September 2007, Ian Wadham wrote:
> > I am sorry this post has been so lengthy, but I hope you have had
> > a few laughs and I really wanted to get across some flavour of
> > what KDE can be like for a first-time user.  And that *is* a matter for
> > developers to consider IMHO.
>
> so if i cut through everything here, i see exactly three concrete issues
> you raise:
>
> - finding file associations; action items might include:
> 	- how easy *can* this be made?
> 	- what are all the ways available now?
> 	- is this documented in a place people can find said documentation?
> 	- write patches to make it more obvious in line with the three Qs above
> 	- is it easier to find right now in kde4's systemsettings vs kcontrol?
> - setting file associations
> 	- write a patch to concretely improve the file associations dialog
> - listing of attachments in kmail
> 	- right now there is a list possible, but it isn't easy to find in the
> config - write a patch to move the inline attachment list (View ->
> Attachments -> "As Icons") to just underneath the header; perhaps change
> 'As Icons' to simple "list". this won't remove all need for the structure
> viewer as that is there for more hard core security requirements AFAIK, but
> would be a nice improvement and would be pretty easy to do.
>

- (IMHO) in addition to xdg shared-mime-info we also need mime actions 
(http://www.freedesktop.org/wiki/Specifications/mime-actions-spec). This way 
we can separate viewers from editors and KMail wouldn't open jpegs in gimp 
anymore.

no patches attached ;-)

Christian
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]