@Quenty I think the sole reason he doesn’t find it that valuable is because he doesn’t spend time working with other people.
Personally I don’t find many frequent uses for it yet but I do believe it’ll be a cornerstone to legitimate development ‘studios.’
I work with other people – both in ROBLOX and in school. It’s because I work with other people that I understand Google docs editing is a fantasy that won’t actually work. See:
To work on the same thing at the same time, you have to communicate real-time. You can’t concentrate on programming if you’re doing that.
Google Docs was released in 2007, so companies have had plenty of time to hop on board the collaborative, real-time editing for programming, but they haven’t (because of what I posted earlier) – the reason it isn’t being used isn’t because it’s new and nobody knew about it until recently.
…do you have any evidence of companies not using auto updating editors?
Combining voip and the ability to see each other type is actually pretty powerful, I’ve tried this in several projects and it works fine, you don’t have to be there in person with the other guy working on the code to work efficiently.
(I’m not fond of comparing this with business life, not only because I have no clue if they may use script editors which support multi-editing, but I also think a feature like that is extremely important for creative collaboration, sharing and learning which are some of the points that ROBLOX emphasizes upon, and are not necessarily important for most businesses.)
Obviously you’re not going to work in pairs (or more) 100% of the time, but it’s nice to have the option, especially when you’re showing someone else the ropes of your code or assisting them with / reviewing a difficult piece of code. Since everything in cloud edit already provides real-time updates (moving parts, unioning stuff, editing terrain, editing other properties of instances) it seems really strange not to have this kind of mechanism also apply to the script editor, instead of having this lock mechanism.
At the least it would be great if we could get real-time read updates on the code itself and only one person being able to write to the script at a time. But like I also said before, it’s not a high priority feature.
There are countless professional source control products on the market (e.g. Git, Mercurial, Subversion, Fossil, Bazaar, darcs, etc), but I haven’t been able to find a single product designed for collaborative real-time programming or a mention of one currently being developed (if you know of any, please let me know so I’m not in the dark). If a sizable amount of companies were interested in and/or using collaborative real-time programming for professional projects, there would be products available or in development for them. (the “real time code editing” website you’ll find are not suited for real projects – look for products that are actually designed for professional projects)
@buildthomas: Yes, teaching and code review were the niches I mentioned you posted in post #120. I am not discounting collaborative, real-time editing because it doesn’t have any uses. I am clarifying that collaborative, real-time editing cannot be productively used for initially programming (initially as in not including revision) a project. It’s up to ROBLOX whether to implement it or not, but as I mentioned in my original post, if it’s just for review/teaching, it probably won’t happen.
Yes, completely agree with that, similarly to how you probably won’t actually need some functionality that source control provides (e.g. merging) in the early stages of a project, when it’s just a single person working on a certain subset of files at a time and mostly only adding things rather than removing/editing them.
I think code review becomes increasingly important as the size and duration of the project increases, and since we’ve seen a steep increase of the complexity of ROBLOX games over the years it seems like these kind of tools may have a better purpose in the future. We’ll see what they plan to do with this I suppose.
Looks like it was a mistake to use the word “initially”. By initially I meant 100% of the programming minus the revision part. Not just when you were starting out. Yeah, neither are useful for solo programmers because they’re designed for multiple people. Source control, however, is useful when you start working with multiple people, while realtime collaborative editing is not useful (close to “not at all”) for actually programming projects with multiple people (minus revision of course).
Yeah, it’s ultimately ROBLOX’s decision.
Not everybody is the same as you. I’ve done this multiple times without any problems.
I have a friend who I help a lot with scripting and he helps me a lot with building, currently whenever he needs my help he had to copy his script, paste it into Skype and send it to me, I then copy it into studio and send it back to test, if there is an error then he has to copy it into Skype, I have to paste it into studio, etc etc.
As you stated in your post about friend request restrictions, arguments against an idea do not help.
Please do not go against an idea just because you personally will not find it useful.
thelolguy301
Love to hear from ROBLOX staff when the new build of this awesome feature is online !
@thelolguy301 check the first post for instructions on how to get access.
@Velibor sorry for the lack of transparency :(. We are releasing incremental fixes every week, though most fixes aren’t very noticable on their own. In the recent release we added a studio player-list widget showing who is in the session along with the ability to publish immediately (not waiting for the next 5m server publish). In the release Wednesday night we should have:
In the following week’s release we should have a bunch of fixes for terrain undo/redo going out, along with support for changing HttpEnabled/FilteringEnabled/StreamingEnabled and LoadstringEnabled, camera zoom, and a few other things, but work is still early for those other things so I’m not sure if they’ll make it into the release.
To update on the script editor I mentioned a few weeks ago, the biggest problem I’m having is merely replicating the full behavior of the script editor in Lua, alongside with a networking model which locks editing to per line rather than per script.
I really want to encourage you guys at Roblox to consider an official implementation of allowing multiple people to edit Lua code.
How I see it working:
@Maximum_ADHD Thank you for the suggestions wrt to real time interactive code editing (like Cloud9). We currently have two buckets for work on Cloud edit: bugs/features that we think we need to complete before we open the feature to general use (e.g. Undo being more predictable and stable), and the rest of things that improve the experience but have reasonable workarounds in the mean time. At the moment real time interactive code editing is in the second bucket (to be completed after public launch).
If you are okay with using LinkedScripts as a medium, there are some workarounds. You may have noticed for LinkedScripts that it keeps your changes locally until you publish. The way studio does this is by creating files in Roblox/UnpublishedChanges/[universeId]/Script/[scriptName]. If studio finds a file there, it treats it as an unpublished change for that linked script. If you use some source control (e.g. git) with a real time editor (like cloud9) you can do your edits in cloud9, then sync your git repo to that directory, and studio should pick up your changes (you may need to hit the reload button on the Game Explorer).
Can someone please add DrewMagger to the beta list?
I would like to cloud edit with him.
Wrong thread, look at the links in the OP.
I wonder how long until this becomes open to the public. I’m already a beta user so I can cloud edit, but I have an upcoming project that would benefit so much from regular users + me being to edit at the same time.
We are preparing a round of updates in preparation for public access release! However, as part of the preparation we are introducing a disruptive change:
+1 for not forcing this awesome update to be BC only.
Great, I’m glad that this isn’t BC only. However it would be nice to be given an idea when the updates will be completed ready for the public release.