Re: [Kicad-developers] Library Editor naming consistency
>I'm leaning towards one of the markdown formats myself. I vote for markdown :D In fact, here, I ran a quick convert of ODT to markdown and imported it into a gitbook setup. Here's chapter 1 and 2 being served from markdown and combined with Gitbook and then being served from a git repo via nodejs. Literally just a 5 minute hack job to demonstrate how easy it is. http://kicad.borkedlabs.com:4000/ which is running off this repo: https://github.com/marekr/kicad-doc-test Also the first time I actually read the *part* of the manual, but what kind of crazy person does that? :P ___ 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] [Solved] CMake fails to find wxWidget in a fresh Ubuntu 14.04 install when trying to build KiCad
I have emailed out a patch for "kicad-install.sh", which will fix the problem you encountered. --Joe On Monday, October 13, 2014 12:14 AM, Benoît Roehr wrote: Finally succesfully build kicad on a all fresh Ubuntu 14.04 yesterday. apt-get build-dep kicad installs wxWidget 2.8 by default (wx3.0 are on other repo). It might be a good idea to advise to install wx3.0.2 before executing apt-get build-dep kicad in this page: http://www.kicad-pcb.org/display/DEV/Building+KiCad+on+Linux Thanks a lot for your help guys :) Le 10/10/2014 15:41, Benoît Roehr a écrit : Hello guys, My problem with wxWidget 3.0 and CMake continues, I've tried to make this work for at least 10 hours now, and can't find any solution anywhere. I'm too noob with linux for the moment. List of what I tried: Installing latest wxWidget package (3.0.2) Removing wx2.8 Removing wx3.0.2 Installing wx3.0.0... Each of the wx3.0.2 and 3.0.0 install were returning correct version number to the command wx-config --verion-full. I created a link each tim using sudo ln -sv wx-3.0/wx wx ...But still, cmake try to find a 3.0 minimum required version in a wx-2.8 folder which doesn't exist anymore... Here is the terminal output below: I give up for today... purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake ../CMake Error at CMakeModules/FindwxWidgets.cmake:868 (file): file Internal CMake error when trying to open file: /usr/include/wx-2.8/wx/version.h for reading. Call Stack (most recent call first): CMakeLists.txt:411 (find_package) CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:136 (message): Could NOT find wxWidgets: Found unsuitable version "..", but required is at least "3.0.0" (found -L/usr/lib/i386-linux-gnu;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0) Call Stack (most recent call first): CMakeModules/FindPackageHandleStandardArgs.cmake:341 (_FPHSA_FAILURE_MESSAGE) CMakeModules/FindwxWidgets.cmake:902 (find_package_handle_standard_args) CMakeLists.txt:411 (find_package) -- Configuring incomplete, errors occurred! See also"/home/purebasic/build/kicad/kicad.bzr/build/CMakeFiles/CMakeOutput.log". ___ 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] [PATCH] kicad-install.sh: Enhanced Error Handling with outcomes of cmake and make
Here is the patch (attached as well) for enhancing "kicad-install.sh" handling
of two error situations with Debian/Ubuntu:
1. The prerequisites are installed individually, rather than a grouped. Thus
it avoids failing for ALL of the group.2. The script stops when either cmake or
make fails. Thus it avoids a false installation.
The patch has been tested and passed with Ubuntu 14.04 LTS.
--Joe
--- old/kicad-install.sh 2014-10-14 18:41:37.834788832 -0600
+++ new/kicad-install.sh 2014-10-14 18:41:13.462986918 -0600
@@ -89,21 +89,26 @@
# assume all these Debian, Mint, Ubuntu systems have same prerequisites
if [ "$(expr match "$PM" '.*\(apt-get\)')" == "apt-get" ]; then
#echo "debian compatible system"
- sudo apt-get install \
- bzr \
- bzrtools \
- build-essential \
- cmake \
- cmake-curses-gui \
- debhelper \
- doxygen \
- grep \
- libbz2-dev \
- libcairo2-dev \
- libglew-dev \
- libssl-dev \
- libwxgtk3.0-dev \
+ prerequisite_list="
+ bzr
+ bzrtools
+ build-essential
+ cmake
+ cmake-curses-gui
+ debhelper
+ doxygen
+ grep
+ libbz2-dev
+ libcairo2-dev
+ libglew-dev
+ libssl-dev
+ libwxgtk3.0-dev
python-wxgtk3.0
+ "
+ for p in ${prerequisite_list}
+ do
+ sudo apt-get install $p
+ done
# assume all yum systems have same prerequisites
elif [ "$(expr match "$PM" '.*\(yum\)')" == "yum" ]; then
@@ -255,14 +260,14 @@
cd kicad.bzr
if [ ! -d "build" ]; then
mkdir build && cd build
- cmake $OPTS ../
+ cmake $OPTS ../ || exit 1
else
cd build
# Although a "make clean" is sometimes needed, more often than not it
slows down the update
# more than it is worth. Do it manually if you need to in this
directory.
# make clean
fi
- make -j4
+ make -j4 || exit 1
echo " kicad compiled."
--- old/kicad-install.sh 2014-10-14 18:41:37.834788832 -0600
+++ new/kicad-install.sh 2014-10-14 18:41:13.462986918 -0600
@@ -89,21 +89,26 @@
# assume all these Debian, Mint, Ubuntu systems have same prerequisites
if [ "$(expr match "$PM" '.*\(apt-get\)')" == "apt-get" ]; then
#echo "debian compatible system"
-sudo apt-get install \
-bzr \
-bzrtools \
-build-essential \
-cmake \
-cmake-curses-gui \
-debhelper \
-doxygen \
-grep \
-libbz2-dev \
-libcairo2-dev \
-libglew-dev \
-libssl-dev \
-libwxgtk3.0-dev \
+prerequisite_list="
+bzr
+bzrtools
+build-essential
+cmake
+cmake-curses-gui
+debhelper
+doxygen
+grep
+libbz2-dev
+libcairo2-dev
+libglew-dev
+libssl-dev
+libwxgtk3.0-dev
python-wxgtk3.0
+ "
+ for p in ${prerequisite_list}
+ do
+ sudo apt-get install $p
+ done
# assume all yum systems have same prerequisites
elif [ "$(expr match "$PM" '.*\(yum\)')" == "yum" ]; then
@@ -255,14 +260,14 @@
cd kicad.bzr
if [ ! -d "build" ]; then
mkdir build && cd build
-cmake $OPTS ../
+cmake $OPTS ../ || exit 1
else
cd build
# Although a "make clean" is sometimes needed, more often than not it slows down the update
# more than it is worth. Do it manually if you need to in this directory.
# make clean
fi
-make -j4
+make -j4 || exit 1
echo " kicad compiled."
___
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] Library Editor naming consistency
On 10/14/2014 4:54 PM, Mark Roszko wrote: >> The manual uses component throughout and indeed Component name in the UI >> Component properties dialog. All the screenshots show Component too. >> If eeschema has changed these, they should be changed back > > An manual should never define the software, it should explain the > software. Or else we'll never have new features or evolutions in > feature sets. > As it stands right now, the pcbnew manual is now out of date because > modules have been completely renamed to footprints in the last few > days. > > I wish the manuals were plain text based, I would be more than happy > to update documentation as I change things. I do it all the time with > the Linux kernel patches I upstream where its a requirement ;) There is actually work on that taking place this right now. Hopefully we will have a list of viable alternatives in the not too distant future and an overview of the advantages and disadvantages of each format so we can make a informed decision. I'm leaning towards one of the markdown formats myself. However, before any decision is make, I will solicit the input of the development team. > > Schematic Library Editor does seem like the most neutral(i.e. it > doesn't pick parts, component or symbol to call it) that the thread > seems to be leaning to. > ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
On 10/14/2014 5:09 PM, Mark Roszko wrote: > Ah, the only thing that changed is I moved all the comments from the > .cpp to .h as you asked before so you can't ding me for that :P And a > description. > There is a white space line I just noticed. Not a problem. I thought I that was the latest version on my work computer. I'll do a bzr merge next time so that way it is what ever is the merge branch. > > > > I am having trouble with wxFormBuillder. I cannot find an > ubuntu/debian compatible package that KiCAD uses anywhere. In fact it > appears Debian somehow diverged from Ubuntu 14 package versions when I > was messing around. Right now, I can get a wxFormBuilder from Ubuntu > upstream that cannot open any KiCAD files, or use the latest > Formbuilder PPA that is a revision ahead :/ > I use the PPA as well. I believe they archive older versions as well. I guess I update to 3.5.0-beta. ___ 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] Library Editor naming consistency
Well, going back to what the manual states it was before is indeed a good point. If this is the final decision, I'll update the library convention. On Tue, Oct 14, 2014 at 5:20 PM, Brian Sidebotham < brian.sidebot...@gmail.com> wrote: > On 14 October 2014 22:16, Mark Roszko wrote: > > Be it just semantics but for me > > > > Documentation != Manual != Specifications > > > > It is probably just semantics, but then this is wrong because > apparently Documentation != Manual !? > > > I wish the manuals were plain text based, I would be more than happy > > to update documentation as I change things. I do it all the time with > > the Linux kernel patches I upstream where its a requirement ;) > > Best Regards, > > Brian. > > ___ > 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] [PATCH] eeschema: add Select button for footprints in single component field edits
On 14 October 2014 22:09, Mark Roszko wrote: > Ah, the only thing that changed is I moved all the comments from the > .cpp to .h as you asked before so you can't ding me for that :P And a > description. > There is a white space line I just noticed. > > > > I am having trouble with wxFormBuillder. I cannot find an > ubuntu/debian compatible package that KiCAD uses anywhere. In fact it > appears Debian somehow diverged from Ubuntu 14 package versions when I > was messing around. Right now, I can get a wxFormBuilder from Ubuntu > upstream that cannot open any KiCAD files, or use the latest > Formbuilder PPA that is a revision ahead :/ > I'm also using the same PPA because that's the only way to easily get wxFormBuilder on Ubuntu that can open the KiCad dialogs. Wayne, as I'm about to commit changes to eeschema/dialogs/eeschema/dialogs_eeschema_options_base.fbp with FileVersion 1.13 I quickly grepped the dialogs and there are quite a few dialogs at the same FileVersion; grep FileVersion -r . ./dialog_annotate_base.fbp: ./dialog_bom_base.fbp: ./dialog_choose_component_base.fbp: ./dialog_edit_component_in_lib_base.fbp: ./dialog_edit_component_in_schematic_fbp.fbp: ./dialog_edit_label_base.fbp: ./dialog_edit_libentry_fields_in_lib_base.fbp: ./dialog_eeschema_config_fbp.fbp: ./dialog_eeschema_options_base.fbp: ./dialog_erc_base.fbp: ./dialog_libedit_dimensions_base.fbp: ./dialog_libedit_options_base.fbp: ./dialog_lib_edit_draw_item.fbp: ./dialog_lib_edit_pin_base.fbp: ./dialog_lib_edit_text_base.fbp: ./dialog_lib_new_component.fbp: ./dialog_netlist_base.fbp: ./dialog_plot_schematic_base.fbp: ./dialog_print_using_printer_base.fbp: ./dialog_sch_edit_sheet_pin_base.fbp: ./dialog_sch_find.fbp: ./dialog_sch_sheet_props.fbp: Best Regards, Brian. ___ 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] [RFC]: Make hotkey editor polished
FYI, latest code is sitting in merge proposal https://code.launchpad.net/~mark-roszko/kicad/hotkey/+merge/238225 ___ 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] Library Editor naming consistency
On 14 October 2014 22:16, Mark Roszko wrote: > Be it just semantics but for me > > Documentation != Manual != Specifications > It is probably just semantics, but then this is wrong because apparently Documentation != Manual !? > I wish the manuals were plain text based, I would be more than happy > to update documentation as I change things. I do it all the time with > the Linux kernel patches I upstream where its a requirement ;) Best Regards, Brian. ___ 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] Library Editor naming consistency
Be it just semantics but for me Documentation != Manual != Specifications A specification defines the feature, behaviors, etc. This is written ahead of time. A manual is for end users in a descriptive and easy to read form to follow. Documentation is for developers to understand what is going on past, present and future ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
Ah, the only thing that changed is I moved all the comments from the .cpp to .h as you asked before so you can't ding me for that :P And a description. There is a white space line I just noticed. I am having trouble with wxFormBuillder. I cannot find an ubuntu/debian compatible package that KiCAD uses anywhere. In fact it appears Debian somehow diverged from Ubuntu 14 package versions when I was messing around. Right now, I can get a wxFormBuilder from Ubuntu upstream that cannot open any KiCAD files, or use the latest Formbuilder PPA that is a revision ahead :/ ___ 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] Library Editor naming consistency
On 14 October 2014 21:57, Brian Sidebotham wrote: > On 14 October 2014 21:54, Mark Roszko wrote: >>>The manual uses component throughout and indeed Component name in the UI >>>Component properties dialog. All the screenshots show Component too. >>>If eeschema has changed these, they should be changed back >> >> An manual should never define the software, it should explain the >> software. Or else we'll never have new features or evolutions in >> feature sets. > > No, you do - you write the documentation first and then write the > code. Then you know what's called what and how it's meant to work. > Even if the documentation is a blueprint, or email or in this case the > manual. > > As with all these things, it's just an opinion, but I nearly always > start with the documentation and then write the code to suit. Funnily enough, just about to commit, and then write the documentation to suit! lol Best Regards, Brian. ___ 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] Library Editor naming consistency
On 10/14/2014 4:43 PM, Brian Sidebotham wrote: > On 13 October 2014 17:22, Wayne Stambaugh wrote: >> On 10/12/2014 9:14 PM, Mark Roszko wrote: >>> Very minor but the main KiCAD window calls it "Schematic Library >>> Editor", eeschema calls it "Library Editor" and the window itself is >>> "Parts Library Editor". >>> >>> Can the name be standardized? >>> >>> It might be better to just call it "Component Library Editor" because >>> that's what the schematic symbols are called instead of Parts. Just >>> like PCB Footprint Editor is for Footprints. >>> >> >> The easy answer to your question is yes, the naming can and should be >> consistent. The hard part of your question is consistently what? This >> topic has been thoroughly discussed before. You will find there is >> really no consensus. Personally, I prefer symbol. When I think of >> parts or components, I think of the physical objects themselves. I >> don't actually place a resistor or an IC in a schematic. I place a >> symbolic representation of that component in my schematic. Dick's >> preference was part and he had valid justifications for his preference. >> He even renamed some of the Eeschema code object names from COMPONENT >> to PART. I really don't have a strong preference, that's why I never >> pushed the issue. I doubt you are going to get a consensus on this >> issue. You'll have to pick a term and live with the unhappy developers >> and users. Welcome to open source programming :). > > I think the manual should probably be the defacto standard, or at > least the first place to look in these inconsistency issues. The > manual uses component throughout and indeed Component name in the UI > Component properties dialog. All the screenshots show Component too. > If eeschema has changed these, they should be changed back. If a > change is made, it'll have to also be rippled through the > documentation which is a very heavy change and that in turn may cause > the translators a headache too. > > Part is not a good candidate because, as per the manual we already > have something designated a part and that is essentially the > individual "gates" in the multi-gate IC. I find the description of > parts per package a bit weird, it should really be "Number of parts > per component" and "Parts in component locked (cannot be swapped)" Actually the term "Unit" is used for UI strings not parts. This is a case of the documentation lagging the code changes. I made that change a while ago in response to a bug report about naming consistency and confusing terminology. I believe I changed everything concerning components with multiple sub-units. If I missed anything, please let me know and I will fix it. > > Of course,it looks like the manual and editor are out-of-sync as the > library editor refers to parts as units and components as parts. It > can get so confusing when the two are not in sync! It'll take longer > to fix the documentation compared to fixing the code most likely. > > I would call it "Schematic Library Editor" or else "Component Library > Editor", the latter probably being more accurate. I fine with changing the UI strings to use the term component. > > I also don't have a strong opinion, but consistency is key. > > Best Regards, > > Brian. > ___ 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] Library Editor naming consistency
On 14 October 2014 21:54, Mark Roszko wrote: >>The manual uses component throughout and indeed Component name in the UI >>Component properties dialog. All the screenshots show Component too. >>If eeschema has changed these, they should be changed back > > An manual should never define the software, it should explain the > software. Or else we'll never have new features or evolutions in > feature sets. No, you do - you write the documentation first and then write the code. Then you know what's called what and how it's meant to work. Even if the documentation is a blueprint, or email or in this case the manual. As with all these things, it's just an opinion, but I nearly always start with the documentation and then write the code to suit. Best Regards, Brian. ___ 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] Library Editor naming consistency
>The manual uses component throughout and indeed Component name in the UI >Component properties dialog. All the screenshots show Component too. >If eeschema has changed these, they should be changed back An manual should never define the software, it should explain the software. Or else we'll never have new features or evolutions in feature sets. As it stands right now, the pcbnew manual is now out of date because modules have been completely renamed to footprints in the last few days. I wish the manuals were plain text based, I would be more than happy to update documentation as I change things. I do it all the time with the Linux kernel patches I upstream where its a requirement ;) Schematic Library Editor does seem like the most neutral(i.e. it doesn't pick parts, component or symbol to call it) that the thread seems to be leaning to. ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
Hey Mark, I just committed this patch to r5188 of the product branch. Thank you for you contribution to KiCad. I do have a few comments. 1) Doxygen comments do not belong in the source file. They belong in the header file. I moved them this time. 2) There was some trailing whitespace. 3) Please downgrade the your version of wxFormBuilder at least one revision. I know it's tempting to use the latest and greatest but for some users that means building it from source every time someone else edits a dialog box with a newer version. I usually try to stay at least one rev behind. It's also a good idea to announce on the mailing list if you want to use the latest version so the rest of us aren't caught off guard when we go to edit a dialog box. 4) Please submit a commit message along with the patch so I don't have to look at the diff to write the commit message. The preferred format is: General statement describing your patch. (fixes lp:x as required) * Details of each change and most importantly why you made the change. * More details * Even more detail Thanks, Wayne On 10/11/2014 1:43 AM, Mark Roszko wrote: > Hi, > > This patch makes the changes to add a selection button to the simple > dialog that appears when you right-click on a component and choose > Edit Component > Footprint. The button will open the footprint > browser. This is just like the component property editor having the > assign footprint button. > + Doxygenization of the class. > > This also works in the library editor when you click on the footprint > text and go to edit it. > > Patches attached and a bazr branch submitted for merge. > > https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick > > > > ___ > 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] Library Editor naming consistency
On 13 October 2014 17:22, Wayne Stambaugh wrote: > On 10/12/2014 9:14 PM, Mark Roszko wrote: >> Very minor but the main KiCAD window calls it "Schematic Library >> Editor", eeschema calls it "Library Editor" and the window itself is >> "Parts Library Editor". >> >> Can the name be standardized? >> >> It might be better to just call it "Component Library Editor" because >> that's what the schematic symbols are called instead of Parts. Just >> like PCB Footprint Editor is for Footprints. >> > > The easy answer to your question is yes, the naming can and should be > consistent. The hard part of your question is consistently what? This > topic has been thoroughly discussed before. You will find there is > really no consensus. Personally, I prefer symbol. When I think of > parts or components, I think of the physical objects themselves. I > don't actually place a resistor or an IC in a schematic. I place a > symbolic representation of that component in my schematic. Dick's > preference was part and he had valid justifications for his preference. > He even renamed some of the Eeschema code object names from COMPONENT > to PART. I really don't have a strong preference, that's why I never > pushed the issue. I doubt you are going to get a consensus on this > issue. You'll have to pick a term and live with the unhappy developers > and users. Welcome to open source programming :). I think the manual should probably be the defacto standard, or at least the first place to look in these inconsistency issues. The manual uses component throughout and indeed Component name in the UI Component properties dialog. All the screenshots show Component too. If eeschema has changed these, they should be changed back. If a change is made, it'll have to also be rippled through the documentation which is a very heavy change and that in turn may cause the translators a headache too. Part is not a good candidate because, as per the manual we already have something designated a part and that is essentially the individual "gates" in the multi-gate IC. I find the description of parts per package a bit weird, it should really be "Number of parts per component" and "Parts in component locked (cannot be swapped)" Of course,it looks like the manual and editor are out-of-sync as the library editor refers to parts as units and components as parts. It can get so confusing when the two are not in sync! It'll take longer to fix the documentation compared to fixing the code most likely. I would call it "Schematic Library Editor" or else "Component Library Editor", the latter probably being more accurate. I also don't have a strong opinion, but consistency is key. Best Regards, Brian. ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
Thanks Orson. I think this patch will be well received so I'm going to go ahead and commit it. Wayne On 10/14/2014 4:19 PM, Maciej Sumiński wrote: > I have briefly tested it and read the patch. No issues came to my mind, > but I am not very familiar with eeschema code. I like the change in > the eeschema behaviour as well - good job! > > Regards, > Orson > > On 10/14/2014 03:58 PM, Wayne Stambaugh wrote: >> Has anyone else looked at this patch? If you haven't, it adds a >> select button that launches the footprint viewer to select a >> footprint to the edit field properties dialog when the footprint >> field is selected. I personally like it but since it's behavioral >> change I would like some input before I commit it. > >> Thanks, > >> Wayne > >> On 10/11/2014 1:43 AM, Mark Roszko wrote: >>> Hi, >>> >>> This patch makes the changes to add a selection button to the >>> simple dialog that appears when you right-click on a component >>> and choose Edit Component > Footprint. The button will open the >>> footprint browser. This is just like the component property >>> editor having the assign footprint button. + Doxygenization of >>> the class. >>> >>> This also works in the library editor when you click on the >>> footprint text and go to edit it. >>> >>> Patches attached and a bazr branch submitted for merge. >>> >>> https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick >>> >>> >>> >>> >>> >>> > ___ >>> 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] [PATCH] eeschema: add Select button for footprints in single component field edits
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have briefly tested it and read the patch. No issues came to my mind, but I am not very familiar with eeschema code. I like the change in the eeschema behaviour as well - good job! Regards, Orson On 10/14/2014 03:58 PM, Wayne Stambaugh wrote: > Has anyone else looked at this patch? If you haven't, it adds a > select button that launches the footprint viewer to select a > footprint to the edit field properties dialog when the footprint > field is selected. I personally like it but since it's behavioral > change I would like some input before I commit it. > > Thanks, > > Wayne > > On 10/11/2014 1:43 AM, Mark Roszko wrote: >> Hi, >> >> This patch makes the changes to add a selection button to the >> simple dialog that appears when you right-click on a component >> and choose Edit Component > Footprint. The button will open the >> footprint browser. This is just like the component property >> editor having the assign footprint button. + Doxygenization of >> the class. >> >> This also works in the library editor when you click on the >> footprint text and go to edit it. >> >> Patches attached and a bazr branch submitted for merge. >> >> https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick >> >> >> >> >> >> ___ >> 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 > -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBAgAGBQJUPYVpAAoJEBRwGu1hpbJ1+nMH/3T5EU2t/eTbMYd3Av707ZNJ zydL9J1tCel1mbK+urKzYwlVb2h0SU1IsVgzDI5RJayzQYXvrrbPuZr1X2H6oG4M 3RzDqSlstKMNqnBfk+aUclMi/RaVeq/t0mAzz4lgBUUoHzmqq1rLGCCccnfNFFAM pn5ugNwK79rR38ryZ9TLV214Yy65RdmW364KXMVikZCL87ggv8mzbV1Gwd2+UBmh m1JubMwjtUwjvrYqUvkipQgvnzQx21vCwf00jd0DYjPJI1UJaGMPxo8OC+tPDBGw UeAPv1Za8qMC6UN51NNZyaiy5+io78unXXMnmURoRrbY7TRmpU6zYd7g7fW/4PY= =54N8 -END PGP SIGNATURE- ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
2014-10-14 19:57 GMT+02:00 Wayne Stambaugh : > On 10/14/2014 1:30 PM, Nick Østergaard wrote: >> I forgot about this patch, but I have now applied it and do not see >> any issue with it. I cannot comment on the code. >> >> But while testing it out I noticed that above the textbox it just says >> "Text" in a label. Shouldn't this be "Footprint name" or something >> similar? > > This dialog is generic for editing all fields not just the footprint > field. The problem is four of the fields are reserved, reference > designator, value, footprint, and document file. Changing "Text" to > something more descriptive for these four fields would be fairly simple. > User defined fields would be another story. I don't believe the > component field template code can store a description along with the > field name. In this case you would have to use something generic and > possibly confusing like "User Defined Field 1". I would leave it as > "Text" for now until a better solution can be found. The name of the > field is included in the dialog title so that does help somewhat. Ok, I see. I just found it confusing that it was even there. It does not really matter much. I do not have a strong opinion on this. So I guess it is good as is. >> >> Nick >> >> 2014-10-14 17:24 GMT+02:00 Wayne Stambaugh : >>> I've already applied the patch to my branch and did some testing. It >>> works as advertized but I just want to make sure we are for the most >>> part on board with the changes. I'll wait a while to make sure there >>> are no strong objections before I commit the changes. Thanks for the >>> feedback. >>> >>> Cheers, >>> >>> Wayne >>> >>> On 10/14/2014 11:15 AM, Brian Sidebotham wrote: Sorry, I didn't get much chance to look at it - but I liked the idea of it - I think this is one of the very reasons behind the KiWay work. It's certainly a bonus of that work which we should be reaping. I didn't get a chance to apply and test though. Let me know if you need that. Best Regards, Brian. On 14 October 2014 14:58, Wayne Stambaugh wrote: > Has anyone else looked at this patch? If you haven't, it adds a select > button that launches the footprint viewer to select a footprint to the > edit field properties dialog when the footprint field is selected. I > personally like it but since it's behavioral change I would like some > input before I commit it. > > Thanks, > > Wayne > > On 10/11/2014 1:43 AM, Mark Roszko wrote: >> Hi, >> >> This patch makes the changes to add a selection button to the simple >> dialog that appears when you right-click on a component and choose >> Edit Component > Footprint. The button will open the footprint >> browser. This is just like the component property editor having the >> assign footprint button. >> + Doxygenization of the class. >> >> This also works in the library editor when you click on the footprint >> text and go to edit it. >> >> Patches attached and a bazr branch submitted for merge. >> >> https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick >> >> >> >> ___ >> 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 >> > > > > ___ > 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] [PATCH] eeschema: add Select button for footprints in single component field edits
On 10/14/2014 1:30 PM, Nick Østergaard wrote: > I forgot about this patch, but I have now applied it and do not see > any issue with it. I cannot comment on the code. > > But while testing it out I noticed that above the textbox it just says > "Text" in a label. Shouldn't this be "Footprint name" or something > similar? This dialog is generic for editing all fields not just the footprint field. The problem is four of the fields are reserved, reference designator, value, footprint, and document file. Changing "Text" to something more descriptive for these four fields would be fairly simple. User defined fields would be another story. I don't believe the component field template code can store a description along with the field name. In this case you would have to use something generic and possibly confusing like "User Defined Field 1". I would leave it as "Text" for now until a better solution can be found. The name of the field is included in the dialog title so that does help somewhat. > > Nick > > 2014-10-14 17:24 GMT+02:00 Wayne Stambaugh : >> I've already applied the patch to my branch and did some testing. It >> works as advertized but I just want to make sure we are for the most >> part on board with the changes. I'll wait a while to make sure there >> are no strong objections before I commit the changes. Thanks for the >> feedback. >> >> Cheers, >> >> Wayne >> >> On 10/14/2014 11:15 AM, Brian Sidebotham wrote: >>> Sorry, I didn't get much chance to look at it - but I liked the idea >>> of it - I think this is one of the very reasons behind the KiWay work. >>> It's certainly a bonus of that work which we should be reaping. >>> >>> I didn't get a chance to apply and test though. Let me know if you need >>> that. >>> >>> Best Regards, >>> >>> Brian. >>> >>> On 14 October 2014 14:58, Wayne Stambaugh wrote: Has anyone else looked at this patch? If you haven't, it adds a select button that launches the footprint viewer to select a footprint to the edit field properties dialog when the footprint field is selected. I personally like it but since it's behavioral change I would like some input before I commit it. Thanks, Wayne On 10/11/2014 1:43 AM, Mark Roszko wrote: > Hi, > > This patch makes the changes to add a selection button to the simple > dialog that appears when you right-click on a component and choose > Edit Component > Footprint. The button will open the footprint > browser. This is just like the component property editor having the > assign footprint button. > + Doxygenization of the class. > > This also works in the library editor when you click on the footprint > text and go to edit it. > > Patches attached and a bazr branch submitted for merge. > > https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick > > > > ___ > 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 > ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
I forgot about this patch, but I have now applied it and do not see any issue with it. I cannot comment on the code. But while testing it out I noticed that above the textbox it just says "Text" in a label. Shouldn't this be "Footprint name" or something similar? Nick 2014-10-14 17:24 GMT+02:00 Wayne Stambaugh : > I've already applied the patch to my branch and did some testing. It > works as advertized but I just want to make sure we are for the most > part on board with the changes. I'll wait a while to make sure there > are no strong objections before I commit the changes. Thanks for the > feedback. > > Cheers, > > Wayne > > On 10/14/2014 11:15 AM, Brian Sidebotham wrote: >> Sorry, I didn't get much chance to look at it - but I liked the idea >> of it - I think this is one of the very reasons behind the KiWay work. >> It's certainly a bonus of that work which we should be reaping. >> >> I didn't get a chance to apply and test though. Let me know if you need that. >> >> Best Regards, >> >> Brian. >> >> On 14 October 2014 14:58, Wayne Stambaugh wrote: >>> Has anyone else looked at this patch? If you haven't, it adds a select >>> button that launches the footprint viewer to select a footprint to the >>> edit field properties dialog when the footprint field is selected. I >>> personally like it but since it's behavioral change I would like some >>> input before I commit it. >>> >>> Thanks, >>> >>> Wayne >>> >>> On 10/11/2014 1:43 AM, Mark Roszko wrote: Hi, This patch makes the changes to add a selection button to the simple dialog that appears when you right-click on a component and choose Edit Component > Footprint. The button will open the footprint browser. This is just like the component property editor having the assign footprint button. + Doxygenization of the class. This also works in the library editor when you click on the footprint text and go to edit it. Patches attached and a bazr branch submitted for merge. https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick ___ 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 ___ 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] Library Editor naming consistency
Le 13/10/2014 16:51, Carl Poirier a écrit : Benoît, this is exactly what I tried to say. I wasn't talking about symbols in Altium, but about components. They are already associated with footprints and so on, thus making them components. They can be not associated and still used... Here a view of the schematic editor, with the library panel open and a totally empty component selected. Here is a view of the schematic library list in the schematic library editor. Notice all the fields: The models linked can be a footprint, a simulation model, an ibis model and a signal integrity model. You can add several footprints for one component which is useful for N, M, L IPC densities and generic components. The drawing that we are working on in the schematic library editor is a symbol. This is where I don't agree. You are indeed drawing a symbol, but mostly you will also set other proprieties making it a component. It doesn't need to have a footprint. For example, an ATMega128rfa1 is a component, not a symbol. In the component properties, we can only put a filter on footprints for it, but AFAIK, that's about it. So I'd say it still stands as a symbol. If some more pairing is going to be done in this editor, such as a unique footprint, a SPICE model, and so on, then we might as well call the editor a component editor. I totally agree with this. The name Component Editor is ambiguous in this context and shouldn't be used here at all, never. I see a /Component editor/ like an editing tool for both the schematic component and the footprint in the same time, and store the resulting footprint privately attached to the component to avoid corrupting the other component using the same base footprint. I think the editor should be called /Schematic Library Editor/, to explicitly say that what you edit is for eeschema. The footprint editor should be called /PCB Library Editor/ to keep consistancy. In fact those are the name altium folks choosed. But what if it's used to create only a symbol? I will take this example: PCB Libraries can contain things that are not footprint (fiducials, holes...). But footprints are not called PCB Features. [off topic] Also, Eeschema should have a method for adding logos or other stuffs (I think it has), and these elements shouldn't be added in a schematic the same way a component is added. You may not store these graphical items in a schlib. You don't want the logo of you company to appears in BOM component list, you just want it in your printings. Also, and this is important: you may put in the schema every objects that will become physical or logical parts of the project (the pcb, the box, screws, cables...). Some electronic engineer even put the firmware version in the schematic which is very smart and would have saved me a lot of time if I knew that when I started. I even burned down a mcu because of wrong version. Now, you want to upload some code but don't remember what is what, well IT'S IN THE BOM, YAY :D. This is good design practice. Components that aren't implantable (screws, box, fiducials) are marked NI in the BOM (not implantable) for the PCB assemblers to know it's not their business. [/off topic] Furthermore, how would the symbol and component libraries be differentiated, once some more serious associations are done? Will they all be mixed together? I think that's also part of the problem. I don't know what is planned about this, but I would strongly support a 2 libraries system based on what already exists, with an All-in-one schematic library containing the abstracts schematics datas of a component (symbol, simulation model, link to footprint) along with a All-In-One PCB library containing the real world PCB datas (footprint, 3d model). A component like a screw for example is very easily used in the whole project. A third library would be useful to make footprints private and pre linked to a schematic component, but it's a pain in the ass using and managing them (Altium daunting system). I don't recommend it, there should be better solutions no one has found yet. The project library is a good feature for this :) On Mon, Oct 13, 2014 at 8:10 AM, Benoît Roehr mailto:benoit.roehr...@gmail.com>> wrote: In KiCAD each project can have its own library of footprints, so this idea duplicates, that exist already. OK thanks ! I did not know about it before :) Le 13/10/2014 13:21, LordBlick a écrit : In response to a message written on 13.10.2014 12:04, from Benoît Roehr: Le 13/10/2014 11:40, LordBlick a écrit : In response to a message written on 13.10.2014 08:01, from Benoît Roehr: For kicad, it could be a good thing to be able to embed a single footprint to a component if the footprint is really special, but it's non sens if you can
Re: [Kicad-developers] [PATCH] eeschema: add Select button for footprints in single component field edits
On Oct 14, 2014, at 6:58 AM, Wayne Stambaugh wrote: > Has anyone else looked at this patch? If you haven't, it adds a select > button that launches the footprint viewer to select a footprint to the > edit field properties dialog when the footprint field is selected. I > personally like it but since it's behavioral change I would like some > input before I commit it. I will test this patch today. It's a brilliant idea. ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
I've already applied the patch to my branch and did some testing. It works as advertized but I just want to make sure we are for the most part on board with the changes. I'll wait a while to make sure there are no strong objections before I commit the changes. Thanks for the feedback. Cheers, Wayne On 10/14/2014 11:15 AM, Brian Sidebotham wrote: > Sorry, I didn't get much chance to look at it - but I liked the idea > of it - I think this is one of the very reasons behind the KiWay work. > It's certainly a bonus of that work which we should be reaping. > > I didn't get a chance to apply and test though. Let me know if you need that. > > Best Regards, > > Brian. > > On 14 October 2014 14:58, Wayne Stambaugh wrote: >> Has anyone else looked at this patch? If you haven't, it adds a select >> button that launches the footprint viewer to select a footprint to the >> edit field properties dialog when the footprint field is selected. I >> personally like it but since it's behavioral change I would like some >> input before I commit it. >> >> Thanks, >> >> Wayne >> >> On 10/11/2014 1:43 AM, Mark Roszko wrote: >>> Hi, >>> >>> This patch makes the changes to add a selection button to the simple >>> dialog that appears when you right-click on a component and choose >>> Edit Component > Footprint. The button will open the footprint >>> browser. This is just like the component property editor having the >>> assign footprint button. >>> + Doxygenization of the class. >>> >>> This also works in the library editor when you click on the footprint >>> text and go to edit it. >>> >>> Patches attached and a bazr branch submitted for merge. >>> >>> https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick >>> >>> >>> >>> ___ >>> 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] [PATCH] eeschema: add Select button for footprints in single component field edits
Sorry, I didn't get much chance to look at it - but I liked the idea of it - I think this is one of the very reasons behind the KiWay work. It's certainly a bonus of that work which we should be reaping. I didn't get a chance to apply and test though. Let me know if you need that. Best Regards, Brian. On 14 October 2014 14:58, Wayne Stambaugh wrote: > Has anyone else looked at this patch? If you haven't, it adds a select > button that launches the footprint viewer to select a footprint to the > edit field properties dialog when the footprint field is selected. I > personally like it but since it's behavioral change I would like some > input before I commit it. > > Thanks, > > Wayne > > On 10/11/2014 1:43 AM, Mark Roszko wrote: >> Hi, >> >> This patch makes the changes to add a selection button to the simple >> dialog that appears when you right-click on a component and choose >> Edit Component > Footprint. The button will open the footprint >> browser. This is just like the component property editor having the >> assign footprint button. >> + Doxygenization of the class. >> >> This also works in the library editor when you click on the footprint >> text and go to edit it. >> >> Patches attached and a bazr branch submitted for merge. >> >> https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick >> >> >> >> ___ >> 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] Website update help.
On 10/14/2014 10:16 AM, Nick Østergaard wrote: > 2014-10-12 1:37 GMT+02:00 Wayne Stambaugh : >> I need some help with the KiCad website if anybody as some spare time. >> >> First the easy one. I was recently contacted by the owner of the >> Contextual Electronics website. He recently released all of his KiCad >> instructional video on youtube at >> https://www.youtube.com/user/contextualelectronic/playlists. This link >> should replace the one already used by "Videos by Chris Gammel" since it >> includes all of his KiCad videos. > > Hi Wayne > > I have just updated the link on the tutorials page [1], is that all > you were requesting or did you have anything more elaborate in mind? > > Nick > > [1] http://www.kicad-pcb.org/display/KICAD/Tutorials > Hey Nick, That was it. Thanks for the help. 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
Re: [Kicad-developers] Website update help.
2014-10-12 1:37 GMT+02:00 Wayne Stambaugh : > I need some help with the KiCad website if anybody as some spare time. > > First the easy one. I was recently contacted by the owner of the > Contextual Electronics website. He recently released all of his KiCad > instructional video on youtube at > https://www.youtube.com/user/contextualelectronic/playlists. This link > should replace the one already used by "Videos by Chris Gammel" since it > includes all of his KiCad videos. Hi Wayne I have just updated the link on the tutorials page [1], is that all you were requesting or did you have anything more elaborate in mind? Nick [1] http://www.kicad-pcb.org/display/KICAD/Tutorials ___ 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] [PATCH] eeschema: add Select button for footprints in single component field edits
Has anyone else looked at this patch? If you haven't, it adds a select button that launches the footprint viewer to select a footprint to the edit field properties dialog when the footprint field is selected. I personally like it but since it's behavioral change I would like some input before I commit it. Thanks, Wayne On 10/11/2014 1:43 AM, Mark Roszko wrote: > Hi, > > This patch makes the changes to add a selection button to the simple > dialog that appears when you right-click on a component and choose > Edit Component > Footprint. The button will open the footprint > browser. This is just like the component property editor having the > assign footprint button. > + Doxygenization of the class. > > This also works in the library editor when you click on the footprint > text and go to edit it. > > Patches attached and a bazr branch submitted for merge. > > https://code.launchpad.net/~mark-roszko/kicad/eeschema_footprint_pick > > > > ___ > 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
