SlickEdit Community

General => General Programming => Topic started by: raywert on July 23, 2006, 03:27:22 pm

Title: DSP Altenate IDE
Post by: raywert on July 23, 2006, 03:27:22 pm
I am a software engineer working on DSP (Digital Signal Processing) software development.
I have used the CodeWright editor as an alternate IDE or editor when working on TI (Texas Instruments) and ADI (Analog Devices) related development.  I would like to hear from anyone that has used the Visual SlickEdit as the alternate editor or IDE for the recent version of Code Composer Studio from TI.  I will probably try SlickEdit in that area, but would like to hear from anyone that has already been there.
Ray Wert
Title: Re: DSP Altenate IDE
Post by: hs2 on July 23, 2006, 08:39:40 pm
Didn't use it for TI dev., but in general: There is no other IDE for cross development like Slick.
It's just the most versatile tool I know. And no - I don't get paid for such statements (yet ?) ;)
HS2
Title: Re: DSP Altenate IDE
Post by: shaker on September 28, 2006, 09:24:50 pm
Has anybody been able to open a Visual DSP project (Visual DSP is Analog Device's IDE) using Slick Edit?

Thanks.

Shaker
Title: Re: DSP Altenate IDE
Post by: Gary on September 29, 2006, 03:28:40 pm
@shaker: could you probably post or send me a dummy Visual DSP project file - if the syntax is not too complex there might have a chance to implement it by yourself (i did that for keil uVision project files)... maybe i can give you some useful hints :)
Title: Re: DSP Altenate IDE
Post by: Clark on September 29, 2006, 08:31:17 pm
If the DSP files are text, this is definitely doable.  All our code for opening third party projects and/or workspaces is written in macro source.  The hard part is support adding/removing files from SlickEdit or handling cut/paste in the project tool window.  We try to support adding and removing files for all third party projects but we only support cut/paste for a couple.  In the case of Codewright, we'll just convert there projects since the product is very dead.

It is easier to just to write something that converts the project every time you open it.  Also, if you write a new command to open just these projects, you won't need to modify any macro source we ship.

If you go the nine yards and do descent job modifying the Slick-C source, then we'll just add it to the product :-)

Title: Re: DSP Altenate IDE
Post by: Phil Barila on September 29, 2006, 09:15:22 pm
Yes, but what if he does a decent job, will you include it then?   :D