Modularising Code

Terence Heaford t.heaford at btinternet.com
Thu May 8 09:11:15 EDT 2014


Thanks for your comments.

I have just placed the DBRoutines into a substack and placed "start using" in the preOpenStack handler.

That seems to be a workaround for not having folders in the IDE.

Are there any downsides to this method?

I have downloaded and tried GLX2 but there are issues on my Mac concerning the display of text being corrupted.

Something like —> in GLX2 would be useful in the LiveCode IDE.

I also thought that an updated IDE was one of the stretch goals of the Kickstarter campaign.
How is that going?
 

All the best

Terry


On 8 May 2014, at 13:55, Dar Scott <dsc at swcp.com> wrote:

> Stack libraries have some nice advantages for me.  I sometimes put some things such as tables into controls.  They are often wrappers for externals.  (Or maybe the externals are helpers for the libraries.)
> 
> If you have a card for putting odd things and the card never shows, you might want to put some objects there to represent your modules and put the scripts into those.  Name them after the modules.  put them in front or in back as seems right when you open your stack.
> 
> If you need some module only on cards with certain background groups, then consider whether those scripts belong in the group.
> 
> If you have a family of applications that use the same splash-screen main stack, consider putting those things that are special to the family in that stack.
> 
> Dar Scott
> Controls, Libraries and Externals




More information about the Use-livecode mailing list