<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IDE on Sigasi</title><link>https://www.sigasi.com/tags/ide/</link><description>Recent content in IDE on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 30 May 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/ide/index.xml" rel="self" type="application/rss+xml"/><item><title>Sigasi's Software Development Kit Part 2</title><link>https://www.sigasi.com/legacy/tech/sigasi_sdk_2/</link><pubDate>Mon, 30 May 2022 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/sigasi_sdk_2/</guid><description>&lt;p&gt;In the &lt;a
 style="white-space: nowrap;"
 href="https://www.sigasi.com/legacy/tech/sigasi_sdk_1/"
 
 &gt;previous installment of this blog&lt;/a&gt;, we talked about why you would want to integrate &lt;a
 style="white-space: nowrap;"
 href="https://www.sigasi.com/legacy/tech/sigasi_sdk_1/"
 
 &gt;Sigasi&amp;rsquo;s SDK&lt;/a&gt; into your own product portfolio. To summarize our arguments:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The SDK allows you to offer an editing experience in your own product line that is similar to a full blown IDE.&lt;/li&gt;
&lt;li&gt;Developing such capabilities from scratch would be prohibitively expensive.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So, hopefully by now you&amp;rsquo;re convinced you want to license our SDK &amp;hellip; but now what? In this installment, we want to focus on some &lt;em&gt;practical&lt;/em&gt; aspects of integrating our SDK. The goal is to make you aware of the (limited) additional work you might be confronted with.&lt;/p&gt;</description></item><item><title>Sigasi's Software Development Kit Part 1</title><link>https://www.sigasi.com/legacy/tech/sigasi_sdk_1/</link><pubDate>Mon, 25 Apr 2022 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/sigasi_sdk_1/</guid><description>&lt;p&gt;At Sigasi, we build tools to make you more productive. Specifically, we enhance your productivity during chip design with SystemVerilog and/or VHDL. For this purpose, two product lines are provided: &lt;a
 style="white-space: nowrap;"
 href="https://www.sigasi.com/legacy/"
 
 &gt;Sigasi Studio for Eclipse&lt;/a&gt; and our &lt;a
 style="white-space: nowrap;"
 href="https://www.sigasi.com/solutions/"
 
 &gt;Sigasi for VS Code extension&lt;/a&gt;. Both are focused on end-users.&lt;/p&gt;</description></item><item><title>Opinion: Why IDEs for hardware design fail [Published in EE Times]</title><link>https://www.sigasi.com/opinion/opinion-why-ides-hardware-design-fail-published-ee-times/</link><pubDate>Wed, 12 Sep 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/opinion/opinion-why-ides-hardware-design-fail-published-ee-times/</guid><description>&lt;p&gt;Hardware designers hate integrated development environments (IDEs), and they have good reasons to do so. Most EDA vendors build IDEs that lock the user in. They force a workflow on the user, limit the number EDA tools that work with their IDE, and provide half-baked usability. The only way to fix this is to stop using IDEs that are built by EDA (electronic design automation) companies. Electronic design engineers should start learning and copying from their colleagues in software engineering.&lt;/p&gt;</description></item></channel></rss>