LiveCode Forums.

Thinking more about this, the Quality Control center can already be used to request updates to the dictionary via an enhancement request.

richmond62 wrote: Mon Aug 21, 2023 11:51 am The 'eternal' problem with the Dictionary is that it lags behind the state of the IDE and the language.

Can you give an example? I've found that every new token or enhancement always has an entry. I admit some of them are a bit spare though. Which one(s) are lagging?

dunbarx wrote: Fri Sep 01, 2023 4:49 pm Paul.

Are you saying that changes made in Github in the manner you describe will appear in everyone's dictionary?

Craig

No I was not saying that, although I think that could be made to happen via a bit of editing the IDE scripts so that it pulls updates from files on GitHub.

What I was describing is the process for building the dictionary files, that then need to be added to the IDE's documentation folder, where the IDE reads them and then generates a cache of web pages for display in the dictionary stack (Browser Widget).

When LC was "an open-source company", I did submit some dictionary changes to their repo, and it was kind of a tedious process.

bwmilby wrote: Tue Aug 22, 2023 1:44 am The stack that does the export isn’t too complicated and can easily be run by anyone to host a copy of the docs locally.

https://github.com/bwmilby/lc-misc/tree ... ebDocMaker

Darn, if I'd seen this before that would've saved me some time figuring out that there were non-relative links in those cached pages that linked to items inside the IDE Documentation folder (preventing the cached copy from being usable in a browser as-is). Oh well, this will be helpful next time I go to update the OXT Community dictionary (hosted on GitHub, it includes some additions like IDE documentation). Thanks Brian.

Now that is a well educated bot. Excellent writing skills, composition and grammar.

Zero value.