tperry2x wrote: ↑Thu Jan 11, 2024 2:09 pm
Community widgets (non com.livecode ones)
Any widgets not developed by Livecode may struggle to load in revidelibrary.8.livecodescript, because of this line:
revIDE.png
Can simply be commented out to allow widgets to load that don't include com.livecode in their name.
Fixed in v1.0 of OXT Lite
I may have patched that at some point? Or I may have left it since most of the modules use that identifier (and it helps me see, what's what and by whom)? I'll have to check. I've searched all of the IDE for instances of the 'livecode' many times, I still find a stray one lurking in a custom property or something like that now and again. But I'm not aware of ever having a problem loading widget or library modules with org.openxtalk.* or community.* What problems have you seen?
EDIT: I didn't patch that in my IDE files, I did now, but just added to what's there:
Code: Select all
if not pObjectTypeID begins with "com.livecode" or not pObjectTypeID begins with "org.openxtalk" then return __revIDEError("No such object type ID: " && pTarget)
I really dislike how non-natural-language many of these scripts reads, but that's the hand we've been dealt.
Anyway, with that edit should enable having mix identifiers, the old com.livecode.. classic 'classic' controls AND new org.openxtalk 'classic' controls. For example we could have a 'classic' control called 'org.openxtalk.classic.GrayFillButton'. I had already added one like that, but I just named it 'com.livecode.interface.classic.FilledButton' (it was mostly an experiment in adding a 'classic' control).
So revIDECreateObject looks like it mostly applies to classic controls and datagrids, but if we were to add our own 'classic' controls then we might need some edits there. there is some bits about the mapkit widget only being available in macOS 10.9+ towards the end of that handler, we could take that out since that mapkit widget was one of their commercial edition things (although It might not be too difficult to build our own mapkit widget).