Recently I've been working with a 3rd party diagramming library written in windows forms. It's been great and it's pretyt fast in building 80% of the applciation I'm working on.

However

I did say 80% yeah.. so, what of the other 20%, well one of the problems is that it doesn't support embedded diagrams and drill down. I can live with this for now, but in future they will become very important.
So, what to do?

Choices

• Buy the source code for existing library

• Write my own

Purchase

Cons..

The problem with this is an unfamiliar code base and it's probably already not the ideal architecture.
I've already replaced the node drawing with my ow GDI+ code with some custom code.
The pros..

Pros..

It got a team of dedicated developers...

Write

Cons..

Ain't got the foggiest how :-)

Pros..

If you're someone like me, for whom coding is more a hobby than a Job.. you'll understand..
If you're not someone like me..then.. read the blog from someone that can actuall spell 

Baby steps 

Lets start with something very easy..

Designer surface..

 Live demo will be here HERE

Stay tuned... "Diagramming"

About Brian Keating

Professional Software Developer, .NET / C++ / Java View all posts by Brian Keating →