Hi Francois, it's good to see the new version out :-)
I tried to run something, but I can't get anything to run. When I press the Run icon, I get an error about Chrome (I use a Chrome -based browser, but will need to change the exe name wherever that is so it runs my browser), and when I try from the command prompt I get this:
"E:/Data/My Documents/AOZ Studio Applications/applications/testaoz/main.aoz/manif
est.hjson:1:1: Error: application manifest not found.
Task failed, no code generated..."
I copied the new manifest, and it's with the main.aoz file.
Those are different examples, as one doesn't compile and I don't give any error messages, and the other creates the HTML, which I can run manually without it launching my Browser for me.
Hey Paul. The first versions had a lot of bugs. Can you try with version 0.9.2?
I've tried from the command prompt with 0.9.2, but I'm getting the same 'manifest not found' error.
E:\Data\My Documents\AOZ Studio Applications\applications\TestAOZ>"E:\Program Files\AOZ Studio Beta\aoz-x64.exe" main.aoz
AOZ Transpiler Version 0.9.2 - 25/12/2019
By Francois 'Amos' Lionet (c) AOZ Studio 2019
Website: https://aoz.studio
Support the project on Patreon: http://www.patreon.com/francoislionet
---------------------------------------------------------------------
main.aoz/manifest.hjson:1:1: Error: application manifest not found.
Task failed, no code generated...
E:\Data\My Documents\AOZ Studio Applications\applications\TestAOZ>dir
Volume in drive E is Main
Volume Serial Number is E877-C471
Directory of E:\Data\My Documents\AOZ Studio Applications\applications\TestAOZ
27/12/2019 11:39 <DIR> .
27/12/2019 11:39 <DIR> ..
26/12/2019 12:57 28,320 files_load.hjson
26/12/2019 09:10 <DIR> html
26/12/2019 09:07 61 main.aoz
21/12/2019 10:07 11,406 manifest.hjson
3 File(s) 39,787 bytes
I uninstalled the previous one, then installed the new one to 'Program Files' instead of the user profile that it defaulted to (I really don't like the idea of installing things to there instead of Program Files), then I tried running the exe from both the exe location and pointing to the application, and also from the application directory pointing to the exe file. Both said it could'n't find the mainfest.
The bit that looks strange to me is this bit: <path>main.aoz/manifest.hjson
It's as though it's looking for the manifest file in a sub-directory called main.aoz
Has everyone else been installing to the Windows profile instead of Program Files?
I too have so many problems. Very few of the programs run... Help 4 , 8 , 11 , 12 , 13 and 14 will stop with an error... here in the images below...
The images from Chris is the same error codes I get. I wonder if this has something to do not installing the program on the same drive as intended by the installer? #edit No. Installing it in the suggested place doesnt make a difference with the errors.
I've been able to get it working in Windows 10 without too much trouble, but some of the demos won't compile. Most of them work. I was also able to get a "Hello World" program to compile, per the example. I'll probably do more testing tomorrow night. The only thing I did differently from the standard installation, was that I changed the folder names with spaces in them, replacing the spaces with underscores. If you want to try and see if that works for you too, you'll need to change the associated environment variables as well. I'm using the F2 & F1 to compile & run. Make sure you click in the source code window before activating the F2 & F1, otherwise they won't work. The run (play) button is working, but the compile button has problems.
By lissening to ising4jesus I have got it to work! When installing I removes the spaces in the suggested directory, and when compiling only pressing F2 og then F1 (not using the buttons up in the right corner). I hope others who has problems get it to work this way as well :)
I think I'll leave it for now. Hopefully the next release will handle spaces (and other locations, if that's a problem, too). I can't be renaming "Program Files" or "My Documents" (where the programs now go), and I hate the idea of installing to somewhere other than Program Files.
Of course if this was an Amiga, I'd just set an 'assign' for aoz: and it would all work!
Hello all. Sorry for the problems. - compile from command line You have to indicate the path to the FOLDER where the manifest is. NOT the path to the .aoz file itself. I will change it so that it works IF the manifest is located just beside the .aoz file, but I cannot do more. I will also make sure you can compile by indicating the path to the manifest, should have done it first thing. So, this will work: aoz-x64 applications/demo This will not work: aoz-x64 applications/demo/main.aoz - F1 and F2 Yes, F1 and F2 are mapped to VsCode tasks that only work if the currently active file is a .aoz file. So make sure to do Ctrl-Tab to activate the file before using them. - spaces in path. I have made sure that all commands I send internally have quotes. And it works here, where I do have spaces in both binaries installation path and applications installation path. Of course, if you use the tool on the command line, you must also put quotes.. So it cannot come from that, or I have forgotten one place.. It is the first thing I will work on starting tomorrow Monday, solve those kind of problems, and will do my best to publish a corrected version tomorrow evening. I know what I will do. All the problems come from the fact that VsCode does not load for a reason the system variables %AOZPATH% and %AOZAPPS% that I create during installation. My solution will be to create a simple INI file with the path in the Windows/System folder during installation, and access it each time I need to run the tools. - demos not compiling. ???!!! They all compiled one day before publication, I must have done on extra modification just before the publication that screwed them... Sorry. Next version will have them all compile. AND I will make a batch to compile them all and test them that I will run before each new version. Please understand that in the rush we did not have much time to test on multiple configurations. If it does not work, just drop it for the moment and wait for the next version. But please don't leave the project! ;)
Thanks, Francois. I've got a bit further.
The above mentions a few places that don't exist:
I do have E:\Program Files\AOZ Studio Beta\languages, but not the one above that's mentioned.
I don't have a c:\snapshot
I'll try the next version, and let you know how it goes.
Thanks Paul... The "snapshot" directory is a temporary directory created by node.js or something like that. But have enough information to debug now... :) If you are OK with it, I will send you a version tonight or tomorrow morning for you to test (and all the people in this thread, I will put a link here only), to make that the version I publish tomorrow work before.
Sounds good. I'm sure I'll be able to try it out once you post the link. I'm off work, so just playing Death Stranding at the moment :-)
Would you recommend an uninstall of AOZ before putting on the new one, or can we just re-install over the top?
I saw the video for 9.2.1. I've just tried it, and I'm getting this:
I get that when running from a command prompt, or pressing the test and run button.
If I press F2 in the code window, I get:
I've created another new application, and that one IS running, so it seems to be my previous code that won't compile.
I re-created the above test (hello world program), and that is now running. Previously it failed until I deleted the application and re-made it.
My other older ones are still failing (same errors as above; c:\snapshot, etc.) even when I made a new app and pasted the code into it.
Paul, can you ZIP your applications that do not work and send them to me?
@Francois Lionet I've just worked it out. There are two things causing the compile problems:
1) Restore - this gives:
2) The old ELSE IF problem that started happening again after February last year.
This code:
Gives:
There was a brief moment when else if's worked, then it broke again. I think you said it was a difficult one to fix.
Restore: corrected. Else If example too, and actually it was crashing because the array was not dimensioned (you have to do a Dim before using an array), and also the "array not dimensionned" error was not reported, only (too may) syntax errors. All corrected now.
Well, my problems has gone away with this update. I installed it on a new computer though, and the problems where back. After uninstall and install again it got better and the only thing not working was the connection to the browser. So I started the browser first, compilet afterwards and then it worked. Really strange, but now I can start making things finally :)
The first time you launch an app, it can take a lot of time... I really do not know why...
I just got the error on my previously working thing. I had a 'then' on a multi-line 'if'. Once I realised and removed it, it started compiling again, so the problems I'm having are just something that used to compile in a previous version but now should probably be giving an error (or should compile normally), but is giving these other errors instead.
Can you post an example of code that does not work? Thanks... :)
@Francois Lionet
This works normally:
but if you accidentally put THEN on the end of the IF statement, you get all the c:\snapshot errors. I'm assuming we shouldn't be getting those at all, and just the syntax error.
@Paul Kitching Corrected!
This was a new one:
It took over 30 seconds I think and I was becoming worried, as my drive was being hammered, then it aborted with that. I realised I missed a bracket off the end of line 59 of the main.aoz that's included in the zip. It may be helpful to trap that happening in the future.
It might be something to do with a missing bracket and a comment after it, as this is the line (missing bracket in blue):
Bad one this one. It was looping endlessly. Fixed for v0.9.2.2... :)