Mirror of forum.nim-lang.org

2451 :: Difficulty getting started with aporia.

• jyelon (orginal) [2016-08-09T06:04:54+02:00] view original

  I recently installed Nim using the windows 64-bit installer. I wrote a hello-world program (just an echo statement). The program compiles and runs when I compile it from the NIM command prompt. Now I'm trying to run it from inside aporia, to see if I can get aporia to work.

  Issue #1:

  When I start aporia using the shortcut in the windows start menu, it asks me to show it the location of NIM.EXE. I do, but the compile immediately fails (exit code 1, no other error message visible in aporia). On the other hand, if I start aporia by opening the Nim command prompt, and then I browse until I find APORIA.EXE, and invoke it manually, aporia compiles my program successfully (exit code 0).

  I believe that what is happening is that NIM is not in the system's PATH environment variable. Launching the NIM command prompt sets the environment variable correctly, but only within that window.

  Issue #2:

  When I use aporia to run my program, it pops open a command prompt. I can only assume that my hello world program is printing into the window, but the window closes so fast that I would never know. I feel that the default behavior needs to be to leave the window open.

  Issue #3:

  When I use aporia to compile, if my program contains a deliberately-introduced error, the error message doesn't end up in the errors tab. The error message is completely invisible.

  Neither of these issues is a show-stopper for somebody like me, who is already enthusiastic about Nim. But they might deter somebody who is evaluating Nim and who isn't sure whether Nim is ready for prime-time.

---

• hcorion (orginal) [2016-08-09T06:55:34+02:00] view original

  I develop my Nim code mostly on Windows, and I just use Atom and keep a terminal open. I tried using Aporia, but I had trouble installing it, because at the time (I don't know if this is still a problem) It was rather hard to build aporia from source on windows (and gosh darn, I wanted the bleeding edge!).

---

• Stefan_Salewski (orginal) [2016-08-09T10:13:54+02:00] view original

  There is much Nim support for many popular editors, see this page middle area:

  http://nim-lang.org/question.html

  Aporia is a nice example application from early days. It contains some examples for GTK usage, launching processes and doing socket communication and a lot more. Using the program may be OK for people interested in GTK programming generally, but we all know that GTK software works better for Linux than for Windows.

---

• jyelon (orginal) [2016-08-09T14:08:14+02:00] view original

  If aporia isn't fully functional, it probably shouldn't be the promoted item in the start menu.

---

• dom96 (orginal) [2016-08-09T22:53:26+02:00] view original

  Please report these issues on GitHub. Also let me know how you installed Aporia, was it through the Nim installer?

---

• jyelon (orginal) [2016-08-10T20:24:22+02:00] view original

  I used the 64-bit nim installer for windows. I didn't install anything else, or build anything myself.

  After installation, if you look at the start menu, the highlighted menu item is Aporia.

---

• Dippo (orginal) [2016-08-13T22:46:54+02:00] view original

  Is Nim executable in your path? If it isn't, then you must create a batch file where you add Nim in your path and then run Aporia. This would solve issue 1, but i think it won't solve issue 2. To solve issue 2 you must add to the end of your code, that you must press a key to actually quit the created app. I think issue 3 has to do with theming within Windows, if you set it to standard the error messages are visible. You can check if the error messages are created (but not visible) by selecting the text. This will give it a different colour.

---

• honhon (orginal) [2016-09-11T07:18:40+02:00] view original

  I've tried a bunch of options including Aporia and I liked Visual Studio Code best for Nim which I am only using for Nim and a little bit of moonscript.

---

• Libman (orginal) [2016-09-11T21:42:36+02:00] view original

  I think it would be best for the cause of Nim adoption to focus on polishing the developer experience on one open source IDE and recommend that to newcommers by default.

  Aporia never seemed fully baked to me. I've also briefly tried nimedit, but now it no longer seems to work. I've had a fairly good experience with Atom and VSCode, the latter being somewhat faster and more stable. All Electron-based editors have a major shortcoming for me - they don't work on BSDs - c'est la vie - but I think VSCode is the best option for Nim.

---