Collin, I think a homebrew tap is useful for users who want to try out a patch. It is very easy to modify a tap to put your own patch in.
Adam Wolf Cofounder and Engineer Wayne and Layne, LLC On Jan 22, 2015 3:10 PM, "Wayne Stambaugh" <[email protected]> wrote: > The Apple OSX HIG for a long time was marching towards the no bitmaps in > menus philosophy. It appears that they are now changing course if I'm > reading this correctly: > > > https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/MenuIconsSymbols.html#//apple_ref/doc/uid/20000957-CH27-SW1 > > Go figure? To answer your question, the older OSX HIG recommended not > using images in menus so that is why they are disabled on OSX. I don't > use OSX so I don't have a preference. If this is something that the > majority of OSX users would prefer, I'm fine with enabling them by > default again. Hopefully this is not a back and forth thing where in > another 3 years it will be taboo to have images in menus again. > > > On 1/22/2015 2:40 PM, Collin Anderson wrote: > > Menu icons: > > So, maybe I missed something and someone resolved the issue, but I just > > built KiCad with the USE_MENU_ICONS turned on and it works flawlessly > > and looks great. I don't understand why it is off for OS X, I could not > > find any issue and indeed, the menu icons really improve everything and > > make things feel a lot more user-friendly and intuitive. > > > > Did someone fix whatever was wrong? Or was it broken, then something > > changed (perhaps due to wx 3.0.2.0 vs. 3.0.1.1?) Or maybe I simply > > didn't notice the problem? They sure seem fine to me: > > > > http://i.imgur.com/LcX6BsV.jpg > > > > http://i.imgur.com/HcpwZim.jpg > > > > http://i.imgur.com/vVzljfg.jpg > > > > > > Boost: > > All but one of the patches that get applied to boost are now part of the > > official 1.57 release, to the point that you can attempt to apply them > > and patch will show it as already applied, meaning its *exactly* the > same. > > > > But one patch, patches/boost_minkowski.patch (which sounds more like a > > Lorentz transformation in flat space time to me....sorry, bad physics > > pun =P), which comments out two lines in one of the covolve_two_polygons > > functions, still correctly patches boost 1.57. But, using > > KICAD_SKIP_BOOST and ditching all that entirely builds what appears to > > be a perfectly fine .app, but I worry something subtle gets broken and I > > just don't know what to look for. I haven't been able to figure out what > > exactly the patch is/was needed for or what issues there might be. > > > > My question is, what's the deail? :) Do we need to patch boost at all > > now? Why is boost_minkowski needed, or was it needed, but no more? Or > > maybe it was done years ago by someone else and no one is quite sure? :) > > > > It is still valuable to build boost as the versions installed by package > > managers are generally unsuitable for multi-architecture, á la > > USE_OXS_DEPS_BUILDER, so if the patch is not needed, it is worth > > repurposing the boost cmake module under that flag at least when making > > distribution builds. > > > > Finally, I have finished a more complete and polished homebrew tap for > > KiCad, along with a kicad-library formula that allows library management > > via homebrew, but is interoperable with KiCad from any source - > > official, unofficial, custom built, homebrewed - without issue. It > > keeps it in the Cellar and symlinks it into Application Support, and it > > would seem symlinking works without issue, so the one OS X user talking > > about storing things on a thumbdrive - well, its a bit of a hack but you > > can. Copy the kicad application support folder to the thumb drive, then > > replace the one in ~/Library with a symlink to it, and you should be > > good to go :). > > > > Anyway, I apologize and won't be tooting my own horn again since my > > homebrew tap is not really helpful to the project. I do find it helpful > > in my own workflow though, as it lets updating the binary to the latest > > revision of kicad:product (but isolated from one's own modifications > > stored elsewhere) be done with a single command from shell. I mostly > > made it for myself, so I will not be butthurt if no one else finds it > > helpful or anything. Just wanted to mention it one last time as it's > > now in a 'finished' state: https://github.com/metacollin/homebrew-kicad > > > > -- > > "Violence is the last refuge of the incompetent." - Isaac Asimov > > > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
