Re: [libredwg] GSoC: Setting stone rolling

[Rodrigo Rodrigues da Silva]

> Moreover regarding my project I want to know what functions are to be
> made. I mean what functions user should get. I had decided a few, I
> will be showing an example in a day or two. Please could you list some
> which you wish to see for the API, I would be very thankful to you.

You can start scratching a .h file (that could be a patch to dwg.h,
actually) with some function prototypes, not the code itself. dwg.h
has some api-like functions already.

Take a look at this GRASS plugin [0] that I wrote some time ago, it
should give you a user perspective. You can also look at the DWG part
in QCAD 3.1[1][2]. They use Theiga (new name of OpenDWG non-free
libs), which has a very ugly API, but that might give you some insight
as well.

In fact, after taking a look I didn't find any DWG related code within
QCAD's git repo, despite they saying that the DWG plugin would be
included without the Theiga library. Anyway, the DXFLib API [3] might
be a good start. Just be cautious and avoid bloating the API.

[0] https://svn.osgeo.org/grass/grass-addons/grass7/vector/v.in.redwg/
[1] http://qcad.org
[2] https://github.com/qcad/qcad
[3] https://github.com/qcad/qcad/tree/master/src/3rdparty/dxflib/src

-- 
Rodrigo Rodrigues da Silva

http://metamaquina.com.br
http://garoa.net.br
http://polignu.org
http://gnu.org