Re: Support for callbacks...

[Krzysztof Foltman <kfoltman portal onet pl>]

James Michael DuPont wrote:

>Basically what I would like to help here with is making a  clean object
>model for scripting dia, and on the basis of that create a very
>abstract API that can be used for network based and non-network based
>applications.
>
I'd prefer basic usability first, fireworks (like scripting and 
collaboration) next. What's the use of network editing-capable diagram 
editor if it doesn't do basic things well enough ? (well enough = 
[almost?] as comfortable as commercial counterparts).

While big goals like adding scripting are a real challenge and add a lot 
to the program's value, they also get in a way when the priority is a 
bug free release that general public can use (and I've got the 
impression that that's where Dia is so far). So far, a general public is 
not complaining about lack of scripting or collaboration - we're mostly 
complaining more about things like inconsistent dialogs, imperfect shape 
library, lack of autorouting information in some shapes, assertions 
failures and many other minor annoyances.

However, both scripting and network editing seem to be good candidates 
for 2.0 - and it looks like the research/design phase is going to take 
quite a lot of time - doing locking, change propagation and conflict 
resolution properly seem to be worth months of work.

Just my 0.02PLZ worth of rant.

Krzysztof