The Instigater: Services with a Smile
Born in 1978, Yerevan, Armenia Holds a Master's degree in Construction Engineering. In 2004 started an engineering center with 7 students. Now there are over 150 engineers working at Instigate cjsc and affiliates across the country. Responsible for strategic planing and implementation, business … More »
October 10th, 2014 by Arman Poghosyan
With this article we would like to start a series of tutorials covering the migration of EDA applications from Windows to Mac OS X and GNU/Linux. For that purpose we will review the technologies for building user-interface, data layer and business logic of typical EDA tools. For each of these technologies we will discuss porting concerns, issues, and solutions.
Nowadays, designers and developers have a variety of options when it comes to getting their development work done. There are choices in the areas, for example, of what application framework, programming language, and SW libraries to use, or what HW and OS platform to run on. Historically, EDA developers were using GNU/Linux and Windows operating systems. Current market trends, however, offer the opportunity for EDA developers to consider choosing a different OS for new developments. E. g. adding support of OS X and/or GNU/Linux to existing products, or permanently migrating to one of these operating systems, and vice versa. Today GNU/Linux and Apple OSX are more appealing for EDA and other applications, yet many EDA applications originated on Windows, and there are several technical difficulties in migrating from Windows to GNU/Linux or OSX. Let’s take a high-level look at one of these issues – the GUI. Also it is important to note that this applies not only to the existing, but also to new code-base. Even new products may initially start on GNU/Linux, and later, with growing adoption and revenue, company may consider porting to relatively less significant platforms.
March 18th, 2014 by Arman Poghosyan
As promised in previous posts, I would like to introduce one of our experience-driven undertakings – Instigate Application Framework. The idea for creating a tool like Framework was conceived while working on customer projects. We had understood that QA and GUI building efforts were often underestimated when doing the estimations and forecasts for SW development. This has actually been a stumbling block for EDA start-ups, since many of them close down due to costs far exceeding forecasts.
A typical EDA application has a huge number of similar looking dialogues, requires an embedded scripting command line, as well as serialization/de-serialization of the objects (also known as save/load) and all this needs to be updated every time the objects change.