kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxxxx>]

On 10/7/2010 6:26 PM, Dick Hollenbeck wrote:
> 
>> (part REFDES is PLID
>>   (at X Y)
>>   (rot 0)  # make this optional, defaulting to zero
>> )
>>   
> 
> 
> Schematic component instantiation:
> ---------------------------------
> 
> I don't know that "part" is best, and there may be a better name.
> 
> But what I see from this, unless there are holes in the concept, is that
> there need be *NO location information* in what we have been calling the
> component, nor any rotation information.
> 
> That can be introduced in the part C++ PART class for the very first
> time.  The graphics primitives in the component have their coordinates,
> but those coordinates are relative to the component's origin, not any
> thing beyond that.
> 
> 
> The component is located and rotated [and mirrored] when it is
> instantiated within a part.
> 
> 
> class PART
> {
>     COMPONENT* component        // points into the parts list
> 
>     POINT pos;
> 
>     wxString  reference;
> 
>     int angle;
> }
> 
> 
> Something like that.  Maybe also mirroring support at the PART level. 
> The get bounding box function delegates to the COMPONENT, and offsets
> and rotates the result of that box to the region on screen.
> 
> Are part and component properly named?

I can't really think of a better one.  Generally speaking, you think in terms
of adding components to your schematic not parts.  At the user level you should
use the term component but internally you could differentiate by defining
components similar to the way we do now which is LIB_COMPONENT ( your
COMPONENT) and SCH_COMPONENT ( your PART ).  But I'm not sure this is any better.

Wayne

> 
> Dick
> 
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>