https://bugs.kde.org/show_bug.cgi?id=386200
--- Comment #11 from Ivan Čukić <ivan.cu...@kde.org> --- Don't apologize for the post length - you explained very well your use-case. > Well my purpose will not be to convince you in something ;) > It's your application and so your decision how to do the things :) This is not how I like to do things - at least not with Vaults. Users and their desires are quite important, and I try to be open to ideas as long as they don't significantly lower the security. And, in this case, I don't think the import feature has a big negative impact on security. So, convincing me has a purpose :) The answer to Nate's question of why spend time to implement something while not exposing it in the UI is simple - 1) to help the users who asked me for the feature and are willing to roll up their sleeves a bit 2) to test the feature on those users. Thanks to this, I already god some feedback on the wizard. @Nate if you have an idea on how to expose this feature in a nice way - without making it into a yet another button in the applet, I'm listening :) I had two ideas and I'm not sure about either of them: - add 'Import existing vault' and 'Create a new vault' (for completeness) to the applet-right-click menu - add the option to import existing vault to the creation wizard which would be more streamlined, but bad usability-wise (IMO) -- You are receiving this mail because: You are watching all bug changes.
