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

Per-project file/folder associations #463

Open
deakjahn opened this issue Aug 11, 2024 · 5 comments
Open

Per-project file/folder associations #463

deakjahn opened this issue Aug 11, 2024 · 5 comments

Comments

@deakjahn
Copy link

Is it possible to get per-project associations? VS Code makes it easy with its settings structure but in Android Studio and other related IDEs? Even if it would require manual editing of XML settings files... I often have specific needs in different projects that I don't want to pollute a global settings table with, or can even contradict each other in different projects.

@mallowigi
Copy link
Collaborator

I have it in mind, it will come in a future release, but I don't know when.

@deakjahn
Copy link
Author

@mallowigi I might be tempted to look into the source but you can be much quicker to answer than discovering the whole structure there (especially as I never worked on AS plugins before, VS and VS Code and some others, yes): are the associations read once when the IDE starts? I have the suspicion that reading a per-project file wouldn't be that hard but those associations should be unloaded when a new project is read.

@mallowigi
Copy link
Collaborator

The bundled associations are loaded from a XML file, then loads the user's settings. Loading from the Project Settings requires to develop a PersistedStateComponent project based, it's not that easy to implement.

Besides I also need to develop the UI pages to define such a thing.

@deakjahn
Copy link
Author

Yep, that's why I said that something as simple as an .atom_icons source file, if present, with a somewhat documented XML format (could be as simple as a single example file) could be just as good. All your users are programmers, by definition, after all.. :-)

@mallowigi
Copy link
Collaborator

Yes but you'd still need to create the PersistentStateComponent either way.

Anyway if you want to tackle this, be my guest, I am already in the middle of another feature and I don't have a lot of time for side-projects...

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