Re: [Kicad-developers] Plot to raster image

[Kliment (Future Bits)]

Hey,

Without prejudice to whether or not this should be in Kicad, and how it
should be implemented, there's a way to do this now, with existing
tools. You start from gerbers - libgerbv supports this operation out of
the box for example, and it knows exactly what it's trying to produce.
So you can plot to gerbers and then run it through gerbv to get what you
need right now.

Kliment

On 23.05.20 22:51, Vesa Solonen wrote:
> Hello,
> 
> This goes mostly to feature wish list, but some technical details may be
> of interest. The use of the feature would be (laser) toner transfer
> process for PCBs.
> 
> After some extensive testing it seems many printers/drivers do not print
> vectors as well as raw raster if one wishes to get the most contrast or
> toner density. E.g. with any settings vector input puts less toner on
> the paper than the same rasterized to printers native resolution.
> 
> For the process in general, color printers are way better as the toner
> is finer and has better binder. Also the paper type setting makes a
> great difference as one would guess, 'Rough' getting the most on HP M452nw.
> 
> Rasterizing e.g. the PDF-output is possible, but it is not optimal as
> the rasterizer does not have any clue what it is trying to produce (a
> PCB). Also many available tools rasterize with anti aliasing that just
> makes it worse as the output is one bit per pixel anyway.
> 
> So some smart rasterizer (with grid fitting) to one bit per pixel raster
> at selected resolution (dpi) would be needed. My guess is that raw png
> output would be the most usable.
> 
> -Vesa
> 
> ___
> 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
> 


___
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] Build on msys2 fails : libngspice-x.dll not found in any executable path

[Wayne Stambaugh]

On 5/23/20 11:55 AM, jp charras wrote:
> Le 23/05/2020 à 17:35, Wayne Stambaugh a écrit :
>> There is definitely something wrong but I'm not sure where the issue is.
>>  I downgraded both cmake a couple of versions but cmake started
>> complaining about missing libraries.  I even modified Findngspice.cmake
>> with the absolute path to libngspice-0.dll and it still didn't work so
>> something is definitely broken.  I'm may try a full clean reinstall of
>> msys2 when I have a *lot* of free time so I don't know when that will
>> happen.  For all of you windows devs using msys2, you might want to hold
>> off updating until this issue is resolved.
>>
>>
> I also tried the last msys version.
> I found 2 issues:
> this issue: libngspice-0.dll is not found even if it is in path.
> This is an issue but one can invoke cmake with option 
> -DNGSPICE_DLL=
> The other issue is the fact the last msys version comes with wxWidgets 3.05 
> compiled with gcc10
> but wxPython was not rebuild and there is an ABI issue.

Thanks for the tip but I still don't understand why the library is not
being found by cmake.  I've pinged the msys2 devs more than once about
the wxPython ABI issue but they don't seem terribly interested in
keeping them synced up.  It's easy enough to rebuild wxPython with the
latest version of gcc although it takes a long time.

___
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] Plot to raster image

[Vesa Solonen]

Hello,

This goes mostly to feature wish list, but some technical details may be
of interest. The use of the feature would be (laser) toner transfer
process for PCBs.

After some extensive testing it seems many printers/drivers do not print
vectors as well as raw raster if one wishes to get the most contrast or
toner density. E.g. with any settings vector input puts less toner on
the paper than the same rasterized to printers native resolution.

For the process in general, color printers are way better as the toner
is finer and has better binder. Also the paper type setting makes a
great difference as one would guess, 'Rough' getting the most on HP M452nw.

Rasterizing e.g. the PDF-output is possible, but it is not optimal as
the rasterizer does not have any clue what it is trying to produce (a
PCB). Also many available tools rasterize with anti aliasing that just
makes it worse as the output is one bit per pixel anyway.

So some smart rasterizer (with grid fitting) to one bit per pixel raster
at selected resolution (dpi) would be needed. My guess is that raw png
output would be the most usable.

-Vesa

___
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] How to redefine default system footprint/symbols/packages3d/templates search paths at build time?

[Ian McInerney]

Have you tried redefining the environment variables to point to the correct
system libraries? Specifically I believe the 4 you need are:
KICAD_TEMPLATE_DIR (the templates)
KICAD_SYMBOL_DIR (the eeschema symbols)
KISYSMOD (the modules)
KISYS3DMOD (the 3d models)

-Ian



On Sat, May 23, 2020 at 8:50 PM Johannes Maibaum  wrote:

> Hello KiCad developers,
>
> TL;DR:
> How can I redefine the default system
> footprint/symbols/packages3d/templates base search paths at build time
> using CMake options, so that KISYSMOD, KISYS3DMOD, KICAD_SYMBOL_DIR, and
> KICAD_TEMPLATE_DIR all point to the directories:
>
> $PREFIX/data/share/kicad/{modules,modules/packages3d,symbols,templates}
>
> instead of:
>
> $PREFIX/share/kicad/{modules,modules/packages3d,symbols,templates}?
>
>
> Longer version:
>
> First a quick update from flatpak land:
>
> This week I merged the update to KiCad 5.1.6, fixed the ngspice
> simulator in Eeschema, activated Python scripting, and added user
> documentation to the KiCad flatpak. This means that flatpak users by now
> get a KiCad experience that should support close to all features that
> the software package offers.
>
> But what I would like to do in order to make the installed size
> (currently 6.2GB, mostly due to the 3D packages) a little bit more
> controllable from the user perspective [1] is to move the footprint,
> symbols, 3D models, and templates into separate "flatpak app extensions"
> which can then be installed or removed independently of the main
> application.
>
> The way flatpak extensions work is that you basically define an
> "extension mount point" inside your main flatpak (I chose /app/data) for
> whatever files and directories an installed extension wants to add into
> the bundle.
>
> I have set up those library extensions already, and they are being
> mounted correctly inside the flatpak at runtime, but so far I wasn't
> able to configure KiCad correctly to use this mount point as base dir
> for the data files.
>
> So far, I have tried either -DDEFAULT_INSTALL_PATH=/app/data or
> -DCMAKE_INSTALL_DATADIR=/app/data during CMake configuration in two
> different test builds (as those two options were appearing in
> CMakeLists.txt and the surrounding lines seemed to indicate that they
> were doing what I was trying to achieve).
>
> Yet, none of the two did change anything (though I didn't try using both
> together yet) regarding to the KiCad system paths. This is what I see in
> "Preferences->Configure Paths" with or without redefining the CMake
> options:
>
> KICAD_SYMBOL_DIR=/app/share/kicad/library
> KICAD_TEMPLATE_DIR=/app/share/kicad/template
> KISY3DSMOD=/app/share/kicad/modules/packages3d
> KISYSMOD=/app/share/kicad/modules
>
> I saw further CMake options which are all marked as advanced, thus I did
> not try them yet.
>
> Is there a way to achieve what I want to do with the current set of
> CMake switches or would this need deeper plumbing?
>
>
> Here's my current CMake setup:
>
> "config-opts": [
> "-DBOOST_ROOT=/app",
> "-DDEFAULT_INSTALL_PATH=/app/data",
> "-DGLEW_INCLUDE_DIR=/app/include/GL",
> "-DOPENGL_glu_LIBRARY=/app/lib/libGLU.so",
> "-DKICAD_BUILD_QA_TESTS=OFF",
> "-DKICAD_SCRIPTING_PYTHON3=ON",
> "-DKICAD_SCRIPTING_WXPYTHON_PHOENIX=ON"
> ]
>
> (--prefix=/app is the default in flatpak land).
>
>
> And version info:
>
> Application: KiCad
> Version: 5.1.6, release build
> Libraries:
> wxWidgets 3.0.5
> libcurl/7.65.3-DEV GnuTLS/3.6.13 (NSS/3.46.1) (OpenSSL/1.1.1d)
> zlib/1.2.11 libidn2/2.2.0
> Platform: Linux 5.6.14-arch1-1 x86_64, 64 bit, Little endian, wxGTK
> Build Info:
> wxWidgets: 3.0.5 (wchar_t,wx containers,compatible with 2.8) GTK+
> 3.24
> Boost: 1.66.0
> OpenCASCADE Community Edition: 6.9.1
> Curl: 7.65.3-DEV
> Compiler: GCC 9.2.0 with C++ ABI 1013
>
> Build settings:
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=ON
> KICAD_SCRIPTING=ON
> KICAD_SCRIPTING_MODULES=ON
> KICAD_SCRIPTING_PYTHON3=ON
> KICAD_SCRIPTING_WXPYTHON=ON
> KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
> KICAD_SCRIPTING_ACTION_MENU=ON
> BUILD_GITHUB_PLUGIN=ON
> KICAD_USE_OCE=ON
> KICAD_USE_OCC=OFF
> KICAD_SPICE=ON
>
>
>
> Cheers,
> Johannes
>
>
> [1] To quote a user: "KiCad is AFAIK the biggest flatpak on Flathub" (
>
> https://github.com/flathub/org.kicad_pcb.KiCad/issues/19#issuecomment-632761066
> )
>
>
> ___
> 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
>
___
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] How to redefine default system footprint/symbols/packages3d/templates search paths at build time?

[Johannes Maibaum]

Hello KiCad developers,

TL;DR:
How can I redefine the default system
footprint/symbols/packages3d/templates base search paths at build time
using CMake options, so that KISYSMOD, KISYS3DMOD, KICAD_SYMBOL_DIR, and
KICAD_TEMPLATE_DIR all point to the directories:

$PREFIX/data/share/kicad/{modules,modules/packages3d,symbols,templates}

instead of:

$PREFIX/share/kicad/{modules,modules/packages3d,symbols,templates}?


Longer version:

First a quick update from flatpak land:

This week I merged the update to KiCad 5.1.6, fixed the ngspice
simulator in Eeschema, activated Python scripting, and added user
documentation to the KiCad flatpak. This means that flatpak users by now
get a KiCad experience that should support close to all features that
the software package offers.

But what I would like to do in order to make the installed size
(currently 6.2GB, mostly due to the 3D packages) a little bit more
controllable from the user perspective [1] is to move the footprint,
symbols, 3D models, and templates into separate "flatpak app extensions"
which can then be installed or removed independently of the main
application.

The way flatpak extensions work is that you basically define an
"extension mount point" inside your main flatpak (I chose /app/data) for
whatever files and directories an installed extension wants to add into
the bundle.

I have set up those library extensions already, and they are being
mounted correctly inside the flatpak at runtime, but so far I wasn't
able to configure KiCad correctly to use this mount point as base dir
for the data files.

So far, I have tried either -DDEFAULT_INSTALL_PATH=/app/data or
-DCMAKE_INSTALL_DATADIR=/app/data during CMake configuration in two
different test builds (as those two options were appearing in
CMakeLists.txt and the surrounding lines seemed to indicate that they
were doing what I was trying to achieve).

Yet, none of the two did change anything (though I didn't try using both
together yet) regarding to the KiCad system paths. This is what I see in
"Preferences->Configure Paths" with or without redefining the CMake
options:

KICAD_SYMBOL_DIR=/app/share/kicad/library
KICAD_TEMPLATE_DIR=/app/share/kicad/template
KISY3DSMOD=/app/share/kicad/modules/packages3d
KISYSMOD=/app/share/kicad/modules

I saw further CMake options which are all marked as advanced, thus I did
not try them yet.

Is there a way to achieve what I want to do with the current set of
CMake switches or would this need deeper plumbing?


Here's my current CMake setup:

"config-opts": [
"-DBOOST_ROOT=/app",
"-DDEFAULT_INSTALL_PATH=/app/data",
"-DGLEW_INCLUDE_DIR=/app/include/GL",
"-DOPENGL_glu_LIBRARY=/app/lib/libGLU.so",
"-DKICAD_BUILD_QA_TESTS=OFF",
"-DKICAD_SCRIPTING_PYTHON3=ON",
"-DKICAD_SCRIPTING_WXPYTHON_PHOENIX=ON"
]

(--prefix=/app is the default in flatpak land).


And version info:

Application: KiCad
Version: 5.1.6, release build
Libraries:
wxWidgets 3.0.5
libcurl/7.65.3-DEV GnuTLS/3.6.13 (NSS/3.46.1) (OpenSSL/1.1.1d)
zlib/1.2.11 libidn2/2.2.0
Platform: Linux 5.6.14-arch1-1 x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.5 (wchar_t,wx containers,compatible with 2.8) GTK+
3.24
Boost: 1.66.0
OpenCASCADE Community Edition: 6.9.1
Curl: 7.65.3-DEV
Compiler: GCC 9.2.0 with C++ ABI 1013

Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=ON
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_PYTHON3=ON
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=ON



Cheers,
Johannes


[1] To quote a user: "KiCad is AFAIK the biggest flatpak on Flathub" (
https://github.com/flathub/org.kicad_pcb.KiCad/issues/19#issuecomment-632761066
)


___
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] Build on msys2 fails : libngspice-x.dll not found in any executable path

[jp charras]

Le 23/05/2020 à 17:35, Wayne Stambaugh a écrit :
> There is definitely something wrong but I'm not sure where the issue is.
>  I downgraded both cmake a couple of versions but cmake started
> complaining about missing libraries.  I even modified Findngspice.cmake
> with the absolute path to libngspice-0.dll and it still didn't work so
> something is definitely broken.  I'm may try a full clean reinstall of
> msys2 when I have a *lot* of free time so I don't know when that will
> happen.  For all of you windows devs using msys2, you might want to hold
> off updating until this issue is resolved.
> 
> 
I also tried the last msys version.
I found 2 issues:
this issue: libngspice-0.dll is not found even if it is in path.
This is an issue but one can invoke cmake with option 
-DNGSPICE_DLL=
The other issue is the fact the last msys version comes with wxWidgets 3.05 
compiled with gcc10
but wxPython was not rebuild and there is an ABI issue.


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

Re: [Kicad-developers] Build on msys2 fails : libngspice-x.dll not found in any executable path

[Wayne Stambaugh]

There is definitely something wrong but I'm not sure where the issue is.
 I downgraded both cmake a couple of versions but cmake started
complaining about missing libraries.  I even modified Findngspice.cmake
with the absolute path to libngspice-0.dll and it still didn't work so
something is definitely broken.  I'm may try a full clean reinstall of
msys2 when I have a *lot* of free time so I don't know when that will
happen.  For all of you windows devs using msys2, you might want to hold
off updating until this issue is resolved.


On 5/20/20 3:13 AM, Nick Østergaard wrote:
> Hi Brian
> 
> Mmm, it sound more like you are not updating msys2 properly...
> 
> But please attach pkglist_with_s.txt.
> pacman -Qs > pkglist_with_s.txt
> 
> It looks like msys2 also recommends an update script (update-core) to
> workaround the issues with the runtime. [1] Especially note:
> 
> "Run update-core. If one of the packages is updated during script run
> you MUST restart MSYS2"
> 
> After this, please try a clean (read new) build dir and run cmake afresh.
> 
> Nick
> 
> [1] https://www.msys2.org/wiki/MSYS2-installation/
> 
> On Wed, 20 May 2020 at 03:53, Brian Piccioni
>  wrote:
>>
>> Hello
>>
>> I updated Msys2 (pacman -Syuu) and it borked the terminal (basically when 
>> building the nice percentages, etc., became more or less random  strings).
>>
>> I decided to reinstall Msys2. I wiped the directory and reinstalled.
>>
>> After doing so and following the directions at 
>> https://docs.kicad-pcb.org/doxygen/md_Documentation_development_compiling.html#build_windows
>>
>> cmake -DCMAKE_BUILD_TYPE=Release \
>>   -G "MSYS Makefiles" \
>>   -DCMAKE_PREFIX_PATH=/mingw64 \
>>   -DCMAKE_INSTALL_PREFIX=/mingw64 \
>>   -DDEFAULT_INSTALL_PATH=/mingw64 \
>>   ../../
>>
>> Fails with
>>
>> -- Found Boost: C:/msys64/mingw64/include (found suitable version "1.72.0", 
>> minimum required is "1.59.0")
>> ERROR:
>> * libngspice-x.dll not found in any executable path *
>>
>>
>> CMake Error at 
>> C:/msys64/mingw64/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164
>>  (message):
>>   Could NOT find ngspice (missing: NGSPICE_DLL)
>> Call Stack (most recent call first):
>>   
>> C:/msys64/mingw64/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:445
>>  (_FPHSA_FAILURE_MESSAGE)
>>   CMakeModules/Findngspice.cmake:63 (find_package_handle_standard_args)
>>   CMakeLists.txt:628 (find_package)
>>
>> 
>>
>> However, I do have C:\msys64\mingw64\bin\libngspice-0.dll and my path is 
>> PATH=C:\msys64;C:\msys64\mingw64\bin; ... (in the cmake file there is a 
>> remark
>>
>> # Note: libngspice-0.dll or libngspice-1.dll must be in a executable path
>>
>>
>> Any suggestions how to fix this would be appreciated.
>>
>>
>>
>> ___
>> 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
> 
> ___
> 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
> 

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

[Mark Roszko]

Ah just a defect with recent changes I made and me never using www. It
shall be fixed.

On Sat, May 23, 2020 at 10:39 AM Wayne Stambaugh 
wrote:

> It was the URL issue but I'm in agreement with Ian.  The old URL should
> redirect to the new one.
>
> On 5/23/20 10:35 AM, Ian McInerney wrote:
> > We should make sure that both are working though. It is common for
> > people to put the www in front of the URL.
> >
> > -Ian
> >
> > On Sat, May 23, 2020 at 3:31 PM jp charras  > > wrote:
> >
> > Le 23/05/2020 à 15:26, Wayne Stambaugh a écrit :
> > > I don't know if it was intentional (I'm guessing not) but the KiCad
> > > website looks completely different today on Firefox and Chrome (see
> > > attached screen shot).  Clicking on the topic links doesn't even
> > take me
> > > to the correct page.
> > >
> > > Thanks,
> > >
> > > Wayne
> > >
> >
> > Be sure you are using:
> > https://kicad-pcb.org
> > and not the old link https://www.kicad-pcb.org
> >
> >
> > --
> > 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
> >
> >
> > ___
> > 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
> >
>
> ___
> 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
>


-- 
Mark
___
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 website

[Wayne Stambaugh]

It was the URL issue but I'm in agreement with Ian.  The old URL should
redirect to the new one.

On 5/23/20 10:35 AM, Ian McInerney wrote:
> We should make sure that both are working though. It is common for
> people to put the www in front of the URL.
> 
> -Ian
> 
> On Sat, May 23, 2020 at 3:31 PM jp charras  > wrote:
> 
> Le 23/05/2020 à 15:26, Wayne Stambaugh a écrit :
> > I don't know if it was intentional (I'm guessing not) but the KiCad
> > website looks completely different today on Firefox and Chrome (see
> > attached screen shot).  Clicking on the topic links doesn't even
> take me
> > to the correct page.
> >
> > Thanks,
> >
> > Wayne
> >
> 
> Be sure you are using:
> https://kicad-pcb.org
> and not the old link https://www.kicad-pcb.org
> 
> 
> -- 
> 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
> 
> 
> ___
> 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
> 

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

[Ian McInerney]

We should make sure that both are working though. It is common for people
to put the www in front of the URL.

-Ian

On Sat, May 23, 2020 at 3:31 PM jp charras  wrote:

> Le 23/05/2020 à 15:26, Wayne Stambaugh a écrit :
> > I don't know if it was intentional (I'm guessing not) but the KiCad
> > website looks completely different today on Firefox and Chrome (see
> > attached screen shot).  Clicking on the topic links doesn't even take me
> > to the correct page.
> >
> > Thanks,
> >
> > Wayne
> >
>
> Be sure you are using:
> https://kicad-pcb.org
> and not the old link https://www.kicad-pcb.org
>
>
> --
> 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
>
___
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 website

[jp charras]

Le 23/05/2020 à 15:26, Wayne Stambaugh a écrit :
> I don't know if it was intentional (I'm guessing not) but the KiCad
> website looks completely different today on Firefox and Chrome (see
> attached screen shot).  Clicking on the topic links doesn't even take me
> to the correct page.
> 
> Thanks,
> 
> Wayne
> 

Be sure you are using:
https://kicad-pcb.org
and not the old link https://www.kicad-pcb.org


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

Re: [Kicad-developers] KiCad website

[Nick Østergaard]

Looks fine for me in chrome. It looks like you are missing some assets, I
assume you already tried to force refrash it to make sure it is not a
caching issue.

lør. 23. maj 2020 15.26 skrev Wayne Stambaugh :

> I don't know if it was intentional (I'm guessing not) but the KiCad
> website looks completely different today on Firefox and Chrome (see
> attached screen shot).  Clicking on the topic links doesn't even take me
> to the correct page.
>
> Thanks,
>
> Wayne
> ___
> 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
>
___
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] KiCad website

[Wayne Stambaugh]

I don't know if it was intentional (I'm guessing not) but the KiCad
website looks completely different today on Firefox and Chrome (see
attached screen shot).  Clicking on the topic links doesn't even take me
to the correct page.

Thanks,

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