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

List:       koffice-devel
Subject:    Re: kivio+karbon? [Grouping of applications in Koffice]
From:       Jaroslaw Staniek <js () iidea ! pl>
Date:       2005-12-14 22:38:59
Message-ID: 43A09F03.6050108 () iidea ! pl
[Download RAW message or body]

Martin Ellis said the following, On 2005-12-14 18:16:
> I'm lost.
> 
> Here (and above in the thread), you seem to be advocating a merge:
> 
> On Wednesday 14 December 2005 16:49, Jaroslaw Staniek wrote:
> 
>>It is not the UNIX way only if you've assumed 'drawing diagrams with
>>connector lines/putting floating text boxes/using stencil libraries'
>>feature set is _different_ from just drawing app. I believe it is not.
> 
> 
> Yet here, you seem to mock the idea of having drawing and diagramming in the 
> same app:
> 
> 
>>Bezier curves in diagramming app? LOL. This is a bit like Mac Shareware
>>style (or even commercial app style) like "pack it with any features that
>>force customers to upgrade".
> 
> 
> Confusing, huh?

It was ironic, read my recent reply to Casper (point 3***.)


[....]

>>Do I need to run Kivio in addition to Karbon? 
> 
> 
> Guess that depends on what you want to do.  :)

To do the same as in Draw: connect obejcts with an arrow. (this is only example)

>>It's your Kivio and Karbon devs, decision, but so far, no single customer I
>>contacted and supported, complained to me about oo.org Draw allowing them
>>more than what they want to achieve, not being splitted to parts and so on.
>>As mentioned before, either Kivio and Karbon can be seen as tools for
>>creating content embeddable in larger documents.
> 
> 
> That said, I've never heard anyone complain that Visio was a standalone 
> application....  

Cannot see the point for this example as until recently MS had reasonable no 
vector drawing app...

 > it's clear that neither of us have any evidence to indicate
> whether drawing/diagramming functionality should be in the same app or not.
> 
> Seems this has turned into another thread we can't solve without some 
> convincing usability testing ... :o(

Most used vector drawing and diagraming app from FOSS universe, merged these 
features into one app. My point was that:
1. IF this doesn't hurt usability, we can do the same at this point when 
changes to architecture of both apps are planned.
2. IF this hurts usability, what (at least) about sharing the same project and 
just building two versions kivio/karbon of the same main application shell.

There are no (known to me) decisions like 'whether Kivio will keep its own 
file format or entirely go with ODF?'. Without that being cleared, above 1./2. 
choice is still open.

-- 
regards / pozdrawiam,
  Jaroslaw Staniek / OpenOffice Polska

  Kexi Developer:      http://www.kexi-project.org | http://koffice.org/kexi
  Kexi Support:        http://www.kexi-project.org/support.html
  Kexi For MS Windows: http://kexi.pl/wiki/index.php/Kexi_for_MS_Windows
  KDE3, KDE4 Libraries For Developing MS Windows Applications:
                       http://www.kdelibs.com/wiki
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]