LiveCode Forums.

What are the differences between extensions, widgets and plugins?

TIA,
Linda

"Extensions" is a generic term for anything that extends LiveCode's capabilities.

"Widgets" are custom controls made with LiveCode Builder.

"Plugins" are LiveCode stack files you can put into a folder for convenient access in the IDE (see Development -> Plugins)

Linda.

I don't use LC builder, and also do not extend the language.

But a plug-in is like a built-in "stack in use". It works the same way, except that instead of having actually to put a stack in use explicitly each session, plug-ins load automatically.

Not that you cannot automate putting any stacks in use, it is just more convenient to set, one time forever , as a plug-in.

Craig

Plugins can be libraries, brought into the message path with "start using". But they can also be just about anything else you find useful to have in your development environment, including additional tools for certain types of layout tasks, or alternate script editors, or even just informational assistance as with the LiveNext plugin.

Richard.

My plug-ins are, on startup in a new session, automatically "in use".

Aren't yours?

Craig

Depends on what you mean by "in use". In this support thread for Linda I'm trying to keep things as simple as possible. The simplest description of a plugin is that it's any stack file you want access to conveniently within the IDE.

Sometimes they can be libraries, where the "stacks in use" would come into play. But I'd rather not bog a new user down with extra details until they're needed.

FourthWorld wrote: ↑

Tue May 05, 2020 10:15 pm

I'd rather not bog a new user down with extra details until they're needed.

Yah, don't use me for details, it would be detrimental to almost everyone

Thanks. Perhaps I should have included "Libraries" in the list as well.

Linda

P.S. Bogs, I have had a few laughs at your posts. You don't have to hold back for my sake.

I'm sorry Linda, I was throwing a joke at Richard because he used the word 'bog', I think this time I really should have held back, but I see that word used so rarely, I couldn't help myself hahah.

dunbarx wrote: ↑

Tue May 05, 2020 9:09 pm

My plug-ins are, on startup in a new session, automatically "in use".

Aren't yours?

Half of mine are not, they are mostly tools that do a specific job and go away when their stack is closed. AirLaunch is one of these, for example. It's in my Plugins folder so I can get to it quickly, but none of its scripts are required in the IDE, it's completely self-contained.