<p></p>
<blockquote>
<p dir="auto">the current experience of opening projects is terrible.</p>
</blockquote>
<p dir="auto">I'm <em>not</em> saying the current experience is great/can't be improved.  The issue is that Geany currently allows new-project workflows that this PR completely eliminates.  I've made suggestions that would avoid that problem.</p>
<blockquote>
<p dir="auto">it's a necessity if you want to set the other 2 values correctly.</p>
</blockquote>
<p dir="auto">Setting project basepath first is not a "necessity".</p>
<ul dir="auto">
<li>Geany currently allows the fields to be completed in any order.</li>
<li>The project name and base path can be changed independently from Project Preferences (showing that they are not related).</li>
<li>The file can be located anywhere, moved in a file manager, symlinked, whatever, like any other file, independently of the project base path.</li>
</ul>
<blockquote>
<p dir="auto">But again, this is how other editors work...</p>
</blockquote>
<p dir="auto">Other editors doing things a certain way doesn't mean Geany must also.  Geany does lots of things differently from other editors.  If other editors are so great, why use Geany in the first place?</p>
<blockquote>
<p dir="auto">what people in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="476625106" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2245" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/2245/hovercard" href="https://github.com/geany/geany/issues/2245">#2245</a> suggested - open project as if it were a directory.</p>
</blockquote>
<p dir="auto"><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="476625106" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2245" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/2245/hovercard" href="https://github.com/geany/geany/issues/2245">#2245</a> (and <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="170155125" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/1171" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/1171/hovercard" href="https://github.com/geany/geany/issues/1171">#1171</a>) suggest opening folders as if they were projects.  This PR is not close to doing that.  For instance, what happens if a user drag/drops a folder into Geany?  What happens if a user runs <code>geany /path/to/folder/</code>?  These could be implemented without touching the New Project workflow.</p>
<blockquote>
<p dir="auto">If you press cancel in the first dialog or select a whatever directory, you can customize everything in the second dialog.</p>
</blockquote>
<p dir="auto">That is not obvious at all.  Cancel usually aborts a process entirely.  So another strike against this PR.  Users who start the new project creation process have to cancel twice to truly cancel the process.</p>
<blockquote>
<blockquote>
<p dir="auto">What (technically) prevents this PR from being implemented as a plugin?</p>
</blockquote>
<p dir="auto">Geany API doesn't contain a function to open project and I don't think this function should be added.</p>
</blockquote>
<p dir="auto">Why not?  It could be useful for some project-based plugin, like Workbench.</p>
<blockquote>
<p dir="auto">Open project properties in the last step is just a convenience thing I added but I don't find essential and can be dropped if disliked by others.<br>
If desired, I could leave "Project->New.." as it behaves now and add "Project->New from folder..." with this new behavior.</p>
</blockquote>
<p dir="auto">New menu item (<em>Project / New from folder...</em>) plus no second dialog after folder selection is preferable to the implementation of this PR.</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/pull/3018#issuecomment-980808051">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ7MWDU4SLPACYDEFFDUOFVIXANCNFSM5IXHKYAA">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub">Android</a>.
<img src="https://github.com/notifications/beacon/AAIOWJ6K6DGTIBG44BG3BJ3UOFVIXA5CNFSM5IXHKYAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHJ27C4Y.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/pull/3018#issuecomment-980808051",
"url": "https://github.com/geany/geany/pull/3018#issuecomment-980808051",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>