Now that it’s been just over a week since I released this, if anyone has any feature requests or has been experiencing any bugs, feel free to file an issue here. Make sure to label it accordingly.
Not a bug, but it seems that when clicking a module script in the explorer, it takes almost one full second to actually open up the script (or jump to the script tab if it already is open). Is this the case for everyone?
I don’t know if a full second is normal (it usually takes less than half that for me), but I cannot control how fast they open since Rojo handles file opening. Is your system or network under load?
Yeah, I had it open while testing and it does seem to slow down when under load. Nothing I can really do about that so it’s no big deal
Been using this plugin for the past two days, it’s really great! I have a couple issues that I posted on the GitHub page, namely disabled scripts not being greyed out, and having to manually type in the project name every time I want to connect Rojo UI (even though the Rojo project config file contains a project name field). Are you actively looking at issues on GitHub? Can we contribute to the project?
1 Like
Continuing the discussion from Rojo UI - A Roblox-style explorer & properties view for Visual Studio Code:
Excited to use this!
Yes, I actively check issues, but I’m currently swamped with coursework. I’ll try to get to the features you requested as soon as possible, but feel free to contribute!
1 Like
Hey, I know this is old now, how do I get the Rojo view container to show, I don’t have it, i tried re installation
There should be an R at the bottom of the activity bar to the left. Click that and the explorer & properties panel will show. You can then click the + at the top of the explorer panel to connect to Rojo.
1 Like
This is so useful!!
Thank you for this amazing resource, huge cheers for the work you put up on this!
1 Like
I set Visual Code to default open lua files and set my plugin to 6.0.0r, but it’s still not able to open the scripts.
If the new typed Luau script analysis is opened for third party tooling upon release, this might actually make me switch to a VSC/Rojo workflow again; otherwise, it’s kinda hard to justify the switch for me. Looks really nice though!
This is incredibly helpful. I’ve been using Rojo for quite a while now, I’ve been working with Rojo for well over 4 - 5 months now, and I can already tell you this will be a game changer 
Are the bugs fixed? I woudl like to use this but dont know if its a good idea yet
1 Like
As long as you use the Rojo CLI found here instead of the Rojo extension for VSC, it’ll work fine.
Note: I have not been able to add any create, delete, or rename functionality as the development of Rojo has stagnated recently. I still have a pull request that I sent months ago on the Rojo repository that would allow me to add this functionality myself, but it hasn’t been reviewed yet.
dont you need the rojo extension if I am using vs code with studio?
You’ll need the Rojo plugin found here and my Rojo UI extension found here, as well as the Rojo CLI which I linked to in my previous reply. This extension is NOT compatible with my extension.
You can find info on how to use the Rojo CLI here, but make sure you install 6.0.0rc1. My extension is not compatible with any previous versions of Rojo.
Hey, I am unable to open any of the scripts. How would I go about fixing this?
Thanks!
Also, whenever I try refereshing Rojo UI, I get this error;
See here. If this is your issue, make sure you’re using the Rojo CLI, not the Rojo extension for VSC.
Where is the rest?