Re: [Pythoncad-developer] Proposal geometry objects

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

OK, I see what a balloon is.
We can implement this as a block that contains a attribute variable.

I agree with you that we first do brainstorming about what entities to  
support and later decide how to implement these entities.

Yes please add a page to the wiki with all entities.
Maybe it is useful to create a link for each entity to its own page.
On that page we can describe this entity (functionality, how it is  
implemented, etc.).
This can also act as documentation for new developers.

Regards,
Gertwin



Op schreef Matteo Boscolo <mat...@bo...>:




> > 11) Is Polygon/Rectangle needed, this is a special form of a polyline.

> > There must be a tool for the user to create it.

> > Internal it is a (closed) polyline.

> ok but tu store this like polilyne we will have some trouble during

> filler or trim operation

> so will be better to have four Segment instead



> > 13) + 14) + 15) + 16) These are all the same.

> > A symbol itself is a entity.

> > A Marker, Arrow, section symbol and a Welding symbol are two instances

> > of the same symbol entity.

> > We need symbol definitions that defines how the symbol looks like.

> > And we need symbol references that is a instance of the symbol

> > definition.

> >

> > 18) Is layer an entity?

> > I thought it is more a entity attribute.

> > A layer itself has no visible representation.



> > 19) Is Label not the same as text?

> > What is the difference?

> For my point of view label is a text with an arrow



> > 20) What is a Ballon?

> Ballon is a number of letter inside a circle or a square with an arrow

> attached that indicate the position of the ballon

> it's used for mark a group/block

> 21) titleblok

> 22) part list

> this two culd be a block rapresentation







> >

> > I think we should keep the list of entities as short as possible.

> this is right,



> what I want to do with this list is to define all the entity that we

> want to support in pythoncad and find for each of it the right

> rappresentation.

> It'like a brain storming to do not miss any entity and have the right

> solution for pythoncad.







> so as i suggest in the starting mail,

> Those are the step to go on with new kernel implementation:

> 1) get a list of all the entity that we need in pythoncad

> 2) describe it with a schema like you have done in this e-mail

> 3) describe how any entity will be described in the database

> 4) start create the kernel with the database

> 5) start convert pythoncad for the new kernel





> may be is better to create in the wiki all the entity that we will be

> support .





> Any Comment ?



> Regards,

> Matteo