PureBasic Forums - English

With difficulty, I learned how to try and set up a Template in the IDE.
But it does not save, so I don't have the templates for use later.

Web searches turn up Softpedia download for "PureBasic Template
Standard Library". The download process does not identify what is
being downloaded, where it goes, or how to use them. There is
really no documentation available related to PureBasic and the
whole Template process.

oldefoxx wrote:With difficulty, I learned how to try and set up a Template in the IDe.
But it does not save, so I don't have the templates for use later.

If you use the portable mode, do you have directory write access rights?

Works fine here: I click the first Icon ("New Template"), enter a name ("test") and in the
edit dialog i write some lines of code.
After restarting the IDE, the template "test" is still there and double click inserts the template code at the current cursor position.

Danilo wrote:Works fine here: I click the first Icon ("New Template"), enter a name ("test") and in the
edit dialog i write some lines of code.
After restarting the IDE, the template "test" is still there and double click inserts the template code at the current cursor position.

That description is far more than can be found in the PB help file:

"The templates tool allows you to manage a list of small code parts, that you can quickly insert into your source code with a double-click. It allows you to manage the codes in different directories, and put a comment to each code. This tool is perfect to manage small, often used code parts."

This sort of documentation is very unhelpful, because it takes up space without providing any details.

I realize that PB is cheap (or should I say inexpensive ), but good documentation should be just as important as sexy features. Over the two years or so that we've been using PB, we've been putting together our own documentation as we discover how PB works.

We have jobs too, and aren't even responsible for PB, but our productivity has increased dramatically since we wrote our own help file. Surely improving the layout and content of the PB help file is not too much to ask, especially as PB is a mature product.

Ok, maybe the PB help could be better, but the system of templates is so simple and clear, that i don't need any helpline. With the help of the tooltips near everybody will check the system of templates in less then one minute. If i don't have adjusted my system to death, (in the most times) i don't need to know where and how the templates are saved. I use them and don't play with them, it's better to use this time for coding.

I agree with you that templates are fairly easy to figure out, but a lot of PB's features are not so easy, especially for programmers who don't have a lot of experience. One can tell this from the questions that are asked.

For example, because of our extensive experience with operating system internals and OOP, we've been able to put together a useful OOP facility using standard PB features. But less experienced programmers would have a hard time understanding prototypes and interfaces, and why they can be useful, from the descriptions that are in the documentation.

Okay. I tried it again, and this time worked. I went to %APPDATA%\PureBasic\Templates.prefs and found this as the new contents: Where you see "\n" above, that is a new line flag, like using the Enter key.

If you don't recognize %APPDATA%, that holds "c:\Documents and Settings\<user name>\Application Data", which is a specific folder on your system. If you have PureBasic copied into another folder besides \PureBasic, it will
share what it finds in %APPDATA% with the original, unless you designate a different folder for Templates.

APPDATA is one of the environmental settings which you can check from the Command line by using "set", or
that you can check inside your program by using a set if functions whose names are: Note that "set" is a good way to find the names and current values of all the environmental variables,
and if you did something like set APPDATA = \PureBasic\AppData you could change one, or do a
set APPDATA = with a blank after it, and you remove that variable from the set altogether. Not to be
played with lightly, although if you change the environmental variables in a program, once the program
is exited, the set is restored to what it was before the program was called.

The unanswered question is still, what is the story on the "PureBasic
Standard Template Library"? You know that the concept of a Template
can extend to many things, from cookie cutters to sketches that have
dimensions marked in like blueprints. But when they add "PureBasic",
it seems like they should be consistent with that feature built into the
PureBasic IDE. So this is still unsettled.

Looks to me like Templates could be such a useful tool that maybe
there ought to be something similar for handling the Include files.
As it is, the Include files are just mixed in with the other files and
you have to sort of sort (yeah, I know) them out manually.

Okay, I just sorted out the information on the "PureBasic Standard
Template Library". I used those exact words in a Google search, and
this time a new link popped up. In that link I found another link to
to the web site, and from there I followed the source file download
link to http://sourceforge.net/projects/pb-stl/files/

And these are not Template files, but Include Files. And there are
quite a few of them. I let WinRAR add the Include folder under
\PureBasic and just copied them in. Time enough to see what they
all are later. But it did answer that final question.