Another question about multiple stack projects
bogdanoff at me.com
Tue Feb 16 15:25:04 EST 2021
Also, if you are going to notarize the application package after code signing in macOS, the files need to be where the standalone maker puts them. Otherwise it will fail Apple’s notarization service.
I found this out after trial and error. Previously I had manually put them into the package where I liked them to be, which is OK for simple code signing and creating and signing the DMG. But not for notarization.
> On Feb 16, 2021, at 10:57 AM, William Prothero via use-livecode <use-livecode at lists.runrev.com> wrote:
> What I should have done is search the help files first, but I somehow chose unhelpful search terms, so didn’t see this until this morning. Sorry.
> So it appears that the only purpose of the “Stacks” setting is to set properties for each stack that locates them within the particular app directory. Very convenient.
> For example, suppose one line of the stackfiles property is, by extracting a line from “the stackfiles of this stack":
> appNavigation-Lib,resources/libStacks/appNavigation-Lib.livecodescript (= theSelectedLine)
> put specialFolderPath("resources”)&”/“&(item 2 of theSelectedLine) into tFilePath
> start using tFilePath
> I see, in the IDE, anyway, that no matter where I am in the multiple stacks in the project, that if I do:
> "put the stackfiles of this stack”, I get the list of stackfiles that was entered from the settings.
>> On Feb 16, 2021, at 8:45 AM, Bob Sneidar via use-livecode <use-livecode at lists.runrev.com> wrote:
>> Listing them in the stack files gives LC the ability to find them when you refer to them by name only (as opposed to the full path.) In the case of script only Libraries, you can start using them at any time before you make a call to them. For instance, I have a database setup card that configures the database connection when the card is opened. I start using my database library on openCard.
>> Bob S
>>> On Feb 15, 2021, at 9:40 PM, William Prothero via use-livecode <use-livecode at lists.runrev.com> wrote:
>>> I have a question about multiple stack projects. My project starts with a splash stack. In the standalone preferences of this stack, I list all stacks the project uses, including script only stacks I use as libraries. Should I do a “Start using” on all of these stacks at this point? But I could have just done a “start using” for the required stacks for each of the other component stacks when they were first accessed, and got the same result?
>>> I guess my question is: how does the build process make use of the list of stacks in the splash stack? Are they all built into the project in some way that doesn’t happen otherwise? I still seem to be required to “Start using” each of the library stacks anyway.
>>> William Prothero
>>> waprothero at gmail.com
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> William Prothero
> waprothero at gmail.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode