[Kicad-developers] [RFC]: Make hotkey editor polished

Hi, I've been poking with KiCAD for awhile and decided to contribute. Using Bazaar was the first hurdle, thankfully I gave up and used the git bridge. I otherwise have no idea how development goes. I've always thought the hotkey editor was a bit "unpolished" so I'm submitting patches to make it p

Re: [Kicad-developers] VRML export.

On Sat, Oct 4, 2014 at 10:52 PM, Wayne Stambaugh wrote: > On 10/3/2014 8:15 PM, Cirilo Bernardo wrote: > > On Sat, Oct 4, 2014 at 5:33 AM, Wayne Stambaugh > > wrote: > > > > I've been trying use Pcbnew the VRML export for a board a work and > > discovered s

Re: [Kicad-developers] Finally!

No hurry. Let me know when you have it sorted out. Please send me a patch so I can verify it on msys2. Thanks, Wayne On 10/4/2014 7:12 PM, Brian Sidebotham wrote: > Hi Wayne, I can't check right now, but I'm sure it is to find > python-a-mingw-us for kicad-winbuilder. I expect the answer is to

Re: [Kicad-developers] Finally!

Here is a another teaser of the mingw64 version of kicad showing the wxPython shell so it appears to be working. On 10/4/2014 5:09 PM, Wayne Stambaugh wrote: > After years of struggling to get KiCad to build with the wxPython > scripting enabled with mingw on Windows, I've finally managed to pull

Re: [Kicad-developers] Macro expansion in module text

Hi Lorenzo, Thanks for sorting this out, it'll make a great difference for my next board! Best Regards, Brian. On 4 Oct 2014 16:26, "Lorenzo Marcantonio" wrote: > Sorry about the delay, we had the automechanika fair and related stuff > to handle :P > > In fact the patch is quite simple (I alre

Re: [Kicad-developers] Finally!

Hi Wayne, I can't check right now, but I'm sure it is to find python-a-mingw-us for kicad-winbuilder. I expect the answer is to remove the custom findpython cmake module and replace it with a findpythonamingwus module instead. Please let me introduce the latter before we remove the former; Sorry i

Re: [Kicad-developers] Finally!

Thanks for the input. I give Brian and chance to reply. It may have been something just for the kicad-winbuilder so I may have to find an alternate solution that works in both cases. On 10/4/2014 6:21 PM, Blair Bonnett wrote: > On 5 October 2014 10:09, Wayne Stambaugh

Re: [Kicad-developers] Finally!

The MSYS2 file layout is configured very much like Linux so that is probably why the stock version worked. The if(MINGW) code in our custom version broke finding the include file path. The MSYS2 version of cmake is 3.0.2 so they are keeping things up to date. On 10/4/2014 5:23 PM, Adam Wolf wrot

Re: [Kicad-developers] Finally!

On 5 October 2014 10:09, Wayne Stambaugh wrote: > > On that note, I had to remove our custom FindPythonLib.cmake in order to > get it to work properly. There are some questionable if( MINGW ) blocks > in our custom version that don't make sense to me. Would who ever > modified the stock CMak

Re: [Kicad-developers] A few issues with new OS X bundles

Oops. Fat finger a send on that last reply :). Thank you for taking care of this Bernhard and thank you Garth for the input. Send me the patch when it is ready. Cheers, Wayne On 10/4/2014 4:57 PM, Bernhard Stegmaier wrote: > Then we should go the way Garth proposed using bundles in bundles (y

Re: [Kicad-developers] A few issues with new OS X bundles

On 10/4/2014 4:57 PM, Bernhard Stegmaier wrote: > Then we should go the way Garth proposed using bundles in bundles (yes, > even Xcode does it this way, I was not aware of doing it this way). > > Inside the single app bundle everything is kept as a single copy, > default is the kicad launcher. > I

[Kicad-developers] Finally!

After years of struggling to get KiCad to build with the wxPython scripting enabled with mingw on Windows, I've finally managed to pull it off. Take a look at the attached screenshot. You'll notice that all of the major KiCad features are enabled. This is due in large part to the excellent work

Re: [Kicad-developers] A few issues with new OS X bundles

Then we should go the way Garth proposed using bundles in bundles (yes, even Xcode does it this way, I was not aware of doing it this way). Inside the single app bundle everything is kept as a single copy, default is the kicad launcher. Individual app bundles for everything are created inside th

Re: [Kicad-developers] A few issues with new OS X bundles

Anything launched by calling Execute() is a separate executable and will run in a separate process. I thought KiPlayer() runs in the same process as kicad but I could be wrong. It makes sense that pl_editor and GerbView are stand alone since they don't make sense in relation to a project. I stil

Re: [Kicad-developers] A few issues with new OS X bundles

Hi, yes, could be easy to do this way. Let’s see what Wayne thinks about different execution of pcbnew/eeschema vs. the other applications, then we will see how to proceed. I’m almost done with adapting scripting stuff in CMake and also found a way without explicit usage of install_name_tool to

Re: [Kicad-developers] A few issues with new OS X bundles

Hi, Bernhard I think that the direction you are heading with the single application bundle is the right one. I think a single draggable application install will be a huge win for OS X users compared to the way it was before. It seems like you are almost there, but just a couple somewhat minor

Re: [Kicad-developers] A few issues with new OS X bundles

Yes, but some of the problems seem to be no OSX specific issues. E.g. pl_editor is run this way (kicad/mainframe.cpp): Execute( this, PL_EDITOR_EXE ); while eeschema/pcbnew related things are run this way: KIWAY_PLAYER* frame = Kiway.Player( FRAME_PCB, true ); I don’t know if it is done

Re: [Kicad-developers] A few issues with new OS X bundles

I’m afraid that’s not true in this case. It does launch separate processes for some some of the applications, gerbview for instance. They show up in ps and as Bernhard pointed out, the launcher even shows you the pid when it launches them. If it isn’t supposed to do this then perhaps just so

Re: [Kicad-developers] A few issues with new OS X bundles

Since this doesn't effect me, I don't have a preference one way or another. Although option 2B makes the most sense to me. OSX users please weigh in so we can get this right. You might want to get some input from the user group on Yahoo. There may be more OSX users than developers and their inp

[Kicad-developers] Macro expansion in module text

Sorry about the delay, we had the automechanika fair and related stuff to handle :P In fact the patch is quite simple (I already did the biggest changes...) It handles % sequences in user text primitives inside modules (usefulness already debated); now it recognizes: %% for a plain % %R inserts

Re: [Kicad-developers] A few issues with new OS X bundles

One additional note on (1): You can create an alias pointing to, e.g., the pcbnew executable inside the kicad bundle and put it where you want. Therewith, you can start pcbnew directly by clicking on it - only downside is that since pcbnew executable looks like a command line binary for OSX a te

Re: [Kicad-developers] A few issues with new OS X bundles

There are 2 possibilities as far as I can see: (1) One single application bundle - like it is now. There are probably still some cosmetic issues as Garth told, but I think these are just minor inconsistencies that could be sorted out. From an efficiency point of view it is no difference… 2 clicks

Re: [Kicad-developers] A few issues with new OS X bundles

On 10/4/2014 4:26 AM, Bernhard Stegmaier wrote: > Hi, > > most of your observations are as far as I can see not a problem of the > bundles itself, but of the KiCad modular concept (kiface). > When you launch pcbnew et al. from KiCad launcher the correct “application” > is only loaded as a module

Re: [Kicad-developers] FOSDEM 2015 EDA devroom

Javier, Great job and thank you for your efforts. Barring anything unexpected, I will be attending FOSDEM. I'm looking forward to meeting as many of you as possible and collaborating with the other EDA projects. If you can, please try to make it to FOSDEM. It sounds like it will be a great tim

Re: [Kicad-developers] VRML export.

On 10/3/2014 8:15 PM, Cirilo Bernardo wrote: > On Sat, Oct 4, 2014 at 5:33 AM, Wayne Stambaugh > wrote: > > I've been trying use Pcbnew the VRML export for a board a work and > discovered some serious design issues with the way file names are > manipulat

[Kicad-developers] FOSDEM 2015 EDA devroom

Dear all, Good news: my request for an EDA devroom in FOSDEM 2015 was accepted! I will send out an official call for contributions in the next week or two, but I wanted to give you a heads up so that you can start thinking about coming and joining the fun. I think this is a very good opportunity t

Re: [Kicad-developers] A few issues with new OS X bundles

I’m sure it will get there. I certainly prefer the approach you are taking of eliminating these as standalone application bundles. There really isn’t a need for them with the kicad launcher. It’s just introduced a couple of minor usability nits for me, which I’m sure will be cured over time.

Re: [Kicad-developers] A few issues with new OS X bundles

Hi again, again for the “dock roulette”… IMHO this is just an inconsistency between how pcbnew/eeschema and gerbview/other apps are started from KiCad launcher. For pcbnew/eeschema no individual icon in the dock is created, but for the others. For the other apps you also see a message “kicad.app

Re: [Kicad-developers] A few issues with new OS X bundles

Right. I get that for the loadable bundles the application is still KiCad, but for those applications there’s no second icon, which is probably better behavior. Then you only have the problem of them having a Quit menu item that does not quit the application but just unloads the bundle, which

Re: [Kicad-developers] A few issues with new OS X bundles

Hi, most of your observations are as far as I can see not a problem of the bundles itself, but of the KiCad modular concept (kiface). When you launch pcbnew et al. from KiCad launcher the correct “application” is only loaded as a module, so the main application is still kicad launcher and I gue

[Kicad-developers] A few issues with new OS X bundles

Hi all, I finally had a chance to build and try out the new all-inclusive OS X application bundles and I’ve encountered a couple of issues that tend to reduce the usability a bit for me. First, an observation unrelated to the new bundles. I noticed with mainline builds on OS X, some of the s