Run/Debug profiles

Team,

I would like to ask a question about Run/Debug profiles and perhaps 
request a change.

Why are there two groups of profiles - one for Running and one for 
Debugging ? It seems that in many cases having the same profile for both 
actions would be sufficient (although I acknowledge that in other cases 
they may be different - Svata would give me good use cases, I am sure). 
So instead of having two groups, could we just have one group, and each 
profile could be used either for running or for debugging ?

The advantage would be that in cases when same or similar setting is 
appropriate for both running and debugging, setting up new profiles or 
modifying existing ones would be much simpler.

There are cases when a given profile type can be only used for execution 
or debugging, but not both - this could be solved if we added 
'properties" (methods, cookies, whatever...) to the profile, called 
canUseForRunning() and canUseForDebugging().

The impact on the UI would be the following:

- The Run menu would only have one item called Run/Debug Profiles
- The "Profile details" subpanel in the Edit Profiles... panel would 
have two checkboxes at the bottom: 'Set As Active Profile for Running' 
and 'Set As Active Profile for Debugging' (instead of just one checkbox, 
as is currently the case). One of these checkboxes could be disabled if 
the profile does not support running or debugging.

Petr