Move HISE project to another computer

[David Healey]

@dannytaurus said in Move HISE project to another computer:

So, the .hip files are completely useless? They must be if the general advice is to exclude them from git.

They're good for little self contained test patches. They should be excluded from git because they are not human readable so git can't keep track of changes to them.

[dannytaurus]

@David-Healey Git should be the single source of truth for your project.

If you're using .hips for test patches they should really be in git, unless you discard them after use.

Doesn't matter that they're not human-readable. Git tracks binary files just fine - images, fonts, audio loops, etc. The diffs don't make a lot of sense but they don't have to for binaries.

If your laptop blows up and you've excluded .hips then they're gone forever.

That goes for your Autosave files too.

I think I'm still trying to wrap my head around the project structure when it comes to git.

Trying to commit a bunch of work, especially different tasks, is really hard to do cleanly because all of the different work mostly likely ends up mixed together in the module tree and UI XMLs.

I can see a lot of folks doing commits like "Loads of stuff"

[David Healey]

@dannytaurus said in Move HISE project to another computer:

If your laptop blows up and you've excluded .hips then they're gone forever.

I have a separate backup, git is for version control, not for backup.

I avoid binary files in git as much as possible. Probably the exception is images and impulse responses.

@dannytaurus said in Move HISE project to another computer:

Trying to commit a bunch of work, especially different tasks, is really hard to do cleanly because all of the different work mostly likely ends up mixed together in the module tree and UI XMLs.

Use a separate branch for each task you're working on, then merge them back to the main branch.

[dannytaurus]

@David-Healey said in Move HISE project to another computer:

I have a separate backup

Yes, same here. But I know not everyone does.

Use a separate branch for each task you're working on, then merge them back to the main branch.

It's the hopping between the terminal/code editor and HISE that usually breaks this flow for me. I'm still trying to decide whether I want to edit scripts in HISE, or to do it all in a code editor, then keep hopping over to HISE to F5.

I wonder if there's any future possibility of using git within HISE, like through a full terminal in HISE. That would be dreamy.

[David Healey]

@dannytaurus said in Move HISE project to another computer:

I wonder if there's any future possibility of using git within HISE, like through a full terminal in HISE. That would be dreamy.

Oh turning the Console into a terminal would be cool. But beyond git I'm not sure there is much benefit to it within HISE.

I edit all my scripts in HISE. The only time I use an external editor is if I make a mistake that causes HISE to crash when loading my project

I usually open a terminal, switch to a branch. Close the terminal and work on whatever I'm working on before opening another terminal and making my commits. If I'm working on something more complicated that I want to split into several commits I'll use Pulsar's git management instead because having a GUI can be easier when you only want to commit specific parts or solve merge conflicts.

[dannytaurus]

@David-Healey Yeah, it would probably just be for git. And I suppose running tests, if that ever became a thing in HISE projects. No idea how that would work though - unit tests for script functions maybe, and system tests for UI stuff

Interactive staging (-p flag) in the terminal is really easy but for merging conflicts, yeah I do use the Cursor UI.

I guess I need to get used to hopping between the two. I just feel like there's an amazing solution out there but I can't quite see it!

[dannytaurus]

@David-Healey

I edit all my scripts in HISE

I'd be happier doing that if the HISE script editor worked anything like ANY other text editor I've ever used! So many weird things throw me off all the time.

[David Healey]

@dannytaurus I guess I'm used to it. I've seen it evolve from the basic text editor we had in the early versions of HISE to the more advanced one now. Still a lot of quirks that need to be fixed but it's getting there.

[ustk]

@dannytaurus lol... The exact opposite for me because I learned mostly with Hise, so I'm lost everywhere else
I use GitHub Desktop. For conflicts it just tells you where the conflict appears so you can open the diff in whatever editor you like (from the app), make the changes and save. GitDesktop will then approve and authorise the merge (or the opposite)

[dannytaurus]

@David-Healey For me, I don't think it's things that need to be fixed - I think it's designed behaviour. Maybe it's a Mac vs Windows thing?

Some of it I can solve by updating the keyboard shortcuts, but most of it is just frustration at how text editing works.

I generally like to use the keyboard as much as I can when editing text and I find myself typing in the wrong place because the cursor isn't where I expect it to be.

And I know there's a keyboard shortcut to move a line up/down but I only ever invoke by accident and I can never find it when I want it!

I suppose there ins't really much difference between using a keyboard shortcut to focus the HISE code editor and one that switches to my own code editor. Maybe I should try that for a week and see how it goes.

[dannytaurus]

@ustk I learned git in the terminal about 15 years ago, when there weren't as many decent git UI apps around. I actually find some of the UI apps more intimidating than typing git commands directly in the terminal!

[dannytaurus]

@David-Healey Oh, and I still don't really know how to open multiple arbitrary script files in the code editor. I'm hoping your new course will get me thinking the HISE-way for stuff like this.