Hi Niklas,

Looks like an interesting one. We designed Gluon for maximum simplicity, so we purposely kept branches out. But... yes, what you describe is exactly that: branches. They could be somehow hidden for the user but...

Tell us more about why you find it useful. I mean, why they feel like checkin if they don't want to send it to the cloud?

Hi Brian,

It is like you can read our mind :)

We have been looking into the Language Server Protocol (LPS) for a few weeks now, and we already plan to integrate it into Semantic Merge. Related to this, we are integrating Semantic Merge into Plastic, and this change will be released very soon. Integration of the LSP into Semantic Merge will follow at some future date.

On paper, the LSP is a neat idea. Write a Language Server (LS) once, give capabilities for said languages to multiple editors at the same time. However, we encountered obstacles in every Language Server we looked into.

Because the same team that implements the LS usually also implements the IDE / editor extension, they feel free to either break the protocol whenever is convenient, or have the server to behave in undocumented / unexpected ways.

This means that for every LS implementation out there we must write a custom wrapper to deal with these quirks. However, once that is completed, it will be easy to translate the LSP format into something Semantic is able to understand and expand the set of languages supported by Semantic Merge.

So, hopefully, Plastic (and gmaster!) will extend their semantic capabilities really soon thanks to the LSP. Differences, merging, and even difference editing with real time semantic outline...

As you can understand, this is something that will require some effort and lots of testing, so while it is definitely in our roadmap, right now we are prioritizing other projects that will for sure improve your experience as well.

In any case, thank you for your kind suggestion. We'll keep you posted on this!

Sergio/Gwyn

Yes, you are SOOOOOOOOOOO right.

No excuses.

We are swamped with a few other topics, but definitely this one is a must.

Sorry to make you wait.

pablo

Hi Niklas,

You mean the "sync view", correct? You said the "merge view" and I can't understand the situation then.

Thanks,

pablo

Sure, good idea. Not that people use locking that much on the developer gui... but... no excuse.

pablo

Ok, thanks for the remark. It is definitely helpful.

Probably you want to unify votes here

https://plasticscm.uservoice.com/forums/15467-general/suggestions/14721126-partial-file-checkin

Just adding a link to https://plasticscm.uservoice.com/forums/15467-general/suggestions/16755301-allow-manual-selection-of-which-hunks-of-each-file which is a duplicate of this.

Reviewing

Hey guys,

Sure, not hard to do and makes lot of sense.

We'll keep an eye on it, but please ping us if we don't respond in a reasonable time.

pablo

I'm going to double check this. Please do not submit as anonymous :'(

I can only say... you are right.

We are not taking care of advanced users.

I know I'm asking you to do our job but, would you mind sharing a full list of things you miss?

pablo

Yep, good point. We'll do it.

Interesting. You could "easily" do that with a trigger. Would that be good for you? We can write one for you :)

Thanks Mikko,

How would you imagine that?? Per view? Some global screen with all shortcuts together??

Not really sure how we can do this.

I mean: repo can be on a central server, workspace on a distant machine. There is no way for the server to trigger the renames, the machine can be down...

We could store an ID and try to figure out if the same ID still exists...

Anyway, how often do you rename repos? Is this really something happening frequently. I just ask because, well, I think we kept the same repo names for like 13+ years :-)

pablo

Hey, thanks for the suggestion. I don't think it is the first time we receive something like this.

Would a REST API that we invoke from Plastic to any external "auth provider" good enough?

Hi Jani,

This is very "git-like", isn't it?

I understand you mean: if you pull the branch you are working on, then immediately do update just after. Do not update if that's not the active branch.

Well, it makes sense to me. I'll check with the team.

Can you please tell me more about this?

I'm sorry but I don't know what you exactly mean by side-scrolling. I guess being able to move the diagram with the wheel or something, but I'm not sure.

Hi David,

Really interesting idea.

But it must be the proxy the one actively downloading once being notified somehow by the server, right?? I mean, normally the central server won't reach the proxy because of network topology in my experience.

pablo

Hi Andrew,

yes, it makes a lot of sense.

We didn't do it so far because we'll need some javascript thing to restart the thing and the server is the one hosting the webadmin console ... but nothing that tons of other servers do... we'll think on it.

pablo

Uhm... ok...

pablo