HyperTalk, SuperTalk, MetaTalk, Runtime Revolution, Transcript, LiveCode, The LiveCode Scripting Language . . .
Before someone gets round to writing any instructive material are we to understand that the programming language in OpenXTalk is called xTalk?
I do feel it is important to have a name for the scripting language that differentiates it from the IDE.
Talk the talk, walk the walk.
Forum rules
Be kind.
Be kind.
- richmond62
- Posts: 4833
- Joined: Sun Sep 12, 2021 11:03 am
- Location: Bulgaria
- Contact:
Talk the talk, walk the walk.
https://richmondmathewson.owlstown.net/
- tperry2x
- Posts: 3211
- Joined: Tue Dec 21, 2021 9:10 pm
- Location: Somewhere in deepest darkest Norfolk, England
- Contact:
Re: Talk the talk, walk the walk.
That's what myself and Paul have been working towards. To give things a name which they can be identified by, but at the same time keeping things unbranded where possible.
So yes, the language as xTalk and the IDE as, well.... the IDE.
The engine as 'the engine' - although I have many other names for it when it won't compile.
We've dropped all OXT and Livecode references where we can, so anyone can pick up our efforts and add to it with their own name with minimal effort. As Paul says, unbranding rather than rebranding.
Same as whenever I encounter a metacard reference, I remove that too.
So yes, the language as xTalk and the IDE as, well.... the IDE.

The engine as 'the engine' - although I have many other names for it when it won't compile.
We've dropped all OXT and Livecode references where we can, so anyone can pick up our efforts and add to it with their own name with minimal effort. As Paul says, unbranding rather than rebranding.
Same as whenever I encounter a metacard reference, I remove that too.
- OpenXTalkPaul
- Posts: 2633
- Joined: Sat Sep 11, 2021 4:19 pm
- Contact:
Re: Talk the talk, walk the walk.
I'm OK with keeping some MetacCard, RunRev, even LiveCode references. Their origin story is the origin of the OXT Engines and so I feel like that's significant from historical perspective.tperry2x wrote: ↑Sun Jun 23, 2024 7:20 am We've dropped all OXT and Livecode references where we can, so anyone can pick up our efforts and add to it with their own name with minimal effort. As Paul says, unbranding rather than rebranding.
Same as whenever I encounter a metacard reference, I remove that too.
I've been calling the language xTalk script (I've recently been abbrev. as xT script ) when I need to call it a name at all. Usually that's only when there's a need to differentiate it from another language like Extension Builder (lately I've been abbrev.. that to XBuilder), and also from AppleScript, JavaScript, Shell script, etc.
-
- Posts: 442
- Joined: Sat Sep 11, 2021 4:37 pm
- Contact:
Re: Talk the talk, walk the walk.
I kinda like the idea of referring to the language as "oxTalk". So many mascot possibilities, the perfect pairing with GNU.
- OpenXTalkPaul
- Posts: 2633
- Joined: Sat Sep 11, 2021 4:19 pm
- Contact:
Re: Talk the talk, walk the walk.
I like that idea, also because since we're still using a scripting language that its original creators basically abandoned 30+ years ago, we here must all be stubborn as OXen.FourthWorld wrote: ↑Thu Jun 27, 2024 5:40 am I kinda like the idea of referring to the language as "oxTalk". So many mascot possibilities, the perfect pairing with GNU.
Who is online
Users browsing this forum: No registered users and 1 guest