Bob wrote:

> The only solution I see is to move to a more formal fixed 
> format than PGML for which we need to make a reader and 
> writer that will be modified for each version. The logical 
> choice with be the OMG diagram interchange format but I was 
> hoping not to do such major change for a long time.

This is 180 degrees out of phase with my thinking.  I'd like to get to a
standard diagram interchange format as soon as its feasible and there are a
reasonable number of tools that support it.  I think we're almost there with
a community of supporting tools and certainly will be longer before we can
get our transition support implemented, so the real gating factor is the
lack of open source library support for UML 2.x.

> But it seems we have a catch 22. The requirements is to 
> stabalise the persistence format but in order to do that we 
> need to change the persistence format.

The transition to UML 2.x Diagram Interchange is one that we know we're
going to have to make.  What I'd like to see eliminated is any changes which
are not on a direct path to that goal.

> As a slight aside. There has been some talk a couple of 
> months back about moving to ArgoUML 1.0.
> 
> To my mind the most important thing for that release is not 
> the bug count but a stable and formal API and persistence 
> format. I think we have some way to go for that. Is that what 
> we should be concentrating on now?

The API is only important to plugin developers, and it only has to be stable
if we claim it's stable.  I think I've come to the conclusion that we've
painted ourselves into a corner with the combination of an implicit promise
of stability, an overly large API surface area, and insufficient review.  We
might be better off just explicitly warning plugin developers that all bets
are off until we explicitly publish the API.

End user quality is higher priority in my books (but I'm not sure how well
correlated it is with bug counts on Tigris).

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to