As you will gain experience with haXe, you will surely encounter new problems to solve. This is an interesting part of programming, but if you find yourself really blocked, then there are several ways to get help.
There is some documentation available on the haXe website (http://www.haxe.org/doc) and you can also find the up-to-date API documentation at http://www.haxe.org/api. By the way, the haXe website is a wiki, which means that once you have registered, and when you have enough experience with haXe, you will be able to contribute to the documentation by modifying it or adding some new pages to it. You can also contribute by translating pages into your own language.
At some point, you will certainly want to talk with people about your problems and queries, or maybe share your thoughts about haXe. There are two main places to do that—the haXe forum and the haXe mailing list.
Once you have registered an account on the haXe wiki, you can use it to post your questions on the haXe forum accessible at http://www.haxe.org/forum. This forum has been created primarily for newcomers who are generally more comfortable with such tools. There, you have great chances of finding other newcomers and also some haXe experts to help you.
The mailing list was the first place where the community grew. Nowadays, it is where most haXe experts are, but they are also pleased to help newcomers there. On the mailing list, people ask questions to solve their problems, but it is also a place to discuss the language and tools evolution. The mailing list can be joined by going to http://lists.motion-twin.com/mailman/listinfo/haxe. If you want to know what is going to happen in the next versions of haXe, this is the place to be.
Before you ask a question on the mailing list or on the forum, here is some advice.
- First of all, always be polite and humble, particularly since you are a new comer.
- Do not hesitate to introduce yourself in your first message (telling people who you are will help them to identify you, making you part of the community)
- Always explain what you are trying to achieve. This point is to help people help you. If they know what you are trying to achieve, they will know better how to assist you.
- Keep in mind that not all participants are native English speakers. Indeed, there are chances that most of them are not. Try to express yourself in an easy-to-understand way.
- Stay focused on one problem (or one group of linked problems) per thread. If you have several very different problems, create several threads.
- Always say what platform you are targeting (PHP, Flash, Neko, Javascript, and so on). Some problems may be platform specific.
- If you have a problem with some code, always try to reduce it to the smallest possible snippet that still reproduces the problem.
- If you send some code, always try to make it easily understandable. People who are trying to help are generally happy to do so, but if they have to guess what the variable is because you named it "avhgk" instead of "userName", they will sense that you are not even trying to help them help you.
There are many people who write about haXe on their own blog.
Nicolas Cannasse, haXe's creator, maintains his own blog at http://www.ncannasse.fr where he discusses new and future things in haXe and its ecosystem, Flash, but also about the IT world.
http://www.weblob.net is Franco Ponticelli's blog. Should I remind you that Franco Ponticelli is the PHP target creator? Although this is a low-traffic blog, you will find many interesting articles about haXe on it.
Hugh Sanderson, the creator of the C++ target, maintains his blog located at http://www.gamehaxe.com. You will find some of his thoughts about haXe, the IT world, and experiments about game development in haXe.
He also explains how one can use haXe to target iOS and Android.
The author's blog, located at http://www.benjamindasnois.com, is where he talks about haXe. As he is also developing a Java target for haXe, he also writes a lot about it.
On http://blog.haxe.org, you can find an aggregate of several blogs about haXe. Some of them we have already discussed.