Review Request 127827: open/fetch project: restore broken workflows after native file dialog port

[René J.V. Bertin]

> On May 4, 2016, 1:07 p.m., Aleix Pol Gonzalez wrote:
> > Maybe the solution is to just have files there? i.e. either CMakeLists.txt/*.pro or .kdev4 files
> > 
> > An extra step sounds a bit much, especially since often one doesn't remember if the .kdev4 file is there or not.
> 
> Milian Wolff wrote:
>     We must be able to open folders that don't contain any project file (e.g. for custom make file or generic projects). This won't work then.

I don't think I ever realised that one could open a project through its directory, though I guess I knew because I do have a few that are just that, directories without Makefile or anything of the sort.

I agree with Aleix that imposing an additional step isn't something I'd be too happy with.
One solution would be to add an additional button to the dialog, "open current directory" (or simply `"here"`?). I suppose that'd be possible with the KDE dialog, less so if the native file dialog allows to add buttons.

If all else fails there's always the possibility to add a "*.*" selection, and then get the directory to open from the selected file.


- René J.V.


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127827/#review95157
-----------------------------------------------------------


On May 4, 2016, 12:32 a.m., Sven Brauch wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/127827/
> -----------------------------------------------------------
> 
> (Updated May 4, 2016, 12:32 a.m.)
> 
> 
> Review request for KDevelop and Kevin Funk.
> 
> 
> Repository: kdevplatform
> 
> 
> Description
> -------
> 
> The native dialog has two significant restrictions: it cannot be embedded, and it cannot be told to accept both a directory _or_ a file at once. The previous change to the open project dialog broke the (important) option to open a directory as a project. This fixes that through introduction of an extra step: you select the method you want to open your project with first. This has the advantage of making it more clear to the user what the options are; many users are still not aware you can simply tell KDevelop to open a folder as a project.
> 
> I'm well aware this is far from an optimal solution, but right now it's just broken and this is certainly an improvement over the current situation. Better ideas welcome.
> 
> 
> Diffs
> -----
> 
>   shell/CMakeLists.txt 83d4db0 
>   shell/openprojectdialog.h d39ff8e 
>   shell/openprojectdialog.cpp 9ccca43 
>   shell/openprojectdialog.ui PRE-CREATION 
>   shell/openprojectpage.h 1e0ff60 
>   shell/openprojectpage.cpp 42d836f 
>   shell/projectsourcepage.h a45ee19 
>   shell/projectsourcepage.cpp 43ab6e9 
>   shell/projectsourcepage.ui 79699aa 
> 
> Diff: https://git.reviewboard.kde.org/r/127827/diff/
> 
> 
> Testing
> -------
> 
> can open from CMakeLists.txt, from foo.kdev5 or from a folder; also fetch works again (before simply random stuff happened)
> 
> 
> File Attachments
> ----------------
> 
> the added dialog
>   https://git.reviewboard.kde.org/media/uploaded/files/2016/05/03/7b6cdfc2-c4d7-4394-9a39-2ccc923f28fa__Screenshot_20160504_001810.png
> 
> 
> Thanks,
> 
> Sven Brauch
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160504/4b408d9b/attachment.html>