Axe Interpreter

[saintrunner]

HEY THAT'S MY TECHNIQUE!! lol

[Michael_Lee]

Scratch that -- longer then 10 mins.  I thought I had pyInstaller or cx_freeze all set up and everything, but that doesn't seem to be the case .

Plus, parents are calling for dinner.

[alberthrocks]

Well, I've tested it and it simply doesn't work, so....
But either way, I had a PyInstaller environment set up for Croquette building and testing, so I easily translated over my build script for this project!

Here's my script:

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

:: This is where PyInstaller is located on your computer. It should be the stable (1.5.x) version! :: Do NOT use the trunk version; it will NOT work. @set PYINSTALLER_PATH=C:\Users\arthur\Documents\pyinstaller-1.5.1 :: This is where you want the build files to be. You should set this to the source dir\build directory, but you're free :: to choose any directory you wish - just make sure it exists. @set BUILD_DIR=C:\SourceCode\axeinterpreter\build :: File to compile (this should be the main one) @set TO_COMPILE=C:\SourceCode\axeinterpreter\source\main.py :: Basename of Python file that you're compiling - for example: ::    Compiling C:\bla\bla\bla\interesting.py ::    The basename for this file is "interesting" ::    (do not specify quotes) @set BASENAME=main :: Final base file name @set FINALNAME=AxeInterpreterv0.0 :: Uncomment if you haven't used PyInstaller before ::C:\Python27\python %PYINSTALLER_PATH%\Configure.py C:\Python27\python %PYINSTALLER_PATH%\MakeSpec.py --onefile --windowed -o %BUILD_DIR% %TO_COMPILE% C:\Python27\python %PYINSTALLER_PATH%\Build.py %BUILD_DIR%\%BASENAME%.spec move %BUILD_DIR%\dist\%BASENAME%.exe %BUILD_DIR%\dist\%FINALNAME%.exe pause

Here's a Windows build for people to play with - again, the program seems to not work, but I release it anyway just in case someone does get it to work.

Attached is a ZIP file - just decompress and enjoy! There are helper BAT files so that you will never have to open a console ever again
This should also work in Linux via WINE.

EDIT: Oops, forgot to include PyGame! It still doesn't work, but YMMV: http://dl.dropbox.com/u/1016340/AxeInterpreterv0.0_Windows_x86.zip (if link is not up immediately, it will be in a few minutes)

[Michael_Lee]

Because I don't want people to play with broken exes, here are working ones!

I made a few minor tweaks.  Double-clicking the exe now starts the interpreter, you can drag and drop a text file over the exe to try and run it, and the program will drop into the interpreter mode after a text file finishes running (so that you can do a postmortem, dissect variables, etc.)

For some inexplicable reason, you need to add a 'import pygame._views' while using pyinstaller in windows but exclude it for linux.

Download Windows version: http://dl.dropbox.com/u/10645749/axe-interpreter-windows.zip
Download Linux version: http://dl.dropbox.com/u/10645749/axe-interpreter-linux.zip

[Nick]

is it possible that you need other files than the exe? it searches for a file in a directory on your pc xp

[Michael_Lee]

Really?  What do you mean?

[Nick]

uh, wow wait, i tried it again and now it all works fine but the first time it gave like 1 minute long an error message in the commandline (but so fast you couldn't read it) and than it stopped saying something like c:\users\michael\dropbox\python files not found or so (i already closed it os it's not exact..ending with ,] that's all i can remember), but now it is ok

[AngelFish]

Nice project. One bug I noticed is that even if you don't use DispGraph, entering anything in the interactive mode will cause the display to update.

As for the name, what about AXE (Axe eXecutable Environment) or AXiE (Axe eXecuting interactive Environment)?

[Art_of_camelot]

AXIS?
Axe
Interpreting
System

[FinaleTI]

Or what about Axecutor?

[Art_of_camelot]

Oooh, I like!

[alberthrocks]

Because I don't want people to play with broken exes, here are working ones!

I made a few minor tweaks.  Double-clicking the exe now starts the interpreter, you can drag and drop a text file over the exe to try and run it, and the program will drop into the interpreter mode after a text file finishes running (so that you can do a postmortem, dissect variables, etc.)

For some inexplicable reason, you need to add a 'import pygame._views' while using pyinstaller in windows but exclude it for linux.

Good tweaks indeed.
Also, that bug you mention about has been fixed rather recently... O_O http://www.pyinstaller.org/ticket/406
There's a "hook" that had to be implemented for it to work. (pygame._view is considered as a "hidden" import.)

Some further suggestions...
1) I suggest you look into threading (you'll be seeing that very soon in Croquette!) for Pygame event pumping. If you don't "process" the events sent to the Pygame window, Windows will think it died and ask to terminate it. The Pygame portion MUST remain in the main thread (unfortunately), but the CLI interpreter can be handled in the thread, making things work out nicely. (Even if it's odd to do graphics processing first )
2) Add an option to hide/show the window? (As you've demoed, some commands do not need the screen shown.)
3) CLI commands - like when I do Output(1,1,"Hello world!"), it shows it in the console instead. A flag must be toggled for this to work, of course. If you want to implement this, you need to use a mix of the ncurses module and the Windows Console module.

Otherwise, it's pretty nice

[Michael_Lee]

Nice project. One bug I noticed is that even if you don't use DispGraph, entering anything in the interactive mode will cause the display to update.

Oh, that's intentional.  To turn that off, type '@DRAW 0' and to turn it back on, type '@DRAW 1'.  I thought that constantly having to type 'DispGraph' was a bit annoying.

Some further suggestions...
1) I suggest you look into threading (you'll be seeing that very soon in Croquette!) for Pygame event pumping. If you don't "process" the events sent to the Pygame window, Windows will think it died and ask to terminate it. The Pygame portion MUST remain in the main thread (unfortunately), but the CLI interpreter can be handled in the thread, making things work out nicely. (Even if it's odd to do graphics processing first )
2) Add an option to hide/show the window? (As you've demoed, some commands do not need the screen shown.)
3) CLI commands - like when I do Output(1,1,"Hello world!"), it shows it in the console instead. A flag must be toggled for this to work, of course. If you want to implement this, you need to use a mix of the ncurses module and the Windows Console module.

Otherwise, it's pretty nice

Thanks for the suggestions!  I ended up using multiple processes instead of threads, but the final effect was the same.  Never mind.  Should have tested on Windows.  Got threads working now.

I'll look into the other suggestions, thanks.

[DJ Omnimaga]

Or what about Axecutor?

That sounds like a Pokémon

Nice idea though lol

Also nice to see this worked on more

[epic7]

Exe file yet?