Dear Fernando, The implementation will be based on half-edge scheme. However by using Boost.Intrusive adapters, it would be possible for our algorithms to use the BGL representations as well. When talking about the 2D we mainly talk about the combinatorial information, so I'll say its the topology (if this is what you mean by topology). Thank you (and others), its really great to get this much interest from the community. huseyin On 4/13/07, Fernando Cacciola <fernando_cacciola@hotmail.com> wrote:
Dear Huseyin,
Dear Janek,
" Regarding the specifics of this project, what I propose to do in a summer is a limited scope Boost library for 2D mesh and polygonal environments, where I will mainly concentrate on the combinatorial information and primitive geometric operations. Thus the proposed library should more aptly be called Boost.2Dmesh than Boost.Geometry. Note that there would very likely be comments as to the incompleteness of such a "geometry" library, since I will not cover application domains like windows / GUI, computer vision, computer graphics (beyond the simple 2D subdivision), etc. By purposely limiting myself to the scope described above, I would provide a foundation for representing and manipulating planar subdivisions which is already a huge help for people writing geometric applications. It is a very common task and having both a representation and generic algorithms (which can adapt to user representation as well) suits the design principle of generic libraries very well. "
Then I assume you will present the mesh as a form of graph and build it on top of the Boost.Graph library, where the geometric embedding is realized trough graph properties.
In that case though, Boost.MeshGraph is probably more descriptive.
Btw, what is the 2D? The topology or the geometry? Or both?
Best
Fernando Cacciola
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost