That's good to hear. I didn't mean to offend anyone (or potentially offend anyone).FourthWorld wrote: ↑Mon Mar 27, 2023 10:05 pm I know Paul, Kevin, and Mark personally. I know how they work. Paul's dedication is admirable, but there is nothing Kevin and Mark would want to take from here.
In an ideal world, we could say - "hey, we found a bug at this point..." and they would reply with "Thanks for letting us know, we'll fix it in Livecode. We found an issue with a glitchy message box, on [OS] and the fix is [X] which perhaps you can incorporate into OpenXTalk"
It would be nice if there was a bit of collaboration - a bit of helpful back-and-forth as we might be able to help and so might they.
All I meant was that anyone can look at OpenXTalk's code at any point, yet we can't look at what they are doing over at Livecode as it's closed source.
Which does not seem fair.
Even if they don't plagiarize OpenXTalk's code in any way, shape or form - they can see what has been modified / fixed and why.
Not to say they would directly copy and paste code from OpenXTalk, but what I meant was might they read it and come up with their own fix, written in a different way but fixing the same issue nonetheless?
I'm not suggesting they would knowingly infringe upon any copyright or anything. But to give you an example. Imagine the first car maker to fit a safety feature, then all the other manufacturers started doing it. That original car manufacturer might think "hmm, doesn't seem fair since we came up with that idea - but for whatever reason they were unable to patent it or claim it as their own". You can't shout at the rival company for using the same idea since the technology is out there and in the public-domain, but you know exactly where it came from. Even if you can't go to their door and flat-out accuse them.
It's a thorny issue, but I didn't mean to get anyone's back up. It's just a "what if" type scenario.