Earlier quoted context omitted.
I would rather have developers work on the IDE than make yet another GUI interface for Git. You have the command line for that.
I think you mean "yet another GUI for Git." "GUI Interface" expands to "Graphical User Interface Interface." Sorry, I could not help myself.
Ninja IDE: written in Python for Pythonists
111–120 of 137 posts
Re: Ninja IDE: written in Python for Pythonists
#112Earlier quoted context omitted.
This is a very strange reason not to like a product. Care to elaborate why?
In this case, it runs using X11 on OSX, which is a terrible way of making software ;)
Re: Ninja IDE: written in Python for Pythonists
#113Crashes on launch for me.
Re: Ninja IDE: written in Python for Pythonists
#114Re: Ninja IDE: written in Python for Pythonists
#115As others have already mentioned, PEP8 validation is enable by default, which is a little excessive in my opinion (specially with the line All in all it looks very nice, thanks for sharing.
I think that we as an industry need to drop the 80 char per line rule.
[1] http://desktoppub.about.com/cs/finetypography/ht/line_length...
Re: Ninja IDE: written in Python for Pythonists
#116Re: Ninja IDE: written in Python for Pythonists
#117Earlier quoted context omitted.
I would rather have developers work on the IDE than make yet another GUI interface for Git. You have the command line for that.
I think you mean "yet another GUI for Git." "GUI Interface" expands to "Graphical User Interface Interface." Sorry, I could not help myself.
Re: Ninja IDE: written in Python for Pythonists
#118Earlier quoted context omitted.
Why is this downvoted? He politely corrected parent's word usage and that should be encouraged, no?
There's a fine line between correction and pedantry.
Re: Ninja IDE: written in Python for Pythonists
#119It would be great to see some screen shots.
I'm a bit reluctant to download an app with so little information except from a sparse bit of text.
Re: Ninja IDE: written in Python for Pythonists
#120Earlier quoted context omitted.
That's a good point, although I feel that "development on KDE" needs a response: KDevelop isn't limited to making KDE applications, and KDE applications like KDevelop aren't limited to running inside the KDE shell - the major Linux desktops are quite interoperable today as far as running applications goes. Furthermore, generally speaking KDE apps are also available for Windows (via the KDE Windows installer) and OS X…
I personally don't feel like downloading all the hundreds of megabytes of KDE runtimes just to fire up an IDE for a test run (this is on Xubuntu).