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

Use "hamster" instead of "hamster-gtk" for the default appdirs #180

Open
Takios opened this issue Apr 23, 2017 · 2 comments
Open

Use "hamster" instead of "hamster-gtk" for the default appdirs #180

Takios opened this issue Apr 23, 2017 · 2 comments

Comments

@Takios
Copy link

Takios commented Apr 23, 2017

Hey,

in my opinion, it would be better to use "hamster" instead of "hamster-gtk" for the default appdirs.
This allows people to easily use/try out different hamster clients without changing their options.
The more common use case I can think of are people alternating between using the gui or the cli.

At the moment, people using hamster-gtk but then switching to hamster-cli would be presented with an empty database before switching their options.

If you agree to this notion, I'd be happy to prepare PRs for hamster-gtk and hamster-cli.

Greetings

@elbenfreund
Copy link
Collaborator

Hi Takios,

this is definitely something that needs to be addressed and I got it on my radar for a while. The current situation however is somewhat deliberate to keep different clients separated as much as possible during development right now.

Once we are preparing the first major release this will need to be revisited and consistent approach to be chosen.

@elbenfreund
Copy link
Collaborator

Hi @Takios
I just wanted to reference this comment in a slightly different context that may shine some light on how I personally this we should handle this.

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

No branches or pull requests

2 participants