A lot of overlap in technology and engineering. Don’t know that we have a timeline we want to commit too yet, but Very Soon
2 Likes
Sure thing - here’s one taken while scrolling:
microprofile-20241210-232539.html (3.8 MB)
And one taken doing nothing, in case that’s useful:
microprofile-20241210-233420.html (776.7 KB)
2 Likes
Cool, I have some ideas on how we can optimize the bottlenecks here.
4 Likes
This is a good point! Next year we plan to include more explorer updates including a revamped explorer search. Responsive/dynamic suggestions are certainly part of our plans…
4 Likes
Nope
Dang, it’s c:Mod that’ll autofill, but not c:model. Will file this, thanks!
3 Likes
List of issues I encountered earlier today with this enabled c.c. @beastoftheeast0
Bugs/Problems
-
ObjectValue&Instanceproperties can’t be set with the beta enabled -
Sometimes expanding/collapsing entries will cause the scroll position to jump very far upwards, which is very disorienting and doesn’t ever occur outside of the beta
-
Dragging an instance and moving the cursor towards the bottom of the explorer window does not scroll the window, making it impossible to reparent instances between services
-
(Possibly related to a clipboard issue with my build of wine, but wanted to mention in case other users have experienced this on Windows) I often encountered an issue where copying an instance will show me the Paste Into option, but then trying to paste will not function until I copy a different instance and then re-copy the original and repeat this a few times
Undesirable Behaviour Changes
- The entries now appear too large to be usable. Previously I could view a large number of instances, now I can only view a small handful in the same amount of space.
- Right clicking to insert objects is inconvenient, and I have strong muscle memory for doing this. The plus on the side (which I normally disable) requires a lot more horizontal mouse movement which doesn’t feel as comfortable for me.
6 Likes
This is fixed in the latest deployment. Please restart Explorer until you see “v0.7” in the title bar. We’re trying out a new experimental way to deploy Lua changes, and it’s a bit scared of updating sometimes.
I think this is also fixed in 0.7.
3 Likes
next gen explorer so good it has a mind of it’s own refusing to update
We even have rough ideas on how to improve this too, since we want to use this style of rapid deployment more and more to get you bug fixes and features across all of Studio much faster than you get them now.
3 Likes
I am frightened of this change because of how often Roblox breaks things; now y’all are gonna do Luau deployments without updating so it’s not even possible to isolate them… Scary.
2 Likes
Me too! Lot of work to be done on making it both resilient to introduced bugs, ability to create good bug reports, etc etc, but the user and engineering implications are really exciting.
If it helps ease your mind, the Explorer codebase has 400+ tests and 96% testing coverage, and all changes must go through that rigorous pipeline.
6 Likes
That’s great for the Explorer… I’m a lot more frightened of the other code that’s gonna get deployed using this. Other teams are not as careful.
3 Likes
So a live cloud-based Explorer system that downloads its dependencies every time you start studio? Neat.
1 Like
Any code that gets deployed through this new system must meet a very similar bar of testing, and Explorer is going to be the gold standard for how to do it 
8 Likes
I trust you dogekidd2012 but don’t let me down or I’ll know who to send a frowny face in DMs
17 Likes
Very cool. Very demure. Good job to all developers working behind this.
4 Likes
I assume that means wait till next year before hitting you with bold suggestions to improve general workflow then? 
1 Like
No need to delay on suggestions, it’ll just be a minute before we get on them.
2 Likes