In K5 it was clear what a project was and how it should be used as part of my work-flow. It provided a logical collection of related code in the same way as Visual Studio still does. As such I could create a project, define its contents, add files and tools to it and remove them from it - I could even delete a project if I wanted to.
In K6 this fundamental idea of a project has gone. I have tried RC1 for the last 3 weeks but just can't see the point of it and have had to move back to K5 in order to get some work done. What I'd like is if someone could explain what a project is and how it fits into the work-flow of development. What were the aspects of the version 5 project concept that were wrong and how does the current design improve them?
I know that there is another thread about projects but that discussion is about fine detail. I don't want to know about whether I can have 1 or 1000 projects or files open, or that I couldn't do 'x' in K5 but I can in K6 - I want to know about the concept of a project. The current K6 has the feel of something that's been created simply to get round some of the limitations and idiosyncrasies of the K5 project and the whole design intent of the original project concept forgotten.