[Uml-devel] RE: karbon/umbrello

rwlbuis at xs4all.nl rwlbuis at xs4all.nl
Tue May 6 13:49:22 UTC 2003


Hi, 
 
>i'm resurrecting a discussion from about a month ago where i'd decided
that  
>the next version of umbrello (the uml app in kdesdk), needed a much nicer  
>drawing framework than, say, a standard canvas. i've been over alot of  
>different possibilities, but ended up with karbon as the drawing
framework.  
>it seems to be capable of everything we need it to be capable of. 
 
Good :) 
 
>i'm finally at a point where i can start prototyping the diagramming
stuff,  
>but had some technical questions that i haven't been able to easily
resolve.  
>umbrello is not a koffice application. it looks like the constructors for
the  
>koffice parts (KarbonPart in particular) seems to require a fair bit of
the  
>koffice framework in order to instantiate the part - which i don't think i

>can provide. that said, is it possible, then to reuse a koffice part in an

>application that doesn't support koffice? or am i just dreaming? 
 
David already answered this... 
 
>if its not possible to do this, the other option would be to use the V*  
>frameworks in karbon's core and supporting libs. unfortunately, the
makefile  
>doesn't really include these for installation. moreover, i don't think the

>core is really meant to be a standalone development environment. iirc,
there  
>was some talk about refactoring karbon's core to provide something like
that.  
>i'm hoping there is because i don't really feel like trying to make
umbrello  
>a koffice app just yet. this _is_ my first qt/kde program :) 
 
Yes it was not intended as a shared lib from the beginning. OTOH its
reasonably abstracted 
and just oriented towards vector graphics (hence the V :)). 
That said, I suppose it could be made a shared lib. To make that work we
would have to 
define useful, common base classes like VObject, VPath, VText, VGroup etc.
The apps 
can then build on this, for instance karbon builds on VPath/VComposite the
shapes 
VEllipse, VRectangle etc. etc. 
So I guess first step would be seperating the common (base) classes and the
app specific 
classes built on top of them. Keep in mind kivio (visio like koffice app)
may want to use 
the base classes as well. 
Maybe next step could be, determining minimum rendering properties 
(fills/strokes/gradients/hatches etc.). And after that, maybe exact demands
on the canvas, 
as I doubt VCanvas currently is optimized enough... 
Cheers, 
 
Rob. 

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .






More information about the umbrello-devel mailing list