Mail Archives: geda-user/2015/07/25/09:20:14
--001a113d1d3868c7a5051bb2f765
Content-Type: text/plain; charset=UTF-8
I vote: 3a, 3b, 4, and 5
Features 3a, 3b, 4, and 5 directly would make your branch of PCB more
usable, right now (for me at least).
The way I see it, these items are quite realistic features that are easy to
write, test, and use. Too often have I seen projects get bogged down on big
ticket items only for them to never materialize.
On Sat, Jul 25, 2015 at 6:14 AM, <gedau AT igor2 DOT repo DOT hu> wrote:
> Hi all,
>
> after the release of pcb-rnd today, I am pondering what to do next. I have
> a list of features I would sooner or later implement. I have my own idea
> about their priority, but I am really interested to see what PCB users
> think of them.
>
> Below is a list of the features. In curly brackets I placed my estimation
> of the relative effort - the larger the feature is, the slower I get
> anything visible/usable done.
>
> Everyone is invited to vote in email (either in private or on the list).
> Even if you are not a pcb-rnd or pcb or geda user. Everyone has 3 tokens to
> spend; reply to the mail and write "token" right under the feature you
> support. You can spend 2 or even all 3 tokens on a single feature if you
> find that important. Spending more than 3 tokens disqualifies your mail. A
> new mail from the same person overwrites their previous tokens.
>
> I will count the tokens next wednesday morning (CET). If there's enough
> voters and strong bias in votes, the outcome will have a direct effect on
> my priorities.
>
>
> 1. {large} merge pcb-gpmi in pcb-rnd: scripting within pcb, using
> 10 different languages (includes python, perl, awk, lua and guile)
> Languages (and the dependencies they mean) are all optional.
>
>
> 2. {large} resurrect the win32 port - only if there are volunteer windows
> testers
>
>
> 3. {small} UI: drill adjust: set drill and/or ring to current style
> individually or all pins on a component
>
>
> 3. {small} UI: trace length calculation and display
>
>
> 4. {small} UI: be able to manually change text line width
>
>
> 5. {small} UI: component dialog: filter by component tags, not only
> by name
>
>
> 6. {medium?} CORE: clear poly should be a per layer flag (on each objects);
> so that a line can clear poly on solder-gnd but join solder-pwr
>
>
> 7. {medium?} CORE: optional inverse silk or copper text: draw a fill
> rect around the text and make the text a cutout of this fill rect.
>
>
> 8. {small} BUILD: menuconfig and a config file for scconfig
>
>
> 9. {medium} HID: resurrect the lesstif HID (pcb-rnd supports gtk at the
> moment)
>
> TIA,
>
> Igor2
>
--
Jason White
--001a113d1d3868c7a5051bb2f765
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>I vote: 3a, 3b, 4, and 5<br><br>Features 3a=
, 3b, 4, and 5 directly would make your branch of PCB more usable, right no=
w (for me at least).<br><br></div>The way I see it, these items are quite r=
ealistic features that are easy to write, test, and use. Too often have I s=
een projects get bogged down on big ticket items only for them to never mat=
erialize.<br><br><br></div></div></div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Sat, Jul 25, 2015 at 6:14 AM, <span dir=3D"ltr">&=
lt;<a href=3D"mailto:gedau AT igor2 DOT repo DOT hu" target=3D"_blank">gedau AT igor2 DOT rep=
o.hu</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
after the release of pcb-rnd today, I am pondering what to do next. I have =
a list of features I would sooner or later implement. I have my own idea ab=
out their priority, but I am really interested to see what PCB users think =
of them.<br>
<br>
Below is a list of the features. In curly brackets I placed my estimation o=
f the relative effort - the larger the feature is, the slower I get anythin=
g visible/usable done.<br>
<br>
Everyone is invited to vote in email (either in private or on the list). Ev=
en if you are not a pcb-rnd or pcb or geda user. Everyone has 3 tokens to s=
pend; reply to the mail and write "token" right under the feature=
you support. You can spend 2 or even all 3 tokens on a single feature if y=
ou find that important. Spending more than 3 tokens disqualifies your mail.=
A new mail from the same person overwrites their previous tokens.<br>
<br>
I will count the tokens next wednesday morning (CET). If there's enough=
voters and strong bias in votes, the outcome will have a direct effect on =
my priorities.<br>
<br>
<br>
1. {large} merge pcb-gpmi in pcb-rnd: scripting within pcb, using<br>
=C2=A0 =C2=A010 different languages (includes python, perl, awk, lua and gu=
ile)<br>
=C2=A0 =C2=A0Languages (and the dependencies they mean) are all optional.<b=
r>
<br>
<br>
2. {large} resurrect the win32 port - only if there are volunteer windows<b=
r>
=C2=A0 =C2=A0testers<br>
<br>
<br>
3. {small} UI: drill adjust: set drill and/or ring to current style<br>
=C2=A0 =C2=A0individually or all pins on a component<br>
<br>
<br>
3. {small} UI: trace length calculation and display<br>
<br>
<br>
4. {small} UI: be able to manually change text line width<br>
<br>
<br>
5. {small} UI: component dialog: filter by component tags, not only<br>
=C2=A0 =C2=A0by name<br>
<br>
<br>
6. {medium?} CORE: clear poly should be a per layer flag (on each objects);=
<br>
=C2=A0 =C2=A0so that a line can clear poly on solder-gnd but join solder-pw=
r<br>
<br>
<br>
7. {medium?} CORE: optional inverse silk or copper text: draw a fill<br>
=C2=A0 =C2=A0rect around the text and make the text a cutout of this fill r=
ect.<br>
<br>
<br>
8. {small} BUILD: menuconfig and a config file for scconfig<br>
<br>
<br>
9. {medium} HID: resurrect the lesstif HID (pcb-rnd supports gtk at the mom=
ent)<br>
<br>
TIA,<br>
<br>
Igor2<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature">Jason White</div>
</div>
--001a113d1d3868c7a5051bb2f765--
- Raw text -