Game plan

[gdude2002]

We need to come up with an overall plan for doing this, and maybe chart it out online. For now, here's
what I have in mind:

• Module-based Ultros. You run the module using, for example, python -m Ultros. This makes it installable and would make it feasible to create a setup.py for those that want it.
• A lack of Singletons - I think we still need one singleton, though.
  • I plan on having an instance manager - this would be our singleton.
  • We would then be able to have instances of Ultros in the same process. Obviously, if you're doing this, you won't be running Ultros in the normal way.
    • I have yet to figure out how this would work with stuff like the Web plugin which might need to get a reference to its own instance.
• AsyncIO for our main framework - Plenty of advantages to doing this.
• I feel like sticking with YAML for configs would be a good choice - thoughts?

Obviously this is still early days. We need to plan this out properly. I've committed a basic structure for the time being.

---

Paging doctor @rakiru.

[gdude2002]

Some more notes from IRC discussion today:

• No need for the instance manager, allow it to be used as a lib instead
• Events should have an identifying string on the class itself, instead of one being passed around
  • Use priority constants, via IntEnum
• We will not be supporting Python versions earlier than 3.5

[gdude2002]

• Message events should provide an extra field; optional data that a protocol can provide along with its message string

[gdude2002]

Storage manager:

• Use filename.default for a default configuration if filename doesn't exist (Kasen edit: allows plugins to provide sane defaults for plugins where you don't necessarily have to provide a config - stops you needing to copy-paste filename.example every time the plugin updates - should not be used to automatically create filename)
• Fix filename fuckery
• Have storage manager try to guess format of a file if not given
  • Use get_config_file(...) and get_data_file(...) with an optional format param
• Add get_database(...)
  • Think about supporting peewee via peewee-async