How does the HaxeFlixel website work. It's got errors compared to the Git documentation.

29 views
Skip to first unread message

Flabby_Fabby

unread,
Apr 28, 2015, 2:49:35 PM4/28/15
to haxef...@googlegroups.com

On the second section 5 it shows this:

_mWalls = _map.loadTilemap(AssetPaths.tiles</strong>png, 16, 16, "walls");


On the documentation the "</strong>" error is not there. How can this be rectified?

Eric Grice

unread,
Apr 28, 2015, 3:50:54 PM4/28/15
to haxef...@googlegroups.com

It should be two underscores.

--
HaxeFlixel Development Community
See our github https://github.com/haxeflixel/ and our documentation http://haxeflixel.com/documentation/
---
You received this message because you are subscribed to the Google Groups "HaxeFlixel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to haxeflixel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/haxeflixel.
To view this discussion on the web visit https://groups.google.com/d/msgid/haxeflixel/98f76122-2354-427a-8491-9b1558877f46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Flabby_Fabby

unread,
Apr 28, 2015, 4:04:21 PM4/28/15
to haxef...@googlegroups.com
But why is the error happening. It's not in the documentation.

Eric Grice

unread,
Apr 28, 2015, 4:11:25 PM4/28/15
to haxef...@googlegroups.com

It has something to do with the html formatting.  However they added the formatting in for the code did not work correctly. So you see things like this:

private function placeEntities(entityName:String, entityData:Xml):Void { var x:Int = Std.parseInt(entityData.get("x")); var y:Int = Std.parseInt(entityData.get("y")); if (entityName == "player") { _player.x = x; _player.y = y;<br> } }

Notice the stray <br> tag after "_player.y".  Unfortunately, in the case you described, the stray html tag actually replaced code that is needed for that statement to work.  So, your best bet when going through the tutorial is to check the source code you find linked at the bottom of each section.  I hope I answered your question.  I just went through the tutorial and noticed many problems with it... in fact, there's another forum post on here regarding issues with the tutorial!

Anyway... good luck!  And ask as many questions as you need :-)

Fabian Jarrett

unread,
Apr 28, 2015, 4:15:46 PM4/28/15
to haxef...@googlegroups.com
How can this be rectified?
You received this message because you are subscribed to a topic in the Google Groups "HaxeFlixel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/haxeflixel/ptj_cc_HuC8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to haxeflixel+...@googlegroups.com.

Eric Grice

unread,
Apr 28, 2015, 4:25:58 PM4/28/15
to haxef...@googlegroups.com

Are you asking how to fix the website?  You need to be more specific.

Fabian Jarrett

unread,
Apr 28, 2015, 4:28:21 PM4/28/15
to haxef...@googlegroups.com
Yea, I'm asking for to fix the website. Why hasn't it been changed? I've flagged this up before. Is there no way that I can edit the webpage in Git and get it authorised?

Eric Grice

unread,
Apr 28, 2015, 4:35:46 PM4/28/15
to haxef...@googlegroups.com

Well, I know you can click on the edit button on the top-right of git if you're signed in -- it's next to the RAW | BLAME | HISTORY buttons.  Then you can make or propose changes.  From that point, I'm not sure what happens... I've never tried it myself so I have no clue :-)

Fabian Jarrett

unread,
Apr 28, 2015, 4:38:04 PM4/28/15
to haxef...@googlegroups.com

But the errors are not on the files on the git so what could I edit? Who is in charge of the website? I don't understand how I'm suppose to get it fixed.

Ashiq A.

unread,
Apr 28, 2015, 4:43:34 PM4/28/15
to haxef...@googlegroups.com
I can speculate for you.

The docs (API, just like tutorials) are generated from one of the
GitHub repositories.

In most cases (at least for the tutorial), the code is just old and
out-dated and needs to be updated. In this case, the latest source in
GitHub is okay, but nobody generated/deployed the latest docs. I would
suggest opening an issue for that.

For the normal case (source is out of date), you can open a "pull
request." This means:

- You create your own copy of the repo (fork)
- You make your changes locally, and verify they look cool
- You commit/push to your local repo
- You open a pull request from your fork to the original

Hopefully, the author accepts it quickly. In the worst-case, they may
ask you to make additional testing/changes before they merge your PR
in.

--Ashiq
> https://groups.google.com/d/msgid/haxeflixel/CA%2BbuFNjD3fFSj9xg4nSQXgia2zUBwNLLN%3DiG5JNktbKPrun0Fg%40mail.gmail.com.

Eric Grice

unread,
Apr 28, 2015, 4:46:00 PM4/28/15
to haxef...@googlegroups.com
Ah... I see your point now!  Ashiq's suggestion sounds like the way to go here.

Reply all
Reply to author
Forward
0 new messages