1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
<link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
<link rel="stylesheet" media="print" type="text/css" href="./print.css" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>
<body>
<div class="dokuwiki export">
<p>
<em>Translations of this page are also available in the following languages:</em> <a href="pcb-roadmap.ru.html" class="wikilink1" title="pcb-roadmap.ru.html">Русский</a>
</p>
<h1 class="sectionedit1"><a name="pcb_roadmap" id="pcb_roadmap">PCB Roadmap</a></h1>
<div class="level1">
<p>
This is a guide to the future direction of the PCB layout editor.
</p>
<ul>
<li class="level1"><div class="li"> <a href="geda-design_flow_and_hierarchy_roadmap.html" class="wikilink1" title="geda-design_flow_and_hierarchy_roadmap.html"> gEDA roadmap</a> has some PCB items.</div>
</li>
<li class="level1"><div class="li"> <a href="geda-todos.html" class="wikilink1" title="geda-todos.html"> gEDA To-Dos</a> also has some PCB items.</div>
</li>
<li class="level1"><div class="li"> <a href="pcb-projects.html" class="wikilink1" title="pcb-projects.html"> PCB Projects</a> lists some wish-list items.</div>
</li>
</ul>
</div>
<!-- EDIT1 SECTION "PCB Roadmap" [109-410] -->
<h2 class="sectionedit2"><a name="general_guidelines_for_releases" id="general_guidelines_for_releases">General Guidelines for Releases</a></h2>
<div class="level2">
<p>
In general, there are three types of changes that go into PCB - bug
fixes, new features, and incompatible changes. A <em>bug fix</em> is when
PCB doesn't do what it's supposed to do - this includes documentation
bugs as well as code problems. A <em>new feature</em> is something that
adds functionality to PCB but doesn't change any existing
functionality. An <em>incompatible change</em> is anything that causes
(intentional) compatibility issues with older versions of PCB, and
usually means a large design change. Note that a new feature that
adds a backwards-incompatible change to the file format <em>when it's
used</em> is not in this category.
</p>
<p>
The current plans are as follows:
</p>
<ul>
<li class="level1"><div class="li"> Bug fix releases every two months or so until we clear the backlog.</div>
</li>
<li class="level1"><div class="li"> Start on a PCB 4.0 release that folds in some large design changes we've been talking about for years.</div>
</li>
</ul>
<p>
At the moment, bugfix releases will be of the form <code>pcb-YYYYMMDD</code>.
Once 4.0 is released, the major.minor.bugfix numbers will correspond
to the three categories listed above: bugfixes cause a *.*.N release,
new features cause a *.N release, major changes cause a N.0 release.
The <code>YYYYMMDD</code> release numbers will then be used for regular
non-release snapshots.
</p>
<p>
The remainder of this page will list the various changes that are
planned (or at least hoped for) for upcoming and future releases.
</p>
<p>
Bugs, patches, and feature requests should be added to the
<a href="https://bugs.launchpad.net/pcb" class="urlextern" title="https://bugs.launchpad.net/pcb" rel="nofollow">Launchpad
trackers</a>. The default status <strong>undecided</strong>. Requests with that
priority will be considered “unreviewed”.
</p>
</div>
<!-- EDIT2 SECTION "General Guidelines for Releases" [411-2015] -->
<h2 class="sectionedit3"><a name="next_bug_release" id="next_bug_release">Next Bug Release</a></h2>
<div class="level2">
<p>
This is a list of fixes that <em>must</em> be fixed before the next bug
release, in addition to any “next bug release” artifacts in the bug tracker.
</p>
</div>
<!-- EDIT3 SECTION "Next Bug Release" [2016-2190] -->
<h2 class="sectionedit4"><a name="future_bug_releases" id="future_bug_releases">Future Bug Releases</a></h2>
<div class="level2">
<p>
This is a list of fixes that should be fixed eventually.
</p>
</div>
<!-- EDIT4 SECTION "Future Bug Releases" [2191-2282] -->
<h2 class="sectionedit5"><a name="next_feature_release" id="next_feature_release">Next Feature Release</a></h2>
<div class="level2">
<p>
This is a list of new features that will be added before the next
feature release (or, perhaps the next bug release, if time permits).
</p>
<ul>
<li class="level1"><div class="li"> Make the code C++ compatible.</div>
</li>
<li class="level1"><div class="li"> Allow via annulii to overlap each other.</div>
</li>
<li class="level1"><div class="li"> More route styles.</div>
</li>
<li class="level1"><div class="li"> Nanometer resolution - this is the “metric units” change we've talked about many times.</div>
</li>
<li class="level1"><div class="li"> Real layer types. Silks, keepouts, mask docs at least. Maybe anti-draw or paste.</div>
</li>
</ul>
</div>
<!-- EDIT5 SECTION "Next Feature Release" [2283-2733] -->
<h2 class="sectionedit6"><a name="future_feature_releases" id="future_feature_releases">Future Feature Releases</a></h2>
<div class="level2">
<p>
Other features that should be added eventually.
</p>
</div>
<!-- EDIT6 SECTION "Future Feature Releases" [2734-2819] -->
<h2 class="sectionedit7"><a name="next_incompatible_release" id="next_incompatible_release">Next Incompatible Release</a></h2>
<div class="level2">
<p>
This is a list of major changes that we think are desirable to include
in PCB, and wish to put effort into.
</p>
</div>
<!-- EDIT7 SECTION "Next Incompatible Release" [2820-2967] -->
<h2 class="sectionedit8"><a name="future_incompatible_releases" id="future_incompatible_releases">Future Incompatible Releases</a></h2>
<div class="level2">
<p>
This is a list of other major changes that we think are desirable to
include in PCB, but so far have not committed any effort to.
</p>
</div>
<!-- EDIT8 SECTION "Future Incompatible Releases" [2968-3140] -->
<h2 class="sectionedit9"><a name="wish_list" id="wish_list">Wish List</a></h2>
<div class="level2">
<p>
This section lists possible projects for future releases, which either
haven't been agreed on, or haven't been scheduled. If you'd like to
work on one of these, go ahead <img src="images/smileys/icon_smile.gif" class="middle" alt=":-)" />
</p>
<ul>
<li class="level1"><div class="li"> <a href="geda-pcb_layers.html" class="wikilink1" title="geda-pcb_layers.html"> New Layers</a> proposal is here.</div>
</li>
<li class="level1"><div class="li"> Other <acronym title="Graphical User Interface">GUI</acronym> cleanups. Gtk upgraded to “best practices”. Importer config.</div>
</li>
<li class="level1"><div class="li"> import/wizard plugins (as well as exports)</div>
</li>
<li class="level1"><div class="li"> DRC cleanups/rewrite</div>
</li>
<li class="level1"><div class="li"> CAM engine? (i.e. ability to say “draw outline on top soldermask” via script/config)</div>
</li>
<li class="level1"><div class="li"> New file format we've been discussing.</div>
</li>
<li class="level1"><div class="li"> Variable-angle arcs. 90 degrees is extremely limiting.</div>
</li>
<li class="level1"><div class="li"> Filled circles, sans kludge. Currently, to get a filled circle you create a zero-length trace of the right width.</div>
</li>
<li class="level1"><div class="li"> Unification of shortcuts in gschem and PCB, or at least an easy option for PCB to mimic gschem's shortcuts.</div>
</li>
<li class="level1"><div class="li"> Better support for free-rotated components: assert that pads at funky angles are rendered correctly, fix autorouter for components at weird angles (the latest git version has a tendency to either ignore the route command or to segfault, depending on the specifics), add rotation to the <kbd>Ctrl</kbd>+<kbd>R</kbd> report, etcetera.</div>
</li>
<li class="level1"><div class="li"> Ability to copy a footprint's name from the library dialogue (so it can be pasted into gschem's attribute list).</div>
</li>
<li class="level1"><div class="li"> Ability to edit netlist in-situ (possibly by drawing on the rat lines layer) - e.g, when you want to add a heatsink soldered to ground, it will always show up as shorted until the netlist is edited to incorporate it.</div>
</li>
<li class="level1"><div class="li"> Trace impedance calculator, with automatic adjustment capability (fill in thickness, stray capacitance and desired impedance, and the width is adjusted to satisfy the conditions).</div>
</li>
<li class="level1"><div class="li"> Integrated footprint lookup and fetch from gedasymbols.org.</div>
</li>
<li class="level1"><div class="li"> Hierarchical pcb model - subcells, footprints-as-pcb, etc.</div>
</li>
<li class="level1"><div class="li"> A shape I've often wanted on a pad is circle with the sides cut off. This is slightly different than an oval. Something like Inkscape's boolean operations would be excellent.</div>
</li>
<li class="level1"><div class="li"> How about text at not-90 degree angles? Or support for rotated square pads (I know, the file format doesn't support those two.)</div>
</li>
<li class="level1"><div class="li"> Editing on the grid has got to go! Counting grid points is the worst possible way to enter positional information into a computer.</div>
</li>
<li class="level1"><div class="li"> Make every field in object reports editable.</div>
</li>
<li class="level1"><div class="li"> Allow direct entry of offsets and absolute positions when editing.</div>
</li>
<li class="level1"><div class="li"> Add “offset” and “trim” feature à la 2D CAD programs.</div>
</li>
<li class="level1"><div class="li"> Add “point to tangent” and “tangent to tangent” line drawing feature à la 2D CAD programs.</div>
</li>
<li class="level1"><div class="li"> Automatic least version required file saving. Set the file format version based on features used, not the version of PCB This will become valuable as we add features like blind vias, custom pad stacks etc….</div>
</li>
</ul>
</div>
<!-- EDIT9 SECTION "Wish List" [3141-] --></div>
</body>
</html>
|
