[QoL Features Request] Few QoL and nice-to-have features request

[Andrei-Stakov]

First of all, thank you for the wonderful development over the original one!

I don't know if these requests are already in your personal to-do list, but I'll listed it just in case you'll get some new ideas out of it.

[QoL features]

• Individual parts removal button moved next to the each parts' field rather than parts' list title bar, might be better if it was iconized to save some space.
• Individual filter clear button next to/below the dropdown filters. Might need some separators between the fields to clear any confusion if it's next to the dropdown fields.
• Parts' search keyword clear button inside the search field.

[Nice-to-have features]

• Trait requirements filter. This would be quite a task to sort tho.
• Traits description and EX tooltip shows both values for min. and max. level, separated by a hyphen ("reduced by 17%-30%"). It means database revision, which might take a while to do it.
• EX's CD and initial CD list values for min. and max. level, also separated by hyphen. Again, hefty database revision.

In the end, this was all just suggestions tho, so it's up your own discretion whether you'd work on it or not. Of course, if you do want to work on it and need some help, I'd be glad to (have no experience on webs tho).

Thanks in advance!

[rmkane]

1. The "Remove" button on the part list was added by the original developer to closely-model the UI in the game. Adding the remove next to each part sounds like a possible improvement.

2. The part trait/skill text with ranges sounds like a good idea. I just stuck with the max, like everyone else.

[rmkane]

I am going to take a look at these in the next few days.

[rmkane]

I experimented with "[i]ndividual parts removal button", but it did not look very good with the current UI. If I were to rewrite this, I would probably try some type of gesture like swiping or something... but this would only help mobile.

A clear button in the part search would be as easy as making the part search input field a true "search" input. I have an example of this here: https://jsfiddle.net/MrPolywhirl/4b79ouy1/ The UI is a responsive flex container.

I added EX skill info, but only max-stat. I am going to attempt to add per-level stats according to Dengeki if they provide that info after the 2.0 update in a few months.