Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature suggestions] #11

Open
jaeminSon opened this issue May 12, 2022 · 3 comments
Open

[feature suggestions] #11

jaeminSon opened this issue May 12, 2022 · 3 comments

Comments

@jaeminSon
Copy link

I understand that this repo mainly aims to demo albumentations, though, I thought it would be nice if following features exist.

  1. Current UI applies augmentations up to 2, though, it would be ideal if a user can apply more augmentations.
  2. If there is a download link for the current augmentation in json or yaml format (or in a code format as well!), it would be convenient!
@IliaLarchenko
Copy link
Owner

Hi! Thank you for your suggestions. But if I understand your proposals correctly, they are already implemented.

  1. There is no limit on augmentations in professional mode. If you select 2 of them, the drop-down menu for the 3rd one will appear. And so on, you can add an unlimited number of augmentations.

image

  1. Code for the current augmentation with currently selected parameters is already below the image and augmentation description. There is also a "copy" button to the right from it.

image

@jaeminSon
Copy link
Author

Thanks for your answer! I overlooked the ever-growing "Select transformation" drop down menus.

Regarding the second suggestion, I imagined a link, when clicked, a json or yaml file or a code snippet for the aggregate augmentations could be downloaded or copied (supposedly bundled with "compose" class so that users can load it with load function in albumenations). As you pointed out, individual lines can be copied but it would be convenient if the configuration of entire augmentations is available.

@IliaLarchenko
Copy link
Owner

Ok. I understand the second point now, and it should be a relatively simple feature to add. But currently, I don't actively develop or support this project, and the current version is frozen in a stable working state.

This feature is about UX improvement and not critical, so I will not change it now. But the next time when I release any significant update, I will add it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants