Re: [Kicad-developers] New eeschema file format

On 8/3/2016 2:34 AM, Sergey A. Borshch wrote: > On 03.08.2016 05:12, Werner Almesberger wrote: >> Chris Pavlina wrote: >>> Very good point about the start/end points. eeschema doesn't currently >>> support that - it can't fill enclosed regions that are enclosed by >>> multiple graphical objects -

Re: [Kicad-developers] New eeschema file format

It wouldn't be difficult to add this to the file format. When this actually gets implemented in the UI is whole different matter. On 8/3/2016 6:04 AM, Eldar Khayrullin wrote: > What about the style of dashed and dotted lines? > It will be good if one can to set the template of dashes, like

Re: [Kicad-developers] New eeschema file format

What about the style of dashed and dotted lines? It will be good if one can to set the template of dashes, like dash=1mm and space=2mm( - - - -) or dash 3mm and space=2mm (--- --- --- ---). В Вторник, 2 авг. 2016 в 11:39 , Wayne Stambaugh написал: On 8/2/2016

Re: [Kicad-developers] New eeschema file format

On 03.08.2016 05:12, Werner Almesberger wrote: Chris Pavlina wrote: Very good point about the start/end points. eeschema doesn't currently support that - it can't fill enclosed regions that are enclosed by multiple graphical objects - but this would ensure it could in the future with minimal

Re: [Kicad-developers] New eeschema file format

Chris Pavlina wrote: > An external script was shared in IRC this morning that does this; I > believe the author intends to share it publicly once it has a bit more > polish. What sort of hints would you store? I think you mean this:

Re: [Kicad-developers] New eeschema file format

On 8/2/2016 4:18 PM, Sergey Borshch wrote: > On 02.08.2016 16:14, Wayne Stambaugh wrote: >> So far here is the list of new file format features I am planning to >> implement: >> >> - Pin and gate swapping and mapping (defined). >> - Differential pair definition (undefined). >> - Net class

Re: [Kicad-developers] New eeschema file format

On 8/2/2016 4:10 PM, Chris Pavlina wrote: > On Tue, Aug 02, 2016 at 10:07:25PM +0200, Clemens Koller wrote: >> Hi, Chris! >> >> [snip] >> >> I am not sure how to support version management easily regarding that. >> Timestamps can be quite annoying, when that's the only change. > > I just want to

Re: [Kicad-developers] New eeschema file format

On 8/2/2016 3:23 PM, Clemens Koller wrote: > Hello, Wayne! > > Below, I added some very visionary features which I have seen (more or > less miserably implemented) in some big design tools, which could affect > the file formats in the long-term view as well. > I am not sure if it's too early to

Re: [Kicad-developers] New eeschema file format

On Tue, Aug 02, 2016 at 11:18:11PM +0300, Sergey Borshch wrote: > On 02.08.2016 16:14, Wayne Stambaugh wrote: > >So far here is the list of new file format features I am planning to > >implement: > > > >- Pin and gate swapping and mapping (defined). > >- Differential pair definition (undefined). >

Re: [Kicad-developers] New eeschema file format

On 02.08.2016 16:14, Wayne Stambaugh wrote: So far here is the list of new file format features I am planning to implement: - Pin and gate swapping and mapping (defined). - Differential pair definition (undefined). - Net class definitions. (undefined other than what we have in the board file

Re: [Kicad-developers] New eeschema file format

On Tue, Aug 02, 2016 at 10:07:25PM +0200, Clemens Koller wrote: > Hi, Chris! > > [snip] > > I am not sure how to support version management easily regarding that. > Timestamps can be quite annoying, when that's the only change. I just want to quote this for emphasis. The timestamps are quite

Re: [Kicad-developers] New eeschema file format

Hi, Chris! On 2016-08-02 21:33, Chris Pavlina wrote: >> Maybe: >> + Support for schematic versioning / timestamping / diff- and git-friendly >> I want to see (ideally in a graphical representation), what's the >> difference of two schematics on logic/netlist level as well as visually >>

Re: [Kicad-developers] New eeschema file format

On Tue, Aug 02, 2016 at 09:23:18PM +0200, Clemens Koller wrote: > Hello, Wayne! > > Below, I added some very visionary features which I have seen (more or > less miserably implemented) in some big design tools, which could affect > the file formats in the long-term view as well. > I am not sure

Re: [Kicad-developers] New eeschema file format

On 8/2/2016 7:16 AM, Chris Pavlina wrote: > My implementation had a large number of symbols, would have allowed > user-supplied arbitrary symbols if I had finished it, and automatically > selected a symbol based on net name _exactly_ as Clemens suggested. All > of these issues are solved. How

Re: [Kicad-developers] New eeschema file format

My implementation had a large number of symbols, would have allowed user-supplied arbitrary symbols if I had finished it, and automatically selected a symbol based on net name _exactly_ as Clemens suggested. All of these issues are solved. On Tue, Aug 02, 2016 at 10:00:51AM +0200, Clemens Koller

Re: [Kicad-developers] New eeschema file format

Hello, Chris! On 2016-08-02 09:19, jp charras wrote: > About shapes: an arrow and 2 gnd symbol shapes is not enough. > 3 or 4 shapes only is a serious regression. > A lot of shapes is what we have now. I was not suggesting to remove/reduce shapes. I prefer using only a few of the shapes and turn

Re: [Kicad-developers] New eeschema file format

Le 02/08/2016 à 08:59, Clemens Koller a écrit : > Hi, Chris! > > On 2016-08-02 01:09, Chris Pavlina wrote: >> I'm in favor of power connects as labels because, well, that's what they >> are! Remember that power components and global labels behave >> identically. IMO keeping this consistency is

Re: [Kicad-developers] New eeschema file format

Hi, Chris! On 2016-08-02 01:09, Chris Pavlina wrote: > I'm in favor of power connects as labels because, well, that's what they > are! Remember that power components and global labels behave > identically. IMO keeping this consistency is very, very good from a user > interface perspective -

Re: [Kicad-developers] New eeschema file format

I'm in favor of power connects as labels because, well, that's what they are! Remember that power components and global labels behave identically. IMO keeping this consistency is very, very good from a user interface perspective - components in general don't make connections to remote places,

Re: [Kicad-developers] New eeschema file format

How is this different or better than being able to edit a power component value? I know we cannot do this right now but I see no reason that it couldn't be done once the new file format is in place and power components are defined by component type rather than naming semantics. On 7/31/2016 5:09

Re: [Kicad-developers] New eeschema file format

It is good. It is convenient. В Понедельник, 1 авг. 2016 в 12:09 , Chris Pavlina написал: Power labels replace power components. Here are a couple screenshots from my feature branch that I dug up - still haven't actually got it building again, it had a few issues, but

Re: [Kicad-developers] New eeschema file format

Power labels replace power components. Here are a couple screenshots from my feature branch that I dug up - still haven't actually got it building again, it had a few issues, but the screenshots should explain. Bear in mind they're all at different levels of development, so I don't necessarily

Re: [Kicad-developers] New eeschema file format

On 7/31/2016 4:45 PM, Wayne Stambaugh wrote: > On 7/31/2016 3:59 PM, Chris Pavlina wrote: >> On Sun, Jul 31, 2016 at 03:25:11PM -0400, Wayne Stambaugh wrote: >>> On 7/30/2016 9:22 PM, Chris Pavlina wrote: Hi, I was reading through the new sch/lib format documents posted back in

Re: [Kicad-developers] New eeschema file format

On 7/31/2016 4:02 PM, Chris Pavlina wrote: > On Sun, Jul 31, 2016 at 07:53:41PM +, Mário Luzeiro wrote: >> Hi all, >> >> Feature request for eeschema: >> >> Not sure if this is the right thread, as now I started using again KiCad, >> one thing I miss and I believe I found somewhere other

Re: [Kicad-developers] New eeschema file format

On 7/31/2016 3:59 PM, Chris Pavlina wrote: > On Sun, Jul 31, 2016 at 03:25:11PM -0400, Wayne Stambaugh wrote: >> On 7/30/2016 9:22 PM, Chris Pavlina wrote: >>> Hi, >>> >>> I was reading through the new sch/lib format documents posted back in >>> February:

Re: [Kicad-developers] New eeschema file format

On Sun, Jul 31, 2016 at 07:53:41PM +, Mário Luzeiro wrote: > Hi all, > > Feature request for eeschema: > > Not sure if this is the right thread, as now I started using again KiCad, > one thing I miss and I believe I found somewhere other requests, is the > ability to > make some kind of

Re: [Kicad-developers] New eeschema file format

On Sun, Jul 31, 2016 at 03:25:11PM -0400, Wayne Stambaugh wrote: > On 7/30/2016 9:22 PM, Chris Pavlina wrote: > > Hi, > > > > I was reading through the new sch/lib format documents posted back in > > February: https://lists.launchpad.net/kicad-developers/msg23302.html > > > > Since work is

Re: [Kicad-developers] New eeschema file format

2016-07-31 21:53 GMT+02:00 Mário Luzeiro : > Hi all, > > Feature request for eeschema: > > Not sure if this is the right thread, as now I started using again KiCad, > one thing I miss and I believe I found somewhere other requests, is the > ability to > make some kind of notes in

Re: [Kicad-developers] New eeschema file format

Hi all, Feature request for eeschema: Not sure if this is the right thread, as now I started using again KiCad, one thing I miss and I believe I found somewhere other requests, is the ability to make some kind of notes in schematics. Usually I use "Add text" but that text is visible and

Re: [Kicad-developers] New eeschema file format

Crap, mis-sent this on my phone. > On Jul 31, 2016 2:06 AM, "Lorenzo Marcantonio" wrote: > > > > > > Il Dom, 31 Luglio 2016 1:22, Chris Pavlina ha scritto: > > > > > - Why both 'polyline' and 'line'? Surely eeschema isn't going to get > > > tired of writing 'poly' and

[Kicad-developers] New eeschema file format

Hi, I was reading through the new sch/lib format documents posted back in February: https://lists.launchpad.net/kicad-developers/msg23302.html Since work is underway to facilitate adding this now, I figured it was a decent time to bring up a few concerns and suggestions I have. Bear in mind I'm