![]() |
LDdictionary not working - Printable Version +- Small Basic Forum (https://litdev.uk/mybb) +-- Forum: Small Basic (https://litdev.uk/mybb/forumdisplay.php?fid=1) +--- Forum: Discussion (https://litdev.uk/mybb/forumdisplay.php?fid=4) +--- Thread: LDdictionary not working (/showthread.php?tid=238) |
RE: LDdictionary not working - litdev - 02-11-2025 Yep, That's the one I'll go for, bit of work to parse the Json return but fairly easy. RE: LDdictionary not working - jrmrhrb00 - 02-11-2025 LitDev, Great if you can do it! Maybe you should rename your extension to "LitDev Basic". JR RE: LDdictionary not working - litdev - 02-12-2025 Hi, Uploaded a new beta 1.2.29.16 version with this. The French and Spanish variants don't seem to work (depreciated from intellisense for now) - also added to LDBasic as suggested. Hope this works for a while! It looks like this one actually scrapes the definitions from https://en.wiktionary.org/wiki. RE: LDdictionary not working - Scout - 02-13-2025 Hi Litdev, thanks for creating the dictionary function. The error output goes to a text window, however. "date" generates the following message: LDDictionary.GetDefinition : Additional text encountered after finished reading JSON content: ,. Path '', line 1, position 874. Unknown or incorrect words like "distroy" result in (404) RE: LDdictionary not working - litdev - 02-13-2025 Scout, Thanks for reporting - my tests were OK, I used the word "world". The problems is that there is no definition of the API Json returned, so I just assumed the format would be similar for different words - unfortunately not. It's hard to write a reader of a syntax that changes with no proper definition or API. I will have a look at this example and see what is returned from the call and what in the Json may be different. We can see the returned Json with a direct call to a browser: https://api.dictionaryapi.dev/api/v2/entries/uk/date The issue then seems apparent! To turn off erro rmessages, you can use LDUtilities.ShowErrors = "False" (not implemented in LDBasic). Of the other suggestions I would go for the Wordnik one after looking at the complexity/restrictions of the ones listed. Of course you can get your own free API key and use LDNetwork.SendWebRequest and parse the result - maybe a fun challenge in itself. But if LDDictrionary is something that is important for some existing users then I will research more test Wordnik. RE: LDdictionary not working - z-s - 02-13-2025 https://free-apis.github.io/#/categories/Dictionaries many free apis from this site i am using in ZSApi extension will be released soon. also try contain audio also : https://dictionaryapi.dev/ also show if word dont exist : https://api.dictionaryapi.dev/api/v2/entries/en/distroy RE: LDdictionary not working - litdev - 02-13-2025 ZS, This is the one I used (api.dictionaryapi.dev - free no signup), just didn't realise lots of words 'don't exist' with it - after actually looking at the other suggestions in more detail some have very limited free trials (1000 words total), some have restrictive signup requirements etc, as I say I think the Worknik one looks best with simple signup, fairly simple Json use with access to good dictionary sources and free non commercial use 100 word/hour. RE: LDdictionary not working - z-s - 02-13-2025 wordnik isnt public api RE: LDdictionary not working - litdev - 02-13-2025 (02-13-2025, 02:01 PM)z-s Wrote: wordnik isnt public api Not sure exactly what you mean, you do have to sign up with email address, but as far as I can see (without actually signing up) you will then get an account with API key that can be used in limited non commercial apps for free. RE: LDdictionary not working - z-s - 02-13-2025 ok got it |