masshuu12 / godot-yat Goto Github PK

Describe the solution you'd like
The cn command should be able to search the node tree.
Syntax:

cn ?Player
cn ?Player

In the first case, cn will search the tree starting from root for Player, while in the second case it will start from the currently selected node.

Would be nice to have the name (or something in the description) indicate the project requires C#. This will be helpful for people to know they cannot use this plugin who use "stock" Godot, such as myself.

YAT - Yet Another Terminal (C#)

is what I would suggest for the name.

Describe the solution you'd like
By default, the selected node should be root. Selected node should be visible before prompt.
It should be possible to set the currently selected scene to the one the user is currently looking at.

Describe the solution you'd like
Something like manual in Linux do.

Commands should return two values, command status and data.

Describe the solution you'd like
The performance command should create a window.
The position of the window should be customizable (e.q. top left, bottom right).
The command should be able to display all the most important information such as FPS, RAM usage, and anything else that can be pulled from Godot, and using C#.

• Name of the Display Server
• Architecture
• FPS
• Engine version
• Locale language
• Memory info
• CPU name
• OS version
• Is debug build?
• Info about what player is looking at

More from here:

• Process time
• Physics time
• Object count
• Object resource count
• Object node count
• Orphans
• VRAM usage

https://docs.godotengine.org/en/stable/classes/class_translationserver.html

Describe the solution you'd like
The command should look like this:
Alias cs.

$ changescene <scene>

Describe the solution you'd like
This command is supposed to allow running system commands.

https://docs.godotengine.org/en/stable/classes/class_environment.html

Commands:

• quit – exit the game
• list – list available commands
• restart – restarts the level
• changescene <scene> – change game scene
• view normal/wireframe
• man <command> – display manual for specified command
• pause – un/pause the game
• performance – displays performance information
• whereami – displays name and path of the current scene

Preferences:

• prompt
• toggle prompt
• history limit
• autofocus
• auto scroll
• auto complete
• auto complete on tab
• default width
• default height
• background color
• input color
• error color
• warning color
• window resizable
• window movable
• min width
• min height
• log severity
• input font size
• output font size
• automatically handle mouse mode
• use colors

Signals:

• CloseRequested
• OptionsChanged
• OverlayOpened
• OverlayClosed
• CommandExecuted
• YatReady

Other:

• history
• autocompletion
• rich text
• prompt
• preferences window
• save options to the disk
• load options from the disk
• load options at runtime
• restore defaults
• colored output
• user can contribute to the commands (e.q. add more options)
• #9

Describe the solution you'd like
Commands run on a separate thread should be able to collect user input in real time.
For example, the Ask<T>(string message) method.

Describe the bug
Terminal is not centered by default.

- [ ] context menu for overlay

• context menu for YAT windows
• add options for quick select in terminal's context menu
• limit context menus to specific rect

Describe the bug
The button that launches the terminal writes to the input.

Is your feature request related to a problem? Please describe.
Currently, the settings screen is ugly and has few options for customizing the plugin.

Describe the solution you'd like
The settings screen should be rewritten.

• #13

The new options should be as follows:

General

• Automatically handle mouse mode when entering/leaving YAT.

Windows

• Background color.

Terminal

• History limit.
• Enable/disable autofocus for terminal input.
• Enable/disable autocomplete for terminal.
• Input color.
• Error color.
• Log severity.
• Input font size.
• Output font size.
• Enable/disable colored output.
• Adjust input prompt.
• Enable/disable input prompt.
• Enable/disable output auto scroll.
• Default width & height.

Is your feature request related to a problem? Please describe.
Currently, users are forced to create keybindings manually when setting up the plugin, which creates unnecessary difficulties and does not allow for immediate checking out the plugin.

Describe the solution you'd like
The best solution would be to create default keybindings when the plugin is initialized (assuming they don't exist), and remove them when it is deactivated (if they have not been changed).

Describe the solution you'd like
Rename CommandArguments to CommandData.
Separate arguments & options.
Move not validated data to RawArguments & RawOptions variables.

A new record should look like this:

• Yat
• Terminal
• Command
• Arguments
• Options
• RawData
• CancellationToken

Describe the solution you'd like
Currently, YAT only works in the game, but it would be useful if the terminal could also be run in the editor in a simplified form.

This simplified form would consist of a text box, plus prompts and autocompletion.

It would also be useful to distinguish between commands that are able to run in the editor, and those that are only able to run during the game. This could be solved by creating an attribute that would be given for commands that are able to run in the editor.

Since this would be a very simplified version of the terminal, any output should be displayed in the editor itself.