Re: [Kicad-developers] progress on 3D plugins

That looks pretty good. Will this also mean that it can render in the normal 3D viewer when the model is placed on board, or has that not been implemented yet? 2015-12-18 3:19 GMT+01:00 Cirilo Bernardo : > I was bored so I tweaked the IDF plugin so that it can also

Re: [Kicad-developers] [PATCH] Improve automatic placement of fields between wires

Le 17/12/2015 20:38, Chris Pavlina a écrit : > autoplace_fields can nudge fields to fit nicely between adjacent > wires, but that didn't work quite well in combination with the recent > flexible-placement patch. This patch improves the heuristics in > fit_fields_between_wires. > > -- Chris >

Re: [Kicad-developers] progress on 3D plugins

Rendering onto the board in 3D viewer depends on the new implementation of 3D viewer which Mario is working on, so at the moment you can only see these models in the preview. However, for IDF users it is now possible to see the IDF component outline before it's added to the board for IDF export.

Re: [Kicad-developers] New development policies.

On Thu, Dec 17, 2015 at 08:39:53PM +0100, Timofonic wrote: > What about systems lacking 3D acceleration? Are those going to be not > supported after total GAL tension? Are there some planning to make an > alternative renderer with low CPU platforms and usable on slow > hardware from embedded

Re: [Kicad-developers] [rfc] actual sexpression parsing

On Fri, Dec 18, 2015 at 12:00:58AM -0500, Mark Roszko wrote: > is just extremely silly and extra work compared to generate SEXPR > trees in memory like SEXPR represents in the first place. God forbid > you accidentally format that double wrong. D'oh you actually want a full in-memory tree

Re: [Kicad-developers] New development policies.

I have started to tag such things missing-gal-tool on the bug tracker. Feel free to creat new tickets with this tag when you notice tools or features that have not been ported and should be. Den 17/12/2015 22.42 skrev "Jean-Paul Louis" : > Is there a place where we can find the

Re: [Kicad-developers] [rfc] actual sexpression parsing

On Thu, Dec 17, 2015 at 11:49:31PM -0500, Chris Pavlina wrote: > Dude. The way it's stored currently is horrible - it's not congruent to > the structure of the file! The s-expr file is supposed to be a tree > structure, why is the binary data stored broken into multiple objects > like that?

Re: [Kicad-developers] [rfc] actual sexpression parsing

On Thu, Dec 17, 2015 at 10:32:10PM -0500, Mark Roszko wrote: > So awhile back, Wayne said to use sexpr for something I wanted to do. > Then I looked at the sexpr parsing and said NOPE. OK, being a lisper and having read the dragon book here's my view on the subject: 1) the parser isn't actually

Re: [Kicad-developers] [rfc] actual sexpression parsing

>You take the BNF form, process it and write the corresponding state machine. >It's not VB6, it's a state machine :D Writing a new state machine for every single list and every single file over and over again is the part I have problems with. There should be a single state machine that takes the

Re: [Kicad-developers] [rfc] actual sexpression parsing

On Fri, Dec 18, 2015 at 07:55:07AM -0500, Mark Roszko wrote: > Writing a new state machine for every single list and every single > file over and over again is the part I have problems with. There > should be a single state machine that takes the tokens and gives you a > list. Not 500 over the

Re: [Kicad-developers] New development policies.

Thanks, Nick. Sent from my Verizon Wireless 4G LTE smartphone Original message From: Nick Østergaard Date: 2015/12/18 3:46 AM (GMT-05:00) To: Jean-Paul Louis Cc: KiCad Developers ,

Re: [Kicad-developers] [rfc] actual sexpression parsing

On Fri, Dec 18, 2015 at 3:49 PM, Tomasz Wlostowski < tomasz.wlostow...@cern.ch> wrote: > On 18.12.2015 15:46, Edwin van den Oetelaar wrote: > > Concerning changing the format of the PCB file again... > > Making a new binary file format is a big NO NO NO (screaming) in my book. > > Hi Edwin, > >

Re: [Kicad-developers] [rfc] actual sexpression parsing

On Fri, Dec 18, 2015 at 10:40:44AM -0500, Mark Roszko wrote: > Simply trying to make parsing simple and easy of sexpr. No file format > change required. Still keep proposing mandatory quotes for strings :D completely backward compatible. > Yes we need a parser especially with some of our

Re: [Kicad-developers] [rfc] actual sexpression parsing

Concerning changing the format of the PCB file again... Just my $0.02 ... I have been lurking on this list for years now... Making a new binary file format is a big NO NO NO (screaming) in my book. I want to be able to edit it with VIM if needed. I personally do not care if the format is

Re: [Kicad-developers] [rfc] actual sexpression parsing

On 18.12.2015 15:46, Edwin van den Oetelaar wrote: > Concerning changing the format of the PCB file again... > Making a new binary file format is a big NO NO NO (screaming) in my book. Hi Edwin, Don't worry, we are not going to change the format :) > I want to be able to edit it with VIM if

Re: [Kicad-developers] [rfc] actual sexpression parsing

On 18.12.2015 13:55, Mark Roszko wrote: > Writing a new state machine for every single list and every single > file over and over again is the part I have problems with. There > should be a single state machine that takes the tokens and gives you a > list. Not 500 over the whole codebase. Hi

Re: [Kicad-developers] [rfc] actual sexpression parsing

So any actual comments on what I did in the commit I linked originally in the first email? >Still keep proposing mandatory quotes for strings :D completely backward compatible. Well yeamy generator class does that all the time. Unless you define a symbol explicitly, all strings are always

Re: [Kicad-developers] New development policies.

17/12/15, 21:39, Timofonic kirjoitti: > I imagine using KiCad on a very low power ARM/MIPS device, or > even a phone/tablet if the UI could be adapted to make it usable. > > What about systems lacking 3D acceleration? If you have a look at the specs of any phone/tablet SoCs you will notice that

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

More and more modern text editing software is moving to fuzzy string matching rather than explicitly requiring users to put in wildcards when doing searches for filenames, code intelligence searches (i.e. match function / class names etc). Have you considered that as an option? On Fri, Dec 18,

[Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

Would everyone be okay with me patching the eeschema component chooser to support wildcards or regexes? And if yes, what's the preference - simple *? wildcards, regexes, or selectable in preferences? (Plan is to make it totally disableable [is that a word? :] in prefs anyway.) -- Chris

[Kicad-developers] [RFC] Reorganize eeschema options a bit

Related to my previous mail, as it would add an option or two - Wayne suggested, and I agree, that the eeschema options dialog is getting stuffed. I suggested that I kind of wanted to rework the options system as a whole, but that's a big project, and organizing them has to come first anyway.

Re: [Kicad-developers] [RFC] Reorganize eeschema options a bit

On 18.12.2015 18:16, Chris Pavlina wrote: > Related to my previous mail, as it would add an option or two - Wayne > suggested, and I agree, that the eeschema options dialog is getting > stuffed. I suggested that I kind of wanted to rework the options system > as a whole, but that's a big

Re: [Kicad-developers] [RFC] Reorganize eeschema options a bit

That's fair. On Fri, Dec 18, 2015 at 06:37:22PM +0100, Tomasz Wlostowski wrote: > On 18.12.2015 18:16, Chris Pavlina wrote: > > Related to my previous mail, as it would add an option or two - Wayne > > suggested, and I agree, that the eeschema options dialog is getting > > stuffed. I suggested

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

Here's a quick example using an open-source JavaScript library and a list of some XMEGA parts I copied from digikey :-) https://jsfiddle.net/o7ms290j/embedded/result/ The search items shows the whole space of things to search over. As you type in the box, it shows what the algorithm returns,

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

We can probably implement it ourselves as a wx based control, The JS implementation is only 100 lines. https://github.com/mattyork/fuzzy/blob/master/lib/fuzzy.js You don't need a C++ library or anything ___ Mailing list:

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

This is just going to clutter up the results with a bunch of annoying false positives. If you want it, fine, but I'm not going to waste my own limited time on it. All I want is a simple, predictable pattern match. On Dec 18, 2015 13:32, "Mark Roszko" wrote: > We can

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

A quick search turns up some interesting looking ones. TRE will do regex AND approximate matching https://en.wikipedia.org/wiki/TRE_%28computing%29 https://github.com/laurikari/tre/ Small: https://en.wikibooks.org/wiki/Algorithm_Implementation/Strings/Levenshtein_distance#C

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

Hi Chris, thanks for the feedback. I certainly don't expect you to waste your time implementing something that you don't want/need! I think if you end up implementing wildcard match it will be a good starting point for adding fuzzy matching later if someone wants to take that on (maybe even I

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

On 18.12.2015 19:25, Jon Evans wrote: > Here's a quick example using an open-source JavaScript library and a > list of some XMEGA parts I copied from digikey :-) > https://jsfiddle.net/o7ms290j/embedded/result/ Wow, that's cool. Does anyone know a similar thing in C++? Tom

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

Thanks, and I don't mean to sound grouchy about it. I don't want to try to be a backseat driver and start insisting we do things My Way, or anything like that. It's just that my proposed change is really quick and simple, and would scratch a massive itch of mine - I'd definitely not object to

Re: [Kicad-developers] [rfc] actual sexpression parsing

O god, your email is just going to start a chain of rage about changing the format. Not trying to do that folks, please rage in another thread if you want to reply to him on that. Simply trying to make parsing simple and easy of sexpr. No file format change required. > Our s-expr format needs

Re: [Kicad-developers] [rfc] actual sexpression parsing

Mark, I haven't had time to look at your commit so I'm not going to comment on that until I do. I don't know when I'll have time as I have a lot of stuff to do and I'm traveling over the holidays so my review time will be limited. In the mean time I will comment on some of the things I've read

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

Hi, Wayne. Thanks for the response. On Fri, Dec 18, 2015 at 03:56:01PM -0500, Wayne Stambaugh wrote: > On 12/18/2015 2:22 PM, Chris Pavlina wrote: > > Thanks, and I don't mean to sound grouchy about it. I don't want to try > > to be a backseat driver and start insisting we do things My Way, or

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

On 12/18/2015 2:22 PM, Chris Pavlina wrote: > Thanks, and I don't mean to sound grouchy about it. I don't want to try > to be a backseat driver and start insisting we do things My Way, or > anything like that. It's just that my proposed change is really quick > and simple, and would scratch a

Re: [Kicad-developers] [RFC] Wildcard and/or regex support in the component chooser

On 18 December 2015 at 09:20, Chris Pavlina wrote: > No, and I'm highly skeptical it'll achieve what I'm looking for. Can you > give an example of what you mean? How do I search for "ATXMEGA*D3" and > get "ATXMEGA64D3", "ATXMEGA128D3", "ATXMEGA256D3", etc to come up? you

Re: [Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

On 18 December 2015 at 21:33, Chris Pavlina wrote: > I'm not going to argue about search methods, it'll suffice to say I > disagree. I don't _want_ to search my library your way, and yes, I > understand that it can work. > > I'm unconvinced that adding one option box is

Re: [Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

On 18 December 2015 at 21:50, Chris Pavlina wrote: > On Fri, Dec 18, 2015 at 09:40:29PM -0800, Henner Zeller wrote: >> On 18 December 2015 at 21:33, Chris Pavlina wrote: >> > I'm not going to argue about search methods, it'll suffice to say I >>

Re: [Kicad-developers] FOSDEM 2016

Hi, > Just a quick heads up. I just made my travel arrangements for FOSDEM > 2016. That always makes it feel official to me. Please try to attend > if you can manage it. I would like to meet as many of the KiCad > developers as possible. I can tell you that EDA dev room dinner > Saturday

[Kicad-developers] 3D refactor

Hi folks, I've gone over the changes in the 3d_initial_merge branch and it looks like it's ready for people to inspect the code and merge with the main branch. At the moment the legacy 3DViewer is left intact but the Footprint Properties dialogs in pcbnew and the Footprint Editor have an

[Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

As discussed earlier today, this patch adds support for both wildcard and regular expression search to the eeschema component chooser. An option is added to eeschema options to select the "Component search method", which defaults to "Simple" (the original behavior). Regular expression search

Re: [Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

On 18 December 2015 at 21:19, Henner Zeller wrote: > On 18 December 2015 at 20:16, Chris Pavlina wrote: >> As discussed earlier today, this patch adds support for both wildcard >> and regular expression search to the eeschema component chooser. An >>

Re: [Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

On 18 December 2015 at 20:16, Chris Pavlina wrote: > As discussed earlier today, this patch adds support for both wildcard > and regular expression search to the eeschema component chooser. An > option is added to eeschema options to select the "Component search >

Re: [Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

I'm not going to argue about search methods, it'll suffice to say I disagree. I don't _want_ to search my library your way, and yes, I understand that it can work. I'm unconvinced that adding one option box is excessive complexity. It's not in the main UI, it's in the preferences dialog.

Re: [Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

On Fri, Dec 18, 2015 at 09:40:29PM -0800, Henner Zeller wrote: > On 18 December 2015 at 21:33, Chris Pavlina wrote: > > I'm not going to argue about search methods, it'll suffice to say I > > disagree. I don't _want_ to search my library your way, and yes, I > >

Re: [Kicad-developers] [PATCH] Eeschema: add wildcard and regex support to component chooser

On 18 December 2015 at 21:57, Henner Zeller wrote: > On 18 December 2015 at 21:50, Chris Pavlina wrote: >> On Fri, Dec 18, 2015 at 09:40:29PM -0800, Henner Zeller wrote: >>> On 18 December 2015 at 21:33, Chris Pavlina wrote: