wiki documentation sections probably way out of date

[mMerlin]

Problem

Reading (and adding to) the content on the wiki, I find several references to what I think are instructions for very old versions.

• 1.4 Building Qt from Source and 2. Developer Guide have references to Qt 5.2.1
• 2. Developer Guide has references to Qt 4.8.5
• 4.1 Via Linux on a virtual-box still includes 32 bit linux. That is also showing ubuntu 12.04, and I think 16.04 is the current recommendation. At least that is what 4. Publishing a Release indicates.
• 4. Publishing a Release has preliminary information about linux package managers, stores and variations. Should flatpak/flathub and snap store be included in that? There is a 0.9.4 release of Fritzing on flathub, even if that is not supported here.
• 2.1 Part file format Connectors, terminalID information says although in theory you can name your **terminalId** attribute anything you want, as long as there's an associated SVG element with that **id**, in practice we find that it's best to use the connector **name** followed by “terminal”. However, what I see is actually using the connector **id** followed by “terminal”.
• 2.1 Part file format Split schematic symbols, schematic svg shows the sub parts as nested elements. Shouldn't they be siblings instead? Especially subpart2 and subpart3 for the op-amp example.
• 1. Building Fritzing install dependencies for libgit2 says to unzip to a sibling folder of fritzing-app, then also says to end up with a libgit2/build folder. That combination needs one of:
  • a rename of the unpacked archive (which is tar not zip on linux) folder
  • different build instructions to create the target folders, and build from the archive folder
  • use a symbolic link (which is simple for linux)

Proposed Solution

Update the documentation to match the current usage environments. Or provide enough details that I can.

[failiz]

I agree that the documentation is not up to date.
I read the Sketch-file-format section and you can find this:

Since Fritzing 0.7, WireFlags are as follows:
PCB Trace = 4
Autoroutable = 32
Breadboard wire = 64
Schematic Trace = 128

However, in the code you can find:

enum WireFlag {
		NoFlag = 0,
		RoutedFlag = 2,
		PCBTraceFlag = 4,
		ObsoleteJumperFlag = 8,
		RatsnestFlag = 16,
		AutoroutableFlag = 32,
		NormalFlag = 64,
		SchematicTraceFlag = 128
	};

This, some of the look like they changed (Breadboard wire is now NormalFlag ) and there are now flags (RoutedFlag, ObsoleteJumperFlag, etc.) Some of these are self-explanatory, but others need some explanation.

Additionally, it would be nice to have a small description f the main concepts for developers. In the code I found virtualWires, which has not been described anywhere and they look like rastnests.

Proposed Solution

It would be nice to update the current wiki (which is focus on the building and the file formats) and create new sections describing the main concepts used in the code.
In the long run, some of these explanations could be in the source code.