Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Platform-specific getting-started guide for Eval/interp? #401

Open
uvtc opened this issue Oct 11, 2019 · 0 comments
Open

Platform-specific getting-started guide for Eval/interp? #401

uvtc opened this issue Oct 11, 2019 · 0 comments

Comments

@uvtc
Copy link
Contributor

uvtc commented Oct 11, 2019

I notice that at the language intro page, where it has the buttons for the platform-specific getting-started guides, there isn't one for eval/interp.

If a new user wants to get started right away learning and using Haxe, I would think that the fastest path for them would be to use interp.

Recently I was trying to find the easiest way for someone to use Haxe on MS Windows (I'm not a regular Windows user). I looked at the list of target guides there, pondering which platform would be the easiest to target (easiest to install prereqs), and also considered using try.haxe.org, until realizing that I don't need any target to start off with --- I can just use --interp.

Maybe, on that page, change this:

"Now that you've downloaded Haxe, you can get started with a specific platform."

to something like

"Now that you've downloaded Haxe, you can get started right away using the built-in interpreter, or else with targeting a specific platform."

uvtc added a commit to uvtc/haxe.org that referenced this issue Dec 26, 2019
The simplest and easiest option to get started writing and locally running Haxe code.

Modeled after the Python one.

See issue HaxeFoundation#401 .
markknol pushed a commit that referenced this issue Oct 1, 2020
* Create eval.html getting started page

The simplest and easiest option to get started writing and locally running Haxe code.

Modeled after the Python one.

See issue #401 .

* fix link to lib.haxe.org to be non-python-specific

* fix path to Haxe logo png file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant