Re: ProjectFileChooser

ok. well, we don't have anything like this spec'd out right now but we 
can get to work on it shortly. :-) Jano and i will get all the 
requirements together and get something out for review. it may not be 
done until after the usability test... let me know if you're in a hurry 
for it.

cheers,
cL

Ondrej Rypacek wrote:
> Svata Dedic wrote:
> 
>> 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. 
>>
>>
> I'll give the specific case I need it for.
> In the Manifest Property Editor dialog, there is a button "Browse..." . 
> If the user presses the button a "File Chooser" dialog should pop up in 
> which the user choses some file as a source for the manifest. The 
> manifest should be preferably chosen from the project resources, maybe 
> it can be provided by other BT. And it would be nice too, if the file 
> was not present in the project yet to have the oportunity to select any 
> file on the local disc and add it to the project right away.
> 
> Using raw FileChooser to select something from the disc bypasses the 
> project altogether (as Svata wrote).
> Projects introduce quite a different view (abstraction layer) on the 
> files user works with, interaction with the raw disk filesystems should 
> probably be reduced only to adding new items to project; everything else 
> should be on top of projects.
> 
> 
>>>
>> 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.
> 
> 
> Did I get it right that there is no such thing, yet?
> If so, isn't there some simillar project-file-chooser written by some 
> module (Svato?) that could be adopted by the infrastructure? I think 
> that choosing "something from the project" is such a common thing that 
> it deserves a support. Not only it'll save work but also all the dialogs 
> will look the same.
> 
> -Ondra
> 
> 
>>
>> -Svata
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

-- 

ui.netbeans.org
interaction designer
[email protected]