Hey Cyan and LMS,
I know we spoke of some of these already. Since I am actively working on contributing more install.xml's and using LML more often, I thought it might be a good idea to add the suggestions I've thought of, whether you consider them for now, later or not at all, I think these could help make LML more attractive to new users and remove the burden of feeling like it creates more conflict.
Install.xml Process
(Implemented, working) - Allow to specify full path to .xml file, since most modders mix models/textures/VCFs.
(Implemented, working) - Upon re-enabling a disabled mod or resource group that has ELS, re-ask to re-copy the specified XML's (ideally be able to set them by group just to re-copy only those to avoid replacing other addons that have already set the .xml)
LSPDFR Website
(Implemented, working) - Allow to create multiple installs on files to be able to create separate install.xml's for replace/addon vehicles or even different versions of certain addons, such as Radiance V (which right now only the oldest version can be installed with LML.)
- Allow to create multiple .xml's inside one .zip file if modders does not separate addon/replace .zip files.
UI
- Some way to see that you can double click on the mods to open the configurability. (Maybe right click and a window showing Open Mod? I just found it today! Amazing!)
- Save the columns sizes when you re-open LML
- Ability to localize it to other languages (I can contribute Spanish translation)
- Allow to maybe add/remove the author's column to the mods view window (Sometimes people put very similar names to mods and to avoid having to double click and check who made it)
(Implemented, working) - When hovering over a table, it'd be nice to be able to view the text as a pop-up maybe as sometimes this text gets lost if it is too long and the size of your screen does not reach.