Hi Alex,
I'm using mbed for a group project at university, and have given this account's user info to all the 4 group members. I'm a little concerned that multiple users may log on to the compiler, make changes and have their changes overwritten by a later save.
Yeah, this is not how it should work; every user should have their own account, just like with your email account.
Every mbed comes with a license key to allow creation of an account for that board type (note that is not tied to that specific mbed board), so you should really have at least as many mbed's as users. However, we know this arrangement of multiple users is more common in education settings (and where money is sometimes a little tighter!), so we will consider sponsoring additional accounts for mbeds being used for this sort of thing. See:
So just drop us a line with the details it asks for, and we'll sort some extra accounts out for you.
Re: multiple users working on the same code in realtime; This is certainly something we've talked about :) I think the wave/google docs stuff shows there is potential for it to work, but it is still all a bit R&D (google docs is currently about the most mainstream thing that supports it, wave got killed).
I think our plan is first looking at the more asynchronous distributed version control route, where multiple users can share a repository (and history), and all the workflows that can work on top of that. We've put a simplistic version of that idea on our beta site in the form of library publishing; you can publish code multiple times (version), pull in someone else's code and edit/publish it yourself (fork). We'll see if and how that gets used to help gauge the interest, and that'll help us see what could work.
FYI, our current hypothesis is we'll integrate git in to the workspaces, and support publishing on mbed or github to get the shared workflows.
Simon
I'm using mbed for a group project at university, and have given this account's user info to all the 4 group members.
I'm a little concerned that multiple users may log on to the compiler, make changes and have their changes overwritten by a later save.
eg: user 1 and user 2 log on at same time. user 1 makes changes, saves, logs out. user 2 makes changes, saves, user 1's changes is overwritten.
I think I've seen this suggested before, but what about some way to have multiple users (accounts each?) access the same code? Ideally you'd be able to see who edited which section of code when, and track clashes. (Similar to wiki)
It might be a bit crazy, but what about being able to collaborate on code together in realtime? Perhaps you could use some code from Google Wave protocol?