Mail Archives: geda-user/2015/06/16/06:48:08
--001a11c29f1a6ac22c0518a04a68
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
The new kicad s-file format has added bezier curves to line, arc and circle
drawn elements, but not ellipses.
Regards,
Erich.
On Mon, Jun 15, 2015 at 9:55 AM, Cirilo Bernardo (cirilo_bernardo AT yahoo DOT com=
)
<geda-user AT delorie DOT com> wrote:
> Sharing a common format will indeed be possible but we would need people =
to
>
> study what can be shared. At the moment for example KiCad supports 32
> copper layers and 32 technical layers; mapping copper layers is easy
> provided both software packages can support the same number of layers but
> the mapping of the technical layers requires more coordination.
> For drawing outlines KiCad only has circular arc and line segments;
> there is currently no support for ellipses and such though I imagine
> in the future some people may demand a few curve types which are
> also supported by MCAD software, particularly Polynomial Curves and
> NURBS. KiCad has no pad stack though some people say they will try to
> find time to implement it. These are just a small portion of issues
> which need to be addressed when communicating data between different
> software.
>
> - Cirilo
>
> >________________________________
> > From: "timofonic timofonic timofonic AT gmail DOT com [kicad-users]" <
> kicad-users AT yahoogroups DOT com>
> >To: geda-user AT delorie DOT com
> >Cc: foss-pcb AT ohwr DOT org; The Open Source Hardware Association Discussion
> List <discuss AT lists DOT oshwa DOT org>; kicad-users AT yahoogroups DOT com
> >Sent: Sunday, June 14, 2015 11:40 PM
> >Subject: [kicad-users] Re: [geda-user] Any news about FOSS EDA
> coordination? Import/export, common file format
> >
> >
> >
> >
> >Oh, the idea looked promising...
> >So what about kicad and geda supporting both formats at least? What abou=
t
> sharing the same library? :)
> >
> >
> >
> >On Jun 11, 2015 5:27 PM, "Ouabache Designworks (z3qmtr45 AT gmail DOT com)" <
> geda-user AT delorie DOT com> wrote:
> >
> >
> >>
> >>
> >>
> >>On Wed, Jun 10, 2015 at 11:29 PM, timofonic timofonic (
> timofonic AT gmail DOT com) <geda-user AT delorie DOT com> wrote:
> >>
> >>What's wrong with IP-XACT?
> >>
> >>
> >>It was created by the spirit consortium that was made up from engineers
> from eda tool vendors, IP houses and Si vendors. Correct me if I am wrong
> but I don't think that they had anyone on the committe who's day job
> actually involved designing IC's. The biggest complaint is that to use i=
t
> you have to use vendorExtensions to do anything useful and once you add
> that you have the same old problem that EDIF had with each vendor having
> their own "flavor" of IP-Xact.
> >>
> >>
> >>My biggest grip was that they don't support design variants that are
> critical in IC design. They support parameters but parameters cannot chan=
ge
> a port list or a file list. If your
> >>
> >>design variant needs to change either of those then you are out of luck=
.
> >>
> >>
> >>IP-Xact has seen some adoption as a way to describe register bits with
> tools that read an IP-Xact component file to generate the RTL,documentati=
on
> and head files for those registers. But it is capable of doing a lot more
> than that.
> >>
> >>
> >>I see IP-Xact as a case of pulling defeat from the jaws of victory. It
> has some really great features that are usefull. For example if you add o=
ne
> IP-Xact file into your IP repository then that will provide a unique
> identifier for your IP. No other repo in the world will have that same id=
,
> no more naming collisions.
> >>
> >>
> >>IP-Xact is a packaging standard that does not tell you how to package
> anything at all. They knew that nobody was going to adopt it if they had
> change anything in their legacy IP so that all you have to do is to add a=
n
> IP-Xact file anywhere in your legacy repos and they will be IP-Xact
> compliant.
> >>
> >>
> >>
> >>John Eaton
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >__._,_.___
> >
> >________________________________
> > Posted by: timofonic timofonic <timofonic AT gmail DOT com>
> >________________________________
> >
> >Reply via web post =E2=80=A2 Reply to sender =E2=80=A2 Reply to group =
=E2=80=A2 Start a New
> Topic =E2=80=A2 Messages in this topic (4)
> >Please read the Kicad FAQ in the group files section before posting your
> question.
> >Please post your bug reports here. They will be picked up by the creator
> of Kicad.
> >Please visit http://www.kicadlib.org for details of how to contribute
> your symbols/modules to the kicad library.
> >For building Kicad from source and other development questions visit the
> kicad-devel group at http://groups.yahoo.com/group/kicad-devel
> >Visit Your Group * New Members 7
> >
> >=E2=80=A2 Privacy =E2=80=A2 Unsubscribe =E2=80=A2 Terms of Use
> >
> >.
> >
> >__,_._,___
> >
> >
>
>
--001a11c29f1a6ac22c0518a04a68
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div>The new kicad s-file format has added bezier cur=
ves to line, arc and circle drawn elements, but not ellipses.<br><br></div>=
Regards,<br><br></div>Erich.<br><div><div><div><br><br><br><br></div></div>=
</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mo=
n, Jun 15, 2015 at 9:55 AM, Cirilo Bernardo (<a href=3D"mailto:cirilo_berna=
rdo AT yahoo DOT com">cirilo_bernardo AT yahoo DOT com</a>) <span dir=3D"ltr"><<a href=
=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</=
a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sharing a common for=
mat will indeed be possible but we would need people to<br>
<br>
study what can be shared. At the moment for example KiCad supports 32<br>
copper layers and 32 technical layers; mapping copper layers is easy<br>
provided both software packages can support the same number of layers but<b=
r>
the mapping of the technical layers requires more coordination.<br>
For drawing outlines KiCad only has circular arc and line segments;<br>
there is currently no support for ellipses and such though I imagine<br>
in the future some people may demand a few curve types which are<br>
also supported by MCAD software, particularly Polynomial Curves and<br>
NURBS. KiCad has no pad stack though some people say they will try to<br>
find time to implement it.=C2=A0 These are just a small portion of issues<b=
r>
which need to be addressed when communicating data between different<br>
software.<br>
<br>
- Cirilo<br>
<br>
>________________________________<br>
> From: "timofonic timofonic <a href=3D"mailto:timofonic AT gmail DOT com"=
>timofonic AT gmail DOT com</a> [kicad-users]" <<a href=3D"mailto:kicad-us=
ers AT yahoogroups DOT com">kicad-users AT yahoogroups DOT com</a>><br>
>To: <a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a><=
br>
>Cc: <a href=3D"mailto:foss-pcb AT ohwr DOT org">foss-pcb AT ohwr DOT org</a>; The Ope=
n Source Hardware Association Discussion List <<a href=3D"mailto:discuss=
@lists.oshwa.org">discuss AT lists DOT oshwa DOT org</a>>; <a href=3D"mailto:kicad-=
users AT yahoogroups DOT com">kicad-users AT yahoogroups DOT com</a><br>
>Sent: Sunday, June 14, 2015 11:40 PM<br>
>Subject: [kicad-users] Re: [geda-user] Any news about FOSS EDA coordina=
tion? Import/export, common file format<br>
<div><div class=3D"h5">><br>
><br>
><br>
><br>
>Oh, the idea looked promising...<br>
>So what about kicad and geda supporting both formats at least? What abo=
ut sharing the same library? :)<br>
><br>
><br>
><br>
>On Jun 11, 2015 5:27 PM, "Ouabache Designworks (<a href=3D"mailto:=
z3qmtr45 AT gmail DOT com">z3qmtr45 AT gmail DOT com</a>)" <<a href=3D"mailto:ged=
a-user AT delorie DOT com">geda-user AT delorie DOT com</a>> wrote:<br>
><br>
><br>
>><br>
>><br>
>><br>
>>On Wed, Jun 10, 2015 at 11:29 PM, timofonic timofonic (<a href=3D"m=
ailto:timofonic AT gmail DOT com">timofonic AT gmail DOT com</a>) <<a href=3D"mailto:g=
eda-user AT delorie DOT com">geda-user AT delorie DOT com</a>> wrote:<br>
>><br>
>>What's wrong with IP-XACT?<br>
>><br>
>><br>
>>It was created by the spirit consortium that was made up from engin=
eers from eda tool vendors, IP houses and Si vendors. Correct me if I am wr=
ong but I don't think that they had anyone on the committe who's da=
y job=C2=A0 actually involved designing IC's.=C2=A0 The biggest complai=
nt is that to use it you have to use vendorExtensions to do anything useful=
and once you add that you have the same old problem that EDIF had with eac=
h vendor having their own "flavor" of IP-Xact.<br>
>><br>
>><br>
>>My biggest grip was that they don't support design variants tha=
t are critical in IC design. They support parameters but parameters cannot =
change a port list or a file list. If your<br>
>><br>
>>design variant needs to change either of those then you are out of =
luck.<br>
>><br>
>><br>
>>IP-Xact has seen some adoption as a way to describe register bits w=
ith tools that read an IP-Xact component file to generate the RTL,documenta=
tion and head files for those registers. But it is capable of doing a lot m=
ore than that.<br>
>><br>
>><br>
>>I see IP-Xact as a case of pulling defeat from the jaws of victory.=
=C2=A0 It has some really great features that are usefull. For example if y=
ou add one IP-Xact file into your IP repository then that will provide=C2=
=A0 a unique identifier for your IP. No other repo in the world will have t=
hat same id, no more naming collisions.<br>
>><br>
>><br>
>>IP-Xact is a packaging standard that does not tell you how to packa=
ge anything at all. They knew that nobody was going to adopt it if they had=
change anything in their legacy IP so that all you have to do is to add an=
IP-Xact file anywhere in your legacy repos and they will be IP-Xact compli=
ant.<br>
>><br>
>><br>
>><br>
>>John Eaton<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
</div></div>>__._,_.___<br>
><br>
>________________________________<br>
> Posted by: timofonic timofonic <<a href=3D"mailto:timofonic AT gmail DOT c=
om">timofonic AT gmail DOT com</a>><br>
>________________________________<br>
><br>
>Reply via web post=C2=A0 =E2=80=A2 Reply to sender=C2=A0 =E2=80=A2 Repl=
y to group=C2=A0 =E2=80=A2 Start a New Topic=C2=A0 =E2=80=A2 Messages in th=
is topic (4)<br>
>Please read the Kicad FAQ in the group files section before posting you=
r question.<br>
>Please post your bug reports here. They will be picked up by the creato=
r of Kicad.<br>
>Please visit <a href=3D"http://www.kicadlib.org" rel=3D"noreferrer" tar=
get=3D"_blank">http://www.kicadlib.org</a> for details of how to contribute=
your symbols/modules to the kicad library.<br>
>For building Kicad from source and other development questions visit th=
e kicad-devel group at <a href=3D"http://groups.yahoo.com/group/kicad-devel=
" rel=3D"noreferrer" target=3D"_blank">http://groups.yahoo.com/group/kicad-=
devel</a><br>
>Visit Your Group=C2=A0 =C2=A0 =C2=A0* New Members 7<br>
><br>
>=E2=80=A2 Privacy =E2=80=A2 Unsubscribe =E2=80=A2 Terms of Use<br>
><br>
>.<br>
><br>
>__,_._,___<br>
><br>
><br>
<br>
</blockquote></div><br></div>
--001a11c29f1a6ac22c0518a04a68--
- Raw text -