sully8391 Posted August 14, 2022 Share Posted August 14, 2022 Hi all, I've been using the GitHub desktop app, and I'm wondering how best to utilize this with some plugins that I'm developing. I would like to avoid copying files from the user library folder into a separate folder just for commits, but with both plugin scripts and resource files, I can't target a single folder. For some of the scripts, I could just set the environment path to the GitHub folder, but that doesn't cover my resource files, or the .vsm's and .vso's Curious if anyone else is using the GitHub client, and what is your workflow like? Quote Link to comment
twk Posted August 15, 2022 Share Posted August 15, 2022 I use Pycharm to develop, which as VCS integration either using Githubg/Bitbucket/etc. I dont use resource files at the moment (I assume you're meaning the vwr pacakges?) Folder structure setup is as below: - Workgroup Folder (Setup/pointed to in the Vectorworks Preferences). Eg (C:\VW Preferences\2022) - Setting this in the Vectorworks Preferences causes vectorworks to setup the required folder structure (that vectorworks uses) for use as a Workgroup folders. Which adds folders such as: Libraries, Plug-ins, Settings, Workspaces, etc. I keep all my plugins (.vso, .vsm, etc) files in the Plug-ins folder, together with my scripts for them. - The plugin development project folder is in the Plug-ins folder, which is what the PyCharm project points to. - This way Pycharm manages the version control for both the script modules and the vectorworks custom plugin files (vso, vsm, vst) Quote Link to comment
sully8391 Posted August 15, 2022 Author Share Posted August 15, 2022 By resource files, I just mean VW files in the user library that I use to import symbols, worksheets and record formats. I had thought about using a work group, but when importing resources, for example, I need to use vs.GetFolderPath(-13) to get to my user libraries. Not only is importing from a workgroup a more arduous task, but it will break portability to any other machine, as it's all meant to be installed in the user folder. Quote Link to comment
JBenghiat Posted August 15, 2022 Share Posted August 15, 2022 VW will recognize aliases/shortcuts for both plug-in files and resource libraries. Keep the originals in your development folder and link into your user folder. Also, include files can reside anywhere on your system, which is where git really becomes useful. Quote Link to comment
sully8391 Posted August 15, 2022 Author Share Posted August 15, 2022 @JBenghiat funny, I had actually wondered if I could just drop a shortcut in there; don't know why I didn't try it. Thanks! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.