fritzing/fritzing-app

Fritzing desktop application

Fritzing

Branch	Badge
master
develop

The Fritzing application is an Electronic Design Automation software with a low entry barrier, suited for the needs of makers and hobbyists. It offers a unique real-life "breadboard" view, and a parts library with many commonly used high-level components. Fritzing makes it very easy to communicate about circuits, as well as to turn them into PCB layouts ready for production. It is particularly popular among Arduino and Raspberry Pi users, and is widely used in education and creative tinkering.

• For more information on Fritzing and its related activities, visit http://fritzing.org. There you can also download the latest releases for all platforms and get help on getting started.

• To report a problem or suggest improvements, use the issue tracker or the user forum. Please provide steps, what operating system you are on, including the version. Add screenshots or copies of error messages, describe what behavior you saw and what you expected.

• If you would like to help with the development, please take a look at those labels:

  • 
  • 

Some of those don't need C++ skills, like reproducing an issue on a certain platform, or verifying translations of languages we don't speak. If there is something for you, you might want to check the developer instructions next. This includes information about how to compile and run the Fritzing app.

Project Structure

• help - End-user documentation included with the app.

• parts - All the part definitions, including meta data (.fzp) and graphics (.svg), as well as some utility tools. They are kept in a separate repository at https://github.com/fritzing/fritzing-parts and only linked from here.

• pri - Submodule definitions for Qt

• resources - Binaries and definitions that are supposed not to be touched by users, such as fonts, images, special parts, etc.

• sketches - Example circuits/sketches shipped with the application

• src - Application logic!

• tools - Utility tools for making releases, converting parts, etc.

• translations - Language translations

Credits

The Fritzing app was maintained by the Friends-of-Fritzing e.V., a non-profit foundation based in Berlin, Germany. The project has grown out of a state-funded research project at the Interaction Design Lab at Potsdam University of Applied Sciences.

The founding team consists of Prof. Reto Wettach, André Knörig, Jonathan Cohen, and Stefan Hermann. Many fantastic people have contributed to it over the years.

Since 2019, the project is maintained by Kjell Morgenstern, with great support from Peter Van Epp, André Knörig, and AISLER.

The Fritzing app is written on top of the Qt cross-platform framework.

Licensing

The source code of Fritzing is under GNU GPL v3, the documentation and part designs under Creative Commons Attribution-ShareALike 3.0 Unported. The full texts of these licenses are shipped with this download.

This means that you can create your own variation of Fritzing, as long as you credit us and also publish it under GPL. Similarly, you may re-publish our documentation, as long as you credit us, and publish it under the same license. You may publish circuits and diagrams that you create with Fritzing and that use our graphics, again as long as you credit us, and publish your works under the same license. A credit can be as simple as "this image was created with Fritzing."

Lookup our FAQs for more details on licensing.

fritzing-app's Issues

Quick Look Generator Plug-In

From [email protected] on December 05, 2007 08:35:10

It would be nice if fritzing would come with a Quick Look Generator Plugin
for Macintosh OS X.
This is a module which OS X versions 10.5 and up uses to show a preview of
documents.

...

Quick Look is the new preview tool in Mac OS X 10.5 Leopard. Similar to the
way the Spotlight Importer is distributed with the application, an
application can have a Quick Look Generator Plugin.
This system works with plugins that gets recognized by the OS and which
then will be invoked whenever the system needs to display a file of the
type, the Quick Look Plugins promises to deliver an image for.

A Quick Look Generator Plugin has to be a CFPlugin, written in C (or at
least a wrapper written in C). Start documentation at Apple: http://developer.apple.com/documentation/UserExperience/Conceptual/Quicklook_Programming_Guide/Introduction/chapter_1_section_1.html

Original issue: http://code.google.com/p/fritzing/issues/detail?id=39

import graphics to pcb

From [email protected] on November 28, 2007 04:20:23

logo import has been suggested by several people as a helpful tool. a few
ULPs exist to do this, but are all marred by pretty nasty UI.

need to create a simplified bitmap logo import ULP and provide access to it
from the command texts menu

Original issue: http://code.google.com/p/fritzing/issues/detail?id=31

my legs are red (v0004)

From [email protected] on December 05, 2007 10:12:07

from the passed-around copy of Fritzing v0002 on OS X; the grid is a lovely
dark red to start.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=42

command texts in Eagle PCB view should follow a workflow model

From [email protected] on November 15, 2007 05:18:30

Currently, the custom Fritzing Eagle command texts menu follows a stateful
model - first placement, then routing. Instead, should propose a workflow
to the user - "first do these things, then do these things, ... , finish up
by doing this"

affected: fritzing_menu.scr
deprecated: fritzing_menu-placement.scr, fritzing_menu-routing.scr

Original issue: http://code.google.com/p/fritzing/issues/detail?id=17

Installation guide README (.html) file for all platforms

From [email protected] on November 15, 2007 05:44:03

A different installation guide for the different OSes: Mac, Windows, Linux. This should be a README
file, preferably html, so it can include css and images.

In this guide it should explain what to do with the Fritzing folder; where you could install it on your
harddisk; whether you want to install it for one user or for all users; where Fritzing will save your
own files by default (**); how to get Eagle running; what to do with bugs; how to contribute.

**: The default saving location for Fritzing should also be improved. (This is actually another issue,
but since it is so small I add it here).
For Mac OS X, the default saving location should be /Users/myname/Documents/Fritzing/...
(right now it is wrong: /Users/myname/Fritzing/)

Original issue: http://code.google.com/p/fritzing/issues/detail?id=18

Copy/paste is screwed

From [email protected] on November 12, 2007 09:26:23

If a part is copied and pasted into the same Fritzing sketch, subsequent
changes to one will also affect the other.

To replicate (from Reto - have been unable to reproduce):

1. place a resistor (A) on the sketch
2. copy and paste A to create A'
3. connect a wire to A, terminal 0
4. connect a wire to A', terminal 0
5. change the name of wire on A-0
6. see name of wire on A'-0 change

Original issue: http://code.google.com/p/fritzing/issues/detail?id=6

Spotlight Importer Plugin

From [email protected] on December 05, 2007 07:20:35

It would be nice if fritzing would come with a Spotlight Importer Plugin
for Macintosh OS X.
This is a module which OS X versions 10.4 and up uses to index files on the
system for meta data, so Spotlight search can find them quickly.

This system works with plugins that gets recognized by the OS and which
then will be invoked whenever the system discovers new files of the type,
the Spotlight Plugins promises to be an importer for.

A Spotlight Importer Plugin has to be a CFPlugin, written in C (or at least
a wrapper written in C). Start documentation at Apple: http://developer.apple.com/macosx/spotlight.html

Original issue: http://code.google.com/p/fritzing/issues/detail?id=38

Improve tab design and behavior

From [email protected] on November 15, 2007 06:09:19

Concerning The tabs for widgets and tools, the special views, like library window, navigitor window
(outline), layer window, Palette, Properties window. etc.

These tabs and windows should have a unified Fritzing look and feel. This means:

• unified design of the tab and window elements itself
• unified design of a tab behind other tabs (and above other tabs)
• design of tab GUI elements: close tab; minimize tab; move tab handler
• design of close tab animation
• design of minimize tab animation
• design of dragged tab ghost preview
• behavior of a dragged tab (where does ghost preview snap to, how does a snap to point look)

Original issue: http://code.google.com/p/fritzing/issues/detail?id=21

Wrong default folder location for New -> Fritzing Sketch

From [email protected] on December 05, 2007 14:33:42

On Mac OS X, when you select New -> Fritzing Sketch it ask for a location
to save the new sketch file.
(Maybe it should not even ask for this save location, but just make an
"untitled" file just in memory, but that's another issue).

The location where it starts now is wrong. Worse is that this also means it
creates a 'Fritzing' folder in this location, even if you do not want this.
(This is a very bad iritating behavior: even when you delete this folder,
next time it creates it again. :-()

It creates a folder directly in your Home folder (~/ = /Users/yourname/).
It should (if all) create a folder in your Documents folder:
~/Documents (/Users/yourname/Documents/)

Original issue: http://code.google.com/p/fritzing/issues/detail?id=45

Image export has problems with spaces in path

From [email protected] on December 06, 2007 06:29:49

What steps will reproduce the problem? 1. Create a sketch inside a path that has spaces
2. Choose File>Export>Image..
3. Click save

Brings up an error because it converts the path to url encoded.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=48

Arduino sockets don't fit on the 0.1 inch grid

From [email protected] on December 05, 2007 06:51:31

There is an issue with snap to grid regarding the Arduino sockets:
The sockets on the arduino are not all lined up. (!!) (the space between
arduino 'pins' 7 and 8 are not a multiple of 0.1 inch).
This could cause a nasty issue in the process of dragging parts, pins and
wires in the breadboard view, which should be as simple and straight
forward as possible.

I can think of a few solutions:

BEST SOLUTION (to my opinion)

1. make the arduinos in the breadboard view have their sockets in the 0.1"
   grid, regardless of the physical reality. Deal with the real exact
   positions of those sockets in the pcb view.
   (downside: a user could fit a part in there which would actually not fit in
   the real world.)

OTHER SOLUTIONS (which make it all the more complex)
2. sockets in parts does not necessarily have to be placed in the 0.1" grid.
(downside: if pins/wires could snap to the 0.1" grid and to sockets –not
in this grid–, this would create very difficult situations for the user
placing parts in sockets with a small offset to the grid.
3. extend the idea I had earlier to have multiple rulers (a ruler per
macro-part: breadboards, perfboards, arduino's ... like the multiple
spreadsheets on a page example I showed in the new Apple iWork'08). Extend
this multiple rulers / multiple origin (0,0 point) idea to also allow
multiple grid offsets and allow this even within one part.
(downside: the grid being drawn in the background makes much less sense,
since there is no global grid anymore, each part will have their own
grid(s). And probably this is also overly complex in programming efforts.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=36

Parts should have 'connectors'

From [email protected] on December 06, 2007 06:24:24

Instead of terminals, parts should have 'connectors'.

A Connector is an abstract super class, which can accept (or refuse) other
connectors.

Different types of subclasses could be:

• Breadboard hole
• Arduino socket
• pin (bendable)
• wire-end
• header pin
• jumper

(This is just a limited set, as an example)
Each subclass type should have a set of connectors, which it can accept.
In the above examples set, the connector type accepts the following other
type of connectors:
Connector Type Can Accept Connector Type
===================== =========================

• Breadboard hole pin, wire-end, header-pin
• Arduino socket pin, wire-end, header-pin
• pin (bendable wire-end (soldered)
• wire-end X
• header pin jumper, arduino socket
• jumper X

Original issue: http://code.google.com/p/fritzing/issues/detail?id=47

Editor tab should only show the file name

From [email protected] on November 24, 2007 16:15:23

What is the expected output? What do you see instead? Editor tabs currently show the full path.
It should show just the file name, even without the extension (i.e., the
project name).

Probably requires our own implementation of URIEditorInput.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=29

Draw behavior of wiring action from one pin (or hole) of a part to another

From [email protected] on November 15, 2007 09:59:27

What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=27

Icons for fritzing document types (.fz, .fzz, .fzb, .fzp)

From [email protected] on December 05, 2007 06:58:27

We need document icons for the different document types that the
application can open and can create:

.fz fritzing project file
.fzb fritzing breadboard file
.fzs fritzing schematic circuit file
.fzp fritzing pcb (printed circuit board) view file

Those icons should be like the application icon is now, designed for
multiple sizes.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=37

Fritzing does not enumerate part names

From [email protected] on November 08, 2007 09:58:45

Fritzing does not automatically give parts unique identifiers but Eagle
requires each part to be uniquely-named

Original issue: http://code.google.com/p/fritzing/issues/detail?id=2

Edit the info.plist (Mac OS X only) to hold correct application metadata

From [email protected] on November 15, 2007 09:07:26

The Mac OS X application, is a package (a folder). Inside this file can be found .../Fritzing.app/
Contents/info.plist

The info.plist should hold all important meta data about the app. a.o:

• version
• manufacturer
• application bundle identifier (1)
• application creator code (2)
• icons for the application
• document types that it accepts (can open, edit or modify)
• icons for these document types

1. The application bundle identifier, CFBundleIdentifier, should be something like
   org.fritzing.app or org.fritzing.fritzing
2. The application creator code, CFBundleSignature, is 4 character string, that identifies which
   application you need to open certain files types (which get the same creator code). The code
   'FRtz' was still available and has now been registered with Apple.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=24

Parts should have hidden wires

From [email protected] on December 05, 2007 08:57:52

Parts should have a hidden wire connection layer inside them as well.
This layer could be toggled on or off.

(with this hidden wire connection layer in parts, also breadboards can be
made as parts)

Original issue: http://code.google.com/p/fritzing/issues/detail?id=40

Create new sketch without specifying anything

From [email protected] on November 28, 2007 06:50:26

What steps will reproduce the problem? 1. Create a new sketch by clicking File->New->Fritzing Sketch.. What is the expected output? What do you see instead? Currently a wizard appears requiring you to enter two file names (although
it provides suggestions).

This should be much simplified, in the Processing style. Click File->New
and a new sketch with a default name based on the date appears immediately.
User should be able to change it to something else using "Save As" or maybe
"Rename".
This needs to be disucussed.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=33

Need smarter auto-routing execution

From [email protected] on November 14, 2007 06:16:12

Currently, auto-routing is run with the default setting but does not
iterate on failure. We should trap on an exit with less than 100% routing
and iterate with a smaller grid, etc.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=14

Enforce unique names for parts, optional names for wires

From [email protected] on November 11, 2007 15:54:07

What steps will reproduce the problem? 1. Customize the look of two wires
2. Save, close, and re-open What is the expected output? What do you see instead? Only one wire's look is restored, the other is reverted to the default

Original issue: http://code.google.com/p/fritzing/issues/detail?id=4

Drag canvas hand cursor should be other type of hand

From [email protected] on December 05, 2007 10:27:52

Dragging the canvas around with the spacebar works on Mac OS X, but it
seems not to work on Windows XP.

The problem this issues is about though, is which mouse cursors are being used.
On my system (Mac OS X 10.4 PPC), the mouse cursor changes into a hand when
the spacebar is pressed, but the wrong kind of hand: the hand with the
pointing finger (1 finger out). It should be the open hand mouse cursor (5
fingers out).

When the mouse is pressed / down the mouse cursor image should be the
closed hand (5 fingers retracted)

Original issue: http://code.google.com/p/fritzing/issues/detail?id=43

Remove automatic contextual pop-up menus

From [email protected] on November 28, 2007 16:34:27

What steps will reproduce the problem? 1. Let your mouse rest over a part or the border of a part

What is the expected output?
Nothing!

What do you see instead?
Annoying pop-up menus that let you add subparts and links.

Get rid of them!

Original issue: http://code.google.com/p/fritzing/issues/detail?id=35

needed Eagle files (ULPs, SCRs, and LBRs) should be referenced in the Fritzing install directory

From [email protected] on November 13, 2007 05:51:17

Current method of requiring users to manually place Eagle support files in
Eagle directories is cumbersome - we can just reference them in the
Fritzing install directory instead

Original issue: http://code.google.com/p/fritzing/issues/detail?id=10

moving wired Arduino terminals may cause several terminals to move to the same position

From [email protected] on November 12, 2007 09:40:23

In at least one case, moving a single Arduino terminal in Fritzing caused a
number of a wired terminals to jump to the same location.

Discovered by Simon, has not been reproduced. Simon's files are available.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=8

A Part should have a 0.1" grid origin (0,0 point) set to a high metric position.

From [email protected] on December 06, 2007 06:59:15

A Part should be able to snap to the 0.1" (1/10 inch) grid.
And some subparts of parts with snapping behavior, like sockets (a
connector-type), should only exist in this 0.1" grid.

Therefore a part should have a 0.1" grid origin: the (0,0) point. This
point should also have a relation to the high metric system. So the origin
has to be set to a position in the in high metric system, which is also
used to design the shapes of the part.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=50

"Export to PCB..." does not do anything

From [email protected] on November 15, 2007 05:56:42

What steps will reproduce the problem? 1. Install Fritzing
2. Set the Eagle location in properties
3. Create a sketch and click "Export to PCB" What is the expected output? What do you see instead? Should launch Eagle, but nothing happens.

The cause is a disk synching issue of FileWriter in the PCBExportAction.

Workaround: Simply restart Fritzing and try again. For Mac OSX, you get an
error on the first try now, just try again and it works.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=20

Put license text and authors into the code

From [email protected] on November 15, 2007 04:17:08

Put a license note and authors to the top of each Java class file.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=16

Drag behavior of a part from the Library to the canvas

From [email protected] on November 15, 2007 09:56:24

Visually redesign the complete procedure from selecting a part from the Library (of Favorites) to
placing the part on the right spot in the breadboard view canvas.

A step by step visualization of this proces, to be used as guideline for the front-end behavior of this
functionality.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=26

Need smarter auto-placement of components

From [email protected] on November 14, 2007 06:25:48

Currently, Fritzing to Eagle conversion utility directly translates
Fritzing component positions to Eagle component coordinates without respect
to keepout violations, board size, etc.

Need a better placement of Eagle parts that at least tries to fit the
circuit within Eagle Light's limits and tries to prevent keepout violations.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=15

Fritzing Application Icon (in cmd-tab or Dock) on OSX is ugly and jagged

From [email protected] on November 12, 2007 09:29:37

The icon that comes up for Fritzing when Apple-Tabbing through applications
on OSX is jagged. It looks like the 16x16 icon is being used.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=7

Parts in the Breadboard view should be a mixture of vector and bitmap

From [email protected] on December 05, 2007 09:17:33

The visual representation of parts in the Breadboard view should be a
mixture of vector graphics and resolution independent bitmap images. (.svg
& .png's).

Resolution independent bitmap images are image-sets with a multiple levels
of detail. (So it has different sized images for different levels of
zoom). Using bitmaps probably improves the performance of the drawing of
complex objects, like the nicely shaded holes in a breadboard.

Also it should be possible to mix these vector images and bitmap images on
different layers.
Then each layer could be:

• vector images,
• bitmap image sets (resolution independent)
• named subparts (which are referenced, so if a subpart changes, the part
  using that subpart changes too. This will be especially useful during the
  development of the parts-library)

Original issue: http://code.google.com/p/fritzing/issues/detail?id=41

the 100% zoom view should display parts bigger (matching the real physical sizes)

From [email protected] on December 05, 2007 14:23:21

The 100% view should be exactly the same size on the screen (on a
'standard' screen) as they appear in the real world.

The rulers should be off permantly, (or only on in the PCB view or in the
part-editing-tool). But if we stick to the measurements of these rulers,
with the current version 0002, this is only achieved
with about 140%-150% zoom. Only then the 0.1 inch grid on the screen also
resembles the 0.1 inch grid on a physical breadboard.

With this 100% zoom level each 1/10 inch is about 10-10.5 pixels. (This
corresponds to 100-105 dpi.)

Original issue: http://code.google.com/p/fritzing/issues/detail?id=44

Fritzing does not enumerate net names

From [email protected] on November 08, 2007 09:58:05

Nets/wires in Fritzing are not automatically given names when created. It
is possible to export a Fritzing diagram with unnamed nets but Eagle
requires nets to be named.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=1

Fritzing files saved on one computer may not properly open on another

From [email protected] on November 12, 2007 09:46:05

Fritzing file saved after program error in Issue 8 is not properly opened
on my system - wire and terminal texts are missing, visual artifacts are
present, etc.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=9

Copying elements from one file to another is broken

From [email protected] on November 28, 2007 06:45:59

What steps will reproduce the problem? 1. Create a sketch
2. Select a part and copy it
3. Create another sketch
4. Paste the part
5. Add a new part from the palette to the sketch What is the expected output? What do you see instead? The copied part suddenly disappears at step 5..

Original issue: http://code.google.com/p/fritzing/issues/detail?id=32

Rotation of parts over the x/y axis (pitch & roll)

From [email protected] on December 06, 2007 05:49:38

It should be possible to not only rotate parts in 90˚ angle over the z-axis
(jaw), but also to rotate parts over the x or y axis (pitch / roll).
This effectively means that parts should have 2 super-orientations:
standing and laying.

Per super-orientation there are 4 z-axis-rotation-orientations (up, down,
left, right or NORTH, SOUTH, EAST, WEST). That makes up to 8 orientations
for most parts.

Rotation-orientation is relatively simple, all the shapes and positions
should be rotated around the center of the outer box.
Super-orientation is much more work, since a complete set of shape and
positions has to be made.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=46

Fritzing to Eagle converter should automatically merge connected wires into nets

From [email protected] on November 14, 2007 06:03:48

Converter should produce real netlists - wires connected to the same
terminal should be named the same. Must support named and unnamed nets and
named nets should override unnamed ones.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=11

Improved splash screen design

From [email protected] on November 15, 2007 05:50:30

The Frizting Splash Screen should be design a little bit nicer:

• the image can be smoother
• the logo should have some color (or the background should have color)
• the current version number should be visible

Original issue: http://code.google.com/p/fritzing/issues/detail?id=19

"Export" menu should contain image export

From [email protected] on November 28, 2007 16:30:48

Image export menu is currently only accessible through a right click on the
diagram itself. Should move to File > Export.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=34

Fritzing allows multiple nets to contact the same pin

From [email protected] on November 08, 2007 09:59:19

Eagle expects each pin to contact one and only one net

Original issue: http://code.google.com/p/fritzing/issues/detail?id=3

"Save As" does not work in Fritzing file menu

From [email protected] on November 12, 2007 09:11:38

The file menu's entry for Save As is grayed-out.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=5

All new toolbar

From [email protected] on November 15, 2007 07:00:39

Remove all current elements from the toolbar.
Make the toolbar a two level toolbar.
First level: tool buttons
Second level: file / view tabs.

In the first level of the toolbar use these elements / buttons:

(copy the buttons from Arduino, Processing)

• run simulation / check circuit (only put this button in, if it actually does something)
• stop simulation (only put this button in, if it actually does something)
• new file
• open file
• save file
• export to ...
• breadboard view
• schematic view
• printed circuit board view
• turn around (see backside). Only activate this button for the views where it applies (pcb)
• zoom buttons / zoom slider

In the second level of the tool bar the file tabs and view tabs, should be.

• different open files/projects should be in different tabs.
• you can also have different views on the same project open in different tabs. (different views:
  breadboard view, front side pcb view, back side pcb view, schematic view on 100%, schematic
  view on 400%)
• the tabs can be rearranged by dragging.
• (This is a long shot, it's not very clear how it would work exactly with all the tab widgets/tool
  windows), but tabs can also be teared-off (dragged out of the main application window) into
  another part of the screen. This will open a new application window, so you can see the different
  views side by side. This could maybe also be accomplished with a (internal) tiled window.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=23

Parts need to be rotatable, not resizable

From [email protected] on November 23, 2007 12:14:21

Currently parts can be resized, but not rotated. It should be the reverse.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=28

Connectors (of parts) should show different states depending on the behavior / status

From [email protected] on December 06, 2007 06:35:35

Connectors (see issue 47 )[1] should have different states depending on what
can be done with them.
States of a connector should be:
(a) - connector is available
(b) - mouse hover state (mouse hover could display addition information)
(c) - connector is accepting connection
(d) - connector is refusing connection
(e) - connector is already occupied

(Except for maybe the mouse-hover-state, which could be a different type of
graphical representation than the others (a,c,d,e) it should not be
necessary to mix these states).

[1] https://code.google.com/p/fritzing/issues/detail?id=47

Original issue: http://code.google.com/p/fritzing/issues/detail?id=49

Improve Outline view (and rename this to Navigator) and Zoom behavior

From [email protected] on November 15, 2007 06:40:51

The current outline view has two modes: an overview-view and an outline-view.
The outline view should be removed and put into its own widget/window: the Layers window.
The overview-view should be renamed to Navigator, like it is called in other drawing apps e.g.
Illustrator or Photoshop (not to be confused the the existing Navigator View in Eclipse !!)

Improvements:

• move the zoom in / zoom out buttons, and the current zoom level ("150%") to this window.
• nicer view box (thicker line, more obvious color)
• remove faint transparent fill-in from view box
• if at all, the faint transparent fill-in should have another color (black) and should be outside
  the view box instead of inside.

Zoom Behavior improvements:
Also the Zoom behavior should be in fixed steps (like in Photoshop instead of Illustrator).
12,5%, 25%, 50%, 100%, 200%, 400%, 800%.
(or a little more fine: 12,5%, 16,6%, 25%, 33,3%, 50%, 66,6%, 100%, 150%, 200%, 300%, 400%,
600%, 800%)
It doesn't make sense for Fritzing to be so fine grained in zooming.
And zoom-in / zoom-out should have a key-equivalent bound to cmd- / cmd= or cmd+ (both
should work).

Original issue: http://code.google.com/p/fritzing/issues/detail?id=22

file "place.scr" produced by Eagle's auto_place.ulp should be saved in the Fritzing project directory

From [email protected] on November 27, 2007 09:13:59

the PCB-generation script "place.scr" should be kept in the same directory
where the Fritzing sketch, Eagle documents, and other project-related files
are kept.

the file is currently saved inside a hidden directory inside the project
workspace directory.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=30

Add support for multiple export formats from Eagle PCB editor

From [email protected] on November 14, 2007 06:10:39

User should be able to export a PDF, an image, or necessary manufacturing
files from a design.

Tentatively, for an image, user should be able to select the layers to
include (probably requires a ULP). For a PDF, might just produce a
multi-page PDF with preset layer views (???). For manufacturing files,
produce Gerbers to spec for at least one manufacturer as a proof-of-concept.

Manufacturing files should ultimately be zipped up with manufacturing
instructions formatted per the PCB house

Original issue: http://code.google.com/p/fritzing/issues/detail?id=12

support double-sided boards

From [email protected] on November 14, 2007 06:13:24

Currently, the only choice is a two-sided board with thin traces and a big
routing grid. Should have at least a few options;

• two-sided for commercial manufacture
• two-sided for home manufacture
• one-sided for commercial manufacture
• one-sided for home manufacture

Original issue: http://code.google.com/p/fritzing/issues/detail?id=13

Nicer Parts Design

From [email protected] on November 15, 2007 09:46:40

The parts in the standard Fritzing Library should look nice, and they should be useable to work
with.

design them with these aspects in mind:

• 100% view should be exactly the same size on the screen (on a 'standard' screen) as they
  appear in the real world.
  The rulers should be off permantly, (or only on in the PCB view or in the part-editing-tool). But if
  we stick to the measurements of these rulers, with the current version 0001, this is only achieved
  with about 125% zoom. (Then the 1 cm on the screen also looks like 1 cm).
• Parts should be a mix of vector graphics and multiple resolution bitmap images. (.svg & .png's)
  Multiple resolution bitmap images means a part has different sized images for different levels of
  zoom. (This greatly improves the drawing of complex objects, like the nicely shaded holes in a
  breadboard)
• Parts (in the breadboard view) should not have removable terminals. They should have pins,
  that can be bend a little bit, representing the same physical restrictions as the pins would have in
  the real world, but then snapping to the 0.1 inch grid
• In the Library (or Favorites) view the parts should always be represented in their 100% view, or
  a cut-out of that view, fitting the 16x16 or 32x32 pixel icon.
• Parts which can accept other parts, like wires connections, or headers should also have a
  mouse hover state (b), accepts connection (c), refuses connection (d), and a connection is
  occupied (e) image for these subsections, besides the normal connection is available (a) state.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=25