20.06.2011, 21:59
(If you remember me then I'm here only for code. Not messing around with GTA problems.)
Now some of you may remember some projects on making OO "trick" in pawn and these generally known types of add-ons in sa-mp such as Streamers, command handlers, utils...
And well I want to know your opinion on possible standards and specifications to make code portable. (Yes, I know there are some, like _ALS_ by ******, among all his other standards). For example, let's consider a code that creates a turismo and handles everything needed. Now let's say it's a FS. But now if we have 20 such "nice thing" handlers, it would be better if they had universal code, that could be incorporated into GM. And then we need specifications, because not always code will be using the same streamers as you are. Or maybe there are commands....
My solution would be such as making general standards for streamer usage, copy paste GM code (especially handling sa-mp callbacks.. I've got an possibly stretchy idea) and utilities coding.
But as sa-mp community haven't got much attention to some information and useful advices, it should be made somewhat like this :
1. It would be a subforum of Scripting Discussion named ± "<Code> Standards and Specifications" (<optional>).
2. There would be general and local standards, and each standard would have it's topic with further development.
3. For specific every day standards there would be topics that would give a list of them as well as short description.
4. Codes would have [tags] or some fast notation that would state, if there's a GM injection available, what streamers it supports...
5. <Your suggestion here>.
And some discussion about OO functionality in pawn in context of specification (you may just skip it) :
* There should be 2 - 3 OO specifications, that would allow the code to be portable and readable in context of specification.
Macros are fun, but as I'm fighting with basic (I mean plain code, no Visual C++) win32 .again. I'd consider future of flexible and useful OO to stand upon teamwork. Basic idea is that, for example, one who knows the specification in project could form a base for everyone else. (Without need to interrupt their code) It may not sound perfect, but those who would work in a team should gain from it. And those who code alone, they always have the full flexibility and probably will gain far more than they could lose from using it. I'll make a topic about it, when I'll be able to make a class in this style, but in basic words now, it's kind'a like you took, for example, ****** OO framework and forgot the macros. And my dream is to optimize it so that it's for real. Or for just a nicer macro where it's harsh .
Another great option would be RP coding specifications, because, in my experience, cool mods are often made as FS, while absolutely useful for RP. And then again <your RP ideas here>.
Now some of you may remember some projects on making OO "trick" in pawn and these generally known types of add-ons in sa-mp such as Streamers, command handlers, utils...
And well I want to know your opinion on possible standards and specifications to make code portable. (Yes, I know there are some, like _ALS_ by ******, among all his other standards). For example, let's consider a code that creates a turismo and handles everything needed. Now let's say it's a FS. But now if we have 20 such "nice thing" handlers, it would be better if they had universal code, that could be incorporated into GM. And then we need specifications, because not always code will be using the same streamers as you are. Or maybe there are commands....
My solution would be such as making general standards for streamer usage, copy paste GM code (especially handling sa-mp callbacks.. I've got an possibly stretchy idea) and utilities coding.
But as sa-mp community haven't got much attention to some information and useful advices, it should be made somewhat like this :
1. It would be a subforum of Scripting Discussion named ± "<Code> Standards and Specifications" (<optional>).
2. There would be general and local standards, and each standard would have it's topic with further development.
3. For specific every day standards there would be topics that would give a list of them as well as short description.
4. Codes would have [tags] or some fast notation that would state, if there's a GM injection available, what streamers it supports...
5. <Your suggestion here>.
And some discussion about OO functionality in pawn in context of specification (you may just skip it) :
* There should be 2 - 3 OO specifications, that would allow the code to be portable and readable in context of specification.
Macros are fun, but as I'm fighting with basic (I mean plain code, no Visual C++) win32 .again. I'd consider future of flexible and useful OO to stand upon teamwork. Basic idea is that, for example, one who knows the specification in project could form a base for everyone else. (Without need to interrupt their code) It may not sound perfect, but those who would work in a team should gain from it. And those who code alone, they always have the full flexibility and probably will gain far more than they could lose from using it. I'll make a topic about it, when I'll be able to make a class in this style, but in basic words now, it's kind'a like you took, for example, ****** OO framework and forgot the macros. And my dream is to optimize it so that it's for real. Or for just a nicer macro where it's harsh .
Another great option would be RP coding specifications, because, in my experience, cool mods are often made as FS, while absolutely useful for RP. And then again <your RP ideas here>.