[Uml-devel] Refactoring the code base -- what should be done?

Oliver Kellogg Oliver.Kellogg at t-online.de
Thu Sep 23 23:34:11 UTC 2004

On Thu, 2004-09-23 at 08:54, Pekka Jääskeläinen wrote:
> Is this list a complete TODO list to get Umbrello to the wanted design?
Not at all. I see two approaches: Gradual evolution of the
current Umbrello code, or redesign from scratch.

> IMO it would make sense to keep the model as portable as possible and
> have minimal logic in the UI code.

Agreed. I think this is doable even with the evolutionary approach.

>  The layouting algorithm could be
> portable too. Isn't it about drawing to a canvas and receiving events
> when certain components are selected. It would be great if most of the
> code could be easily ported to other environments than Qt.
That might be difficult.

> Would it make sense to go the other way around with this? I mean not
> trying to think how Umbrello could be changed, but think about how the
> high level architecture *should* look like, and then think which parts
> of the current Umbrello code base could be used in the new design?

Yes, but IMHO it helps a lot to first have an in depth look at the
existing implementation (Umbrello), and work out an exact critique of
what needs improvement or redesign. Doing that will help arriving at a
qualified decision on whether to go with evolution or revolution.


More information about the umbrello-devel mailing list