Mail Archives: geda-user/2016/01/07/10:40:59
--001a113de56843dd3c0528c04be9
Content-Type: text/plain; charset=UTF-8
No... we accept votes one idea per patch.
Suggest you pick a favourite idea, (if want to ensure would be considered
for inclusion before coding - ask about the idea first), then write a
patch. (Or patch series).
Sometimes you'll need to write the patch in order to test the idea - and
perhaps you want it anyway, even if the idea is not accepted for the main
repository.
We are not short of insight as to where things need to go, we are short of
people with the time and skills to execute those ideas successfully.
Peter
On 7 January 2016 at 13:33, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> Attached filename is in line with README, INSTALL, ... put a file like
> this into the source directory?
>
> In some cases it is rather simple in gschem like for example just decide
> what attribute name to use but in other case there might be good with more
> text about in particular implementation details. There might be need to
> list different algorithms, reference white papers or list
> advantages/disadvantages with different solutions. It would also be
> possible add an extra sub folder with documents for this purpose if
> necessary.
>
>
> Nicklas Karlsson
>
> > DJ,
> >
> >
> > http://wiki.geda-project.org/
> >
> > Can 'we' have write access to the wiki? I've never in my life edited a
> wiki
> > page. Can you give me some pointers how to do that? A place where we
> store
> > the ideas, conclusions and suggestions would be nice.
> >
> > Lev
> >
> >
> >
> > On Thu, Jan 7, 2016 at 12:40 PM, Levente <leventelist AT gmail DOT com> wrote:
> >
> > > This is a good idea, however, I think only some sort of socket between
> > > gpcb and gschem would be enough. But I don't want to do the design
> right
> > > away.
> > >
> > > Lev
> > >
> > > On Thu, Jan 7, 2016 at 6:20 AM, Marvin Dickens (mpdickens AT gmail DOT com)
> [via
> > > geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> > >
> > >> Hi Everybody,
> > >>
> > >> If your looking at tuning up or otherwise redesigning the file format
> for
> > >> PCB
> > >> I would really like gschem to understand the PCB file format and
> > >> visa-versa.
> > >> What I would like to be able to do is have a PCB layout up at the same
> > >> time I
> > >> have the schematic for that design up in gschem. If I select any part
> or
> > >> portion
> > >> of the layout in PCB that part or portion is visually highlighted in
> > >> gschem and
> > >> visa-versa.
> > >>
> > >> This ability could possibly be used as the starting point for
> introducing
> > >> boundary scan and other sophisticated usages of interconnects into
> gEDA.
> > >> I am
> > >> thinking verification, design for test, diagnostics and such. In my
> > >> world, completing
> > >> a design does not retire a project and it would be nice if gEDA
> reflected
> > >> this dynamic.
> > >>
> > >> Regards
> > >>
> > >> Marvin
>
--001a113de56843dd3c0528c04be9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>No... we accept votes one idea per patch.<br></div><d=
iv><br></div><div>Suggest you pick a favourite idea, (if want to ensure wou=
ld be considered for inclusion before coding - ask about the idea first), t=
hen write a patch. (Or patch series).<br><br></div><div>Sometimes you'l=
l need to write the patch in order to test the idea - and perhaps you want =
it anyway, even if the idea is not accepted for the main repository.<br><br=
><br></div><div>We are not short of insight as to where things need to go, =
we are short of people with the time and skills to execute those ideas succ=
essfully.<br><br></div><div>Peter<br></div><div><br></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On 7 January 2016 at 13:33,=
Nicklas Karlsson (<a href=3D"mailto:nicklas DOT karlsson17 AT gmail DOT com">nicklas.=
karlsson17 AT gmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">ged=
a-user AT delorie DOT com</a>] <span dir=3D"ltr"><<a href=3D"mailto:geda-user AT d=
elorie.com" target=3D"_blank">geda-user AT delorie DOT com</a>></span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">Attached filename is in line with README, =
INSTALL, ... put a file like this into the source directory?<br>
<br>
In some cases it is rather simple in gschem like for example just decide wh=
at attribute name to use but in other case there might be good with more te=
xt about in particular implementation details. There might be need to list =
different algorithms, reference white papers or list advantages/disadvantag=
es with different solutions. It would also be possible add an extra sub fol=
der with documents for this purpose if necessary.<br>
<br>
<br>
Nicklas Karlsson<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
> DJ,<br>
><br>
><br>
> <a href=3D"http://wiki.geda-project.org/" rel=3D"noreferrer" target=3D=
"_blank">http://wiki.geda-project.org/</a><br>
><br>
> Can 'we' have write access to the wiki? I've never in my l=
ife edited a wiki<br>
> page. Can you give me some pointers how to do that? A place where we s=
tore<br>
> the ideas, conclusions and suggestions would be nice.<br>
><br>
> Lev<br>
><br>
><br>
><br>
> On Thu, Jan 7, 2016 at 12:40 PM, Levente <<a href=3D"mailto:levente=
list AT gmail DOT com">leventelist AT gmail DOT com</a>> wrote:<br>
><br>
> > This is a good idea, however, I think only some sort of socket be=
tween<br>
> > gpcb and gschem would be enough. But I don't want to do the d=
esign right<br>
> > away.<br>
> ><br>
> > Lev<br>
> ><br>
> > On Thu, Jan 7, 2016 at 6:20 AM, Marvin Dickens (<a href=3D"mailto=
:mpdickens AT gmail DOT com">mpdickens AT gmail DOT com</a>) [via<br>
> > <a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a=
>] <<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>&g=
t; wrote:<br>
> ><br>
> >> Hi Everybody,<br>
> >><br>
> >> If your looking at tuning up or otherwise redesigning the fil=
e format for<br>
> >> PCB<br>
> >> I would really like gschem to understand the PCB file format =
and<br>
> >> visa-versa.<br>
> >> What I would like to be able to do is have a PCB layout up at=
the same<br>
> >> time I<br>
> >> have the schematic for that design up in gschem. If I select =
any part or<br>
> >> portion<br>
> >> of the layout in PCB that part or portion is visually highlig=
hted in<br>
> >> gschem and<br>
> >> visa-versa.<br>
> >><br>
> >> This ability could possibly be used as the starting point for=
introducing<br>
> >> boundary scan and other sophisticated usages of interconnects=
into gEDA.<br>
> >> I am<br>
> >> thinking verification, design for test, diagnostics and such.=
In my<br>
> >> world, completing<br>
> >> a design does not retire a project and it would be nice if gE=
DA reflected<br>
> >> this dynamic.<br>
> >><br>
> >> Regards<br>
> >><br>
> >> Marvin<br>
</div></div></blockquote></div><br></div>
--001a113de56843dd3c0528c04be9--
- Raw text -