[ https://jira.jboss.org/jira/browse/JBIDE-3916?page=com.atlassian.jira.plu... ] Denis Maliarevich updated JBIDE-3916: ------------------------------------- Description: Steps to reproduce: 1. Select any css file in Package Explorer by mouse click. 2. Notice that there is no CSS Class Dialog icon in the toolbar. 3. Right click on the selected css file -> Popup menu will appear with "Open CSS Dialog" menu item. The problem is in the mismatch between icon presence and menu item presence. If there is a menu item then there also should be a toolbar icon to open CSS Class Dialog. was: Steps to reproduce: 1. Select any css file in Package Explorer by mouse click. 2. Notice that there is no CSS Class Dialog icon in the toolbar. 3. Right click on selected css file -> Popup menu will appear with "Open CSS Dialog" menu item. The problem is in the mismatch between icon presence and menu item presence. If there is a menu item than there also should be a toolbar icon to open CSS Class Dialog. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3916?page=com.atlassian.jira.plu... ] Denis Maliarevich commented on JBIDE-3916: ------------------------------------------ I've found another situation: 1. Open any css file with CSS Editor. 2. Notice enabled "Open CSS Dialog" icon in the toolbar. 3. Select another css file in Package Explorer. 4. Right click on this selected css file -> Popup menu will appear with "Open CSS Dialog" menu item and the icon in the toolbar becomes disabled but still presents there. So in any case we should manage it somehow. Concerning "overpopulating": There are "Run As", "Debug As" context menu items, the same submenus are in toolbar "Run", "Debug" items. So it is duplicated. In my opinion the same behaviour is good for CSS Dialog icon too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3916?page=com.atlassian.jira.plu... ] Denis Maliarevich commented on JBIDE-3916: ------------------------------------------ Yeah, Run/Debug is more important. Their icons are always shown therewith. So, what about the second situation when after selecting another css in package explorer toolbar icon becomes disabled? If we decide not to add duplicating functionality then we can leave it as is but to my mind it leads to a little misunderstanding. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3916?page=com.atlassian.jira.plu... ] Denis Maliarevich commented on JBIDE-3916: ------------------------------------------ So it appears from conversation that: 1. Making CSS Dialog icon visible in the toolbar when user selects css file in Package Explorer is superfluous. 2. And it enough to have only contextmenu menu item on such a file. 3. When one css file is already opened in the editor and there is enabled toolbar icon selecting another css file in Package Explorer disables that icon and it's ok. If user wants to edit this file he should open it in the editor. Am I right? If so we can close this bug. I just wanted to clarify my observation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3916?page=com.atlassian.jira.plu... ] Denis Golovin updated JBIDE-3916: --------------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.)] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3916?page=com.atlassian.jira.plu... ] Maxim Areshkau updated JBIDE-3916: ---------------------------------- Fix Version/s: 3.1.0.M4 (was: 3.1.0.M3) Assignee: Sergey Dzmitrovich (was: Maxim Areshkau) Possibly this issue no more actual as we have css editing perspective with two views. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3916?page=com.atlassian.jira.plu... ] Yura Zhishko commented on JBIDE-3916: ------------------------------------- So, I don't see any reason to have this issue still opened. I think that now we have a full functionality provided by CSS Editor (Perspective) and CSS Dialog. I'm closing it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira