Hello Sean! Thank you for your feedback.
> The only technical concern I immediately see is that there's an implicit risk > assumed. Namely the use of the GOBLIN library is an unknown quantity since > we've not worked with it before. There should be some evaluation time > allocated and a contingency plan in place should it not work out for whatever > reason. Just to make sure, the purpose of one of this graph libraries is to help me in applying graph algorithms for the interactive part of the application. GOBLIN got my attention because it was mentioned in the description of the project and after a bit of a discussion with Cliff Yapp it seemed to me that it would be useful. You are right, I should allocate some research time to dig deeper and see if it's a doable plan. As alternatives, I've also considered working with the Adaptagrams library, http://adaptagrams.sourceforge.net/ or with the Open Graph Drawing Framework library, http://www.ogdf.net/doku.php, but these would also imply the same steps as the ones mentioned in the GOBLIN case. A contingency plan that I'd take into account would be to use the Boost Graph Library (BGL), http://www.boost.org/doc/libs/1_49_0/libs/graph/doc/index.html, for the usage of graph algorithms in the interactively display scenario. Do correct me if I'm wrong in any of these affirmations. Best regards, -- Cristina Precup ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
