<p><a href="https://github.com/sagarchalise" class="user-mention">@sagarchalise</a> yes I believe they have different use-cases, and its my opinion that the file manager part of tree browser is inappropriate for a plugin in an IDE.  If it was part of a refactoring plugin it would make sense, but not simply for file management.</p>
<p>If it was just a browser as its name says, it would still fit the use-case of <a href="https://github.com/vfaronov" class="user-mention">@vfaronov</a> of having many directories visible at the same time, and in that role could replace file browser so there is not a confusing proliferation of core plugins.  But it should be developed in that role within G-P until shown to be safe and reliable, not moved to core as an unmaintained unknown quantity.</p>
<p>Also if it was moved to core <a href="https://github.com/geany/geany/pull/1414" class="issue-link js-issue-link" data-url="https://github.com/geany/geany/issues/1414" data-id="210505893" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#1414</a> would need to be updated to include it.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1485#issuecomment-298851362">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ7FqsnYaJpKAGr5sTJcSQbiHlCWjks5r2Dr5gaJpZM4NNoli">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ___t31_FwX9dHLS0_9ez4XyYygRks5r2Dr5gaJpZM4NNoli.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/1485#issuecomment-298851362"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #1485: @sagarchalise yes I believe they have different use-cases, and its my opinion that the file manager part of tree browser is inappropriate for a plugin in an IDE.  If it was part of a refactoring plugin it would make sense, but not simply for file management.\r\n\r\nIf it was just a browser as its name says, it would still fit the use-case of @vfaronov of having many directories visible at the same time, and in that role could replace file browser so there is not a confusing proliferation of core plugins.  But it should be developed in that role within G-P until shown to be safe and reliable, not moved to core as an unmaintained unknown quantity.\r\n\r\nAlso if it was moved to core #1414 would need to be updated to include it."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1485#issuecomment-298851362"}}}</script>