Summary: | The Default project configuration | ||
---|---|---|---|
Product: | [Developer tools] kdevplatform | Reporter: | Sphere <sphere1952> |
Component: | appwizard | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sphere
2003-06-19 23:07:03 UTC
I don't think kdevelop should be doing this - this is something that the user should be setting up. I know that I want my project to be installed in my live system (even in a debug mode), because I know what I am doing with my system. Other shops have a completely separate test system that they'll install to. This is really about what happens when we try and _install_ a project. It's here that the user should see an appropriate warning (that could be turned off btw) as has been suggested in another wishlist item I believe. IMO we don't need this. I know the problem that newbes have problems with installing because they don't know how to specify the installation destination, BUT there is good documentation for kdevelop 3 that explains everything (look in KDevelop on the right sitebar the Documentation "QT-Designer 3 and KDevelop 3"). If a user goes though such a tutorial he knows what to do to set the destination path. So I close this BR as WONTFIX - we can reopen the bug if more users wants this behaviour. btw: it is possible to open a specified file directly after project generation. We could open a README.devel that contains information about how to set installation destination and other important things. What do you think about that??? |