Substack vs. Library Stack

William Prothero prothero at earthednet.org
Wed Apr 29 18:29:49 EDT 2015


Peter:
Ok, if that makes it a library stack, then I’m using it as a library stack. BUT, it’s also a substack. So I guess in this instance, they are the same thing, functionally at least. One of the nice differences is I don’t have to provide a file path to the start using command. Don’t know if libraries require this, because I haven’t really tried to use “Libraries” per se.
Best,
Bill

> On Apr 29, 2015, at 2:30 PM, Peter Haworth <pete at lcsql.com> wrote:
> 
> Maybe I'm confused over what you're doing but "start using" is how you make
> a stack available as a library so you're already using a library, not a
> substack.
> 
> Pete
> lcSQL Software <http://www.lcsql.com>
> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
> 
> On Wed, Apr 29, 2015 at 1:37 PM, William Prothero <prothero at earthednet.org>
> wrote:
> 
>> Scott:
>> I use substacks as code libraries in a large project. The substack
>> handlers are callable (without specifying the substack name) from any other
>> substack and also from the main stack. It is like having a giant stack
>> script. Of course, you have to “Start using mySubstack” to make the code
>> available. You can also remove the substack and use it elsewhere and attach
>> it to another main stack by setting its mainStack property. e.g. set the
>> mainStack of this stack to “myMainStack”.
>> 
>> I find it very convenient. But, as I get more familiar with Livecode, I’ll
>> like the libraries approach.
>> 
>> Best,
>> Bill
>> 
>> 
>>> On Apr 29, 2015, at 12:31 PM, Phil Davis <revdev at pdslabs.net> wrote:
>>> 
>>> Another thing about libraries: they can have substacks if needed. Of
>> course, substacks can't.
>>> 
>>> Phil Davis
>>> 
>>> 
>>> On 4/29/15 10:36 AM, Scott Rossi wrote:
>>>> I imagine you'll get a lot of responses to this, but one reason to use a
>>>> library is its code is available to all open stacks in LC: functions,
>>>> commands, etc.  Sort of like having a backscript for all open stacks,
>>>> instead of just one.  A substack doesn't do this.
>>>> 
>>>> Another frame of reference that might help is the difference between
>>>> behaviors and libraries: code in behaviors is object-specific, available
>>>> only to those objects that have the behavior assigned to them, while
>> code
>>>> in libraries is universal, available to all objects anywhere, and
>> doesn't
>>>> require any assignment.
>>>> 
>>>> Other people will probably chime in with additional insights.
>>>> 
>>>> Regards,
>>>> 
>>>> Scott Rossi
>>>> Creative Director
>>>> Tactile Media, UX/UI Design
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 4/29/15, 9:56 AM, "Mike Kerner" <MikeKerner at roadrunner.com> wrote:
>>>> 
>>>>> I have not read a straight answer on this, yet.
>>>>> 
>>>>> Library stacks vs. substacks why use one vs. the other?  I don't see
>> any
>>>>> clear advantage to Libraries, per se, even for...libraries.
>>>>> 
>>>>> --
>>>>> On the first day, God created the heavens and the Earth
>>>>> On the second day, God created the oceans.
>>>>> On the third day, God put the animals on hold for a few hours,
>>>>>  and did a little diving.
>>>>> And God said, "This is good."
>>>>> _______________________________________________
>>>>> use-livecode mailing list
>>>>> use-livecode at lists.runrev.com
>>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>>> subscription preferences:
>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>> 
>>>> 
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>> 
>>> 
>>> --
>>> Phil Davis
>>> 
>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the Use-livecode mailing list