+
Skip to content

Conversation

rattybag
Copy link

@rattybag rattybag commented Oct 9, 2025

About the pull request

Added new launch targets for running TGUI build / dev (hot reload)

Explain why it's good for the game

  • Improved Developer Experience: TGUI tasks are now directly accessible from VS Code's Run and Debug interface instead of requiring manual terminal commands
  • Consistency: Aligns with existing BYOND launch configurations, providing a unified workflow
  • Convenience: One-click access to common TGUI development tasks without memorizing command paths
  • Better Integration: Leverages VS Code's built-in task management system for better IDE integration
  • Reduced Context Switching: Developers can stay within the VS Code interface instead of switching to external terminals

This streamlines the TGUI development workflow and makes the codebase more accessible to new contributors who may not be familiar with the command-line build tools.

image

🆑 rattybag
code: adding TGUI build and dev launch targets
/:cl:

@cmss13-ci cmss13-ci bot added Code Improvement Make the code longer size/XS Denotes a PR that changes 0-19 lines, ignoring generated files. labels Oct 9, 2025
@rattybag rattybag force-pushed the add-tgui-launch-targets branch from efa5867 to 801547e Compare October 9, 2025 16:18
Comment on lines +133 to +137
"name": "TGUI Build",
"type": "node-terminal",
"request": "launch",
"command": ".\\bin\\tgui-build.cmd",
"cwd": "${workspaceFolder}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TBH I don't really think tgui build is useful. Yes, it will tell you about errors that linters would tell you about, but as far as fixing them you'd want tgui-fix.cmd. But also weird to make this be a debugging launch target when you actually want to make a command (so something in the command palette (ctrl+shift+p)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason why I added this even though it's not that useful is more so for consistency, this approach does allow the debugging of the node code but like I said in the other comment not sure if that's a common or necessary use case. Happy to remove this completely.

Comment on lines +126 to +130
"name": "TGUI Dev Server",
"type": "node-terminal",
"request": "launch",
"command": ".\\bin\\tgui-dev.cmd",
"cwd": "${workspaceFolder}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This works, but its kinda odd to be debugging the dev server. That sure could have uses, but its not the general usecase of using the tgui dev server. Likely better as a command.

Copy link
Author

@rattybag rattybag Oct 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean it does depend on whether we want to be able to debug the node code, which could be useful, but not something I have had to do yet in the codebase. Honestly it's a much of a muchness to me, I'm happy to convert it into a command if that aligns better with the general use cases.

I don't think any change is necessary here then - I wasn't aware that tasks could be ran like this via the command palate

Copy link
Author

@rattybag rattybag Oct 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thinking more about this, I kind of like it better as a launch target, even disregarding the aspect of debugging the tgui server, as it has better vscode integration. It's nice to be able to see the running dev server integrated in VS code's debug panel, and allowing for debugging of the dev server in this way even though it's not a common use case is a plus. It's nice to be able to have the long running processes be visible in this way.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I messed around with this a bit and I couldn't really get the debugging to work properly on the tgui server sadly, I think it's probably not ideal to have a debugging target that doesn't actually debug so I'll close this

@github-project-automation github-project-automation bot moved this from Awaiting Review to Changes Requested in Review Backlog Oct 10, 2025
@rattybag
Copy link
Author

Closing due to existing task being able to be ran through command palate and unable to get debugger to properly attach to tgui server

@rattybag rattybag closed this Oct 10, 2025
@github-project-automation github-project-automation bot moved this from Changes Requested to Closed in Review Backlog Oct 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code Improvement Make the code longer size/XS Denotes a PR that changes 0-19 lines, ignoring generated files.
Projects
Status: Closed
Development

Successfully merging this pull request may close these issues.

2 participants
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载