EAGLE has the worst UI of any software I’ve ever persisted in using

Dear Lazywebs,

If you have suggestions, this is one of my present-day problems:  http://electronics.stackexchange.com/questions/30197/placing-a-device-in-eagle

I just added a new library (the adafruit library) in EAGLE comprised of many devices and packages. I can place packages, but not devices (usually devices represent a few different specific packages).

I’m using EAGLE-6.2.0. How do I get the devices onto a board?

This really shouldn’t be as difficult an issue as it’s been proving versus my “try every button” and “googling” problem-solving techniques.  I even tried to solve it by making my own modified EAGLE library (called starfruit, obvi) out of Ada’s devices, which did not solve.  If you have any suggestions I will be pretty grateful!

In the long term, I feel like it should be within our capabilities as a humanity to make tools that are better than EAGLE.

6 thoughts on “EAGLE has the worst UI of any software I’ve ever persisted in using

  1. Use KiCAD. It is GPL and doesn’t suck as bad as Eagle. It has a learning curve, but at the end of it you aren’t greeted with a high price tag, or a wall to smash your head against.

    KiCAD has a different workflow, and there are a couple of good tutorials out there. Pick one and follow it. Never look back.

  2. Are you in schematic capture or board layout view? The only way to build circuits (afaik) is to add devices in schematic capture, then go to board layout and play trace sokoban.

    This is in Eagle 5, of course; I haven’t bothered with 6 after the feedback I’ve been hearing.

    Hth, and isn’t just me repeating something you already knew.

  3. You’re so fast! Thank you for the replies!

    The solution I found (for today) is that you can actually click “ADD” for the package, within the device, in Control Panel-> Library. Weird nomenclature and weird UI defeated!

    I may revisit KiCAD in the future — it had a lot of issues last time I touched it, but it’s certainly in the direction of where I hope things go.

  4. I’m in the process of switching from Eagle to KiCAD as well, and I won’t go back. It’s got a learning curve, sure, but the keyboard shortcuts seem natural in a way that Eagle never did — and I’m only just starting to get the hang of them.

    Some seem to complain about this, but I actually rather like that it keeps footprints (modules) and symbols logically separate — this seems perfectly natural to me and, in fact, makes it quite natural to change packages (say, from TSSOP to QFN) without touching your electrical design at all.

    Coming from the world of enterprise software such as Allegro, which is similar in its implementation (but far far more expensive, and has its own bizarre, er, features), KiCAD seems much more powerful and less … toylike? … than Eagle ever did.

    1. Well that sounds awesome. I only got to experience KiCAD as “difficult to interoperate with EAGLE” on a collaborative project, which didn’t give me long enough to try out its good side. I will return with new eyes. Thanks, Scott!

  5. Star,

    I used gEDA in the past and had lots of trouble with it (even though I actually produced my PCB in the end). Recently I tried KiCAD and it is much much better! I’m really happy about it and strongly suggest you to try it again.

    The only thing I didn’t like in KiCAD is that apparently (I hope I’m wrong) there’s no well structured repository for people to contribute more modules/footprints (yet!).

    happy hackng,
    Felipe Sanches

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>