Why complicating something that was previously very simple for the average user. Experienced people can and have already been able to set everything exactly manually, if necessary directly in the Ini.
More advanced plugin installation
Moderators: white, Hacker, petermad, Stefan2
Re: More advanced plugin installation
Re: More advanced plugin installation
As already said, integrating the TC Plugin Manager would satisfy most needs.
I only install and manage plugin settings with this tool since many years.
There was never a need to manually edit the ini files.
I only install and manage plugin settings with this tool since many years.
There was never a need to manually edit the ini files.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3672)
TC 11.03 x64 / x86
Everything 1.5.0.1378a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.78
QAP 11.6.3.3 x64
TC 11.03 x64 / x86
Everything 1.5.0.1378a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.78
QAP 11.6.3.3 x64
Re: More advanced plugin installation
Which part of my suggestion is making things more complicated in terms of UI/UX than currently? Does anybody have to tick any checkboxes or set a detect string? Of course not. If the additional GUI elements are distracting or whatever, they can be hidden behind an "Advanced" or "Options" button or something.
NB: We should avoid cluttering this thread with more off topic stuff further.
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Re: More advanced plugin installation
Considering the feedback in this thread I changed the mockup of Form2.
Here's what it could look like when collapsed.
After pressing the "Advanced" button, it could look like this.
To address the potential security concerns of the first proposal, I added a "Read Interface Data From Plugin" button which tells TC to get the data from the plugin only on user request. TC should still automatically fill out all fields that can be read from pluginst.inf, e.g. plugin name, version, description, the packer extensions of a WCX plugin etc.
I also added the new links to the first post.
Regards
Dalai
Here's what it could look like when collapsed.
After pressing the "Advanced" button, it could look like this.
To address the potential security concerns of the first proposal, I added a "Read Interface Data From Plugin" button which tells TC to get the data from the plugin only on user request. TC should still automatically fill out all fields that can be read from pluginst.inf, e.g. plugin name, version, description, the packer extensions of a WCX plugin etc.
I also added the new links to the first post.
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror