meiszwflz / autongui Goto Github PK

There needs to be a method for users to customize the dimension of their robot. This should be implemented as a configuration option with a scope of resource. For now, we'll ignore shape-shifting robots that can change their dimensions.

Currently, the ASTTranslator only tries to find actions in the auton function, ignoring any actions hidden away in calls to other functions

These function calls should also be searched to allow for modularization of code. For example:

void turnTowardGoal() {
  auton::turnTo(64,64,1500);
}
void autons::shootIntoGoal() {
  turnTowardGoal(); // look into this function and find turnTo()
  auton::shoot();
}

This may be difficult, especially if the "nested" function is defined in another file.

Currently, to recognize auton functions the autons namespace is used, and the same for actions where the auton namespace is used. This should be configurable by the user.

This should be implemented as a configuration option with a scope of resource. This should also be able to handle no namespace.

Users will likely want to add their own custom actions.

This is not difficult to implement, until you get to the webview at which point things fall apart. If you're interesting in pursuing this, please discuss how you want to do it with me, either in this issue or by messaging me on discord.

This is very open ended, good luck..

The webview does not currently understand pure pursuit actions. The webview should be augmented with this ability.

To do this hopefully some modifications can be made to path.jerryio. If this is the route that is taken, jerryio should be a dependency of some sort. This will likely require coordination with the developers of jerryio.

This is a very open ended issue as I'm not sure how to go about it.

Currently, the webview receives actions but only understands actions that modify the position of the robot. Other actions, such as shoot, intake, and stopIntake, should also be understood by the webview.

To do this robot's image should be modified in some way to indicate the current state, or be shown thrown a game object.

For now only do intake, shoot, and stopIntake as these are actions relevant to the current game.

The user should be able to customize the field that is displayed in the webview.

They should be able to select both from a list of fields included in the extensions (eg. Spin Up, Over Under, Over Under Skills, etc) and their own image on their machine.

This should be implemented as a configuration option with a scope of resource.

The current actions are a bit outdated.

In the future, this will not be required as there will be action sets that are created for each game, using custom actions.

This extension relies on vscode-clangd's AST api, which doesn't exist yet...

Information

The stuff that needs to be done to complete this is outlined here and the progress made on this is currently in this fork.

Difficulty - Easy

Required Knowledge:

• Zero understanding of this project
• Limited understanding of clangd
• Decent understanding of typescript (libraries and DefinitelyTyped)

Completion

1. clangd/vscode-clangd#501 (comment)

Note: You don't have to do the GitHub Pages, guides, or example, but please point towards the usage in clangd as an example

2. Release new version with exposed AST of Clangd.
3. Replace RawASTNode and ClangdAPI with imported types from new @types/vscode-clangd-api package.
4. Modify CONTRIBUTING.md to indicate that Clangd can be installed from the VSCode Marketplace, instead of the .vsix method.

Help

If you would like to help, please make a comment indicating so, and you will be assigned to this task.