documentation

[kns]

I apologize if the following has been stated above, but I will ramble for a moment or two.

If a documentation project is to be successful it may be best to provide coding guidelines for the contributors. That is, the examples should follow good programming practices with a consistent look and feel. I've said this before. There are any number of ways to code a particular task but they are not all suited to producing readable code that may be extended, or even serve a foundation for learning.

The above may seem obvious, but it certainly has not been put into practice when considering what's available.

Purebasic aims to be full integrated programming environment, with what would otherwise be separate libaries in languages like C or C++. As such, it's not only the language that needs explanation but how those basic constructs interact with the available bells and whistles. A plan must be put in place to truly introduce the environment and language.

---

By definition enthusiasts will dedicate themselves to an activity, which inevitably leads to success or progress. By contrast the typical user looking for a tool approaches a programming environment with a different mindset. In his or her mind not every step should be a challenge. Entry should be eased as much as possible. I've noted that some users imply that there is something wrong when questions are asked, or there is a request for documentation. So, think about the variability of the wider audience.

As noted in my earlier post I have ceased any personal exploration of PureBasic but will/may return to tinkering when the quality of help improves. Given my position feel free to disregard the above.