Index: doc-rnd/devlog/20150731a_menu.html
===================================================================
--- doc-rnd/devlog/20150731a_menu.html (revision 772)
+++ doc-rnd/devlog/20150731a_menu.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
Dynamic menus
Background
Before integrating gpmi scripting, pcb-rnd needs to be prepared to
Index: doc-rnd/devlog/20150731b_gtk.html
===================================================================
--- doc-rnd/devlog/20150731b_gtk.html (revision 772)
+++ doc-rnd/devlog/20150731b_gtk.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
dynamic gtk menus
As described in the previous post,
pcb-rnd will feature dynamic menus. I first implemented this in the
Index: doc-rnd/devlog/20150801a_events.html
===================================================================
--- doc-rnd/devlog/20150801a_events.html (revision 772)
+++ doc-rnd/devlog/20150801a_events.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
events
PCB has a nice action infrastructure: most user actions are
implemented in smallish functions taking (int argc, char *argv[]). Menu
Index: doc-rnd/devlog/20150803a_scriptig.html
===================================================================
--- doc-rnd/devlog/20150803a_scriptig.html (revision 772)
+++ doc-rnd/devlog/20150803a_scriptig.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
scripting
Most of the infrastructure for a scriptable pcb had been there in pcb-gpmi.
I had also finished some gpmi cleanup and pcb
Index: doc-rnd/devlog/20150816a_scriptig.html
===================================================================
--- doc-rnd/devlog/20150816a_scriptig.html (revision 772)
+++ doc-rnd/devlog/20150816a_scriptig.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
scripting, 2
I've been working on the documentation for pcb-rnd scripting lately.
Proof reading and comments would be appreciated. The documents are
Index: doc-rnd/devlog/20150820a_dimensions.html
===================================================================
--- doc-rnd/devlog/20150820a_dimensions.html (revision 772)
+++ doc-rnd/devlog/20150820a_dimensions.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
fp2anim dimensions
After attacking the qfn()/qfp() parametric footprint problem today,
I realized fp2anim lacked a very important feature: dimension lines.
Index: doc-rnd/devlog/20150820b_qf.html
===================================================================
--- doc-rnd/devlog/20150820b_qf.html (revision 772)
+++ doc-rnd/devlog/20150820b_qf.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
qf()
The next group of footprints I decided to generate are qfn(), tqfp(), lqfp().
The generic set of rules for these footprints is:
Index: doc-rnd/devlog/20150821a_parametric_requirements.html
===================================================================
--- doc-rnd/devlog/20150821a_parametric_requirements.html (revision 772)
+++ doc-rnd/devlog/20150821a_parametric_requirements.html (revision 773)
@@ -1,6 +1,6 @@
- pcb-rnd devlog
+
requirements for parametric footprint generation
It's appealing to write parametric footprint generators for new footprint