Jump to content

Gluon and Plastic Workspaces Formats


ThatGuy

Recommended Posts

I was hoping to run plastic and gluon in a mixed environment.  Where users would use gluon for day to day needs and then use plastic when extra functionality was needed.  But the two applications use different workspace formats.  This makes it less seamless to switch between one and the other.  Is using a common workspace format something that is in the roadmap?

Link to comment
Share on other sites

  • 1 year later...

Hello @NC3D,

I'm afraid we don't have that specific document but by reading the official Gluon site you can understand for what it was made: https://www.plasticscm.com/gluon.html

Let me summarize the main differences:

Workspace configuration:

Update operation:

  • Gluon allows you to have the workspace partially updated, some files might load the head revision, some other might now. The update operation can happen for a single file.
  • The update operation for the Plastic SCM GUI will target an entire changeset specification, it's not allowed to have a mixed configuration.

Merge:

Branching:

  • Gluon support the "Switch to branch" operation.
  • Plastic SCM supports Switching and creating new branches.

At the end of the day Gluon has been designed for an Artist point of view workflow meanwhile Plastic SCM is used by developers and it covers much more complex scenarios.

If you need more details just let me know it.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...