[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libredwg] First release: what is missing for it?

From: Felipe Castro
Subject: [libredwg] First release: what is missing for it?
Date: Fri, 2 Aug 2013 08:46:26 -0300

That's my point. My intention in the beggining was in fact to create a read-only library. And that's why I'd like to see as soon as possible a read-capable first version.

By the messages and the status of the code, I understood that support for R2004 is the bottleneck rigth now, for releasing 0.4, ok? So, if it is so difficult to solve a bug in this, I would suggest to leave R2004 decoding ability to a next release, 0.5, for example. Why not? One have to start at some point.

2013/8/1 Duncan Lithgow <address@hidden>

May I humbly suggest concentrating on read quality? There are a number of CAD packages out there that would be able to make good use of read ability but would be fine continuing to export to their own format for now. This would build a relationship with the cad software people early on.


Sendt fra min vanilla Android mobil

On Aug 1, 2013 10:42 PM, "Avneet Kaur" <address@hidden> wrote:
On Thu, Aug 1, 2013 at 11:26 PM, Felipe Castro <address@hidden> wrote:
> Hello,

Welcome back.

> It's nice to see that people keep working on this stuff. I'm having a bit of
> time to dive into libredwg in these next few months, and I'd like to offer
> some help in order to reach a first release

We feel lucky that we got a chance to work with you.

> Isn't it to get a working and useful reading library for the early versions (R13, R14, R2000, R2004)? If
> it is working, why not to release just like that, an alpha version?

Library supporting these versions. But on parsing R2004 DWG file, it
throws segFault.
I think you should go through out once from previous mails to get an Idea.

> Next step, try to work out the writing capability?

Yes, agreed with you.
We have to concentrate on it's encoding functionality too.

> Next one, work on further versions (R2007, and so on)?

It is already in our GSoC milestones [0].

> I'm trying to understand the changes in the "refactoring" branch. I think
> it's mainly a matter of splitting the code in some smaller files. More
> include files to worry about, maybe it's worthwhile, if it brings more
> organization.

You can suggest any improvements.

>The doxygen stuff is cool also.

Thank you.

> And the r2007 stuff, I didn't touch it, too much for my brain now...

We will do now. :)


Er. Avneet Kaur

"Coming together is a beginning; keeping together is progress; working
together is success."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]