Todo Compilation

Todo Compilation

What’s This?!

This page collects all todo blocks throughout osb-learn. They’re here as a way to highlight the particular portions of the documents that either need more content, an image, or just something that, well, needs to be done!

Todo blocks are split in three different priorities, seen by the block’s lefthand border color.

  • Low: Green. Not a big deal. Would be nice to have done.
  • Medium: Yellow. For this to be done would help the page a great deal.
  • High: Red. Basically, this page or portion is virtually blank. It needs content.

Unfortunately, there isn’t any finer organization at this point unless I extend Sphinx’s todo extension. For now, that in itself is a low priority. (Ha!)

How Can I Contribute?!

If you’d like to make edits to the documents directly and propose changes that way, then you should take a look at contributing through Github. Github is a great way in collaborating online coding projects and efforts such as these!

Our Discord server also has a channel to propose and make changes there too.

You will be credited as a contributor for the section if you do help in the effort of finishing one of these Todo blocks! :)

Todos Todos!

Last updated 10/06/17.

Todo

Correct for list length -> count

(The original entry is located in “programming/arrays_and_lists”, line 427.)

Todo

0x0 is hex lol

(The original entry is located in “programming/enumeration”, line 241.)

Todo

Consider different number (i.e. the same number for both base-10, base-2)

(The original entry is located in “programming/enumeration”, line 288.)

Todo

Write about sprite creation optimization and hazards.

(The original entry is located in “programming/loops”, line 150.)

Todo

Spoilers on the DLC: There is none yet. It probably can be simplified into two primary pages though:

  • The Interface. (Similar to storybrew’s interface page) Be sure to include screenshots and things like that though!
  • Tips and Efficiency related things for the design editor.

(The original entry is located in “storyboarding/design_editor/intro”, line 11.)

Todo

Proofread and check for any formatting issues. Fill in remaining blank definitions. Improve existing ones.

(The original entry is located in “storyboarding/glossary”, line 10.)

Todo

I want to rewrite this, as this is simply content from the old Learn page.

(The original entry is located in “storyboarding/introduction/intro”, line 5.)

Todo

The SGL section doesn’t need to be too elaborate. I’d rather push for storybrew due to its strength and the fact it’s a spiritual successor. However, I think a general page about the syntax would be helpful. In some senses, it can be possible to just redirect or rewrite most of the storybrew basic fundamentals into osu!SGL’s context.

(The original entry is located in “storyboarding/osu_sgl/intro”, line 10.)

Todo

All the command sections are in a heavy work-in-progress. They’ll need the following:

  • A code-block. This can be grabbed from the cheatsheet.
  • A visual example demonstrating the command.
  • Remarks. (e.g. A sprite’s opacity is from 0 to 1)

(The original entry is located in “storyboarding/scripting/basic_commands”, line 9.)

Todo

All the routes need to be finished writing for, probably. And also do cross-referencing links. Particularly, “storybrew” and “Other Pursuits” are blank. Also consider how programming fundamentals should be covered throughout the documentation.

(The original entry is located in “storyboarding/scripting/branching_paths”, line 75.)

Todo

This is a big venture, but this script needs to be walked through bits by bits. This requires:

  • Working the commands step by step.
  • Drawing sprites as it goes.
  • And the finale code-block as we see here.

Also probably offer a blank .osz to test this as well.

(The original entry is located in “storyboarding/scripting/case_study”, line 9.)

Todo

Storyboard loops

(The original entry is located in “storyboarding/scripting/compound_commands”, line 12.)

Todo

Add an example .osz file of a map that utilises this effect.

(The original entry is located in “storyboarding/scripting/compound_commands”, line 399.)

Todo

Mechanic explanation, use-case: workaround for triggering on negations (player missed a note), hopefully a cool example that takes advantage of the very specifics of the mechanic!

(The original entry is located in “storyboarding/scripting/compound_commands”, line 406.)

Todo

Command Locking, Fade Behaviour

(The original entry is located in “storyboarding/scripting/compound_commands”, line 416.)

Todo

This might go into the Trigger Groups part in detail because it is most relevant there. A quick summary would make sense though.

(The original entry is located in “storyboarding/scripting/compound_commands”, line 422.)

Todo

Write a small summarising list to give an overview on which gameobjects triggers are working and maybe more importantly on which ones not.

(The original entry is located in “storyboarding/scripting/compound_commands”, line 428.)

Todo

It would be nice if we can set up a Pygments language for OSB scripting.

(The original entry is located in “storyboarding/scripting/doubletime”, line 9.)

Todo

Add a picture demonstrating the nine origin points of an image.

(The original entry is located in “storyboarding/scripting/objects_and_layers”, line 76.)

Todo

Summarize all the sections mentioned in Objects & Layers to this collective point.

(The original entry is located in “storyboarding/scripting/objects_and_layers”, line 148.)

Todo

Similar to how sprites work, write about how animations work and provide an example.

(The original entry is located in “storyboarding/scripting/objects_and_layers”, line 156.)

Prev: Contributing to osb-learn || Next: Template
Last update: 01/18/2018 3:46 a.m. (GMT)

Search