Disconnect from Mothership

[bwmilby]

I'm late to the party, but decided to take a look around. I cloned the repo and noticed it is still set as a fork from the mothership. Has disconnecting been discussed?

https://stackoverflow.com/questions/183 ... wn-project
(Bottom line is that you contact GitHub Support and they take care of it)

From a workflow standpoint, it may be better if the OpenXTalk repo was the parent and then everyone working on it could have a fork to work in and then submit pull requests. As it stands, since I already have a fork, I can't make a fork of the fork since the parent is the same.

[richmond62]

I'm late to the party, but decided to take a look around.

Frankly, as parties go, it's been sort of slow and quiet so far, so if you've brought some "you-know-what" to liven things up, that's super!

I think that 'Mothership' might be a misnomer, unless of course you mean 'Mother' as in 'Mother' in Disney's Snow White.

the OpenXTalk repo was the parent

I am sure you are absolutely right.

[OpenXTalkPaul]

I'm late to the party, but decided to take a look around. I cloned the repo and noticed it is still set as a fork from the mothership. Has disconnecting been discussed?

https://stackoverflow.com/questions/183 ... wn-project
(Bottom line is that you contact GitHub Support and they take care of it)

From a workflow standpoint, it may be better if the OpenXTalk repo was the parent and then everyone working on it could have a fork to work in and then submit pull requests. As it stands, since I already have a fork, I can't make a fork of the fork since the parent is the same.

Welcome to the party Brian, glad to have you!

I didn't think it was necessary to 'detach' from the progenitor fork, specially since that's been archived. But you're saying it causes problems in your own fork of it? You should be able to clone and then push to our main branch "OpenXTalk-develop-1.963.1" here: https://github.com/OpenXTalk-org/OpenXT ... op-1.963.1
That's only IF you're sure you want to work from my fork of the engine. I haven't really touch any C++ engine code in that repo. Only the Dictionary and the 'Builder" copy of revDocsParser have been modified in that repo for rebuilding the dictionary data.

Most changes (de-branding, IDE script fixes, additions and such) are in the IDE repo:
https://github.com/OpenXTalk-org/OpenXt ... nicEdition
Which I've made a bit of a mess out of (although there was some method to my madness).

That StackOverFlow question also had a few workarounds for 'detaching' manually by moving all the files to a newly created repo. But again I didn't think it was necessary, but I'm not git expert either.

Additionally Tom Perry (tPerry2x) maintains a different, more frequently updated fork of the IDE called 'OpenXTalk Lite', but he doesn't use GitHub or other remote version control. Search the forum for download link (I think he's on v1.0.6 currently).
I've tried to merge his changes into DPE repo, but just haven't had the time to keep up with his pace of changes. I have recent changes I've made myself that I haven't even pushed yet.

[OpenXTalkPaul]

We'll have to keep a look out for knocks at our door from castaways, it seems like there may be another exodus from ex- happening since the recent announcement.

It seems to me that indicates they may now realize that having the open-source edition wasn't the actual problem.
I do think it's good that at least they're willing to try to adjust pricing.

I don't know if it's enough of an adjustment though, as the pricing seems high (compared to competition like Xojo ) and there seems to be a lot of negative reaction comments. I wonder if they'll wind up deleting that thread in a few days like they did with the announce thread from Sept.1 2021.

[bwmilby]

I was able to clone/download the OXT repo, but I couldn't fork a copy of it. I already have a fork of livecode and livecode-ide in my GitHub that I believe still have unmerged changes. I may be able to pull the branch in from OXT into my repo though. I’ll look into that first.

I have not built the full project on my laptop, so it has been quite a while since I did it. My iMac is still set up with it, so I should be able to build on it still.

I'll download the Lite version and take a look as well.

[tperry2x]

I'll download the Lite version and take a look as well.

Welcome!
I hope I can help as needed.
Here's the link to download OXT Lite 1.06

All the stuff to do with the engine source I was tinkering with is here.

This is the engine source code I used, which was from the livecode github page (I wanted to start with as 'vanilla' version of the 9.7.0-dp1 source that was available). I had to make a lot of corrections to the gyp build tool, as it had lots of depreciated keywords which needed to be replaced. - I also made a tweak to the build scripts, so they fetch the prebuilts from a local folder, rather than trying to get anything from a remote server.

I should add, I did get the Windows version of the engine to compile - but it ran slowly.
You can also download that from this link, in the subfolder 'Compiled version'.

[mwieder]

Brian- my updated engine repo is here

https://github.com/mwieder/OpenXTalkEngine

It doesn't show as forked from LC's original because apparently it's no longer possible to fork archived repos on github.