summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhellekin <hellekin@dyne.org>2016-08-08 14:48:19 +0000
committerhellekin <hellekin@dyne.org>2016-08-09 20:11:34 +0000
commitb3a615ba3a2227f3aeae86c081325e03ecf9b84f (patch)
tree84c23082560b5fd76c75246553b89e9baf3f6435
parent09b85e1eedbf3ffff572ee2cedf6a2e8f57c9cb4 (diff)
downloadwww-b3a615ba3a2227f3aeae86c081325e03ecf9b84f.tar.gz
www-b3a615ba3a2227f3aeae86c081325e03ecf9b84f.tar.bz2
www-b3a615ba3a2227f3aeae86c081325e03ecf9b84f.zip
Integrate wpwrak's corrections
-rw-r--r--content/0021-migrating-away-from-eagle-to-kicad.html17
1 files changed, 8 insertions, 9 deletions
diff --git a/content/0021-migrating-away-from-eagle-to-kicad.html b/content/0021-migrating-away-from-eagle-to-kicad.html
index 6c94b86..2ff6a75 100644
--- a/content/0021-migrating-away-from-eagle-to-kicad.html
+++ b/content/0021-migrating-away-from-eagle-to-kicad.html
@@ -79,7 +79,7 @@
<p>A <a href="http://talk.maemo.org/showpost.php?p=1507624&postcount=21">new
paper discusses <abbr title="Input Output">IO</abbr>
expanders</a>, that provide more <abbr>IO</abbr> than
- the <abbr>CPU</abbr> has, and comes with the added benefit of
+ the <abbr>CPU</abbr> has, and come with the added benefit of
simplifying the connections between LOWER and UPPER
boards.</p>
@@ -113,7 +113,7 @@
schematics and layout.</p>
<p>In 2016, Nikolaus faded away from Neo900, absorbed by the
- finishing touch to our cousin project
+ finishing touches to our cousin project
<a href="https://pyra-handheld.com">Pyra</a>. Just a few weeks
ago he confirmed that he couldn't follow up on the layout for
Neo900, which prompted Joerg and Werner to consider
@@ -121,7 +121,7 @@
<p>In the <abbr title="Electronics Design Automation">EDA</abbr>
market, besides Eagle, there's Altium. But Altium, although
- it's probably powerful enough to serve our needs, has the same
+ it's probably powerful enough to serve our needs, shares a major
flaw as Eagle: it's proprietary, and moreover, quite expensive.
Our rationalizing mind wants to say there's cognitive dissonance
in using non-free software for a free hardware project. And in
@@ -149,12 +149,11 @@
couldn't change in the schematics in a timely manner.</p>
<p>That gives us wings: with KiCad, we can now provide a more
- transparent development process and can now operate in a more
+ transparent development process and operate in a more
schematics-centric mode, using white papers only where something
actually needs explaining.</p>
- <p>We found out that KiCad's routing capabilities are superior to
- Eagle's:</p>
+ <p>KiCad's routing capabilities are superior to Eagle's:</p>
<figure>
<iframe width="560" height="315" src="https://www.youtube.com/embed/CCG4daPvuVI" frameborder="0" allowfullscreen></iframe>
@@ -163,9 +162,9 @@
</figcaption>
</figure>
- <p>Moving to KiCad proved to be quite
- an <a href="https://www.youtube.com/watch?v=d5oO6fiyB7o">improvement
- over that</a>.</p>
+ <p>Moving to KiCad proved to be quite an improvement over
+ <a href="https://www.youtube.com/watch?v=d5oO6fiyB7o">the
+ corresponding Eagle experience</a>.</p>
<h4>What's the progress on converting Neo900 schematics from Eagle
to KiCad?</h4>