Structuring Projects in github

General
1

Hi.
I have created a GitHub Xojo Repo that has two projects that share a common module.

I am currently using git from the command line and an older version of Xojo.

My goal hear is that I have several projects that depend on my reusable classes, modules and resources.

Keeping in mind that if I change a module or class it should be reflected in the all projects that ‘reference’ that module, class or resource.

When I ‘include’ a module I believe it should be ‘external’ to the project.

When creating a module you still need a project and that project seems to require an app instance (at least).

2

I know it is somehow possible as I’ve seen it on other github projects. Unfortunately I don’t Know how.
I’d be interested in knowing how to.

3

If those projects are open when you change the file, the changes will not appear. Xojo currently doesn’t track that.

That said, the easiest way I’ve found to accomplish this is to put your shared code into a module and export it as XML. It’s not terribly git-friendly but it will work with it being an external item.

If you don’t mind a little more difficult, you can use submodules, but your mileage may vary.

4

It’s been a while, but I think you’re talking about submodule repos.

Basically it consists of nested repos where the folders of child repos are “hidden” using the .gitignore file. The nested repos are your shared files, which ultimately creates duplicate repos (one for each project using them), but I’ve managed this easily in the past because some git client tools like https://www.git-tower.com take care of uploading/downloading the submodules automagically for you.

I’ve done this successfully with .NET and Xojo projects in the past. The nested repos are just folders of files within the Xojo project, so the Xojo IDE doesn’t mind. But in order for the second Xojo project to see the changes, git commits & fetches are required - and potentially a reloading of the IDE.

I have since changed back to using External Items. Which are not a perfect solution, but it is less time consuming.

Maybe git client tools are smarter these days, so maybe it’s worth trying again…?

5

@Jürg_Otter described a technique in this blog post: Xojo Projects in a MonoRepo

1 Like