palmin, 1 month ago

@Migueldeicaza That should work. Working Copy just gets the user to pick a directory and manages the repository there.

But I suggest configuring Working Copy to put the .git folder inside the working directory. It does the opposite by default because so many apps freak out if they spot a .git folder but it is much nicer to keep it inside.

Migueldeicaza, 1 month ago

@palmin another question, I wonder if I could call out to working copy with a url handler to configure this - so users don’t have to do it.

simsaens, 1 month ago

@Migueldeicaza @palmin 👀 if there's a way to do this I'd love to do it for Codea as well

palmin, 1 month ago

@simsaens @Migueldeicaza I will do everything possible to make this as easy as possible.

Right now the fastest way to configure linking is to drag a folder (where the NSItemProvider allows writing back changes) into the repo list in Working Copy. You can try this out from the Files app.

If there is a .git directory it gets to stay there otherwise it puts .git somewhere to avoid a confused app deleting it.

simsaens, 1 month ago

@palmin @Migueldeicaza if we placed an empty .git folder inside each Project.codea bundle, would Working Copy take over and manage in-place?

palmin, 30 days ago

@simsaens @Migueldeicaza Right now it would assume this wan an existing repository with a standard .git directory.

Currently it would leave the .git directory in-place but also complain like crazy that the repository wasn’t valid.

I could add a special case where an empty .git directory gets initialized and left in-place.

palmin, 30 days ago

@simsaens @Migueldeicaza I have a new TestFlight out with two improvements.

It is easier to setup linked repos to document packages like Codea projects.

When a linked repo is being configured the app will check the UTI to see if you picked Codea Projects, Swift Playgrounds or if there is a “project.godot" file and consider the .git directory safe inside the picked directory/package.

It doesn't yet care about empty .git directories.

You can try it out now:
https://testflight.apple.com/join/jWRvinra

Migueldeicaza, 30 days ago

@palmin @simsaens OMG that is beautiful! Thank you Anders!

simsaens, 30 days ago

@palmin @Migueldeicaza that’s incredible! You are so fast. Will give it a test with an init’d git repo inside a Codea project

palmin, 21 days ago

@simsaens @Migueldeicaza Improvements are in the App Store version as well.

I feel silly for not doing this year ago.

Migueldeicaza, 21 days ago

@palmin @simsaens woohoo! Magical! Thank you Anders!

palmin, 1 month ago

@Migueldeicaza There needs to be some user interaction as that is what grants the permission for Working Copy to access a Godot folder.

Textastic and Working Copy had a wonderful url scheme that included the path the user should pick such that the document picker started out the right place and the user should just tap Done.
https://x.com/palmin/status/1487155542841769984

But Apple changed the document picker to break this. Can't remember exactly when.

Migueldeicaza, 1 month ago

@palmin I think the user interaction is fine, the metadata would be “please put the .git in the directory the user chooses”

palmin, 1 month ago

@Migueldeicaza That could definitely be done.

Is there a way this could be communicated by Universal Type Identifiers such that the UTI for Godot projects registered by your app derives from some type telling Working Copy that .git directories are welcome?

Migueldeicaza, 1 month ago

@palmin I am not sure about what that would entail exactly; but Godot directories have a “project.godot” file in the top directory.

palmin, 1 month ago

@Migueldeicaza Is there a TestFlight of your Godot IDE I can try?

Want to make Working Copy work as nice as possible with it.

Migueldeicaza, 1 month ago

@palmin sadly, not yet. I am hoping in a few more weeks.

palmin, 1 month ago

@Migueldeicaza No problem.

Do you want to run the Working Copy beta?

I plan to adjust how to setup linked repositories over the next week or so.

Migueldeicaza, 1 month ago

@palmin I might, but give me a couple of weeks.

For now, this just took a big weight off my shoulders.

I just finished an exploration on file coordinator, and I just don't think I can make it work any time soon.

I should have explored the "Can working copy open a folder" option much earlier.