Native MAC support

[rajkej]

1) Native MAC support

2) Run SE on MAC but run compiler/debugger on remote platform (Linux). Maybe SE can do this now, I'm not sure.

[snobored]

+1 Native Mac support

Or, perhaps a better solution would be a SlickEdit plugin for XCode, giving us the superb code navigation, completion, etc that we've come to love with SlickEdit.

Think of all the Windows developers now forced to use XCode for iPhone development...

[greggman]

+1 on Native Mac support. I'd buy that in an instant.

[zhangxudong]

Could you port slickedit to Qt, wxWidget or Gtk, the there toolkit are LGPL. They provide powerful font, graphics functions. Qt and wxWidget are native Mac support.

[spence]

Parsing of complex Makefiles to automatically work out the project hierarchy and #ifdef values that are set.

+1 vote for Mac native.

[xy22y]

Native Mac support. Please.

[John H.]

Native Mac support, please!!  SlickEdit mostly works really well on the Mac, but it needs to be as good as the Windows experience. 

[jkwuc89]

• Native Mac support (!!!!)
• Eclipse project support
• Maven project support
• Linux 64 bit build

[drac]

- STL types support in debugger
- CDB debugger support for Visual Studio
- ditch the Motif UI library to something more modern -> Qt. This would make MAC support easier and overall platform integration.
Slickedit for Windows looks OLD.

[asandler]

- ditch the Motif UI library to something more modern -> Qt. This would make MAC support easier and overall platform integration.
Slickedit for Windows looks OLD.

+1
Indeed it looks old on Windows.
It looks even older on Linux. I tried it on Ubuntu 9.04. Lots of small things seems to be broken. Icons on toolbars that expected to have transparent background have black background. Arrow in combo box control appear as a black box. List of fonts is a weird mixture of old X style names (all low caps) and new names (DejaVu Sans Mono). When over SE's window, mouse cursor seems to be from 80's, totally ignoring mouse theme. Etc.
I didn't test SE on other distributions, so I can't tell if this is because of Ubuntu or because of SE uses oldish Motif library. Yet I am sure that there are things that SE can do to make it look better.

[SlimHeilpern]

If native Mac support is not in the cards at this time, PLEASE at least fix Brief-style copy/paste when running under a recent version of X11. I'm running X11 2.3.3.2 and am not able to down-rev it and copy/paste in either direction does not behave correctly, regardless of the X11 settings. I now have to use JEdit as an intermediate copy/paste buffer, which is pretty silly and extremely annoying.

Thanks,

- Slim.





 

[Bhelyer]

- STL types support in debugger
- CDB debugger support for Visual Studio
- ditch the Motif UI library to something more modern -> Qt. This would make MAC support easier and overall platform integration.
Slickedit for Windows looks OLD.

Qt support would be lovely. That way the Mac guys don't have to use X11 and us Linux guys don't have to use the Motif interface (even with the splash of tan that it got in 14 -- lipstick on a pig and all that =p).

EDIT: Oh, and is it just me, or do the fonts (under Linux, at least) start out as huge for the UI elements? The first thing I do after installing SlickEdit is go through every font setting and make it smaller.

[magpie]

Proper Ruby and Native Mac support. Nothing else.

[John H.]

Native Mac OS X support, please!  I'm stuck on a Mac, and the X Windows interface is a dog. It is killing me.  I can't live without SlickEdit, but I'm being punished for that.

I know it's not fair to ask this, but: is there another competing editor that I can use on Mac?  SlickEdit, you should either support the platform properly, or stop selling it for Mac.

[dunkers]

I'm stuck on a Mac, and the X Windows interface is a dog

Isn't SE usable from the Parallels thingy (where you run Windows apps on the Mac desktop)? I don't have a Mac and I'm sure you have your reasons for not doing that,  but I know of some Mac users who swear by this facility for Windows apps they can't do without, so I'm kind of intrigued as to why this might not be suitable for SE.