[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-10264: ------------------------------------- I don't see how that would introduce a dependency to the maven stuff any more than now. The idea here would be to make the project examples wizard centric. Having the maven project examples extending specific behavior to a base wizard is no different (in theory) than having a dedicated maven import job implementation, as you have today. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10264: ---------------------------------------- Description: In the wake of JBIDE-9776 and JBIDE-10140, it turns out that, in order for us to contribute 5 new wizards to the "New " menu under the Jboss perspective and in the "New project" section of JBoss central, "project examples" based projects should be created via a Wizard implementation from the get go. Current project examples workflow involves : - displaying a form dialog : to display missing runtimes and let the user install/download the required runtimes - launching a workspace job, which in turn : * downloads the example * does the actual project import (launches a wizard for maven archetypes) * resolve quickfixes Ideally, all these steps would be part of a single wizard, spanning one to 3 pages (depending on the complexity/requirements of the examples). Everything contributed by the form dialog would be replaced by a wizard page, which would bring consistency to the UI. The intent is not to add dependencies to project example for specific examples but to make it possible for examples to add a wizard page or more. This of course also needs to change the project example UI to use a wizard to begin with. I'm aware this is not a simple task to refactor the existing workflow to such an infrastructure but ultimately, that would allow us to easily contribute new project wizards to the IDE in a standard way. Current target is 3.3.0.Beta1. Snjeza, WDYT? was: In the wake of JBIDE-9776 and JBIDE-10140, it turns out that, in order for us to contribute 5 new wizards to the "New " menu under the Jboss perspective and in the "New project" section of JBoss central, "project examples" based projects should be created via a Wizard implementation from the get go. Current project examples workflow involves : - displaying a form dialog : to display missing runtimes and let the user install/download the required runtimes - launching a workspace job, which in turn : * downloads the example * does the actual project import (launches a wizard for maven archetypes) * resolve quickfixes Ideally, all these steps would be part of a single wizard, spanning one to 3 pages (depending on the complexity/requirements of the examples). Everything contributed by the form dialog would be replaced by a wizard page, which would bring consistency to the UI. I'm aware this is not a simple task to refactor the existing workflow to such an infrastructure but ultimately, that would allow us to easily contribute new project wizards to the IDE in a standard way. Current target is 3.3.0.Beta1. Snjeza, WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10264: --------------------------------------------- Following dialogs is shown for basic project example: 1) project example choice 2) details about "missing requirements" 3) wait for download (can be put in background) 4) open quickfix dialog 5) "open the readme.*" Thus project examples even without maven have several steps. dependency to m2e can be fixed by extensions point providing "UI" for specific example types. Any issue concerning "having UI block while downloading" can be solved by providing a "go to background" for the wizard and once it has finished donwloading showing a dialog reporting download have completed and we are now going to import + open readme.whatever (unless user cancles) is worthwhile to "guide" the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10264: --------------------------------------- Will I create a wizard in the following way: - Page 1 The Project Example wizard - project example choice (1) - JBoss Central doesn't need this page because project examples are shown in the Project Examples section of the JBoss Central editor JBoss Central - details about "missing requirements" (2) - Page 2 The Project Example wizard - details about "missing requirements" (2) JBoss Central - nothing - Page 3, 4, ... project examples contributions (currently, only mavenArchetype would have those pages) - the last page "open quickfix dialog" (4) - this page wouldn't be accessible until the user downloads/builds a project example "open the readme.*" (5) can't be added to the wizard because it is opened in a separate view/editor "wait for download (can be put in background)" (3) - would be executed when the user clicks Finish Does this mean we have to add the "go to background" checkbox to the first page of the wizard. If the user checks it, the wizard would be closed when he clicks the Finish button and dialogs will be being opened as before? Will I contribute wizard pages necessary for the mavenArchetype project example? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10264: --------------------------------------------- Added UI Mockup: <wizardsuggestion> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10264: --------------------------------------- I have a few questions: 1) The mockup doesn't show the first page when calling the Project Examples wizard using Help>Project Examples. Would it be as it is now? 2) If a project doesn't have any requirements, the Project Examples Requirements page wouldn't be shown. If they are satisfied, the Project Examples Requirements page would be shown with the "green checkmark" (JBIDE-10691). Right? 3) Why wouldn't we set the QuickFix/Readme checkboxes to the first page and remove the last page? 4) If there is a Quick Fix, would it be on the new wizard page or in the dialog as it is now? readme/cheatseet have to be separated 5) I am not sure what page you mean when saying Page 3 or 4. Do you mean the page I mentioned or a page in the mockup? I can try to solve this, but it would be good if you would know an example of an Eclipse wizard that works this way? I haven't succeeded to find any wizard that goes to the background and gets back at some point. Wizards use a modal dialog. What will we do if the user opens some other wizard or a modal dialog when our wizard should be shown again? 6) The page containing "project name, package, ..." is specific for maven archetypes. It should be added as a contribution to o.j.t.maven.project.examples if we don't want to introduce maven dependencies to the project examples. The mockup seems to be created to solve project examples of the mavenArchetype type when they are called from JBoss Central. I have understood that this jira requires creating a wizard that could be used for any type of project examples and could be used from JBoss Central as well as using Help>Project Examples. As to the project examples of the mavenArchetype type, the problem has been solved by JBIDE-9776. It would be enough to make JBoss Central not to open the Project Example dialog for those project examples that have the "wizard" tag, but to call their implementation method directly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10264: --------------------------------------- OK. The details (requirements) panel can also be removed. I don't think that is important. There is also a problem when adding this as a separate wizard page. Let's say we start a project example that is not of the mavenArchetype type from JBoss Central (the problem exists in any other case, but this is the easiest one to explain). We have two pages (or three when including Quick Fix as a wizard page): Page 1 - Requirements Page 2 - a page with these two checkboxes On the Page 1, before downloading we don't know if the Page 2 (or 3) will appear at all. Would we enable the Next button on this page? Would the Next/Previous buttons exist at all? If we enable Next, it could happen the following: - the user clicks it - the project example is downloaded and we see that there aren't any errors or readme/cheatcheet files We should finish the wizard allthough the user hasn't clicked Finish. If we disable Next - the user clicks Finish - the project example has been downloaded and we see that there are errors or readme/cheatcheet files We need to show a new page allthough the user clicked Finish. In my opinion, it is better to move these two checkboxes to the first page. The Quick Fix is a wizard too. We could move its wizard page to our new wizard. The problem is that the wizard wouldn't finish the project build and we wouldn't be able to determine the state of the Next button on the previous page (as previously described. Now, the Page 3 exists only for the project examples of the mavenArchetype type. As to all other project examples, the Page 3 doesn't exist and we can't start download on that page. It would start on the Page 1 (for JBoss Central) or Page 2 (Help>Project Examples). As to project examples that contribute a wizard page(s), the download would have to be delegated to the contributed wizard page. A cheatsheat/readme is opened in a view/editor. It can't pop-up. The Quick Fix is a wizard that can pop-up, but the user can disable it. There are, at least, 4 cases: - project examples that don't contribute some page and start from JBoss Central - project examples that don't contribute some page and start using Help>Project Examples - project examples that contribute some page (mavenArchetype) and start from JBoss Central - project examples that contribute some page (mavenArchetype) and start using Help>Project Examples Each of these cases would have to have different pages. There would also exist wizard pages depending on whether requirements/readme/cheatsheets/quickfixes exist. That is OK if we treat this mockup as a simplified mockup for special case. IMO, creating this wizard would have some advantage for project examples of the mavenArchetype type, but that is already solved by adding the wizard tag to the project examples file (JBIDE-9776). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10264: --------------------------------------- We will have a separate page related to requirements. I am talking about the page that only contains the QuickFix/Readme checkboxes. That is the page on the up-right corner of your mockup. If you are talking about JBIDE-10421, it is fixed. Yes, they are there, but shouldn't show up if there aren't either errors (Quick Fix) or readme/cheatsheet. We have previously agreed that the page doesn't need to show up in this case. Does this mean that you still want the page to be shown although there is no any quickfix/readme/cheatsheet? We will have a separate wizard page having 0, 1 or 2 checkboxes? If you think so - OK, I will do it, but I still do not see any reason why not to set that on the first page if we want to make the UI easier. The user will finish the wizard with Next or he will get an empty page at the end, saying "This wizard has been finished". On this page, the user would need to click Finish that wouldn't do anything, but close the wizard. Is that what you want? If the user doesn't get any error or Quick Fix dialog, everything is fully imported. Re Run As (https://issues.jboss.org/browse/JBIDE-10218), we could add yet another checkbox "Select imported projects in Package Explorer" (true by default) We can remove the Project Example dialog for those project examples that have the wizard tag (mavenArchetype) so that the mavenArchetype wizard can be independent. Archetype wizards work this way when calling from the Create Projects section (JBIDE-9776). Yes, we can't show errors until the project is built. That works for all project examples no matter if they are started from JBoss Central or using Help>Project Examples. The user can disable showing this dialog. See https://issues.jboss.org/browse/JBIDE-10264?focusedCommentId=12663905&... The Pages 3 and 4 are contributed pages and exist for Maven archetype only. Yes, the mockup describes special cases of the project examples - the project examples of the mavenArchetype type that are started from JBoss Central. The mavenArchetype wizard (or the contributed page in our new wizard) will download the project example content. Project examples don't depend on m2e so they can't know what this wizard (or the wizard page) will do. They, maybe, don't need anything to download (if the archetype has already been downloaded), but to create a project according to it. Yes, that is the difference. I think we agreed about the first page (selecting project examples starting the wizard using Help>Project Examples). However, the maven archetypes are different. They require adding a contribution page to the wizard that will import project examples. The mockup doesn't show that. It shows only the flow when importing a project example of the mavenArchetype type. For instance, the mockup requires the Project Examples to download mavenArchetypes which is not possible. The Project examples doesn't depend on m2e and can't download any archetype. I agree that we improve the project examples. However all the issues you have mentioned are related to the mavenArchetype project examples. Other project examples don't allow changing of the project name. They contain the project name in the .project file (an Eclipse project) or in the pom.xml (an ordinary maven project). They are based on the Eclipse and Maven import action that doesn't allow changing the project name. The project description specifies what projects will be created. What would you change here which isn't related to the mavenArchetype? Could you please explain me what is "ugly and non-intuitive" using the kitchensink quickstart as an example and I will correct that? Could you tell me what problematic dialogs are for some project example that is not of the mavenArchetype type. I suggest the following: - the Project Example wizard when starting using Help>Project Examples to have an additional page - Requirements instead of the Details panel - to replace the Project Example dialog with the Requirements page in JBoss Central The page wouldn't be shown in the case of those project examples that have the wizard tag when starting from JBoss Central. These project examples would have their own wizard as it is mavenArchetype (JBIDE-9776) now. Agree to add caching. We can do this without adding new dependencies. We already have the downloading/caching procedure that we could apply to cache the project example archive. However, that wouldn't reduce the delay when starting a project example the first time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10264: --------------------------------------- The Requirements page won't show up if all requirements are satisfied when using Help>Project Examples When starting from JBoss Central, I think, some dialog needs to appear primarily to ensure the user didn't click any wrong project example. I thought that page was a simplified page contributed by Maven archetype. All the pages have the same title and project name so that it is difficult to see if it is a separate page. The problem is that we use archetype page from m2e that already includes output directory/workingset properties. If we add this page, those properties will be shown twice for project examples of the mavenArchetype type. We don't know what a contributed page will show and can't decide if we will show the output directory/workingset page or not. Or, you mean that we need to add yet another tag? Or we need to create maven archetype page from scratch and remove those properties? In JBIDE-10421, I suggested to add the Preferences link. Since there weren't any other suggestions, I implemented it. IMO, it is rather than complicate the wizard by adding a new page. The most of the users won't use those properties, and those who will want to change them, will be able to do that using the link or standard preferences pages. So this page needs to be shown no matter if a project example has been imported correctly or not? When everything is imported correctly and there aren't readme/cheatsheets, the user will only be able to click Finish. The Back button has to be disabled? Right? The Project Example dialog shows up when clicking some tutorial/project examples in the Project Examples section of JBoss Central. The mavenArchetype wizards in the Create Projects section have been implemented so that they start a project example without showing the Project Example dialog (JBIDE-9776). They differ from other project examples because they have the wizard tag in the project xml file. What I suggest is that those project examples that have the wizard tag (mavenArchetype currently) start without showing the Project Example dialog even if they are added to the Project Examples section. We can still add a few entries to the Create Projects section, otherwise it will get bloated. Or JBIDE-10652 is related to the Create Projects section? I have expected that we define this wizard no matter of the project examples type, contributed page(s) that would be used from JBoss Central and using Help>Project Examples. Anyway, we have to define a contributed page(s) API. The mavenArchetype project examples is just one special case. If we implement the git project examples (JBIDE-8452), they will also have a contributed page(s). We don't know how they will look and what they will do; we only need to define API for them. Yes, we have to define APi for contributed page(s) no matter if they are contributed by mavenArchetype, git, svn ... If you mean output directory/workingsets, I have given my opinion above. Already not allowed for the standard project examples. Ok. Agree that we add the Requirements page. This is, IMO, better that it will be when we create this wizard. As to the previous discussion, when implementing the wizard, the user will have to wait (or cancel the wizard) for project examples to be downloaded and built. You have agreed this to stay the same. I don't see what will be changed. A readme is opened in the editor and a cheatsheet in the view no matter how we do that. I don't understand. We can't change the steps. The Project Example dialog that we get when starting project Examples from JBoss Central has been created using the Forms API as well as the JBoss Central editor. I agree that we replace it with the Requirements page since no any dialog related to the project examples uses the Forms API. Currently, the user imports the kitchensink project example from JBoss Central with two clicks: - the kitchensink entry in the Project Examples section - the Start button in the Project Example dialog The user can send "downloading and building a project example" to the background and work something else until the project example finishes its work. If we add all the pages you suggested, the user will have to do the following: - click the kitchensink entry in the Project Examples section - click Next in the Requirements page - click Next in the Ouput Directory/WorkspaceSet properties page - wait for the project example to be downloaded and built (which could take a long time and the user wouldn't be able to do anything else) - click Finish on the page with quickfix/readme/cheatsheet checkboxes Could you please tell me what the improvement is when using this solution? No, you didn't understand me. I propose the following: When starting a project example using Help>Project Examples, we would start a wizard that would have two pages: Page 1 - improved current page Page 2 - Requirements page ... - contributed page When starting a project example from JBoss Central, it would skip Page 1 and start with the Requirements page (Page 2). If the project example has the wizard tag, it would skip the Requirements page and go directly to the contributed page (as mavenArchetype when starting from the Create Projects section). This way, we would solve several issues: - the project examples that have a contributed page(s) would be wizardified (mavenArchetype) which is requested by this jira - the project examples that have a big archive would be able to be executed in the background What else would have to be determinated is the following: - is it necessary to add output directory/workinkset properties page (already exists in the maven archetypes pages) If you want we to add it to other types of project examples, we would have to add a tag (skipOutputDirectory for example) saying that showing this page is unnecessary (for all the mavenArchetype project examples, for instance) - whether to implement the last page with checkboxes or not I will implement it if you insists, but we will loose the "download in background" advantage -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10264: --------------------------------------- OK. It will be always shown. Because we are using m2e archetype page that already includes those properties. ...but doesn't create a separate page for those properties. The user that doesn't use those properties doesn't need any additional click. We can add those properties to the Requirements page after the user has chosen a project example on this page. The properties wouldn't be shown for mavenArchetype or a project example with the skipOutputDirectory tag. OK? OK The contributed page(s) will have to implement some interface that contains the downloadContent() method (or something similar it). OK. The last page prevents us from implementing download correctly and requires an additional user action (click Finish). As to the "select projects", we can select it without the page. We select it when a project example is downloaded and built. Can be controlled by a property. OK. The only difference would be the existence of Page 1 when using Help>Project Examples (project example choice). When starting from JBoss Central, we go to the Page 2 (Requirements) directly. Currently, the mavenArchetype project examples show the outputdirectory/workingset properties. We somehow have to skip showing those properties in the standard wizard pages when handling a mavenArchetype project example. Agree. I suggest the following: - Page 1 - project example choice (this page is skiped when starting from JBoss Central) - Page 2 - Requirements - includes output directory/workingset properties (these properties are hidden for some project examples - mavenArchetype, for instance) - contributed page ... If a project example doesn't include any contributed page, the wizard will always finish on the Page 2. If there are contributed pages, they will do the download. When the wizard finishes, we open the Quick Fix dialog, readme/cheatsheet and select a project(s) if the user required that. OK? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10264: --------------------------------------------- but m2e archetype are not used/shown when we aren't working with archetypes. He can press finish and never see that page. Then the page looks different from maven than examples - unnecessary complexity IMO. I disagree with this but fine skipping that last page. don't think this should be done - should just select the projects imported by default. Makes it nice and clear what got imported. Yes. Yes? if "no additional pages" add the page for output directory for the examples. Agree. I suggest the following: I suggest: Page 1 - project example choice (this page is skiped when starting from JBoss Central) Page 2 - Requirements if contributed pages: else Page 3 - includes output directory/workingset properties. (this page is optional since its all defaulted so pressing finish on Page 2 hides this completely) If a project example doesn't include any contributed page, the wizard will be possible to finish on the Page 2, Page 3 is optional. If there are contributed pages, they will do the download. Yes - except now I don't see where we put the checkboxes for these things (quickfix, cheatsheet and projects..) so I guess these should be defaulted. I've added a workflow showing this. Could also simply when all the import is done show dialog showing those three options plus info on "Example xyz imported and ready to use". But that is what you don't want as far as I understand ;) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10264: --------------------------------------- I have created all wizard pages for a new Project Examples wizard. The wizard pages differ from the mockup so I would like to know if you agree with the following: Page 1 (for the Help>Project Examples only) !jbide-10264page1.png! I can add the "Download in the background" button. If that button isn't checked, everything will be done in one wizard (including the Quick Fix page). If it is checked, the "Ready" Project page and the Quick Fix page would be in a separate wizard that would appear when a project example has been downloaded and built. Agree? Page 2 (Requirements) - the page has been changed related to the mockup !jbide-10264page1.png! I can't add/remove widgets (fixes and their container) when they are used within a wizard page. That's why I have added a table viewer. All requirements are shown and those that are satisfied are checked. The user can do the following: - install a selected runtime or a plugin - call the standard P2 install action - call the Download Runtimes dialog and download any runtime (JBIDE-10691) The Requirements page will always show up when calling from JBoss Central. When calling using Help>Project Examples, it can't be shown if there is no requirements Page 3 (Location) !jbide-10264page1.png! Page A, B, C - contributed pages - won't be changed. Page 4 Ready page !jbide-10264page1.png! This page contains only one check box because the Quick Fix page is the next page. If there is the Next button, there are some errors and the user can look at Quick Fixes. Page 5 Quick Fix page !jbide-10264page1.png! Could you please comment this on? I will add logic and add the contributed pages today. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-10264 at 2/14/12 12:23 PM: ----------------------------------------------------------------- I have created all wizard pages for a new Project Examples wizard. The wizard pages differ from the mockup so I would like to know if you agree with the following: Page 1 (for the Help>Project Examples only) !jbide-10264page1.png! I can add the "Download in the background" button. If that button isn't checked, everything will be done in one wizard (including the Quick Fix page). If it is checked, the "Ready" Project page and the Quick Fix page would be in a separate wizard that would appear when a project example has been downloaded and built. Agree? Page 2 (Requirements) - the page has been changed related to the mockup !jbide-10264page2.png! I can't add/remove widgets (fixes and their container) when they are used within a wizard page. That's why I have added a table viewer. All requirements are shown and those that are satisfied are checked. The user can do the following: - install a selected runtime or a plugin - call the standard P2 install action - call the Download Runtimes dialog and download any runtime (JBIDE-10691) The Requirements page will always show up when calling from JBoss Central. When calling using Help>Project Examples, it can't be shown if there is no requirements Page 3 (Location) !jbide-10264page3.png! Page A, B, C - contributed pages - won't be changed. Page 4 Ready page !jbide-10264page4.png! This page contains only one check box because the Quick Fix page is the next page. If there is the Next button, there are some errors and the user can look at Quick Fixes. Page 5 Quick Fix page !jbide-10264page5.png! Could you please comment this on? I will add logic and add the contributed pages today. was (Author: snjeza): I have created all wizard pages for a new Project Examples wizard. The wizard pages differ from the mockup so I would like to know if you agree with the following: Page 1 (for the Help>Project Examples only) !jbide-10264page1.png! I can add the "Download in the background" button. If that button isn't checked, everything will be done in one wizard (including the Quick Fix page). If it is checked, the "Ready" Project page and the Quick Fix page would be in a separate wizard that would appear when a project example has been downloaded and built. Agree? Page 2 (Requirements) - the page has been changed related to the mockup !jbide-10264page1.png! I can't add/remove widgets (fixes and their container) when they are used within a wizard page. That's why I have added a table viewer. All requirements are shown and those that are satisfied are checked. The user can do the following: - install a selected runtime or a plugin - call the standard P2 install action - call the Download Runtimes dialog and download any runtime (JBIDE-10691) The Requirements page will always show up when calling from JBoss Central. When calling using Help>Project Examples, it can't be shown if there is no requirements Page 3 (Location) !jbide-10264page1.png! Page A, B, C - contributed pages - won't be changed. Page 4 Ready page !jbide-10264page1.png! This page contains only one check box because the Quick Fix page is the next page. If there is the Next button, there are some errors and the user can look at Quick Fixes. Page 5 Quick Fix page !jbide-10264page1.png! Could you please comment this on? I will add logic and add the contributed pages today. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-10264: ---------------------------------- Attachment: jbide-10264page2.png jbide-10264page4.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-10264: ------------------------------------- The maven pages are broken. Archetype parameters are no longer set to the advanced page meaning we can't click on finish early. I'll take a look in the morning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-10264: ------------------------------------- Setting field values (project name, package, selecting an EAP runtime) in the simple page of the Maven wizard was not propagated to the advanced page (artifact id, package and group id, enterprise parameter). I committed a fix. The extra wizards have been added to fix JBIDE-10212 : we need available wizard ids to contribute new entries in the File > New menu. If you have a better solution, we can fix that for CR1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-10264. ------------------------------------ verified in jbdevstudio-product-universal-5.0.0.v201203010100M-H88-Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira