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

List:       koffice-devel
Subject:    Re: OASIS file format for Krita
From:       Thomas Zander <zander () kde ! org>
Date:       2004-03-24 9:03:55
Message-ID: 200403241003.56525.zander () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I picked this email from the lists.kde.org archives after I discovered you 
were still in my blacklist; sorry for the wrong-threading..

JRT wrote:
> Thomas Zander wrote:
> >>Perhaps more of KOffice base libs can be put into the core libs? So
> >>that 
> >>standalone applications can be built usind KOffice technology, without
> >>actually be KOffice components?
> > 
> > 
> > You can't have one without having the other, so what's the point?
> > Naming? 
> 
> The point is what shipped with the suite.
The KDE project does not decide what is shipped with what; for example the 
debian packagers ship each application separate; its easy to install kword 
without kpresenter if you want.
So this is something you have to take up with the individual packagers, at 
best KDE can write a packager-guidelines file for koffice.

> It is perfectly OK to have  
> additional applications based on KOffice libraries.  But, Krita (and 
> probably Karbon14 as well) are becoming large artist's applications which 
> are not what the average office suite user needs.  No complaints at all 
> about the existence of these applications.  My point is that the suite 
> needs to ship with a simpler graphics application that can do simple
> stuff  
> for DTP and presentation slides.  That is: Artist != Office-Suite-User. 
> Office-Suite-Users do not need DSP (convolution) based water color
> painting  
> simulation -- it is nice but not needed by this class of user.

Ok; that might be a reasonable assumption; but I fail to see why we should 
dumb-down the office-suite because users won't use features; we just have 
to make sure that the simple things stay simple usability-wise. What 
concerns me more is that the simple things should be possible in the first 
place. With this I mean that we should not make the mistake that artsd 
made; create a really nice app that does lots of thins quite-ok, but fails 
to do the thing most users use it for really well.

This is a challange that is solved per application; not by excluding some 
applications because its too feature rich.

Hope that makes sense.
- -- 
Thomas Zander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAYU77CojCW6H2z/QRAg8BAJ9TaXwiwj0Ox67M8GUVw+Wfrd6y/QCfdqik
Nhxp2xP7txmOqnEzkk53Kgg=
=2ms2
-----END PGP SIGNATURE-----
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

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