I just checked out Mark's updated OOPEngine from gitHub.
I opened the OOPEngine.livecode file and for the first time, opened the Card Scripts.
I found out why there are newClass and deleteClass scripts.
Below is the openStack handler for that card.
Apparently there was the expectation of storing class script files down in the plugins folder.
Are these supposed to be .livecodescript text files? With the way the code is written, the file name must be the class name, which means no extension on the file name.
Was this a potential mechanism for people to distribute classes?
Seems interesting to have, but if one puts one's classes down there, does the LiveCode "create a standalone application file" process know to collect up those files?
Code: Select all
on openStack
local tPath, tFiles
local tFolder
local tNewObjectID
local tScript
put the defaultFolder into tFolder
start using this stack
put revEnvironmentUserPluginsPath() into tPath
put "/Classes" after tPath
if there is a folder tPath then
set the defaultFolder to tPath
put the files into tFiles
push card
go card "Classes"
repeat for each line tFile in tFiles
put newClass(tFile) into tNewObjectID
put url ("file:" & tPath & "/" & tFile) into tScript
set the script of control id tNewObjectID to tScript
end repeat
pop card
set the defaultFolder to tFolder
end if
end openStack