On 11/29/2017 06:21 PM, Tomasz Wlostowski wrote: > On 30/11/17 00:18, Wayne Stambaugh wrote: >> Hi Andreas, >> >> Per our previous conversation, if you want to write your solver in C++, >> then I would prefer that you do it as part of a solver plugin rather >> than a command event handler in Pcbnew. I image there would be other >> uses for a solver plugin object such as a thermal mapping solver which >> has been proposed in the past. The other option would be to use the >> Python action object and write the entire solver in Python rather than >> C++. That may make your life a bit easier. >> > Hi Wayne, > > I fully agree about the C++ part, but I would object doing it in Python > given the current state of pcbnew's Python support. It's not mature > enough IMHO to allow development of large plugins.
I agree but something like a signal integrity solver would definitely shake out any weaknesses in our python support. > > BTW - I guess the plugin part is rather trivial compared to the actual > solver, which I believe is not Kicad-dependent? Besides the plugin loading and unloading, the only method I could think of is Solve( const BOARD& aBoard ). Maybe a rendering method to display the results of the solver but that would outside the board rendering. It will be interesting to see were this leads. > > Cheers, > Tom > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp