1. Is there anything that has stopped you from making a JASS submission in the past? Any reason that made you unwilling to bother to make a submission?
Back when I entered THW and started mapping I knew nothing about programming, except that I wanted to learn it. I did not consider my codes good enough to post them, as they were mostly the results of practice, so I choose to keep them for myself. Even though that's no longer the case, I still refuse to post anything, simply because ain't nobody is gonna tell me how to write my snippets. Especially not someone who's been known for writing spaghetti because it was (assumed to be) a millisecond faster.
2. How strict should the coding standards be? Should we have a strict standard, with all code looking similar in format? Or should we have a more lax one, similar to the spells section? Or something in-between (JPAG)?
Recommendations are okay and are good in general. Some restrictions too, related to the skeleton of the code (for example: options at the top, initializer at the bottom). But telling people how to name their variables/functions/fields/pets is like.... what did you smoke? I want some too!
3. How do you think the forums should be organized? There have been complaints about resources being cluttered e.g. snippets being spread across multiple threads, difficulty finding particular resources, etc. Please tell me how you would feel about the following organizations:
(A) Subforums: Snippets, Systems, Samples
This would allow you to browse systems independently from smaller snippets, which could reduce clutter. Samples would refer to resources that might not be entirely systematic, and that are mostly just demo-maps or are map-specific.
(B) Subforums: Category-based (e.g. AI, Units, Items, Strings, Effects, Execution, etc.)
This would be more similar to the old wc3jass.com organization. Keep in mind that THW has quite a few forums already, but it may help organization.
(C) Subforums: Data Structures
A minimal change. It would move all the data structures/collections to a separate area since they take up a lot of space when trying to browse through resources.
(D) No changes (current system of just one forum for all)
(E) Other (explain)
A+C. Systems (with a DS subforum), Snippets, Samples.
4. How do you feel about the reviewing process? Should we factor in subjective "usefulness"? Should we only accept one type of resource--e.g. a unit indexer, multiboard system, etc. (when they are very, very similar) or should we not use that as a factor?
Reviewing process? Did we really have one? I thought it was Nes going into every submission that he did not make and bashing the OP and telling them that its inferior to his one, until they give up. This includes the lab too, of course (you don't need to go far to find examples).
5. How do you feel about vanilla JASS resource submissions? Should they be allowed to be approved (e.g. "GUI-friendly" resources), or should those just go in the spells section?
I personally wouldn't use a vanilla JASS resource, don't want my "0 variable editor variables" ruined
But it'd be fine, a JASS resource can be just as useful as a vJASS one.
6. Any extra features for the JASS forum/JASS-related? e.g. wurst tags (probably will be an extension of the highlight tags). I can't think of much, but I'm sure you guys are filled with ideas, and I'd love to hear them.
-
7. How do you feel about multiple resources in one thread, assuming that they are related? For example, similar data structures, or a projectile system with a dummy system, or a multiboard system with some extension system.
Well, I really wanted to be sarcastic here, but meh, let's be serious for once. I think things that belong together should be posted together. There's no reason to put extensions/subsystems of a system into a different thread. Or at least I don't see one.
8. How do you feel about some of the not-so-efficient vJASS features, such as interfaces, inheritance, etc.? This would also include using the regular struct allocator vs. using extends array + alloc alternative. The underlying code is not so great, but it allows cool things API-wise.
Regular struct allocator is okay. Interfaces are okay too, to a certain extent (the complaint has always been that it copies the functions, but it's perfectly fine for shorter ones, plus what if the user doesn't care?). Inheritence is meh, haven't checked how it's implemented, so IDK.
-----------------
Those are my thoughts. Feel free to agree with them or curse/negrep/incinerate me for posting it, I couldn't care less. I know that most people who I respect on this site are at their right mind and agree with me, so it's cool.
