OpenXTalk Forums

First order of non-business is for any forks of the LC Community Edition should be to remove any references to LiveCode Ltd, any branding related to that commercial enterprise, and any indication of support from that company for open source builds, so as to not confuse their customers.

I'm just now looking for where exactly in the IDE those things may be locate.

Any help with that would be much appretiate.

Thanks

I'll have some time tomorrow to dig into the ide stacks and help look for LC branding and links. I think we probably need some kind of placeholder icons/branding to replace at least some of this stuff with.

SethMorrow wrote: ↑Sat Sep 11, 2021 10:31 pm I'll have some time tomorrow to dig into the ide stacks and help look for LC branding and links. I think we probably need some kind of placeholder icons/branding to replace at least some of this stuff with.

I just spent some time editing images with a temp logo, and editing the menubar scripts
Probably do some more before I pass out.

Noticing there's some of bloat, like redundancy in the about box, which has text property with list of contributor names (added mine and yours) but then the scripts pull a new list of names from an about.txt file, and there's old graphics from 6 that are still included in 9.

Just temp placeholder logos for now

- -
Thse icons, of course, presuppose that we wish to keep the LiveCode connexion.

For the moment, at least, I think that to totally detach ourselves and sail off into the wide blue yonder might be unwise
as it seems sensible to "capture" all those of the erstwhile LiveCode 'Community' [that's a very bad joke in hindsight]
who are prepared to pitch in and contribute rather than just merrily continue with LiveCode OS 9.6.3.

I also suggest that at the moment ay numbering scheme of the new "thang" should closely ape that of LiveCode, and
as far as is possible we should aim to implement new features that appear in LiveCode in the new "thang". Doing that
may make the LiveCode people realise that they have made quite a large mistake . . . well, if LiveCode now does not
go into a descending spiral that results in its death.

richmond62 wrote: ↑Sun Sep 12, 2021 11:17 am OLC_icon.jpeg
-
OLC_doc_icon.jpeg
-
Thse icons, of course, presuppose that we wish to keep the LiveCode connexion.

A fork should not confuse LC customers with branding that is too close to theirs, I've been formally informed that this is legal thin ice, which is why I'm rushing to remove references to LC in this current OTX fork. If it was humorous / parody I believe that would be protected, at least in the US (1st Amendment). Your modifications to their existing logo / icons I don't think would be enough. Not that I want to do that anyway. I don't want to hurt their business in anyway. I believe their own actions recently may have done that enough already. I hope that I'm wrong.

richmond62 wrote: ↑Sun Sep 12, 2021 11:17 am LiveCode now does not go into a descending spiral that results in its death.

I sincerely hope that doesn't happen, but if it ever does there will still be this open source work for anyone who wants to continue it.

Removing references to LiveCode (and a few to Runtime Revolution)
in the Dictionary and the Preferences is going to be a tedious business.

-
The icons in the menuBar will need to be altered, and 3 of them will have to be removed completely
as they link to Proprietary stuff.

-
Mind you, it beats banging one's head on the wall . . . a bit.

It sounds like the dictionary might be a good place to start. I'll look into this tonight, perhaps we can get some of the work done programatically. I also think that ".OXT" might be a good potential file format rename, as we surely can't use ".LIVECODE".

I also think for this to really work, we should create a solid list of what needs done currently, and what everyone is working on, to avoid wasted time due to overlap. I'm not a GitHub expert, but that seems like the obvious choice for this. I've set up a github account and repository to secure the name "openxtalk", but Paul has also been busy doing a lot of work in his DPE edition repository.

I'm not sure what the future may bring, but I'm here to help in anyway I can. As the community hopefully grows, we can get this thing moving.

Pehaps an "introduction thread" where users could introduce themselves and talk about what they hope to see or are willing to contribute is in order?

.OXT seems a very good idea . . .

HOWEVER, the "new thang" should still be able to open files with .MC, .REV or .LIVECODE as suffix.

"Removing references to LiveCode (and a few to Runtime Revolution)
in the Dictionary and the Preferences is going to be a tedious business."

Is there not a way to automate this, like using a search and replace function?

Possibly, although there are thousands of documents inside the Macintosh LiveCode package
so, if one can find a search-and-replace "thingy" that does NOT have to be run individually for
each document but can span them all . . .

richmond62 wrote: ↑Sun Sep 12, 2021 5:20 pm .OXT seems a very good idea . . .

HOWEVER, the "new thang" should still be able to open files with .MC, .REV or .LIVECODE as suffix.

I like .OTX too, except it is already used by Apache OpenOffice.

https://fileinfo.com/extension/oxt

How about .XTO ? sort of a french or reverse polish notation where the adjective or operator comes last?

Or .OPENXT

richmond62 wrote: ↑Mon Sep 13, 2021 6:04 pmOr .OPENXT

I like this best.

boley wrote: ↑Mon Sep 13, 2021 4:51 pm

richmond62 wrote: ↑Sun Sep 12, 2021 5:20 pm .OXT seems a very good idea . . .

HOWEVER, the "new thang" should still be able to open files with .MC, .REV or .LIVECODE as suffix.

I like .OTX too, except it is already used by Apache OpenOffice.

https://fileinfo.com/extension/oxt

How about .XTO ? sort of a french or reverse polish notation where the adjective or operator comes last?

Hmmm I didn't realize that .otx was already taken. Probably seen that before, I haven't used OpenOffice in a long time.

.OPENXT or .OTXScript could maybe be workable. For .rev, .livecode, .livecodescript, etc. and I'd like to support others like .stak (I still have HyperCard stacks lying around) or any others (perhaps there could be transpilers or converters?) We could just change the dialogs to something like "Show compatible formats" for example.

I'd like to make the dialogs as generic as possible. For example "LiveCode UI elements appear in lists of stacks" in the prefs window becomes "Show IDE UI elements..." There's unnecessary branding all over this beast!

I'm thinking it would be good to reduce gratuitous use of logos as well, that way if anyone wants to redecorate, change the logo or whatever, in the future it will be easier.

susan wrote: ↑Tue Sep 14, 2021 4:26 am

richmond62 wrote: ↑Mon Sep 13, 2021 6:04 pmOr .OPENXT

I like this best.

google search for ".openxt file extension" doesn't turn up anything so that may be good along with .openxtscript for script only files
It might be good to try to find one that is 3 chars (like .rev was), just in case someone is using some 1980s-centric Linux distro or similar OS?

3 chars

. . . XTC . . .