LC 8 Property Inspector

Ali Lloyd ali.lloyd at
Fri Oct 9 03:35:08 EDT 2015

On Fri, Oct 9, 2015 at 3:23 AM Mark Wieder <mwieder at> wrote:
>It seems from the App Browser / Project Browser and Property Inspector
>arguments that I've been expecting too much, and we really can't have

I have no idea why you've drawn this conclusion, as I've repeatedly told
you and said elsewhere that this is not the case.

There are two separate issues here:
1) Our out-of-the-box palettes should be as useful as possible for someone
with no plugins. Hence the soliciting of opinion. Disagree? I'm happy for a
million application browsers to exist, I just don't want to maintain them.
I can't understand how you're viewing the idea of seeking to improve the
IDE's palettes as somehow a negative.

2) Making it possible to replace the palettes. Gradually the IDE routes all
palette-related opening through a revIDEPaletteToStackName function. So
once everything goes through that, and we provide a hook to override it,
you will be able to use any stack in place of a given palette.

Moreover the better the data provision for *our* palettes, the more useful
IDE functions there are for replacement palettes to use. Whatever we add to
a given object's inspector properties, for example, is parsed into the
properties array that the IDE library passes to the inspector.

Should a user plugin wish to use that array, adding the tooltip fixes it
for them too. Adding tooltip to the old inspector helps no-one in this
particular regard, as far as I can see.

On 10/08/2015 02:14 AM, Ali Lloyd wrote:
> > 2) The new inspector is *really* flexible for the classic objects. Have a
> > look at this fix for bug 16118 (no way to change a scrollbar's tooltip in
> > the property inspector):
> >
> > We'd like to make it as good and useful as possible. If the worst you can
> > say is you can't see any advantages, then I think the non-obvious ones
> > above make it well worth it ;-) Otherwise it would be great to hear
> > constructive criticism and suggestions for improvement.
> Well, I've been thinking of the the new IDE framework as just being that
> and allowing for plugin replacement of the various components.
> --
>   Mark Wieder
>   ahsoftware at
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the use-livecode mailing list