Review of "Light Dict" version 73

Details Page Preview

Manipulate primary selections on the fly, typically used as Lightweight Dictionaries For support, please report issues in time via the Homepage link below rather than the review section below it

Extension Homepage
https://github.com/tuberry/light-dict

No comments.

Diff Against

Files

Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.

All Versions

Previous Reviews on this Version

JustPerfection rejected
I'm sorry but I have to reject this one again, because this is really hard to review. and I see multiple `eval`s in the code that I cannot find the possible string they are trying to evaluate. and we still having hard time to follow how you remove those timeouts with `Symbiont()`.
grroot posted a review
> and I see multiple `eval`s in the code that I cannot find the possible string they are trying to evaluate. These strings to be evaluated are provided by the user via the settings. > and we still having hard time to follow how you remove those timeouts with `Symbiont()`. Would it help if I changed `Symboint` to the following `SourceManager`? ```js export class SourceManager { constructor(host, removeSource, addSource) { host.connectObject('destroy', () => this.removeResource(), getSignalHolder(host)); this.addResource = (...args) => (this._delegate = addSource?.(...args)); this.removeSource = () => { removeSource(this._delegate); this._delegate = null; }; } refreshSource(...args) { this.removeSource(); return this.addSource(...args); } } ```
JustPerfection posted a review
Yeah, it will be much better. It would be much nicer to see more readable code across all the lines. and for eval I cannot still tell that comes from gsettings.
grroot posted a review
> Yeah, it will be much better. It would be much nicer to see more readable code across all the lines. OK, please list other unreadable content that have to be changed. > and for eval I cannot still tell that comes from gsettings. I can only say that these strings are coded to be read from gsettings. If they were to come from somewhere else, I would also be curious as to where that might be. Do you have any feasible suggestions to make it easier to identify their source?
JustPerfection posted a review
Maybe inside `getCommand()` (413 extension.js) we can have a more readable code. And it would be much better if `ldocr.py` could be hosted on `pip` as we mentioned in the review guidelines: https://gjs.guide/extensions/review-guidelines/review-guidelines.html#scripts-and-binaries btw, line 27 extension.js shouldn't be in global scope. It can be created inside `DictAct`.
grroot posted a review
>Maybe inside `getCommand()` (413 extension.js) we can have a more readable code. How about `return (name && this._scmds.find(x => x.name === name) || this._scmds[this.scommand]) ?? this._scmds[0];`? > And it would be much better if `ldocr.py` could be hosted on `pip` as we mentioned in the review guidelines: btw, line 27 extension.js shouldn't be in global scope. It can be created inside `DictAct`. Fine, the future uploaded version will not include `ldocr.py`.
JustPerfection posted a review
Yes, it's better. Thanks!