Task Template

Started by Blizzard, March 12, 2011, 09:18:24 pm

Previous topic - Next topic

Blizzard

March 12, 2011, 09:18:24 pm Last Edit: July 06, 2012, 01:59:24 pm by Blizzard
First thing a task needs is obviously a title. This is the topic title.

Example: RMXP Hidden Classes

Titles should include a tag to mark what part of the project it is for and what special kind of task it is.

Project Tags:

  • [ARCed] ARC Editor

  • [ARCed][LE] ARC Editor Legacy Edition

  • [RGSS] Zer0 RGSS engine, LE only

  • [Zer0] Zer0 Division engine, non-LE only



Fixes Tags:

  • [Glitch] bugs of graphical nature that do not disrupt the normal usage flow

  • [Bug] general bug

  • [Lock] critical bug that leads to a hardlock

  • [Crash] critical bug that leads to a crash/freeze



Status Tags:

  • [Finished] finished task

  • [Abandoned] will not be finished

  • [On Hold] cannot be finished now for some reason, will be finished later






If there is a problem with a finished task (i.e. a few bugs in a code), the task won't be opened again. Instead a new task will be made. Additionally to this, each task needs to have following template in order to ensure that everything can be overviewed easily.

Spoiler: ShowHide
[center][size=30pt][b]<TASK NAME> (shouldn't differ too much from the topic title)[/b][/size][/center]

[hr]
[size=16pt][b]Description[/b][/size]

<Description> Here goes a detailed description of what needs to be done.

[hr]
[size=16pt][b]Priority[/b][/size]

<Priority> Lowest, Low, Normal, High or Critical.

[hr]
[size=16pt][b]Prerequisites[/b][/size]

<Prerequisites> Mention any classes or files that need to be completed before this task can actually be started.

[hr]
[size=16pt][b]Assigned[/b][/size]

All members currently assigned for this task.

[hr]
[size=16pt][b]Everything else[/b][/size]

<Everything else> Everything that doesn't belong anywhere else.



And here is how this could look like:

Spoiler: ShowHide
RMXP Hidden Classes




Description

The hidden classes in RMXP need to be outlined into C++ equivalents. Don't worry about all the implementation, but for the most part just make an .h and .cpp file of the class that emulates RMXP's methods and arguments.

Here are the classes that need to be done:

  • Color

  • Font

  • Rect

  • RGSSError

  • Table

  • Tone

  • Audio

  • Bitmap

  • Graphics

  • Input

  • Plane

  • Sprite

  • Tilemap

  • Viewport

  • Window





Priority

Normal.



Prerequisites

None.



Assigned

Captain Obvious.
Chuck Norris.
Your mom.



Everything else

Nothing.


Who will get which task? Simple rule: First come, first served. In case a member doesn't finish a task, that member will be removed from the task so somebody else can take care of it. If another person already posted to be assigned, but the task was already assigned, then the second person will get the task after the first person has been removed. Also, it is possible in some cases that more people are assigned to one task.

Finished tasks will be archived in the other subsection of this section for easier searching.
Check out Daygames and our games:

King of Booze 2      King of Booze: Never Ever
Drinking Game for Android      Never have I ever for Android
Drinking Game for iOS      Never have I ever for iOS


Quote from: winkioI do not speak to bricks, either as individuals or in wall form.

Quote from: Barney StinsonWhen I get sad, I stop being sad and be awesome instead. True story.

ForeverZer0

You so sexy.

I updated the post to reflect our current project a little more. I took the liberty of removing a couple of headers since the dev team is small, and I think we all know what tasks require what, etc. 
I am done scripting for RMXP. I will likely not offer support for even my own scripts anymore, but feel free to ask on the forum, there are plenty of other talented scripters that can help you.

Blizzard

Sure thing. I copy pasted it from the Remexos threads after all.
Check out Daygames and our games:

King of Booze 2      King of Booze: Never Ever
Drinking Game for Android      Never have I ever for Android
Drinking Game for iOS      Never have I ever for iOS


Quote from: winkioI do not speak to bricks, either as individuals or in wall form.

Quote from: Barney StinsonWhen I get sad, I stop being sad and be awesome instead. True story.

Ryex

I updated the post is include that the title should be tagged so that we know what part of the project the task is for, if it's for the editor it should be marked [ARCed] and if is for the RGSS lib it should be marked [RGSS]ect.
I feel that this keeps the task list easier to over view.
I no longer keep up with posts in the forum very well. If you have a question or comment, about my work, or in general I welcome PM's. if you make a post in one of my threads and I don't reply with in a day or two feel free to PM me and point it out to me.<br /><br />DropBox, the best free file syncing service there is.<br />

Blizzard

Check out Daygames and our games:

King of Booze 2      King of Booze: Never Ever
Drinking Game for Android      Never have I ever for Android
Drinking Game for iOS      Never have I ever for iOS


Quote from: winkioI do not speak to bricks, either as individuals or in wall form.

Quote from: Barney StinsonWhen I get sad, I stop being sad and be awesome instead. True story.

Blizzard

July 06, 2012, 01:50:35 pm #5 Last Edit: July 06, 2012, 01:52:40 pm by Blizzard
*bump*

While we're alpha testing the engine and the editor, add [Glitch] (bugs of graphical nature that do not disrupt the normal usage flow), [Bug](general bugs), [Crash] (critical bugs that lead to crashes) and [Lock] (critical bugs that lead to hardlocks) for the title and explain how to reproduce it in the description as well as the description of the bug/glitch/crash itself. This convention will stay even after the testing is over. I'll add this to the first post.
Check out Daygames and our games:

King of Booze 2      King of Booze: Never Ever
Drinking Game for Android      Never have I ever for Android
Drinking Game for iOS      Never have I ever for iOS


Quote from: winkioI do not speak to bricks, either as individuals or in wall form.

Quote from: Barney StinsonWhen I get sad, I stop being sad and be awesome instead. True story.