- Joined
- Jul 10, 2007
- Messages
- 6,306
Categorization
Libraries
Utilities
Systems
Frameworks
I'll take a page out of MFN's documentation to clarify ^_^. I'm only using this model because I think it is a good model, that way there are no categories like spells with systems jumbled up in them and so on : o.
Overview
Description-
Designers are those who design libraries, utilities, systems, and frameworks using MFN.
MFN adheres to a strict set of rules when compared to standard JASS.
Types
Library-
Utility-
System-
Framework-
Submission
I propose a private invisible forum that only moderators of the overall thingie can even see. To post in that forum, you'd be using a forum like this
Type-
Title-
Version-
Code- (a jass code box)
Documentation- (a box for docs on it)
Icon
Attached Map(s) (the container map and or demo map)
Attached Docs
And when they are approved this information is viewed
Type, Title, Version, Icon, Attached Map, Attached Docs
The code and documentation boxes would only be used so moderators would have an easier time approving or not approving of systems
From here, the specific submission would be viewable in a new category for the account under pending submissions as something of a thread.
This same model could be used for other types of submissions as well ^_^, but I do believe it will keep everything more organized.
Also, there should be a standard form for moderators to use when giving feedback, like so
Follows JASS/vJASS conventions or Framework conventions that it was designed for
Missing Features that it should include
Leaks
Bugs
etc etc ^_^. This way, no matter who moderates, the type of feedback will be standard =).
Libraries
Utilities
Systems
Frameworks
I'll take a page out of MFN's documentation to clarify ^_^. I'm only using this model because I think it is a good model, that way there are no categories like spells with systems jumbled up in them and so on : o.
Overview
Description-
Designers are those who design libraries, utilities, systems, and frameworks using MFN.
MFN adheres to a strict set of rules when compared to standard JASS.
Types
Library-
A library is a compendium of defined data using functions, methods, objects, and or variables from standard JASS, vJASS, utilities, and or systems.
Libraries do not define any of their own data
Pre-defined string colors
Pre-defined objects from a system or utility
Set of spells or even one spell
Utility-
A utility is a compendium of defined data that might use functions, methods, objects, and or variables from standard JASS, vJASS, libraries, utilities, systems, and or frameworks.
Utilities have no internal memory (globals for managing data related to objects, variables, functinos, and methods within the utility).
Utilities define their own data and use the data of other things
For infinite memory expansion, all data pertaining to a utility can be contained within a textmacro so that various instances of it can be created. Utilities created in this fashion are not pre-defined.
A set of functions
A set of objects
System-
A systems is a compendium of defined data that might use functions, methods, objects, and or variables from standard JASS, vJASS, libraries, utilities, systems, and or frameworks.
Systems have internal memory (globals for managing data related to objects, variables, functinos, and methods within the systems).
Systems define their own data and use the data of other things
Systems do not manage external memory unless they must have a reference to that memory. While it might manage what is attached to its own objects, it will not manage what the objects its objects are attached to.
For infinite memory expansion, all data pertaining to a system and all functions that manipulate that data can be contained within a textmacro so that various instances of it can be created. Systems created in this fashion are not pre-defined.
A caster system
A spawning system
Framework-
A framework is a compendium of defined data that might use functions, methods, objects, and or variables from standard JASS, vJASS, libraries, utilities, systems, and or frameworks.
Frameworks have internal memory (globals for managing data related to objects, variables, functinos, and methods within the systems) and external memory (globals for managing data related to the map it is inside of).
Frameworks define their own data and use the data of other things
Frameworks do manage external memory and can change aspects of how a map runs.
MFN controls basic map settings, map start up areas, conventions, etc
FTMN (footmen wars framework) has stuff like startGame. It runs most of the map.
Submission
I propose a private invisible forum that only moderators of the overall thingie can even see. To post in that forum, you'd be using a forum like this
Type-
Title-
Version-
Code- (a jass code box)
Documentation- (a box for docs on it)
Icon
Attached Map(s) (the container map and or demo map)
Attached Docs
And when they are approved this information is viewed
Type, Title, Version, Icon, Attached Map, Attached Docs
The code and documentation boxes would only be used so moderators would have an easier time approving or not approving of systems
From here, the specific submission would be viewable in a new category for the account under pending submissions as something of a thread.
This same model could be used for other types of submissions as well ^_^, but I do believe it will keep everything more organized.
Also, there should be a standard form for moderators to use when giving feedback, like so
Follows JASS/vJASS conventions or Framework conventions that it was designed for
Missing Features that it should include
Leaks
Bugs
etc etc ^_^. This way, no matter who moderates, the type of feedback will be standard =).