Widgets and the Dictionary
ali.lloyd at livecode.com
Wed May 25 22:53:24 CEST 2016
That is a correct description of how it currently operates, although the
'thought experiment' of having 1000 widgets is valid - we are aware that it
would be a problem but it is not current a priority. I hope that at some
point we will able to remove all but the entry content from the dictionary
browser widget and make everything else out of other objects.
The same future problem exists with the tools palette and the object -> new
On Wed, 25 May 2016 at 17:40, Devin Asay <devin_asay at byu.edu> wrote:
> > On May 25, 2016, at 8:13 AM, [-hh] <hh at hh.on-rev.com> wrote:
> > I wonder who will manage (and how) the description of
> > 1000 widgets/externals in the dictionary? A menu with
> > 1000 entries? And all the updates?
> > Perhaps it would be better if each widget/external
> > had his own help file/demo stack?
> > Or if the dictionary will be split into LiveCodeScript
> > and LiveCodeBuilder and Guides in one part and all
> > the rest in a second part?
> My understanding is that inline documentation must be created with each
> widget or it will not compile correctly. Once the widget is imported to
> one’s LiveCode installation the documentation will automatically appear in
> the option menu in the Dictionary’s API tab.
> Others may have more accurate or detailed information about this.
> Devin Asay
> Office of Digital Humanities
> Brigham Young University
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode