← Back to team overview

kicad-developers team mailing list archive

Re: Decoupling issues with python


On 08/13/2012 11:15 AM, Dick Hollenbeck wrote:
> On 08/13/2012 01:25 AM, Lorenzo Marcantonio wrote:
>> On Mon, Aug 13, 2012 at 12:15:53AM -0500, Dick Hollenbeck wrote:
>>> But since BOARD_ACTIONS could also stand alone, the scripting could use it in a form
>>> independent of PCB_EDIT_FRAME.  
>>> That might give you the best of both worlds then.
>>> Another nice thing about this design and plan is that it can be done evolutionary, i.e.
>>> over time.
>> Why should we use a class, 
> To hold the BOARD.
> SCREEN was on my todo list to kill off.  I saw no reason to have it common between both
> I even got permission to do that.

Anyways, I had given all this a lot of thought, because I could foresee these problems a
year ago or more.

The BOARD_ACTIONS class is my preferred solution, and it diligently implemented would mean
scripting is easier and you also can get rid of compiling things twice, because you can
park the process main()s on top of the DLL/DSOs, which is what should happen eventually.


Follow ups