Re: profile editor dialog non modal?

It's not my ideal solution, but the preferred solution came about 
because there was pushback on the ideal solution..

This preferred solution involves showing the Context Root (CR) as an 
uneditable text field for a Web Apps Profile Type within the Profile 
Editor Dialog. there'd also be a way to launch the Server Configuration 
file Editor that will open so user can edit the context root (since this 
is where the context root property resides). It is important to show the 
Context Root propert to the user, since it is such a salient, though not 
often altered property of a web module. If this property doesn't show 
here, then the user would have to edit the property by first knowing 
where this property lives, and then launching the "Configure Server 
Specific Data" (name TBD) action on the project itself.

 The Profile Editor Dialog seems the best place for this CR property 
since it seems that users would look here when running their project 
(which is where the context root comes into play), and this property's 
proximity to the component which allows the user to pick which Server 
Configuration File they want to use to run would hint at the 
relationship of the property and the Server Configuration File.

-Ann

Vitezslav Stejskal wrote:

> Hi Ann,
>
> Ann Sunhachawee wrote:
>
>> Would it be possible to make the profile editor dialog a non-modal 
>> dialog? As the WebApps team has been working on coming up with a 
>> projects implementation, we've come up with a preferred way to solve 
>> an issue we're facing by being able to launch an editor (in the src 
>> editor area) from the profile editor dialog. 
>
>
> I admit that I am not an UI expert, but launching source editor from 
> profiles dialog sounds wierd to me. Could you describe your usecase 
> please.
> -vita
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>