How ever, i don't have the src directory at all... from whitch i can grab the python file...

Wait, what? Seems theres something wrong with the latest Tolk build, hm. Also Kind of didn't mention you also needed the screen reader drivers, heh. Anyway, download the appveyor file and go into x86, copy Tolk.dll, dolapi32.dll, nvdacontrollerclient32.dll, and saapi32.dll to your working directory. Next in the github version go into the /src/python directory and copy over Tolk.py, that should get you what you need.

@30
The TolkDotNet.dll isn't the same as Tolk.dll, which the python wrapper is for, though both are in the download, or were as the case may be. When I try running scripts without the drivers in the same working directory I'd get no output, although maybe its the environment variables in my setup. Not sure how the .NET version handles,

Hm, well this is more annoying than it usually is. Alright try downloading a test file I put up in my repo awhile ago [here].

I agree that game development is bit different from other systems, so selected software architecture depends much on what you want to do.

@22: it depends if you understand not just how to make a class, but also why to make a class and how to deal with its structure.
To let me explain why I'm saying that you need to know encapsulation and inheritance, there is one maior difference between those things and software architectures like mvc, mvvm, mvp, various patterns like statics, singletons, service locators etc.

Encapsulation and inheritance is a native property of object oriented programming languages like python. Like variables or functions. You can code without knowing them and also get some results. But in that case you can't say that you know how python works, because you haven't covered all its features. inheritance for example is widely used in gui systems. If you want to code a form with WxPhoenix for example, first thing you need to do is to inherit from its WindowFrame class (not to be confused with windows of pygame or pyglet, they work bit differently).
Also just by declaring a class you are inheriting from object class, although it is not visible.
So understanding of oop is connected with understanding of language.

On the other hand, there are software architectures and patterns. They have nothing to do with any programming language. They are just ways, how to use oop to make the most readable and most maintainable code. You can ignore them and still have no problems using python and understanding its libraries,. Of course if you know them, that can help you much especially in robust projects, they weren't developed just because someone was bored.
But you can use every aspect of language even without knowing them.

With that said, if you think you are confused when reading code using external libraries, the reason why you don't understand it may be because you are missing some language features and thus it would make sense that code seems more like a cypher to you than a code.
So my advice is to learn what you can expect from the language, then go and study libraries, source codes, etc.
of course exercising is required during the entire process, not on its end only, that's right. But in that case, if you study how to use libraries and so on, it is normal that you get confused at some points and there is no reason to be worried about it.

@21: it makes sense that C++ compiler is written in C, because there was no C++ to write C++ in.
But even if it was, how would you want to divide an algorithm, which's only task is to  grab the code and translate it to machine code to objects? Compiler is object itself, like tons of dlls which are written in C.
On the other hand, gui systems or any bigger apps, which can be divided to reasonable objects are not in C, but at least in C++. There are exceptions like Wordpress in this, but that's shame of developers and in most time cause of old roots.

I have no time to write here examples why oop is important and why every application where it is possible should use it.
But that is luckyly not needed, because someone already did so. This perfect course:
https://www.ict.social/software-design/ … hitectures
Is primary targeted to di, but it covers all important software architectures including unstructured code and practical example why to avoid it. That's already in this first lesson, so if you want, you can study it and get some ideas from professionals, along with examples and proofs.

Best regards

Rastislav

@Rastislav Kiss, it I think you only know about OOP paradigm, correct? It's totally understandable, I mean it's often the only one that's taught and no doubt it's the most used paradigm. It has a lot of advantages, but it's always important to know strengths and weaknesses of something. You see, nothing is perfect ans so is OOP. Here's a very good article showing the weaknesses of OOP and while I do not necessarily agree with everything that guy is saying, it's very well written with solid arguments: https://medium.com/@cscalfani/goodbye-o … cda4c0e53.

It's just to show you other opinions about OOP. I'm not saying OOP is bad, not at all, I'm saying that saying that OOP is one solution fits all is bad. It's just like saying plasters are good for all injuries. Sure, they will do great most of the time, but if you break an arm, you'll need something else. I'm sure you understand why people might prefer different languages and there is no harm if you say that you recommend OOP because of this and that, the problem is when you make it look like it's the only thing out there, please don't make the same mistakes as many teachers do.

You also mixed two things which I don't really like: the way OP writes code and the libs OP must read, use and understand.

Regarding how OP writes code is OP's business. When you start programming, you are not perfect the first time. You learn by making design mistakes, by realizing that the code you wrote is extremely painful to maintain, by realizing that if you knew you wanted this game feature in the first place, you should've structured the code in a different way. It's totally fine and as I said, the best code you can write for games is the one that makes your game progress the quickest.

Then, there's the part where OP needs to use libs and understand how they work. And for that, you are indeed totally right. If OP uses OOP libs, which all of them are really, then yes, OP needs to understand classes, how they work and how to use them. You don't need OOP to write your own code, it's not necessary, but you need it to read and use third party code, no doubt of that. But the skill required to read code is very different than writing code. I can understand most languages I don't know by reading a few source files, but it doesn't mean I can write code in that language. Likewise, I can read lib documentation and get running very quickly, but it doesn't mean I would be able to write that lib myself as quickly.

Even if it's a DLL, you need to consume the library, use their functions, classes, objects that is. You don't need to know the source behind it, but you at least need to know how to use it.

You say your own post is true? That's a totology?