Skip to content

[request] better plugin documentation #1187

@atesin

Description

@atesin

hi... currently in homepage there is a "documentation" link, that leads to a webpage with summarized general help (usage, configuration, plugins, etc.) (note "adding an interpreter" link is disabled)

the "plugin" section lacks proper documentation classes like plugins, interpreters, apis, specs, ide, editor or whatever involved (i.e. global variables, required variables, properties, methods, parameters, return values, etc) (either doxygen, readthedocs. github wiki or whatever)... they just have links to some actual code files, UNCOMMENTED and poorly styled (e.g. no blank lines between functions, etc)

(required variables: i broke the entire ide startup, i don't know what i did wrong, the backtrace was not detailed enough, had to rename my plugin file temporarily to start the ide again)

as a novice self-learner programmer i am, i found the plugin "documentation" as it is now VERY unclear, confusing and hard to understand... i would like to try to write a plugin, but the fact i can't find out how things work and progress despite my efforts is exhausting and frustrating

please improve documentation, at least with comments in code, that way luadoc (doxygen?) can be passed after

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions