Re: ProjectFileChooser

cL wrote:
> well... you work with files that are in the project through the 
> explorer. you add files to the project through actions on the project 
> (adding will use a normal filechooser most times).
> 
> i'm not sure this is what you're asking though.
> 
Well... suppose that the user needs to locate a directory for packaging. 
  Such directory is presumably already present in the project in some 
way or another (manually added, output of a build target, ...). I don't 
think a filechooser would be a great UI in this case since it completely 
bypasses projects concepts.

Another use case: for configuration the user has to specify a source 
file (or data file), e.g. manifest, or gif image. Again, the file is 
very likely to live in project's contents. And if it is not, it should 
be, since it will become an essential part of the project after the 
configuration is done.
Again for browsing for the file, a standard filechooser is bad idea, 
since the user is likely to locate the same directories as she once 
added to the project. The user deserves a shortcut so it can locate the 
file faster.

These and other use cases should be fair easy to see if common 
development scenarios are followed.

-Svata