Allow upper case in current working directory, but not in what follows (Allow upper case chars in current working directory, but not in what follows)

[mationai]

Love to try, but the installation seems daunting. Think an install script can get many people on board who is deterred by the installation.

[Coolrunner86]

Good idea. Mind to participate?:)

[yegordovganich]

@fuzzthink can you provide a bit more details what exactly seemed daunting? Perhaps we need to update installation guide because it should be easy as a pie.

[mationai]

Ya, the installation guide is very confusing.

First, there's a simple Installation section in README, but it doesn't work, I got errors. Even if it does, it doesn't say what that command does. I recommend just removing that section and have link to the installation pages instead.

The installation page (https://github.com/area9innovation/flow9/blob/master/doc/mac.markdown) is really confusing, so "easy as a pie" seems to be the opposite of that. Plus I would not call anything easy if I a compilation step is needed (see "Compile Flow itself"). If compilation is not needed, leave it off or put it under "Flow9 Development".

The steps in haxe section is too complicated. So I need to create a haxe working path, set the path, and use a new terminal. -- I skipped this part, the barrier was too high.

I did brew install haxe however, and if brew install does work for haxe, replace the download to install instructions with brew install haxe.

Say if I want to compile to javascript/web, it seems that the "Try it (C++ runner)" part can be skipped.

After doing all required installs except the Haxe part, I run the flow --js demos/helloworld.flow sandbox/helloworld.flow and it says Could not find sandbox/helloworld.flow. Use -I <path>. So is sandbox supposed to be created via flowcpp under "Try it (C++ runner)"? Since that's the first time sandbox is introduced. If not, how was sandbox created?

I'm one of the most adventurous person to try new language, but this is just too much even for me.

[mationai]

https://github.com/area9innovation/flow9/tree/master/bin at the minimum needs a README.

Better, there should be only one flow command and all other bins should be an option. Is that the case? I can't tell since the instructions all point to different bin commands. Once unified, it will be just flow --option.

[mationai]

FYI, I don't think an installation page that spans 8 screen scrolls will get the conversion rate one would desire.

[mationai]

Finally did everything in instructions and figured out sandbox refers to sandbox path in repo.
Few issues.

1. Instruction's flow --js helloworld.js sandbox/helloworld.flow should be hello.flow, not helloworld.flow.

2. You will get "For consistency, file names should be all lower case" if absolute path is used. Eg. flow --js hello.js ~/libs/flow9/sandbox/hello.flow

3. The "For consistency, file names should be all lower case" above, It's an error even though it doesn't say it's an error. You have to figure that out by listing hidden files and cat .compile-errors to know it's an error.

4. Why "file names should be all lower case" error when the filename is all lower case? Guessing since absolute path was used and it starts with upper case /Users/..

5. README says these instructions are actually "original compiler". "The flowc is the current compiler, written in flow itself. See tools/flowc." So where's the instructions in using tools/flowc?

[alstrup]

1. Is fixed. 2.+3.+4. This warning is a limitation in the compiler. We should allow upper case in the cwd part of the path, and only complain if the upper-case is in the part beyond that. Until then, try to place things in a folder without any upper case parts in the entire path. About 5. Where is that reference?

[mationai]

Where is that reference?

It's under tooling: https://github.com/area9innovation/flow9#tooling

Thanks for changing title to reflect the issue. Can you label it as bug?

[alstrup]

5. Instructions for using flowc will come if you just run "flowc1" or for more detail "flowc1 help=1".