Bugzilla – Full Text Bug Listing
| Summary: | Problem deploying apps which are not in the root of Orion project | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Szymon Brandys <Szymon.Brandys> |
| Component: | Deployment | Assignee: | Szymon Brandys <Szymon.Brandys> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | antonm |
| Version: | unspecified | ||
| Target Milestone: | 5.0 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 425959 | ||
|
Description
Szymon Brandys
Gosia, any thoughts on it? Anton,
the problem we have is that when we click the Deploy button we always assume that the application root is the project root folder. In example attached by Szymon the application root is one folder down.
One of the propositions to solve it is that the Deploy button is sensitive to selection and if we click it when a folder is selected then this folder will be treated as application root. This may however be a little confusing for the user if the selection was made some time before the deploy button is clicked (or for instance he is just editing a file that selected this file automatically). The other idea is to add Deploy submenu to our new context menu and made it context sensitive only there (this is however not coherent with what we do for other actions). Third idea is most brutal: we may add a submenu to Deploy action ("Deploy subfolder") that would contain duplication of all deploy actions that would always trigger the prompt which folder is supposed to be deployed.
What do you think is most intuitive for the user?
Fixed. Deploy action works with selection now. |