Jump to content

Search the Community

Showing results for tags 'fork'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Roadmap
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
    • Forum Feedback
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Previsualization
    • Braceworks
    • ConnectCAD
    • Energos
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • AI Visualizer
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
    • Data Tags
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Calendars

  • In-Person Training - US
  • In-Person Training - UK
  • Coffee Breaks
  • Essentials Seminars
  • Webinars
  • Community Groups

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 1 result

  1. Software engineers do a much better job of tracking versions than architects. I've long thought that Vectorworks could benefit from a system of Forking/Branching, not only as a means of enabling better collaboration but also tracking changes over time. This is particularly important when projects are being built and changes are being requested - it can be very valuable to keep track of these changes. I was impressed by Onshape's implementation of something like this where versions of a file can selectively be merged to the main file, and the main file also compared with previous versions visually to compare the changes. I think this is a viable alternative to the current project sharing system, which for our office at least, is the source of a lot of frustration and time wasting. Some clear benefits I see are: Better file integrity: You remove many people trying to commit to a project file at once which for us leads to problems. The merging is controlled by a project leader at specific points, and merging could take place collaboratively as a team whilst reviewing them in a meeting for example, not all at once at 5pm on a Friday Better approval process: Files are only merged by project leaders after reviewing the potential change and its impact. Information is "pulled in" by a project leader with an oversight of the whole project rather than "pushed in" by whoever made the change who may only be working on a small aspect of the project. Clear overview of project history: See who made changes (branched file), when and why. Project Sharing has project history, but there is too much noise and not clear enough data. The branched file is a clear mark of "we were asked to make this change by this person" not "Chris checked out this window object". I wouldn't be against these types of files being hosted exclusively on Vectorworks Cloud Services to avoid the current "Project Sharing works well on Dropbox, but not Google Drive" etc. Would be interested to hear other's thoughts or if they have other software that tracks these kinds of things for them.
×
×
  • Create New...