X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 9 Aug 2016 13:28:22 +0000 From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] [pcb-rnd] release 1.1.0 Message-ID: <20160809132822.GO12988@foo.stuge.se> References: <20160808102438 DOT 12df1886 AT jive> <362971c9-89a9-d628-21ce-4e18349cf95a AT prochac DOT sk> <20160808225137 DOT GN12988 AT foo DOT stuge DOT se> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk gedau AT igor2 DOT repo DOT hu wrote: > > Are the file format plugin systems in pcb and pcb-rnd compatible? > > Nope. > > > If not, why not? > > My goal with the io_* plugin was not only to allow multiple file > formats but to make them plugins. I understand. How does it look if we ignore the plugin implementation(s) and only look at the semantics of file format abstraction? > Pcb-rnd has an improved plugin system in place Cool, but orthogonal to abstracting file formats. The file format abstraction can and would be useful to have compatible between mainline and pcb-rnd IMO. > I especially don't think that big infrastructural changes like the > improved plugin system (that heavily depends on the build system) > would ever hit mainline. I'm much more focused on the semantics and behavior of the file format abstraction. Sorry, I could have made that more clear by not mentioning plugin in my original message. Thanks! //Peter