Shared code projects stored in git for sharing should be maintainable in their own project. Projects using this code should update it automatically (at least as long as the major version number doesn’t change). The Swift package manager has a clever way of handling these dependencies. The Xojo IDE doesn’t.
Copying code from a shared git and pasting it at the target as a standard way is bad practise. Doesn’t surprise me that one gifted coder at Xojo implements it this way.
Xojo’s handling of release version numbering is abysmally bad and they introduce code-breaking stuff every now and then.
Git however doesnt seem to like to share individual files this way
At least I’ve not managed to be able to make a git project bring in anything other than an entire directory
So any “shared” code has to be in the originating project as a Folder - with whatever contents
Then its fairly easy to bring that into other projects
I have 6 or 7 shared items between these 3 client projects & add more all the time
Yes this is sometimes annoying … for example if I zip up a set of project folders for backup and forget to move or delete the archive from the root folder Git is managing (or just create it somewhere else to being with), Git wants to add it to the next commit, lol. But … it is a simple mechanism that way. Doubtless an artifact of its roots in Linux.
It just means that if I want to share parts of Xojo projects across multiple projects I stuff those items in a xojo project folder, which ends up being a directory on disk, and off I go
but this IS off topic for this thread
FWIW I now have 3 IDE’s to keep working on C# on MacOS projects
Something Xojo DOESNT have
BIG COMPANY ABANDONS MacOS IDE is just click bait
since they ignore the fact the language etc are all open source & available in multiple IDE’s
Yes it is to an extent but the lede isn’t technically inaccurate … they are abandoning a particular IDE and I know that I used that IDE for awhile because I preferred it, or would have if it had been substantially feature-compatible with VS for Windows. I could see they were doing a complete rewrite (since finished) to bring it more on parity and solve some performance issues and provide Apple silicon versions and so forth. I would have thought that much of an investment would make them reluctant to abandon it, even if it was kind of a sunk cost fallacy. I was, as usual, wrong. Every time I adjust my view of MSFT’s bottomless mercenary disregard for existing users (VB6, FoxPro, etc) further downward, they manage to top it.
Anyway I switched, not to VS Code, but to JetBrains Ryder, because it’s closer to what I want / am accustomed to than VS Code or the other alternatives and seems the best supported … plus it promises to continue to move VB.NET forward which isn’t an immediate concern of mine anymore but a nice plus arguably.
@samRowlands, for anyone receiving the Xojo Forum summary email today, you may have noticed that Sam’s post (the one Sam thought would never last), has in fact led (is highlighted) in the section of Popular Posts. One of those universe-in-harmony moments - as your views are inadvertently shared to a broader audience.
For people who do not really follow TOF (the vast majority according to Xojo), it may appear Sam now moved to Xojo and is hugely enthusiastic about it. This paragraph is ripped out of context. Probably just some algorithm that marked it because it had so many likes, but still misleading to the skimming reader. Xojo had a lucky break here the system did not include:
So my answer to this question is “Yes, I do feel it is safer buying into a development tool / ecosystem from a Big Name.”
Yes, without the benefit of the backstory, the casual reader may get the wrong impression entirely.
That is completely diabolical! (and funny).
Four additional points (not to one-up you but to add to the fun):
forum activity, is a very telling metric for the health (or otherwise) of a development tool (software company), regardless of nonsense to the contrary.
forum activity can mature / settle when an offering is solid, well documented and well supported, but that is far from the case here. Given the level of change, migration of APIs, new and immature platforms, and the sense that the platform remains largely in beta, no developer could seriously last a day without access to the forum.
Those ignoring the forum are probably fighting on with 2019r3.2 and praying they can wing-it (improvise) till 2030, retirement or the end-of-the-world.
…and maybe whilst skimming those casual readers digested the last line in Sam’s snippet:
I’ve learned a lot from people who used to participate here.
and think to themselves, that can’t be good, can it?
I have played quite a bit with C Lion and it is really impressive.
PyCharm could not find the Python interpreter on MacOS and I never did get it to work or get any support help on it … although I didn’t try super hard, I just wanted to play with it, didn’t have an immediate need.
The VS IDE is being discontinued
NOT the entire tool set, not .Net , etc
Xojo completely misunderstood WHAT was happening and assumed that the IDE going away meant the entire tool chain was going away
NOT true
On macOS, File.Copy() has significantly improved its speed by relying on the OS’s clonefile function, if it is available, for the copying process.
There are at least 3 other IDE’s for using .Net and C# on the Mac - VS Code, Jet Brains Rider, and REM Objects
How many alternate IDEs are there for Xojo ?
oh yes, and shortly after showing me that it installed a slew of new updates
not to forget that Jetbrains Rider is also available for Dotnet Development There are several possible IDE’s to use. And yes, also for Xojo…ahh, nay, sorry…
).