Powertoys: Fluent UX: PowerRename

Created on 6 Dec 2019  路  23Comments  路  Source: microsoft/PowerToys

PowerToys should do its best to look like a system level integration. PowerRename is great but has a UX that doesn't match the OS. This shift would also allow PowerRename to respect darkmode (#887)

@itsMichaelWest did a great mockup on the Twitters of what it could look like.

image
ELIZZUZWsAEybmm

During this upgrade, i suggest we shift the UX to WinUI3 as well.

Area-User Interface Help Wanted Product-PowerRename

Most helpful comment

I made a working XAML proto based on @zeealeid's awesome UX concept for Image Resizer.

PowerRename

Dark theme:
PowerRename dark

UX alignment with Image Resizer?
It would be nice to have a common UX for these configuration/action windows within PowerToys. Since we're also working on bringing Fluent to the Image Resizer powertoy (issue #1053), aligning the two might be useful?

ImageRenamer

XAML can be found in this repo. Happy to port the right stuff over once we have a working XAML Island project.

All 23 comments

getting there :) This is the UX done in real XAML. Datagrid for files needs to be added. Need to sync with WinUI on that.

image

I think we should have the top be highest Z, middle with a middle Z and results be bottom Z

Make enter rename

@crutkas you may want to consider using the compact density for the Xaml WinUI versions of these Power Toy apps

Will there be a need for Icons for each individual PowerToy?

Power Rename appears on the context menu, so will that need a modern Fluent style icon?

image

That icon is incoming.

I made a working XAML proto based on @zeealeid's awesome UX concept for Image Resizer.

PowerRename

Dark theme:
PowerRename dark

UX alignment with Image Resizer?
It would be nice to have a common UX for these configuration/action windows within PowerToys. Since we're also working on bringing Fluent to the Image Resizer powertoy (issue #1053), aligning the two might be useful?

ImageRenamer

XAML can be found in this repo. Happy to port the right stuff over once we have a working XAML Island project.

Is there a need to replicate the Icons from the original Icon Grid in the PowerRename Xaml View?

These mock ups replace it with a text only list/grid.

I made a working XAML proto based on @zeealeid's awesome UX concept for Image Resizer.

PowerRename

@niels9001
what about switching the two pane, and have the Rename criteria on the left?

I made a working XAML proto based on @zeealeid's awesome UX concept for Image Resizer.

PowerRename

@niels9001
what about switching the two pane, and have the Rename criteria on the left?

@enricogior Yeah I guess that makes sense, it needs some re-work overall. In smaller sizes it would be nice to have the list of items at the bottom - for that the TwoPaneView is perfect.

For it we'd need to move to Xaml Islands / WinUI anyways.. not something that is planned for 1.0, right?

I think we should be good with the vertical placement of the Rename criteria an the left and the Preview results on the right. For portrait mode screens, it may be better to have them one on top of the other, but I don't think we need that in the first release of the new UI.
For sure I don't want this to be a huge project with too many dependency and slow to start, ideally it will remain C++ (haven't looked into WinUI 3.0 for C++ yet, but if it requires XAML Islands we might reconsider it).

PowerRename

Made some improvements to the earlier concepts based on @crutkas earlier feedback.

  • 'Advanced options' is now categorized in more logical groupings. Still needs some work to move away from CheckBox where not appropriate (e.g. for file exclusions) and title casing.

  • Added tooltip/flyouts when typing to show e.g. RegEx commands or the File Date Creation options.

@enricogior @crutkas Looking forward to your feedback!

image

image

image

Other than IMO true banding for the list, that is pretty fantastic.

@niels9001 looking good!
Does that mean we can expect it soon? 馃馃徎

Could the new UX support drag and drop feature? I was hoping that you can launch ImageResizer and Rename directly from task bar, than making a selection first then open from the context menu.

@niels9001 looking good!
Does that mean we can expect it soon? 馃馃徎

Waiting for WinUI to be stable enough.. moving towards WinUI and aligning UXes is on the strategy/roadmap (see wiki). Not sure what the timeline would be.

Could the new UX support drag and drop feature? I was hoping that you can launch ImageResizer and Rename directly from task bar, than making a selection first then open from the context menu.

Sounds like a good idea to me! That does mean they would have to be visible in the taskbar in the first place. I'm guessing that they currently do not show up here _because_ they cannot be triggered as standalone apps right now. See also #6538.
Very handy if you want to rename multiple files from different folders. Also thinking about their location: If the directory would be included in the renaming (as in #1391), that means you can move lots of files at once.

By the way, is #3930 still of interest?

@Jay-o-Way
it is for the new UI.

@Jay-o-Way the most recent UX concept for the WinUI version (posted a couple of comments up) tries to bring more grouping and logic in place.

Please review those to see if that matches your need. Post your feedback here so we can iterate on it and make it better!

You'll have to forgive me if I start to repeat myself, but since my other issue got closed, I believe I am alright to add my idea here...

  • Personally, I don't like things to be hidden when it's not necessary. So I want all of the options always visible.
  • I would use "Apply to:" in stead of "Exclude" check boxes.

    Apply to

  • [x] &folders

  • [x] file &names
  • [ ] file e&xtensions
  • [x] include &subfolder items

I believe these four are logical and are the minimum of controls needed to achieve every option.
As shown, I think it would be good to add &access keys to the check box labels.

@Jay-o-Way
I agree with the approach, we only have to validate if those cover all the needs.

In the concept of 1 September, I don't see any Help link yet.

If the text on the button says Rename, but the action is "Rename and close", then that's not correct. Would it be better to update the text to match the action, or to change the action to match the text? See also #628 I think it's best to connect the action to the Apply button and leave the closing to the X in the title bar, Esc or _maybe_ an extra Close button.

Coming from ~#7218~ #628, the request there is to not close after Rename action. That does mean some kind of visual confirmation would be necessary, because the user needs to see that the action is done, and we can't rely on the File Explorer window being in field of view.

Was this page helpful?
0 / 5 - 0 ratings