Re: [Kicad-developers] [PATCH] Eagle schematic and project import.

[jp charras]

Le 16/09/2017 à 07:28, Russell Oliver a écrit :
> Hi, 
> 
> Jean-Pierre: can you send me a link to the files you tested it on? 
> 
> Also for opening either an Eagle schematic or board file, the intended 
> workflow starts within the
> KiCad launcher. File > Import Project > Eagle Cad. This launches both 
> Eeschema, Pcbnew for the
> matching files and then synchronises the timestamps across the files. 
> 
> Regards
> Russell
>  

I found the issue!

The crash is due to the fact certainly the schematic Eagle plugin is missing a 
switch to the "C"
locale (adding a "LOCALE_IO dummy;" declaration before reading the file), so 
the floating numbers
create issues in countries that use the comma as floating number separator 
(like in France).

However, when parsing a file, the Eagle plugin should show an error and abort 
the load process,
without crashing Eeschema.


-- 
Jean-Pierre CHARRAS

___
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

[Kicad-developers] small typo - please fix

[Marco Ciampa]

diff --git a/eeschema/dialogs/dialog_edit_libentry_fields_in_lib_base.cpp 
b/eeschema/dialogs/dialog_edit_libentry_fields_in_lib_base.cpp
index 4325d58..449f563 100644
--- a/eeschema/dialogs/dialog_edit_libentry_fields_in_lib_base.cpp
+++ b/eeschema/dialogs/dialog_edit_libentry_fields_in_lib_base.cpp
@@ -34,7 +34,7 @@ 
DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB_BASE::DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB_BASE
bSizer8->Add( moveUpButton, 0, wxALL, 5 );

moveDownButton = new wxBitmapButton( this, wxID_ANY, wxNullBitmap, 
wxDefaultPosition, wxDefaultSize, wxBU_AUTODRAW );
-   moveDownButton->SetToolTip( _("Move Move the selected optional fields 
down one position down") );
+   moveDownButton->SetToolTip( _("Move the selected optional fields down 
one position down") );

bSizer8->Add( moveDownButton, 0, wxALL, 5 );


TIA

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.



 GNU/Linux User #78271
 FSFE fellow #364




___
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

Re: [Kicad-developers] small typo - please fix

[Clemens Koller]

On 2017-09-16 21:12, Marco Ciampa wrote:
> +   moveDownButton->SetToolTip( _("Move the selected optional fields down 
> one position down") );

- down?
lower?

> +   moveDownButton->SetToolTip( _("Move the selected optional fields one 
> position down.") );

And we put colons after full sentences, propably.

Clemens

___
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

Re: [Kicad-developers] small typo - please fix

[Kevin Cozens]

On 2017-09-16 03:23 PM, Clemens Koller wrote:

And we put colons after full sentences, propably.


Good catches on the typos. I think you meant to say that we put periods 
(aka. full stops) at the end of sentences.  :)


--
Cheers!

Kevin.

http://www.ve3syb.ca/   |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
| powerful!"
#include  | --Chris Hardwick

___
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

Re: [Kicad-developers] KiCad Libraries (again)

[Oliver Walters]

Hugo can use external JSON data during the build step, so I've worked out
how to list the GitHub library releases directly onto the downloads page!

Some progress images here:

https://imgur.com/a/2V6E3

Most of the framework is in place now. I need some assistance with wording
for /discover/libraries but other than that, almost ready to go :)

Oliver

On Sat, Sep 16, 2017 at 1:52 PM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:

> Some more progress: https://github.com/KiCad/kicad-library/issues/1622
>
> On Sat, Sep 16, 2017 at 12:53 PM, Oliver Walters <
> oliver.henry.walt...@gmail.com> wrote:
>
>> I have worked out how to transfer the KLC page to the Hugo templating
>> system (it is SO much harder to use than Jenkins :p)
>>
>> Example:
>>
>> https://i.imgur.com/4kZnvOA.png
>>
>> The libraries information is also moved across, but that's just static
>> content so it's much simpler.
>>
>> I'll keep you posted.
>>
>> On Fri, Sep 15, 2017 at 10:41 PM, Wayne Stambaugh 
>> wrote:
>>
>>> On 9/14/2017 8:54 PM, Oliver Walters wrote:
>>> > Ben,
>>> >
>>> > That's also an option, I hadn't considered that! Perhaps I was focused
>>> > on the GitHub-side solution too closely.
>>> >
>>> > Wayne, do you want to weigh in here before I spend too much further
>>> > effort developing this? Could the libraries page be developed on the
>>> > KiCad website itself?
>>>
>>> The libraries page could be developed on KiCad website although I'm not
>>> sure how that would work.  I am comfortable with either solution.  Pick
>>> which ever solution is the most comfortable for you.  Since you are
>>> doing the work, you should choose the implementation unless someone else
>>> is willing step up and help out.  Even the basic overview that you
>>> presented is far better than anything we have at the moment.  We can
>>> always add more features later.
>>>
>>> >
>>> > The structure could remain largely the same but the formatting would
>>> > need to change from Jekyll to Hugo.
>>> >
>>> > Cheers,
>>> > Oliver
>>> >
>>> > On Fri, Sep 15, 2017 at 1:17 AM, Ben Hest >> > > wrote:
>>> >
>>> > Does this method provide an advantage over doing a similar thing
>>> > using Hugo and putting the docs on the kicad-pcb.org
>>> > 
>>> > website? https://github.com/KiCad/kicad-website
>>> > 
>>> >
>>> >
>>> > - Ben
>>> >
>>> > On Thu, Sep 14, 2017 at 7:01 AM, Oliver Walters
>>> > >> > > wrote:
>>> >
>>> > Hi everyone,
>>> >
>>> > The conversation of how best to manage and distribute KiCad
>>> > libraries has been raging for a while now.
>>> >
>>> > Users looking to download or contribute to the libraries are
>>> > currently presented with a github landing page and some bland
>>> > wiki pages (e.g. for the KLC information).
>>> >
>>> > I have been working on a new-and-improved website system for
>>> the
>>> > following:
>>> >
>>> > * Clear information about the libraries
>>> > * A place to download the latest libraries
>>> > * Information on what is *in* the libraries
>>> > * Instructions on how to contribute to the libs
>>> > * Better presentation of the KLC
>>> >
>>> > This website will need to be updated periodically to present
>>> the
>>> > latest version of the libraries to the users. Also, if users
>>> are
>>> > going to be downloading library files then it could potentially
>>> > use a lot of bandwidth. Thirdly, the generated content should
>>> be
>>> > scripted but statically hosted.
>>> >
>>> > The solution? GitHub pages! - https://pages.github.com/ -
>>> >
>>> > These are hosted from your github repository, and for e.g. ours
>>> > would have the URL kicad.github.io  -
>>> > this could be easily redirected from kicad-lib.org/library
>>> >  (for example).
>>> >
>>> > GitHub pages use the jekyll toolset to generate static content.
>>> >
>>> > With a small amount of additional Python scripting I have
>>> > created a bare-bones example of what this might look like
>>> > (locally hosted on my laptop for now):
>>> >
>>> > Here are some screenshots! Ignore the colors and simple layout
>>> > scheme, this is currently just a framework.
>>> >
>>> > https://imgur.com/a/0GELG
>>> >
>>> > The main objectives of this project are:
>>> >
>>> > a) Present a more professional landing page for the libraries
>>> > b) Leverage GitHub Pages functionality
>>> > c) Improve KLC
>>> >
>>> > And, eventually:
>>> >
>>> > Provide a standardised way to separate the KiCad libraries from
>>> > the KiCad installer!
>>> >
>>> > Thoughts and comments appr

Re: [Kicad-developers] KiCad Libraries (again)

[Oliver Walters]

I have also created a FOOTPRINTS repository at -
https://github.com/KiCad/footprints

The intent is to have ALL the .pretty repos merged here, to combat the ever
decreasing maintainability of the libraries.

For now, it contains each .pretty repository as an individual submodule.

On Sun, Sep 17, 2017 at 2:13 PM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:

> Hugo can use external JSON data during the build step, so I've worked out
> how to list the GitHub library releases directly onto the downloads page!
>
> Some progress images here:
>
> https://imgur.com/a/2V6E3
>
> Most of the framework is in place now. I need some assistance with wording
> for /discover/libraries but other than that, almost ready to go :)
>
> Oliver
>
> On Sat, Sep 16, 2017 at 1:52 PM, Oliver Walters <
> oliver.henry.walt...@gmail.com> wrote:
>
>> Some more progress: https://github.com/KiCad/kicad-library/issues/1622
>>
>> On Sat, Sep 16, 2017 at 12:53 PM, Oliver Walters <
>> oliver.henry.walt...@gmail.com> wrote:
>>
>>> I have worked out how to transfer the KLC page to the Hugo templating
>>> system (it is SO much harder to use than Jenkins :p)
>>>
>>> Example:
>>>
>>> https://i.imgur.com/4kZnvOA.png
>>>
>>> The libraries information is also moved across, but that's just static
>>> content so it's much simpler.
>>>
>>> I'll keep you posted.
>>>
>>> On Fri, Sep 15, 2017 at 10:41 PM, Wayne Stambaugh 
>>> wrote:
>>>
 On 9/14/2017 8:54 PM, Oliver Walters wrote:
 > Ben,
 >
 > That's also an option, I hadn't considered that! Perhaps I was focused
 > on the GitHub-side solution too closely.
 >
 > Wayne, do you want to weigh in here before I spend too much further
 > effort developing this? Could the libraries page be developed on the
 > KiCad website itself?

 The libraries page could be developed on KiCad website although I'm not
 sure how that would work.  I am comfortable with either solution.  Pick
 which ever solution is the most comfortable for you.  Since you are
 doing the work, you should choose the implementation unless someone else
 is willing step up and help out.  Even the basic overview that you
 presented is far better than anything we have at the moment.  We can
 always add more features later.

 >
 > The structure could remain largely the same but the formatting would
 > need to change from Jekyll to Hugo.
 >
 > Cheers,
 > Oliver
 >
 > On Fri, Sep 15, 2017 at 1:17 AM, Ben Hest >>> > > wrote:
 >
 > Does this method provide an advantage over doing a similar thing
 > using Hugo and putting the docs on the kicad-pcb.org
 > 
 > website? https://github.com/KiCad/kicad-website
 > 
 >
 >
 > - Ben
 >
 > On Thu, Sep 14, 2017 at 7:01 AM, Oliver Walters
 > >>> > > wrote:
 >
 > Hi everyone,
 >
 > The conversation of how best to manage and distribute KiCad
 > libraries has been raging for a while now.
 >
 > Users looking to download or contribute to the libraries are
 > currently presented with a github landing page and some bland
 > wiki pages (e.g. for the KLC information).
 >
 > I have been working on a new-and-improved website system for
 the
 > following:
 >
 > * Clear information about the libraries
 > * A place to download the latest libraries
 > * Information on what is *in* the libraries
 > * Instructions on how to contribute to the libs
 > * Better presentation of the KLC
 >
 > This website will need to be updated periodically to present
 the
 > latest version of the libraries to the users. Also, if users
 are
 > going to be downloading library files then it could
 potentially
 > use a lot of bandwidth. Thirdly, the generated content should
 be
 > scripted but statically hosted.
 >
 > The solution? GitHub pages! - https://pages.github.com/ -
 >
 > These are hosted from your github repository, and for e.g.
 ours
 > would have the URL kicad.github.io  -
 > this could be easily redirected from kicad-lib.org/library
 >  (for example).
 >
 > GitHub pages use the jekyll toolset to generate static
 content.
 >
 > With a small amount of additional Python scripting I have
 > created a bare-bones example of what this might look like
 > (locally hosted on my laptop for now):
 >
 > Here are some screenshots! Ignore the colors and simple layout
 > sc

[Kicad-developers] Questions regarding .sweet format

[Oliver Walters]

Hi Wayne, others,

It has been a while since I have heard anything on here regarding the
.sweet format for schematic symbols.

I remember reading that Wayne was not wanting extra input on this, but this
was a very long time ago!

With my current effort to consolidate the libraries before v5 release, it
has again brought into focus the areas in which the current symbol file
formats are lacking.

For reference, the most recent version of the .sweet proposal I have been
able to find is here -
https://lists.launchpad.net/kicad-developers/binDp0KdUNMWc.bin (perhaps
there is a newer one Wayne?)

Following is a short list of question:

*1.  Specify multiple functions for a single pin*

I have asked this before here -
https://lists.launchpad.net/kicad-developers/msg27071.html - however I did
not really get much of a response.

It would be great to be able to assign multiple functions to a given pin,
and users can select a pin func (drop-down-box) which then enforces ERC
accordingly)

*2. Symbol Variants*

One of the pressing shortfalls in the current library scheme is that the
footprint field is common to all aliases. Thus, if a symbol is made for
e.g. a SOIC-8 there cannot be an alias for a DIP-8 version of the symbol.
Many components have pin-compatible footprints.

In this case, is it as simple as doing the following:

(part "MYPART_DIP-8" inherets "MYPART_SOIC-8"
  (footprint "DIPS:DIP-8")
)

That's how I read the specification document. If my reading is correct,
then I think that's great.

*3. Token Default Values*

The spec. doc. does not indicate what default values will be inferred from
a file that is missing particular tokens. e.g. does a text field missing
the "visible" tag default to YES or NO?

Thanks,

Oliver
___
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