Re: [Pythoncad-developer] Pushed many changes to the R38 branch

[<ger...@gm...>]

Hi Yagnesh,

There are not many changes made in the Generic part of PythonCAD.
I think you can still push your modified code into the repository.

A while ago I had a discussion with Matteo about blocks.
The idea was to create some special layers, each of the layer could contain  
a block definition.
The layers are not shown in the layer manager, they just have a block  
definition function.
This is just an idea an has not been worked out yet.

The hatch, ellipse and other entities are also on the list.

You are right it is easier to work with standard fonts.
Otherwise we can look at the *.cxf font definition files used by QCad (I  
don't know the license of this format), this is a vector format.
QCad uses dxf as its native file format so these fonts has to mimic the  
AutoCAD fonts as good as possible.

Regards,
Gertwin



On Jan 12, 2010 2:54am, Yagnesh Desai <yn...@gm...> wrote:
> I understand that you are in middle of reorganizing of

> code for better performance.



> I have started writing the code for import/export of color

> to & from dxf. I am writing it on my earlier git download

> hope should have no issue with the new organized code.



> On the loss of blocks and entities during the import if

> pythoncad can support similar blocks it would be lot

> more easier. (block is handy tool for the CAD user too)

> (Hatch, ellipse & splines are few entities currently

> not available in pythoncad)



> Issue with text is multifold :

> 1. Autocad fonts are proprietary and we will have to leave

> with some adjustment of width and height (by the way AutoCAD

> supports width-factor adjustment if that can be supported

> life becomes a lot more easier with the truetype fonts also)

> 2. Autocad formating is a bit funny since it was taken from

> older way of doing it ie %%u is a tag in text for underlining

> %%b & many more and now with newer version of dxf they

> even have tags in between to change fonts for few words

> in para.

> 3. Dimension text also has some such issues as they have

> some block like behavior. (This I have not yet gone in depth

> since I have not come on dimension).