kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #08828
Re: Decoupling issues with python
On 08/15/2012 12:21 AM, Lorenzo Marcantonio wrote:
> On Tue, Aug 14, 2012 at 04:39:40PM -0500, Dick Hollenbeck wrote:
>> We have polymorphism posturing across process boundaries, and of course that cannot work.
>> So why a base class with virtual functions, e.g. BASE_SCREEN?
> We also have the common code built differently depending on the user
> unit for pcbnew and eeschema, too :(
This is fine, my idea in fact. CERN is paying to have this done, it is just another stage
in decoupling.
The things that need to be common should be pulled out into finer granularity classes like
GRID rather than BASE_SCREEN.
Or made into templates.
References
-
Decoupling issues with python
From: Lorenzo Marcantonio, 2012-08-12
-
Re: Decoupling issues with python
From: Miguel Angel Ajo Pelayo, 2012-08-12
-
Re: Decoupling issues with python
From: Dick Hollenbeck, 2012-08-13
-
Re: Decoupling issues with python
From: Lorenzo Marcantonio, 2012-08-13
-
Re: Decoupling issues with python
From: Dick Hollenbeck, 2012-08-13
-
Re: Decoupling issues with python
From: Dick Hollenbeck, 2012-08-13
-
Re: Decoupling issues with python
From: Lorenzo Marcantonio, 2012-08-13
-
Re: Decoupling issues with python
From: Dick Hollenbeck, 2012-08-14
-
Re: Decoupling issues with python
From: Dick Hollenbeck, 2012-08-14
-
Re: Decoupling issues with python
From: Lorenzo Marcantonio, 2012-08-15