I'm wondering what the plans are for organizing widgets, both in a project and in the tools palette?
I'm working on a new project. There are some widgets I am writing that I will use for lots of projects. Some widgets will be specific to the project I'm working on and won't be used anywhere else. Will all of these widgets needs to be installed all of the time? At some point will it be possible to have widgets associated with a project and only get loaded up when that project loads?
What about the tools palette? I can see it filling up very quickly. Will there be categories so we can keep widgets organized and not have a huge palette?
Organizing widgets
-
trevordevore
- VIP Livecode Opensource Backer
- Posts: 1005
- Joined: Sat Apr 08, 2006 3:06 pm
- Location: Overland Park, Kansas
- Contact:
Organizing widgets
Trevor DeVore
ScreenSteps - https://www.screensteps.com
LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder
ScreenSteps - https://www.screensteps.com
LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder
Re: Organizing widgets
@trevordevore: Ben would probably be a more appropriate person to chime in here - but I believe there are plans to allow you to customize the layout of the tools palette and to put widgets in categories.
In terms of per-widget projects then this is something we can consider although we still need some sort of notion of 'project' in the engine for that to really work... One option might be to allow a stack to specify a (relative?) folder which contains widgets which are for it and related stacks so the IDE loads those into the tools palette when the stack is loaded / focused.
Internally the plan is to make it so that widgets will load on demand as they are needed and unload as the last reference to them leaves - this should mean that you can have as many widgets as you want installed, without having any issue using only a few of them.
In terms of per-widget projects then this is something we can consider although we still need some sort of notion of 'project' in the engine for that to really work... One option might be to allow a stack to specify a (relative?) folder which contains widgets which are for it and related stacks so the IDE loads those into the tools palette when the stack is loaded / focused.
Internally the plan is to make it so that widgets will load on demand as they are needed and unload as the last reference to them leaves - this should mean that you can have as many widgets as you want installed, without having any issue using only a few of them.