Improving the dictionary [was: LiveCode release notes]
pete at lcsql.com
Wed Dec 16 14:02:29 EST 2015
That would certainly help. I still believe a fully searchable database of
the release notes would be useful though and still willing to take that
on. I need to be able to minimize or even eliminate the manual effort
required to enter the release note data into the database. I don't believe
I can do that using the pdf versions of the release notes so if there is
indeed an html version somewhere as mentioned recently, I'd love to get
access to it in the hope that I can parse it programmatically and load it
into the database.
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
On Wed, Dec 16, 2015 at 12:50 AM, Peter TB Brett <peter.brett at livecode.com>
> On 15/12/2015 19:26, Mark Wieder wrote:
>> On 12/15/2015 11:09 AM, J. Landman Gay wrote:
>> Most of the entries do show the initial release date in the dictionary
>>> but the problem is that we often can't recall what term to look up.
>> Also, bug fixes don't necessarily fall into that category and probably
>> won't show up in the dictionary.
> Anything that changes the behaviour of the syntax definitely should be
> noted in the dictionary.
> If it doesn't change the behaviour but just, for example, improves
> performance or fixes a crash in a pathological case, then it generally
> shouldn't be noted in the dictionary.
> The core dev team tries very hard to *not* change behaviour of existing
> script syntax where it can be avoided -- because it's important not to
> break stacks that currently work (c.f. discussion about "save" vs
> I would like the dictionary to have a way to search its entries by "last
> changed in", "introduced in", and "deprecated in", but it currently looks
> like we won't have time to introduce that in 8.0.0.
> Dr Peter Brett <peter.brett at livecode.com>
> LiveCode Open Source Team
> LiveCode on reddit: https://reddit.com/r/livecode
> 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