Whar my unitron??? What crap is this monodevalp???

Unity Engine
1

Hi,

Preface: I’m one of those “picky” users who prefers software that feels like it was written for the platform I’m on.

I can’t stand MonoDevelop. I have a pretty high end system, and TYPING has lag.
That’s just wrong. In addition, it has the following hilariously crap UI issues:

  1. Can’t easily edit files from multiple projects
  2. Double-click to open files inside an app?
  3. Visual glitches out the ass, like missing entire lines
  4. Double-clicking on a parenthesis doesn’t highlight the entire block, unlike every other development tool.
  5. Takes forever to load.
  6. Uses jacked up Java IDE shortcuts for everything, instead of Mac commands like Command+E/F/G for working with search entries.
  7. Defaults to case-sensitive searches??? WTF man, this isn’t 1989.
  8. Regularly screws up syntax highlighting, or just doesn’t have it AT ALL for Unity commands.
  9. Doesn’t have command+click awareness for accessing the file path for a given file at the top of the window. I used to use the hell out of that.
  10. Has meaningless popups like “Release/Debug” for a text file. I get it, if it’s project, that makes sense. That does not make sense for one file.
  11. Command / Option / Shift + Arrow key combos that are standard on all Mac text editors don’t work at all.

Any chance we could get Unitron back, or at least get some fixes for this, so I can feel like my text editing isn’t being done on a PC?

Thanks!
-Chilton

2

In Unity 4.2.2 at least, there is a Unitron.app file found inside the Applications/Unity folder.

3

Not in Unity 4.3. It’s gone, brother, gone.

4

Use C# and Visual Studio

EDIT: I’m not trying to be a douche. IF you are a picky programmer that you appear to be then I honestly advice you to use C# (regardless of your IDE problems) and then use Visual Studio because it’s the IDE to use.

5

There are more than enough people happily working with JS. I will definitely not switch to the for me weaker solutions for no reason. Not to C#, not to VS.

As mentioned already, you can still use Unitron from the old installation. But chances are big that from now on more and more features will not longer work. Like open the code when an error message appears. So it`s time to search for a substitute.

I have a look at Sublime at the moment. Here`s a thread how to set it up to work with Unity: http://forum.unity3d.com/threads/128352-Using-Unity-with-Sublime-Text-2-(How-to-get-everything-set-up)

6

C# just doesn’t do enough for me, for me to consider using it all of the time. It’s too verbose, compared to JavaScript. More text = harder to find bugs.

I use C# when I need to, especially when I outsource stuff to new programmers–many of them, especially ones I find on Elance, are only good at one language, and it’s usually C#, thanks to all the schools cranking out .NET centric students.

But most of the time I prefer typing less, so I usually go with JavaScript for my personal projects.

-Chilton

7

Seeing all the MonoDevelop bugs in the support section is reassuring. At least it’s not my install :slight_smile:

-Chilton

8

When I saw the line about removing the other IDE’s I had a moment of silence for those UnityScript users.

9

Microsoft doesn’t make a Mac version of Visual Studio.

–Eric

10

… and I just lost an hour’s worth of work to MonoDevelop crashing, and taking my file with it. Thanks, MonoDevelop, may you burn in hell for an hour.

Also, I just noticed that it forces autocompletion for words like transform, into the class name. That’s a major pain in the ass.

Not only did it replace the good text editor, it’s now actively slowing me down.

11

Either copy unitron from a 4.2 folder and point Unity 4.3 to it in unity preferences, or simply switch to sublime text 2 (search forum). you’re like a big baby who actively can’t solve this most simplest of issues, and I mean that in a nice way :slight_smile:

12

While I understand the general thrust of what you’re getting at, this in particular is not a hard and fast rule or even a good heuristic. Many bugs I see in UnityScript/JavaScript and other similar languages are caused by people not using enough text, which then makes it harder to find the bug because it’s caused by implied instructions instead of written ones. When someone asks me to help them solve a bug in that style of language my first response is for them to go and make everything explicit and see if the error persists. Typically it doesn’t, either because that was the cause in the first place or because the act of being more explicit and thinking through how a computer works suddenly makes the problem clear.

I like to quote Einstein here, in that “Everything should be made as simple as possible, but not simpler.”

Anyway, I certainly agree that MonoDevelop is one of the weakest parts of Unity. I know that it’s a supporting application rather than a core part of the package, but since programming is such a core part of the Unity experience I’m surprised that a better solution hasn’t been found. I don’t know if there is a better solution, though, given the requirements at hand.

13

Brilliant post, I couldn’t agree more. I was going to post something similar but thought better of it as I wouldn’t have been as tactful :stuck_out_tongue:
Strongly typed languages are a plus in my book.

I develop on a Mac and I don’t personally use the Mono4 that comes with Unity 4.3, but an alternative called Xamarin Studio, which I hear is essentially (and appears to be) Mono4.
Never have any problems with it… maybe give it a try?

14

How well does Xamarin Studio integrate? Do errors link to lines, do you get full code completion support, and can you attach the debugger to the Unity process and use it? If that’s three yes’s then I’m in. (Downloading it to give it a go on my Windows machine now.)

15

Leans back, fires up visual studio, does all the coding…

commit.

start mac.

checkout.

build.

Development on a mac can go blow a goat… Im too used to the end key meaning go to the end of the line… not the goddamn file… of all the stupid designs… maybe this is configurable. Dont care tbh. Ill stick to my pc where I can code fast.

16

Using the end key for end of line doesn’t make sense to me…cmd-right arrow does that, it’s much more logical.

–Eric

17

not if im trying to select a line of code to copy. I then have to press 3 keys when 2 should be enough.

stupid.

18

Nope, easier to hit cmd-shift-right arrow, since you don’t have to reach alllll the way up to the end key. Not stupid.

–Eric

19

Pressing End is what I am used to and that is what I prefer to get to the end of a line quickly. Are you going to tell me I’m doing it all wrong too?

20

Yeah, I’m with Team End-of-Line here. How often do you need to go to the start/end of a file compared to the start/end of a line? The Mac defaults just don’t make sense in this case.