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

Projectorganizer: Add external directory is grayed out #329

Open
derba opened this issue Jan 13, 2016 · 2 comments
Open

Projectorganizer: Add external directory is grayed out #329

derba opened this issue Jan 13, 2016 · 2 comments

Comments

@derba
Copy link

derba commented Jan 13, 2016

  1. Click Project/New and create a new project. Try to add an external directory. It will fail, as its button is grayed out.
  2. There is a message that file patterns are to be set first. Poor user may think that is the reason, but actually it has nothing to do with it.
  3. Add a new file, e.g. untitled.c in your project. Save it. Still nothing changes.
  4. Oh, there is a "Reload all" button in Project side bar. Click it. Voila, you can add external directories.
  5. Now you can remove the untitled.c, if you do not need it. And actually that is my case. The reason for leaving the actual project directory empty is that I want to have a project with 2 apps and their libs. And I have other projects, with somewhat overlapping content. So they cannot be moved to a Geany project directory. (Unless I symbolic/hard linking each and every file to the project root directory. Dir symlinks do not show up in Geany project organizer, though.)
  6. Oh, no, I removed untitled.c and I cannot add external directories, anymore. The existing ones are fine, though.

Poor user thinks that Projectorganizer is useless. Though it is cool, just some scenarios are not tested.

@techee
Copy link
Member

techee commented Jan 13, 2016

OK, this is quite an esoteric use case but you are right, there's no reason for having the "add external directory" grayed out. Will fix.

@techee
Copy link
Member

techee commented Jan 15, 2016

@derba Alright, I remember now why I did it this way - the reason is psychological. I remember how Enrico and Frank were exposed to my plugin for the first time (without reading the manual which is what everyone else will do too) and the thing they wanted to do was to add files to the project. So they clicked the "Expand All" button (hey, there's a nice + button, this will surely add the files to the project!) and nothing happened. Conclusion: the plugin doesn't work.

The thing is that the plugin adds all files satisfying the given patterns into the project automatically and I'm a little worried people might do crazy things like adding stuff outside the project directory just because they don't see any files initially. So this is why there's the message and the buttons are disabled.

The main purpose of the plugin is to show files in the project directory - the external directories thing is just an additional (but often useful) feature. Your use case is pretty specific and actually you don't want a project with no files at all and lots of external directories - you want a project consisting of several subprojects - and this will be best achieved by making the symlinks (which should work now).

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

3 participants