-
Notifications
You must be signed in to change notification settings - Fork 19
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
Deprecate in favor of project manager #95
Comments
Indeed I had not seen how much progress the Project Manager's settings had done. |
I thought the empty tree problem was something wrong in project-plus, so I switched to project-manager today to see if the empty tree problem was fixed and it was not. Seems to be an atom thing. But in doing so I see how much progress has been made on project-manager. It seems to fulfill all the needs of a project management package. It looks like project-plus may not be needed with all of the functionality that is in project-manager. Thank you for all the great work on project-plus. |
Same feeling here. However I downgraded back to 1.16 due to this bug. |
Agreed. I now use Project Manager. Thank you :) |
Going to close this issues in favor of https://github.com/danielbrodin/atom-project-manager/issues/345 |
A lot of time has past and Project Manager (what I based this project on) now has most of the functionality of this package (including usage of atom-project-util which contains the project in-window switch by myself).
I'm seeing tons of issues crop up of this package not working for various reasons and while it still happily works on my machine (insert amusing "works here" comment) I'm not seeing a reason to not officially deprecate this package.
Thoughts?
If you're actively using this package, would you see if project-manager can satisfy how you use project-plus ?
The text was updated successfully, but these errors were encountered: