[Netron-graphlib] Re: Weekend

[Martin C. <mar...@ei...>]

Good Morning Francois,

Okay so we chuck out MagicLibrary, fine by me. Send over a ZIP file when 
your done and I'll incorporate it into CVS :-)

I'll leave the module aliasing alone for the moment. Let's get things 
stable first.

Source code control systems aside, intentionally checking broken code 
into a repository is bad form. We've all done it in error at some point, 
i.e. we thought the code worked. I think Visual Studios integration with 
   SourceSafe can sometime force you into thinking, I must checkin in 
case I loose something. Also SourceSafe doesn't handle conflicts or 
multiple people working on the same file. I use both source code control 
systems on a daily basis, SourceSafe in work for our own code, CVS at 
home or when dealing with open source projects. Hell I've even started 
to tinker with subversion. I have no problem managing the repository in 
my spare time, but I would be great if you could get up to speed too :-)

GraphML support will probably take more than two weeks as I won't be at 
it full time. I think we need to discuss layouts and decide which ones 
to implement and in what order. From what I've seen when looking at this 
before, is that some algorithms are just variation on a theme. We could 
look at coding the algorithms in 'families'?

As regards your summary below what are you working on, or more to the 
point what do you want me to do? I need item one implemented for the 
start of this week, but if you've already done some work on it, I don't 
want to duplicate the effort.

BTW: I don't know if you realised but most of the mails you've sent were 
  directly to me. If your intention was to send to the list make you 
send it to net...@li....

Regards,

Martin

Illumineo wrote:
>  
> 
> Morning Martin,
> 
> 
> Docking again. My intention is to drop the Magic lib altogether. The reason
> it's still present in NAF is because it is not re-written yet in function of
> the DockPanel. Not too much work but hasn't been a priority since preview 4
> of NAF for me.
> 
> CVS module aliasing. I'd say: keep it as simple as possible. The graph lib
> is an integral part of NAF and I did quite a bit of efforts to have it
> bi-valent, i.e. a control for everyone and a control inside the framework.
> How much people are interested in using the graph control inside NAF is
> another issue...at least I try to make it work.
> 
> WIP (work in progress) and CVS. You are right I suppose about having things
> compilable if in CVS. Regarding this I have always seen 'releases' as true
> intermediate units and not CVS modules. Whenever I download open source
> stuff I always take releases and never use the CVS but I suppose I've the
> wrong perception. In my professional life people dump code in VSS in any
> state: buggy, finished, half-started...It's an agreement and I tend to think
> that the CVS community and the VSS community are different kind of people.
> This says nothing about values of course, merely an observation. 
> If I can be totally honest with you, I'd rather prefer to leave everything
> CVS to you. 
> 
> New features. I would not mind to integrate your code (or whoever submits to
> Netron) and deliver it as part of V2. You are probalby aware of the
> difference between V1b and V2; undo/redo, intermediate connectors in
> connections, ...I took one step back to go two steps forward. I believe the
> code is now much cleaner than before and I rewrote quite a bit. The custom
> connection where somewhere around in v1b but not well implemented. If you
> have code for GraphML and/or layout, let me know. Try to estimate how much
> time it'll cost, more than two weeks integration is too much. I hope Helge
> will pop up with some VB.Net code but I'm not sure. Recently a funny guy
> said he got Netron working in ASP.Net (see the blog), maybe an example of
> this would be nice too.
> 
> 
> Let me summarize:
> 
> 1. User defined connection, we go for it. 
> 
> 2. User definable context menu on an Entity/Shape, we go for it. 
> 
> 3. Make Entity/Shape mouse aware, we go for it.
> 
> 4. Clean CVS. You take care. A compilable cvs module should now be
> available, the next one will contain the new items above.
> 
> 5. Time estimation of GraphML and layout. Not a must for V2.
> 
> 
> 
> What and how do you use the graph lib by the way (curious about the bias)?
> In a professional context?
> 
> I am writing a technical paper for the moment about the lib, not much coding
> these days. Well, that's not true; I am coding but not related to Netron.
> 
> 
> 
> Have a nice weekend!
> 
>