comment on

perldigious:

At the moment, I'm just working on a tool that lets me interoperate between LTSpice and OmniGlyph. Since both use text file formats they ought to be easy enough to swap between them. That way, I won't have to re-enter schematics twice. Since there are a lot of KiCAD users out there, I'd probably target that next, and make the tool be able to migrate schematic symbols and PCB footprints between them.

I don't really have an ultimate goal, though, as I'm just puttering around with my hobbies at the moment. I'm currently decompressing from my last job and trying to figure out what I'd like to do next. It's kind of funny that I studied Electrical Engineering at school but have always worked as a programmer. Though knowing my way around an oscilloscope has been helpful in quite a few jobs, as I really enjoy working on embedded systems.

(I realize that OmniGlyph is a niche, and not particularly well known, but I find it more convenient to use than other packages. It not only uses the same file format for schematics and PCBs, but it's very keyboard friendly. I tend to think of it as the VI of electronics. It also happens to be the tool of choice for my electronics-oriented friends.)

...roboticus

When your only tool is a hammer, all problems look like your thumb.

In reply to Re^2: Solved! I would have expected a syntax error here by roboticus
in thread Solved! I would have expected a syntax error here by roboticus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks