Skip to content

API index grouping & type definition interfaces#3

Description

@THDigi

For example all block interfaces (they're quite scattered), all entity component interfaces (would likely need to check what class implements it), all extension classes, then "Everything else" for the unsorted 馃槃 maybe "Data" group for all structs, enums, vragemath namespace stuff and things implementing collection interfaces.

Also, the https://malforge.github.io/spaceengineers/pbapi/Type-Definition-Listing.html could link to the closest available interface (including IMyCubeBlock to make it clear that it's a non-terminal one) - for example survival kit does not show anything, it should be showing IMyAssembler as that's the closest one and they can already see in the TypeId that it's its own special type, but they would have to use a decompiler and have to know that MyObjectBuilder_SurvivalKit makes a MySurvivalKit and then see that it extends an assembler. The jump from TypeId to class or interface is not always obvious either, e.g. MyObjectBuilder_OxygenGenerator goes to MyGasGenerator and IMyGasGenerator.

All these to better direct people to something like a list of blocks, currently you'd have to just tell them what the interface is because teaching them to discover it is very complicated 馃憖

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions