SGI Releases IDE

johnrpenner writes " SGI has released "Jessie" - an open source development environment for Linux. It provides an advanced IDE (integrated application environment) with comprehensive debugging tools and a highly graphical interface that eliminates the need for employing older command-line tools." However there doesn't seem to be linkage to anything more than a press release.Update: 09/21 11:41 by H : Check SGI's Jessie site for more information.

Comments

Can "Free" or "Open Source" sofware be in Java

[Chandon Seldon]

I'm pretty sure that it's being in Java rules it out of the class of RMS "Free Software" as it requires propritatary software to run. (It may be an open standard, but I don't know of any Free JRE)

I'd also think this violates (at least in spirit, if not in practice) the OSI "Open Source Principles".

It doesn't really matter if it's released under and Open Source licence if it requires closed tools to run.

Re:Can "Free" or "Open Source" sofware be in Java

[Tim Sutherland]

So is Emacs running on Solaris not free software then? The GNU tools were running on proprietary Unixes well before Linux came into being, but that didn't make them any less free.

Re:Can "Free" or "Open Source" sofware be in Java

[SimonK]

Oh great, so all that GNU software I used prior to 1990 didn't really exist. Some people have short memories.

Linkage

[Signal 11]

You really want to go to this link instead.

--

Already posted

[HeUnique]

Hi,

I already posted a feature about this "jessie" (If I'm not mistaken)..

Isnt this old news?

[alsta]

I thought this was old news. I remember myself reading about "Jessie" a while ago, here on slashdot. http://slashdot.org/articles/99/08/27/0846234.shtm l

But then again, I might be off the edge here.

Jessie tool linkage

[The Musician]

Linkage...

• Jessie Home
• FTP Download
• CVS Source instructions
• License

A bit of the license opening material (trimmed):

SGI grants permission to use, copy, modify, merge, publish, distribute, sublicense and/or sell copies of the Original Software in both source code and executable form...

Qt commercial - Re:Yes - Re:KDevelop Vs. Jessie

[mallan]

>Funny how the Qt and KDE supporters gloss over this little "problem"

Why do you see the Qt commercial licence as a "problem"?

GPL = no commercial/closed source development
LGPL = anything goes.

The Qt commercial licence offers a middle ground of sorts - if you want it for free, you have to distribute source. If you want to write closed source commercial apps, there is a strong financial incentive not to. This deters the proliferation of $10-40 closed source shareware apps that plague the Windows world. As far as I know, there's nothing to deter people from creating closed source GNOME apps.

IMO, Troll Tech has found a great way to support themselves (through commercial support and licences) while providing the Open Source community with a great toolkit free of charge. If you don't pay, you have to deal with the 'GPL-like' terms of their licence. Where's the problem?

MBA

SGI should be recognized for their goood work

[Bruce Perens]

SGI is being an honest and productive participant in the Free Software community. Be nice to them and help them out! I wish Sun had SGI's policies regarding free software.

Thanks

Bruce Perens

Re:Just a debugger/profiler?

[dtj@sgi.com]

We actually considered doing that. DDD has some very nice qualities. We especially liked it's data display capabilities.

There are several reasons that we didn't just start with DDD.

1. It is very difficult to retrofit non-debugger functionality into a debugger and come up with an IDE that is intuitive and extensible. Our team has tried it before and lived with code that has had that happen to it. Not a pretty sight.
   
2. We wanted this to be truly cross-platform, including NT and non-*nix platforms. Qt vs. Gtk wars were raging then and they are raging still, albeit with more civility. I personally evaluated Gtk and found it to be quite reasonable. Qt was dismissed because of its licensing issues at the time. Java and Swing provided a very rich and consistent GUI toolkit.
   
3. We have spent literally years designing the infrastructure to create a powerful, intuitive, and extensible environment. It isn't fully filled out yet, but the missing parts will come.
   
4. Scaling was of the utmost importance to us. Like trying to retrofit IDE stuff onto a debugger,
   retrofitting scalability is just as bad. Ask any debugger folks that have added things like thread support and other SMP constructs.
   
5. We wanted to build an infrastructure that was usable for other complex tools. Look at VA Linux's VACM product and think of what it would be like using the Jessie infrastructure.
   

There were several other reasons that have been lost in the mists of time.

-Dean

Kicking the gift-horse in the mouth

[Pengo]

Hmm.. It is so damn funny..


I have never seen more complaining in my life.

I just came from the Corel thread, COMPLAIN COMPLAIN COMPLAIN.

SGI Gives away a new IDE.. COMPLAIN COMPLAIN COMPLAIN.



The funny thing is, I don't see people that actually contribute to the compunity complaining.


Dean from SGI seems to be running around answering questions, trying to please you babies.



Just show a bit of grattitude.

Re:Just a debugger/profiler?

[dtj@sgi.com]

I also contains a little bit of static analysis functionality as well. It doesn't, however, have some of the things that people traditionally consider part of a full IDE [emphasis mine] such as GUI builders, etc. Those will come. Instead of waiting until Jessie was stocked with every conceivable piece of functionality, we decided to launch it into the world so that the community could help influence its evolution, rather than depending on marketing feedback for
its direction.

Re:Where is the syntax highlighting?

[dtj@sgi.com]

It's in there for several languages (C, C++, Java, and Ada). If you aren't seeing it, please send us the particulars to jessie@sgi.com. That's my code and I am committed to fixing it.

Also, please send us your required AND desired features list. If you would like to help make those features a reality, please check out the How to Contribute section.

-Dean

Try Kdevelop

[Anonymous Coward]

Kdevelop seems have support for autoconf and automake, and actually generate the correct configure and make.am files for you when you start a project. From what I see, you can then either modify the linked libraries within kdevelop or modify the make.am again within kdevelop. It also generates templates for Xwindows programs using the kde toolkit or qt. Also, it automagically generates help file and documentation for your project. On top of this it seems to have nice built in help files. From what I've seen so far, even as a beta, it's a nice, very slick development environment.