[jira] [Updated] (NETBEANS-5928) Proposed improvements to FlatLAF tab components+borders/margins
[ https://issues.apache.org/jira/browse/NETBEANS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5928: -- Description: In a previous PR ( https://github.com/apache/netbeans/pull/2967 ), the tab components in the NetBeans window system were redesigned and modernized for the Windows LAF. This PR ports related tabcontrol improvements back into FlatLAF, and proposes a similar tab style for FlatLAF. See the attached screenshots. The proposed style, compared to the current FlatLAF style, makes the selected tab look like an actual "tab" with an actual rectangular border around it, while keeping the much simpler "separators only" look for unselected tabs. The proposed style also tightens up vertical space significantly, like in other LAFs. See the attached screenshots. The new tab controls work well on all HiDPI scaling levels, and on all platforms (Windows, Linux, MacOS). Advantages of the proposed tabcontrol style: * Other applications that have tabs as part of their window system still tend to render at least the active window system tab as an actual "tabs", e.g. Chrome, Excel, Photoshop, Unity. * Personally, I find it hard to orient my eyes around the old FlatLAF tab style; the drawn selected tab seems to fix this. (Hard to explain in a fully objective way!) * The tab content areas (contents of editor, projects pane, navigator pane etc.) has borders around them, so it is logical that the border continues around the tab that is associated with them. * Conserve vertical space. Modern monitors have tended to become wider but not taller. With e.g. 2x HiDPI scaling (as on all MacBooks), there may actually be _fewer_ logical pixels available in the vertical direction than on older laptop screens. This PR also removes an extraneous border around the editor area, and introduces a little bit of extra space in the toolbar area. was: In a previous PR ( https://github.com/apache/netbeans/pull/2967 ), the tab components in the NetBeans window system were redesigned and modernized for the Windows LAF. This PR ports related tabcontrol improvements back into FlatLAF, and proposes a similar visual style. See the attached screenshots. The proposed style, compared to the current FlatLAF style, makes the selected tab look like an actual "tab" with an actual rectangular border around it, while keeping the much simpler "separators only" look for unselected tabs. The proposed style also tightens up vertical space significantly, like in other LAFs. See the attached screenshots. The new tab controls work well on all HiDPI scaling levels, and on all platforms (Windows, Linux, MacOS). This PR also removes an extraneous border around the editor area, and introduces a little bit of extra space in the toolbar area. > Proposed improvements to FlatLAF tab components+borders/margins > --- > > Key: NETBEANS-5928 > URL: https://issues.apache.org/jira/browse/NETBEANS-5928 > Project: NetBeans > Issue Type: Improvement > Components: FlatLaf >Affects Versions: 12.4 > Environment: Windows, MacOS, and Linux with FlatLAF Light and FlatLAF > Dark >Reporter: Eirik Bakke >Priority: Major > Attachments: flatlaf-dark-1-before.png, flatlaf-dark-2-after.png, > flatlaf-light-1-before.png, flatlaf-light-2-after.png > > > In a previous PR ( https://github.com/apache/netbeans/pull/2967 ), the tab > components in the NetBeans window system were redesigned and modernized for > the Windows LAF. This PR ports related tabcontrol improvements back into > FlatLAF, and proposes a similar tab style for FlatLAF. See the attached > screenshots. > The proposed style, compared to the current FlatLAF style, makes the selected > tab look like an actual "tab" with an actual rectangular border around it, > while keeping the much simpler "separators only" look for unselected tabs. > The proposed style also tightens up vertical space significantly, like in > other LAFs. See the attached screenshots. The new tab controls work well on > all HiDPI scaling levels, and on all platforms (Windows, Linux, MacOS). > Advantages of the proposed tabcontrol style: > * Other applications that have tabs as part of their window system still tend > to render at least the active window system tab as an actual "tabs", e.g. > Chrome, Excel, Photoshop, Unity. > * Personally, I find it hard to orient my eyes around the old FlatLAF tab > style; the drawn selected tab seems to fix this. (Hard to explain in a fully > objective way!) > * The tab content areas (contents of editor, projects pane, navigator pane > etc.) has borders around them, so it is logical that the border continues > around the tab that is associated with them. > * Conserve vertical space. Modern monitors have tended to be
[jira] [Updated] (NETBEANS-5928) Proposed improvements to FlatLAF tab components+borders/margins
[ https://issues.apache.org/jira/browse/NETBEANS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5928: -- Attachment: flatlaf-light-1-before.png flatlaf-light-2-after.png flatlaf-dark-1-before.png flatlaf-dark-2-after.png > Proposed improvements to FlatLAF tab components+borders/margins > --- > > Key: NETBEANS-5928 > URL: https://issues.apache.org/jira/browse/NETBEANS-5928 > Project: NetBeans > Issue Type: Improvement > Components: FlatLaf >Affects Versions: 12.4 > Environment: Windows, MacOS, and Linux with FlatLAF Light and FlatLAF > Dark >Reporter: Eirik Bakke >Priority: Major > Attachments: flatlaf-dark-1-before.png, flatlaf-dark-2-after.png, > flatlaf-light-1-before.png, flatlaf-light-2-after.png > > > In a previous PR ( https://github.com/apache/netbeans/pull/2967 ), the tab > components in the NetBeans window system were redesigned and modernized for > the Windows LAF. This PR ports related tabcontrol improvements back into > FlatLAF, and proposes a similar visual style. See the attached screenshots. > The proposed style, compared to the current FlatLAF style, makes the selected > tab look like an actual "tab" with an actual rectangular border around it, > while keeping the much simpler "separators only" look for unselected tabs. > The proposed style also tightens up vertical space significantly, like in > other LAFs. See the attached screenshots. The new tab controls work well on > all HiDPI scaling levels, and on all platforms (Windows, Linux, MacOS). > This PR also removes an extraneous border around the editor area, and > introduces a little bit of extra space in the toolbar area. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5928) Proposed improvements to FlatLAF tab components+borders/margins
Eirik Bakke created NETBEANS-5928: - Summary: Proposed improvements to FlatLAF tab components+borders/margins Key: NETBEANS-5928 URL: https://issues.apache.org/jira/browse/NETBEANS-5928 Project: NetBeans Issue Type: Improvement Components: FlatLaf Affects Versions: 12.4 Environment: Windows, MacOS, and Linux with FlatLAF Light and FlatLAF Dark Reporter: Eirik Bakke Attachments: flatlaf-dark-1-before.png, flatlaf-dark-2-after.png, flatlaf-light-1-before.png, flatlaf-light-2-after.png In a previous PR ( https://github.com/apache/netbeans/pull/2967 ), the tab components in the NetBeans window system were redesigned and modernized for the Windows LAF. This PR ports related tabcontrol improvements back into FlatLAF, and proposes a similar visual style. See the attached screenshots. The proposed style, compared to the current FlatLAF style, makes the selected tab look like an actual "tab" with an actual rectangular border around it, while keeping the much simpler "separators only" look for unselected tabs. The proposed style also tightens up vertical space significantly, like in other LAFs. See the attached screenshots. The new tab controls work well on all HiDPI scaling levels, and on all platforms (Windows, Linux, MacOS). This PR also removes an extraneous border around the editor area, and introduces a little bit of extra space in the toolbar area. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5927) Switch Windows LAF to the now-standard "Segoe UI" font
[ https://issues.apache.org/jira/browse/NETBEANS-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5927: -- Attachment: fontchange-1-before.png > Switch Windows LAF to the now-standard "Segoe UI" font > -- > > Key: NETBEANS-5927 > URL: https://issues.apache.org/jira/browse/NETBEANS-5927 > Project: NetBeans > Issue Type: Bug > Components: platform - Other >Affects Versions: 12.4 > Environment: NetBeans 12.4 with Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Attachments: fontchange-1-before.png, fontchange-2-after.png > > > For the last 14 years (since Windows Vista), the default UI font on Windows > has been Segoe UI 12. But Swing's Windows LAF stayed with Tahoma 11, for > reasons of backwards compatibility only (see JDK-6669448). This makes > NetBeans look a little dated, and the font size smaller than in other Windows > application. In the words of one blogger: "On a related note, this is one of > the bigger visual deficiencies of NetBeans running on Vista – the smaller > Tahoma font makes it less visually appealing that it could have been." > https://www.pushing-pixels.org/page/213?m > This PR switches the NetBeans Windows LAF to the newer Segoe font, by > borrowing logic from FlatLAF to get the actual Windows default font from the > "win.messagebox.font" desktop property, which is initialized from the Win32 > API. This also avoids one of the problems that were fixed in the earlier > https://github.com/apache/netbeans/pull/1777 , with the Swing Windows LAF > using incorrect font sizes on certain HiDPI configurations. > Segoe UI 12 looks similar to Tahoma 11, but with ascenders and descenders > that extend one pixel farther up/down. Letters like "j" and "y" have some > differences in their shapes. > Note that certain UI elements, notably the menu bar, were already using Segoe > UI 12. And FlatLAF is already using Segoe UI 12 on Windows. Note also that > this PR should not affect the main code editor font. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5927) Switch Windows LAF to the now-standard "Segoe UI" font
[ https://issues.apache.org/jira/browse/NETBEANS-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5927: -- Attachment: fontchange-2-after.png > Switch Windows LAF to the now-standard "Segoe UI" font > -- > > Key: NETBEANS-5927 > URL: https://issues.apache.org/jira/browse/NETBEANS-5927 > Project: NetBeans > Issue Type: Bug > Components: platform - Other >Affects Versions: 12.4 > Environment: NetBeans 12.4 with Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Attachments: fontchange-1-before.png, fontchange-2-after.png > > > For the last 14 years (since Windows Vista), the default UI font on Windows > has been Segoe UI 12. But Swing's Windows LAF stayed with Tahoma 11, for > reasons of backwards compatibility only (see JDK-6669448). This makes > NetBeans look a little dated, and the font size smaller than in other Windows > application. In the words of one blogger: "On a related note, this is one of > the bigger visual deficiencies of NetBeans running on Vista – the smaller > Tahoma font makes it less visually appealing that it could have been." > https://www.pushing-pixels.org/page/213?m > This PR switches the NetBeans Windows LAF to the newer Segoe font, by > borrowing logic from FlatLAF to get the actual Windows default font from the > "win.messagebox.font" desktop property, which is initialized from the Win32 > API. This also avoids one of the problems that were fixed in the earlier > https://github.com/apache/netbeans/pull/1777 , with the Swing Windows LAF > using incorrect font sizes on certain HiDPI configurations. > Segoe UI 12 looks similar to Tahoma 11, but with ascenders and descenders > that extend one pixel farther up/down. Letters like "j" and "y" have some > differences in their shapes. > Note that certain UI elements, notably the menu bar, were already using Segoe > UI 12. And FlatLAF is already using Segoe UI 12 on Windows. Note also that > this PR should not affect the main code editor font. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5927) Switch Windows LAF to the now-standard "Segoe UI" font
[ https://issues.apache.org/jira/browse/NETBEANS-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5927: -- Description: For the last 14 years (since Windows Vista), the default UI font on Windows has been Segoe UI 12. But Swing's Windows LAF stayed with Tahoma 11, for reasons of backwards compatibility only (see JDK-6669448). This makes NetBeans look a little dated, and the font size smaller than in other Windows application. In the words of one blogger: "On a related note, this is one of the bigger visual deficiencies of NetBeans running on Vista – the smaller Tahoma font makes it less visually appealing that it could have been." https://www.pushing-pixels.org/page/213?m This PR switches the NetBeans Windows LAF to the newer Segoe font, by borrowing logic from FlatLAF to get the actual Windows default font from the "win.messagebox.font" desktop property, which is initialized from the Win32 API. This also avoids one of the problems that were fixed in the earlier https://github.com/apache/netbeans/pull/1777 , with the Swing Windows LAF using incorrect font sizes on certain HiDPI configurations. Segoe UI 12 looks similar to Tahoma 11, but with ascenders and descenders that extend one pixel farther up/down. Letters like "j" and "y" have some differences in their shapes. Note that certain UI elements, notably the menu bar, were already using Segoe UI 12. And FlatLAF is already using Segoe UI 12 on Windows. Note also that this PR should not affect the main code editor font. was: For the last 14 years (since Windows Vista), the default UI font on Windows has been Segoe UI 12. But Swing's Windows LAF stayed with Tahoma 11, for reasons of backwards compatibility only (see JDK-6669448). This makes NetBeans look a little dated, and the font size smaller than in other Windows application. In the words of one blogger: "On a related note, this is one of the bigger visual deficiencies of NetBeans running on Vista – the smaller Tahoma font makes it less visually appealing that it could have been." https://www.pushing-pixels.org/page/213?m This PR switches the NetBeans Windows LAF to the newer Segoe font, by borrowing logic from FlatLAF to get the actual Windows default font from the "win.messagebox.font" desktop property, which is initialized from the Win32 API. This also avoids one of the problems that were fixed in the earlier https://github.com/apache/netbeans/pull/1777 , with the Swing Windows LAF using incorrect font sizes on certain HiDPI configurations. Segoe UI 12 looks similar to Tahoma 11, but with ascenders and descenders that extend one pixel farther up/down. Letters like "j" and "y" have some differences in their shapes. Note that certain UI elements, notably the menu bar, were already using Segoe UI 12. And FlatLAF is already using Segoe UI 12 on Windows. > Switch Windows LAF to the now-standard "Segoe UI" font > -- > > Key: NETBEANS-5927 > URL: https://issues.apache.org/jira/browse/NETBEANS-5927 > Project: NetBeans > Issue Type: Bug > Components: platform - Other >Affects Versions: 12.4 > Environment: NetBeans 12.4 with Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > > For the last 14 years (since Windows Vista), the default UI font on Windows > has been Segoe UI 12. But Swing's Windows LAF stayed with Tahoma 11, for > reasons of backwards compatibility only (see JDK-6669448). This makes > NetBeans look a little dated, and the font size smaller than in other Windows > application. In the words of one blogger: "On a related note, this is one of > the bigger visual deficiencies of NetBeans running on Vista – the smaller > Tahoma font makes it less visually appealing that it could have been." > https://www.pushing-pixels.org/page/213?m > This PR switches the NetBeans Windows LAF to the newer Segoe font, by > borrowing logic from FlatLAF to get the actual Windows default font from the > "win.messagebox.font" desktop property, which is initialized from the Win32 > API. This also avoids one of the problems that were fixed in the earlier > https://github.com/apache/netbeans/pull/1777 , with the Swing Windows LAF > using incorrect font sizes on certain HiDPI configurations. > Segoe UI 12 looks similar to Tahoma 11, but with ascenders and descenders > that extend one pixel farther up/down. Letters like "j" and "y" have some > differences in their shapes. > Note that certain UI elements, notably the menu bar, were already using Segoe > UI 12. And FlatLAF is already using Segoe UI 12 on Windows. Note also that > this PR should not affect the main code editor font. -- This message was sent by Atlassian Jira (v8.3.4#803005) -
[jira] [Created] (NETBEANS-5927) Switch Windows LAF to the now-standard "Segoe UI" font
Eirik Bakke created NETBEANS-5927: - Summary: Switch Windows LAF to the now-standard "Segoe UI" font Key: NETBEANS-5927 URL: https://issues.apache.org/jira/browse/NETBEANS-5927 Project: NetBeans Issue Type: Bug Components: platform - Other Affects Versions: 12.4 Environment: NetBeans 12.4 with Windows LAF on Windows 10. Reporter: Eirik Bakke For the last 14 years (since Windows Vista), the default UI font on Windows has been Segoe UI 12. But Swing's Windows LAF stayed with Tahoma 11, for reasons of backwards compatibility only (see JDK-6669448). This makes NetBeans look a little dated, and the font size smaller than in other Windows application. In the words of one blogger: "On a related note, this is one of the bigger visual deficiencies of NetBeans running on Vista – the smaller Tahoma font makes it less visually appealing that it could have been." https://www.pushing-pixels.org/page/213?m This PR switches the NetBeans Windows LAF to the newer Segoe font, by borrowing logic from FlatLAF to get the actual Windows default font from the "win.messagebox.font" desktop property, which is initialized from the Win32 API. This also avoids one of the problems that were fixed in the earlier https://github.com/apache/netbeans/pull/1777 , with the Swing Windows LAF using incorrect font sizes on certain HiDPI configurations. Segoe UI 12 looks similar to Tahoma 11, but with ascenders and descenders that extend one pixel farther up/down. Letters like "j" and "y" have some differences in their shapes. Note that certain UI elements, notably the menu bar, were already using Segoe UI 12. And FlatLAF is already using Segoe UI 12 on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2360) HiDPI scaling (and anti-aliasing on KDE) not applied automatically on Linux
[ https://issues.apache.org/jira/browse/NETBEANS-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400693#comment-17400693 ] Eirik Bakke commented on NETBEANS-2360: --- I'm about to create a PR for this issue, which also covers anti-aliasing issues on KDE. So I adjusted the title of this issue to include the anti-aliasing issue, since they should be tested together. > HiDPI scaling (and anti-aliasing on KDE) not applied automatically on Linux > --- > > Key: NETBEANS-2360 > URL: https://issues.apache.org/jira/browse/NETBEANS-2360 > Project: NetBeans > Issue Type: Bug > Components: platform - Launchers&CLI >Affects Versions: 11.0, 12.2 > Environment: Kubuntu 18.03 > Oracle JDK 11.0.2 >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, Linux > Attachments: kubunt.jpg > > > Running NetBeans 11 on Kubuntu 18.03, GUI text size does not seem to take > into account the system's default HiDPI scaling. This was reported in a > Twitter thread on https://twitter.com/nicktail/status/1114789604337405952 . > Note that Window decorations seem to be the correct size. > Setting the GDK_SCALE environment variable seems to fix the problem, if I > understand the originally reporter correctly. This could probably be done > easily from the NetBeans launcher script (netbeans/bin). But it wouldn't fix > the problem in multi-monitor setups. We should investigate what could be done > to make scaling work properly in multi-monitor setups involving one HiDPI > screen and one non-HiDPI screen. > Before merging a patch to the launcher script, it should be tested on a > couple of different Linux environments, using both HiDPI and non-HiDPI > screens. Note that the UNIX launcher script is also used on MacOS. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2360) HiDPI scaling (and anti-aliasing on KDE) not applied automatically on Linux
[ https://issues.apache.org/jira/browse/NETBEANS-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-2360: -- Summary: HiDPI scaling (and anti-aliasing on KDE) not applied automatically on Linux (was: HiDPI scaling not applied automatically on Linux) > HiDPI scaling (and anti-aliasing on KDE) not applied automatically on Linux > --- > > Key: NETBEANS-2360 > URL: https://issues.apache.org/jira/browse/NETBEANS-2360 > Project: NetBeans > Issue Type: Bug > Components: platform - Launchers&CLI >Affects Versions: 11.0, 12.2 > Environment: Kubuntu 18.03 > Oracle JDK 11.0.2 >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, Linux > Attachments: kubunt.jpg > > > Running NetBeans 11 on Kubuntu 18.03, GUI text size does not seem to take > into account the system's default HiDPI scaling. This was reported in a > Twitter thread on https://twitter.com/nicktail/status/1114789604337405952 . > Note that Window decorations seem to be the correct size. > Setting the GDK_SCALE environment variable seems to fix the problem, if I > understand the originally reporter correctly. This could probably be done > easily from the NetBeans launcher script (netbeans/bin). But it wouldn't fix > the problem in multi-monitor setups. We should investigate what could be done > to make scaling work properly in multi-monitor setups involving one HiDPI > screen and one non-HiDPI screen. > Before merging a patch to the launcher script, it should be tested on a > couple of different Linux environments, using both HiDPI and non-HiDPI > screens. Note that the UNIX launcher script is also used on MacOS. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397926#comment-17397926 ] Eirik Bakke commented on NETBEANS-5914: --- Looking at the "blame" output for the pre-Apache years, there were already a discussion back in 2011 about deadlock avoidance in this area before; see https://bz.apache.org/netbeans/show_bug.cgi?id=205533 and https://github.com/emilianbold/netbeans-releases/commit/fc0b2c38a179b07acfdf834b5088fd3686feb081 . Maybe [~jgl...@netbeans.org] could chime in as well. > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Assignee: Jaroslav Tulach >Priority: Major > Attachments: 210506 NetBeans Deadlock on Startup 2.txt, 210506 > NetBeans Deadlock on Startup.txt, 210516 Another NetBeans Deadlock.txt, > 210526 NetBeans Deadlock again.txt > > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397451#comment-17397451 ] Eirik Bakke commented on NETBEANS-5914: --- I couldn't immediately see anything in common with NETBEANS-5913. Note that the thread named "Event Dispatch Thread" is actually a red herring... the real AWT EDT is the one named "AWT-EventQueue-0". > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Attachments: 210506 NetBeans Deadlock on Startup 2.txt, 210506 > NetBeans Deadlock on Startup.txt, 210516 Another NetBeans Deadlock.txt, > 210526 NetBeans Deadlock again.txt > > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5914) NetBeans 12.4 freezes on startup
Eirik Bakke created NETBEANS-5914: - Summary: NetBeans 12.4 freezes on startup Key: NETBEANS-5914 URL: https://issues.apache.org/jira/browse/NETBEANS-5914 Project: NetBeans Issue Type: Bug Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. Reporter: Eirik Bakke Attachments: 210506 NetBeans Deadlock on Startup 2.txt, 210506 NetBeans Deadlock on Startup.txt, 210516 Another NetBeans Deadlock.txt, 210526 NetBeans Deadlock again.txt On NetBeans 12.4, I was previously experiencing some intermittent freezes on startup, at the time when projects were being loaded and such. I did some thread dumps of the frozen IDE using VisualVM. I'm uploading these now in case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5914: -- Attachment: 210506 NetBeans Deadlock on Startup.txt 210506 NetBeans Deadlock on Startup 2.txt 210516 Another NetBeans Deadlock.txt 210526 NetBeans Deadlock again.txt > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Attachments: 210506 NetBeans Deadlock on Startup 2.txt, 210506 > NetBeans Deadlock on Startup.txt, 210516 Another NetBeans Deadlock.txt, > 210526 NetBeans Deadlock again.txt > > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5896) Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
[
https://issues.apache.org/jira/browse/NETBEANS-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391151#comment-17391151
]
Eirik Bakke commented on NETBEANS-5896:
---
I think these are the sources for the Enter class:
https://github.com/openjdk/jdk/blame/jdk-11+28/src/jdk.compiler/share/classes/com/sun/tools/javac/comp/Enter.java
https://github.com/openjdk/jdk/blob/master/src/jdk.compiler/share/classes/com/sun/tools/javac/comp/Enter.java
https://github.com/oracle/nb-javac/blob/master/src/jdk.compiler/share/classes/com/sun/tools/javac/comp/Enter.java
It seems the "unenter" method does not exist on Java 11, but does exist in
later Java versions (from 15 and above?).
> Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
> ---
>
> Key: NETBEANS-5896
> URL: https://issues.apache.org/jira/browse/NETBEANS-5896
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.4
> Environment: Java 11.0.11 on Windows 10 on NetBeans 12.4 with vanilla
> javac (nb-javac _not_ installed)
>Reporter: Eirik Bakke
>Priority: Major
>
> Working with Compile-on-Save enabled on a Maven-based NetBeans Platform
> project, with vanilla javac (nb-javac _not_ installed), I frequently get the
> following stack trace:
> {noformat}
> java.lang.NoSuchMethodException:
> com.sun.tools.javac.comp.Enter.unenter(com.sun.tools.javac.tree.JCTree$JCCompilationUnit,
> com.sun.tools.javac.tree.JCTree)
> at java.base/java.lang.Class.getDeclaredMethod(Class.java:2475)
> at
> org.netbeans.api.java.source.TreeUtilities.unenter(TreeUtilities.java:927)
> at
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:916)
> at
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:845)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:502)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:477)
> at
> org.netbeans.modules.java.source.parsing.MimeTask.run(MimeTask.java:60)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
> at
> org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
> at
> org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
> at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
> at
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:431)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.resolve(DeclarativeHintsParser.java:477)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.access$000(DeclarativeHintsParser.java:83)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseCondition(DeclarativeHintsParser.java:311)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseConditions(DeclarativeHintsParser.java:258)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseRule(DeclarativeHintsParser.java:215)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseInput(DeclarativeHintsParser.java:184)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.access$200(DeclarativeHintsParser.java:90)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.parse(DeclarativeHintsParser.java:395)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHints(DeclarativeHintRegistry.java:263)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHintFile(DeclarativeHintRegistry.java:239)
> at
> org.netbeans.modules.java.hints
[jira] [Updated] (NETBEANS-5896) Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
[
https://issues.apache.org/jira/browse/NETBEANS-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5896:
--
Description:
Working with Compile-on-Save enabled on a Maven-based NetBeans Platform
project, with vanilla javac (nb-javac _not_ installed), I frequently get the
following stack trace:
{noformat}
java.lang.NoSuchMethodException:
com.sun.tools.javac.comp.Enter.unenter(com.sun.tools.javac.tree.JCTree$JCCompilationUnit,
com.sun.tools.javac.tree.JCTree)
at java.base/java.lang.Class.getDeclaredMethod(Class.java:2475)
at
org.netbeans.api.java.source.TreeUtilities.unenter(TreeUtilities.java:927)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:916)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:845)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:502)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.source.parsing.MimeTask.run(MimeTask.java:60)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
at
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
at
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
at
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
at
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
at
org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:431)
at
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.resolve(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.access$000(DeclarativeHintsParser.java:83)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseCondition(DeclarativeHintsParser.java:311)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseConditions(DeclarativeHintsParser.java:258)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseRule(DeclarativeHintsParser.java:215)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseInput(DeclarativeHintsParser.java:184)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.access$200(DeclarativeHintsParser.java:90)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.parse(DeclarativeHintsParser.java:395)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHints(DeclarativeHintRegistry.java:263)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHintFile(DeclarativeHintRegistry.java:239)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.readHints(DeclarativeHintRegistry.java:128)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.computeHints(DeclarativeHintRegistry.java:111)
at
org.netbeans.modules.java.hints.spiimpl.RulesManagerImpl.readHints(RulesManagerImpl.java:139)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:133)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:128)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:114)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:65)
at
org.netbeans.modules.java.source.JavaSourceAccessor$CancelableTaskWrapper.run(JavaSourceAccessor.java:273)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:561)
at
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:786)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
at
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerf
[jira] [Updated] (NETBEANS-5896) Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
[
https://issues.apache.org/jira/browse/NETBEANS-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5896:
--
Description:
Working with Compile-on-Save enabled on a Maven-based NetBeans Platform
project, with vanilla javac (nb-javac _not_ installed), I frequently get the
following stack trace:
{noformat}
java.lang.NoSuchMethodException:
com.sun.tools.javac.comp.Enter.unenter(com.sun.tools.javac.tree.JCTree$JCCompilationUnit,
com.sun.tools.javac.tree.JCTree)
at java.base/java.lang.Class.getDeclaredMethod(Class.java:2475)
at
org.netbeans.api.java.source.TreeUtilities.unenter(TreeUtilities.java:927)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:916)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:845)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:502)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.source.parsing.MimeTask.run(MimeTask.java:60)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
at
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
at
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
at
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
at
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
at
org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:431)
at
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.resolve(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.access$000(DeclarativeHintsParser.java:83)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseCondition(DeclarativeHintsParser.java:311)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseConditions(DeclarativeHintsParser.java:258)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseRule(DeclarativeHintsParser.java:215)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseInput(DeclarativeHintsParser.java:184)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.access$200(DeclarativeHintsParser.java:90)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.parse(DeclarativeHintsParser.java:395)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHints(DeclarativeHintRegistry.java:263)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHintFile(DeclarativeHintRegistry.java:239)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.readHints(DeclarativeHintRegistry.java:128)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.computeHints(DeclarativeHintRegistry.java:111)
at
org.netbeans.modules.java.hints.spiimpl.RulesManagerImpl.readHints(RulesManagerImpl.java:139)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:133)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:128)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:114)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:65)
at
org.netbeans.modules.java.source.JavaSourceAccessor$CancelableTaskWrapper.run(JavaSourceAccessor.java:273)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:561)
at
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:786)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
at
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerf
[jira] [Created] (NETBEANS-5896) Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
Eirik Bakke created NETBEANS-5896:
-
Summary: Missing "com.sun.tools.javac.comp.Enter.unenter" with
vanilla javac
Key: NETBEANS-5896
URL: https://issues.apache.org/jira/browse/NETBEANS-5896
Project: NetBeans
Issue Type: Bug
Components: java - Compiler
Affects Versions: 12.4
Environment: Java 11.0.11 on Windows 10 on NetBeans 12.4 with vanilla
javac (nb-javac _not_ installed)
Reporter: Eirik Bakke
Working with Compile-on-Save enabled on a Maven-based NetBeans Platform
project, with vanilla javac (nb-javac _not_ installed), I frequently get the
following stack trace:
{noformat}
java.lang.NoSuchMethodException:
com.sun.tools.javac.comp.Enter.unenter(com.sun.tools.javac.tree.JCTree$JCCompilationUnit,
com.sun.tools.javac.tree.JCTree)
at java.base/java.lang.Class.getDeclaredMethod(Class.java:2475)
at
org.netbeans.api.java.source.TreeUtilities.unenter(TreeUtilities.java:927)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:916)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:845)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:502)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.source.parsing.MimeTask.run(MimeTask.java:60)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
at
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
at
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
at
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
at
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
at
org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:431)
at
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.resolve(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.access$000(DeclarativeHintsParser.java:83)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseCondition(DeclarativeHintsParser.java:311)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseConditions(DeclarativeHintsParser.java:258)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseRule(DeclarativeHintsParser.java:215)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseInput(DeclarativeHintsParser.java:184)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.access$200(DeclarativeHintsParser.java:90)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.parse(DeclarativeHintsParser.java:395)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHints(DeclarativeHintRegistry.java:263)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHintFile(DeclarativeHintRegistry.java:239)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.readHints(DeclarativeHintRegistry.java:128)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.computeHints(DeclarativeHintRegistry.java:111)
at
org.netbeans.modules.java.hints.spiimpl.RulesManagerImpl.readHints(RulesManagerImpl.java:139)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:133)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:128)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:114)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:65)
at
org.netbeans.modules.java.source.JavaSourceAccessor$CancelableTaskWrapper.run(JavaSourceAccessor.java:273)
at
org.netbeans.mod
[jira] [Commented] (NETBEANS-5863) "Test results" spuriously clears tests during run, and shows success despite failure
[ https://issues.apache.org/jira/browse/NETBEANS-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17387361#comment-17387361 ] Eirik Bakke commented on NETBEANS-5863: --- [~asbachb] I hadn't noticed anything about the status bar when reporting this bug. If you see new problems, feel free to report them! (Thanks again [~dbalek] for the quick fix to this bug!) > "Test results" spuriously clears tests during run, and shows success despite > failure > > > Key: NETBEANS-5863 > URL: https://issues.apache.org/jira/browse/NETBEANS-5863 > Project: NetBeans > Issue Type: Bug > Components: java - JUnit, utilities - Test Runner >Affects Versions: 12.4 > Environment: NetBeans 12.4 on 64-bit Windows 10 on OpenJDK 11.0.11. >Reporter: Eirik Bakke >Assignee: Dusan Balek >Priority: Major > Labels: pull-request-available > Fix For: 12.5 > > Attachments: Failure became success!.png, Test results dropped.png > > Time Spent: 50m > Remaining Estimate: 0h > > In NetBeans 12.4, test results displayed in the "Test results" pane will get > randomly cleared while the tests are running. The final output thus ends up > not including all tests that were run. See the attached series of > screenshots. Sometimes the "Test results" pane will end up showing a green > bar with "Tests passed: 100.00 %" even when there were test failures. > My application's test suite is JUnit in a maven-based NetBeans module running > maven-surefire-plugin version 3.0.0-M4. Using an older version of the > surefire plugin (2.18.1, which I previously used to avoid NETBEANS-458 ) did > not solve the problem. > This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. I verified > this by running my application's test suite on both NetBeans versions, > without changing surefire versions or anything else. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5757) Compile-on-Save drops static initializer (vanilla javac)
[
https://issues.apache.org/jira/browse/NETBEANS-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke resolved NETBEANS-5757.
---
Fix Version/s: Next
Resolution: Fixed
Confirmed fixed by https://github.com/apache/netbeans/pull/3054 , which was
merged.
> Compile-on-Save drops static initializer (vanilla javac)
>
>
> Key: NETBEANS-5757
> URL: https://issues.apache.org/jira/browse/NETBEANS-5757
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.4
> Environment: NetBeans 12.4 _without_ nb-javac installed (started from
> clean user and cache directories to ensure no trace of nb-javac was left from
> my old installation). Java 11.0.11 or Java 17-ea+25. Windows 10.
>Reporter: Eirik Bakke
>Priority: Major
> Fix For: Next
>
>
> Very great to see Compile-on-Save now working without the external nb-javac
> plugin! Here's the first bug I've found around this. To reproduce, create an
> empty maven-based Java project and add the following class:
> {code:java}
> public class StaticInitializerExample {
> private static final String SOME_CONSTANT;
> static {
> SOME_CONSTANT = "I am a constant.";
> }
> public static final void main(String args[]) {
> System.out.println(SOME_CONSTANT);
> }
> }
> {code}
> Do a clean build and run. The application will print, "I am a constant."
> Now do any trivial change to the code, such as adding a comment, and save.
> Run again. The application will now print "null", rather than the correct
> output.
> Tested on both Java 11.0.11 and Java 17-ea+25. I also tested with NetBeans
> 11.3 with nb-javac installed; in that case the output is correct (still "I am
> a constant."). In the latter case you can also change the constant in the
> static initializer, and CoS will apply the change correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5863) "Test results" spuriously clears tests during run, and shows success despite failure
[ https://issues.apache.org/jira/browse/NETBEANS-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5863: -- Description: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. Sometimes the "Test results" pane will end up showing a green bar with "Tests passed: 100.00 %" even when there were test failures. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I previously used to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) was: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. Sometimes the "Test results" pane will end up showing a green bar with "Tests passed: 100.00 %" even when there were test failures. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) > "Test results" spuriously clears tests during run, and shows success despite > failure > > > Key: NETBEANS-5863 > URL: https://issues.apache.org/jira/browse/NETBEANS-5863 > Project: NetBeans > Issue Type: Bug > Components: java - JUnit, utilities - Test Runner >Affects Versions: 12.4 > Environment: NetBeans 12.4 on 64-bit Windows 10 on OpenJDK 11.0.11. >Reporter: Eirik Bakke >Priority: Major > Attachments: Failure became success!.png, Test results dropped.png > > > In NetBeans 12.4, test results displayed in the "Test results" pane will get > randomly cleared while the tests are running. The final output thus ends up > not including all tests that were run. See the attached series of > screenshots. Sometimes the "Test results" pane will end up showing a green > bar with "Tests passed: 100.00 %" even when there were test failures. > My application's test suite is JUnit in a maven-based NetBeans module running > maven-surefire-plugin version 3.0.0-M4. Using an older version of the > surefire plugin (2.18.1, which I previously used to avoid NETBEANS-458 ) did > not solve the problem. > This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified > this by running my application's test suite on both NetBeans versions, > without changing surefire versions or anything else.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5863) "Test results" spuriously clears tests during run, and shows success despite failure
[ https://issues.apache.org/jira/browse/NETBEANS-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5863: -- Description: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. Sometimes the "Test results" pane will end up showing a green bar with "Tests passed: 100.00 %" even when there were test failures. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I previously used to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else. was: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. Sometimes the "Test results" pane will end up showing a green bar with "Tests passed: 100.00 %" even when there were test failures. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I previously used to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) > "Test results" spuriously clears tests during run, and shows success despite > failure > > > Key: NETBEANS-5863 > URL: https://issues.apache.org/jira/browse/NETBEANS-5863 > Project: NetBeans > Issue Type: Bug > Components: java - JUnit, utilities - Test Runner >Affects Versions: 12.4 > Environment: NetBeans 12.4 on 64-bit Windows 10 on OpenJDK 11.0.11. >Reporter: Eirik Bakke >Priority: Major > Attachments: Failure became success!.png, Test results dropped.png > > > In NetBeans 12.4, test results displayed in the "Test results" pane will get > randomly cleared while the tests are running. The final output thus ends up > not including all tests that were run. See the attached series of > screenshots. Sometimes the "Test results" pane will end up showing a green > bar with "Tests passed: 100.00 %" even when there were test failures. > My application's test suite is JUnit in a maven-based NetBeans module running > maven-surefire-plugin version 3.0.0-M4. Using an older version of the > surefire plugin (2.18.1, which I previously used to avoid NETBEANS-458 ) did > not solve the problem. > This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. I verified > this by running my application's test suite on both NetBeans versions, > without changing surefire versions or anything else. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5863) "Test results" spuriously clears tests during run, and shows success despite failure
[ https://issues.apache.org/jira/browse/NETBEANS-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5863: -- Attachment: Failure became success!.png Description: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. Sometimes the "Test results" pane will end up saying "All tests succeeded" even when there were test failures. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) was: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) Summary: "Test results" spuriously clears tests during run, and shows success despite failure (was: "Test results" gets reset during test execution, leading to omitted results) > "Test results" spuriously clears tests during run, and shows success despite > failure > > > Key: NETBEANS-5863 > URL: https://issues.apache.org/jira/browse/NETBEANS-5863 > Project: NetBeans > Issue Type: Bug > Components: java - JUnit, utilities - Test Runner >Affects Versions: 12.4 > Environment: NetBeans 12.4 on 64-bit Windows 10 on OpenJDK 11.0.11. >Reporter: Eirik Bakke >Priority: Major > Attachments: Failure became success!.png, Test results dropped.png > > > In NetBeans 12.4, test results displayed in the "Test results" pane will get > randomly cleared while the tests are running. The final output thus ends up > not including all tests that were run. See the attached series of > screenshots. Sometimes the "Test results" pane will end up saying "All tests > succeeded" even when there were test failures. > My application's test suite is JUnit in a maven-based NetBeans module running > maven-surefire-plugin version 3.0.0-M4. Using an older version of the > surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not > solve the problem. > This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified > this by running my application's test suite on both NetBeans versions, > without changing surefire versions or anything else.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5863) "Test results" spuriously clears tests during run, and shows success despite failure
[ https://issues.apache.org/jira/browse/NETBEANS-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5863: -- Description: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. Sometimes the "Test results" pane will end up showing a green bar with "Tests passed: 100.00 %" even when there were test failures. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) was: In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. Sometimes the "Test results" pane will end up saying "All tests succeeded" even when there were test failures. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) > "Test results" spuriously clears tests during run, and shows success despite > failure > > > Key: NETBEANS-5863 > URL: https://issues.apache.org/jira/browse/NETBEANS-5863 > Project: NetBeans > Issue Type: Bug > Components: java - JUnit, utilities - Test Runner >Affects Versions: 12.4 > Environment: NetBeans 12.4 on 64-bit Windows 10 on OpenJDK 11.0.11. >Reporter: Eirik Bakke >Priority: Major > Attachments: Failure became success!.png, Test results dropped.png > > > In NetBeans 12.4, test results displayed in the "Test results" pane will get > randomly cleared while the tests are running. The final output thus ends up > not including all tests that were run. See the attached series of > screenshots. Sometimes the "Test results" pane will end up showing a green > bar with "Tests passed: 100.00 %" even when there were test failures. > My application's test suite is JUnit in a maven-based NetBeans module running > maven-surefire-plugin version 3.0.0-M4. Using an older version of the > surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not > solve the problem. > This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified > this by running my application's test suite on both NetBeans versions, > without changing surefire versions or anything else.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5863) "Test results" gets reset during test execution, leading to omitted results
Eirik Bakke created NETBEANS-5863: - Summary: "Test results" gets reset during test execution, leading to omitted results Key: NETBEANS-5863 URL: https://issues.apache.org/jira/browse/NETBEANS-5863 Project: NetBeans Issue Type: Bug Components: java - JUnit, utilities - Test Runner Affects Versions: 12.4 Environment: NetBeans 12.4 on 64-bit Windows 10 on OpenJDK 11.0.11. Reporter: Eirik Bakke Attachments: Test results dropped.png In NetBeans 12.4, test results displayed in the "Test results" pane will get randomly cleared while the tests are running. The final output thus ends up not including all tests that were run. See the attached series of screenshots. My application's test suite is JUnit in a maven-based NetBeans module running maven-surefire-plugin version 3.0.0-M4. Using an older version of the surefire plugin (2.18.1, which I used to use to avoid NETBEANS-458 ) did not solve the problem. This problem occurs on NetBeans 12.4, but not on NetBeans 12.1. (I verified this by running my application's test suite on both NetBeans versions, without changing surefire versions or anything else.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5696) Replace animated spinner icon with HiDPI-scalable version
[ https://issues.apache.org/jira/browse/NETBEANS-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke resolved NETBEANS-5696. --- Fix Version/s: 12.5 Resolution: Fixed PR was merged; marking as fixed. > Replace animated spinner icon with HiDPI-scalable version > - > > Key: NETBEANS-5696 > URL: https://issues.apache.org/jira/browse/NETBEANS-5696 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: All LAFs. >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Fix For: 12.5 > > Attachments: New Spinner Icon.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > The window system tabs component has a spinning "busy" icon which is > displayed e.g. while the Navigator is initially loading. This issue's Pull > Request replaces the current bitmap-based icon (busy_icon.png) with a > scalable spinner graphic (drawn with Java2D code) that looks better on HiDPI > and Retina screens. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke resolved NETBEANS-5698. --- Fix Version/s: 12.5 Resolution: Fixed PR was merged; marking as fixed. > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Fix For: 12.5 > > Attachments: Java 11 Tabs New.png, Java 11 Tabs Old.png, MacOS > Catalina Border Style Example.png, Summary.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of headaches. > The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with > the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style > has changed a bit, with either bright or dark colors depending on light/dark > mode (rather than midtone greys), and "glass pane" textures rather than > metallic surface gradients. It's probably best to keep the existing Aqua LAF > style for now, though perhaps some of the bevel effects could go away to make > it look more up-to-date. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke resolved NETBEANS-5673. --- Fix Version/s: 12.5 Resolution: Fixed PR was merged; marking as fixed. > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Assignee: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Fix For: 12.5 > > Attachments: Planned Windows LAF improvements.png > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and need improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses HiDPI-safe. > * Make lines line up and connect on HiDPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5697) Various smaller LAF/HiDPI improvements in Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke resolved NETBEANS-5697. --- Fix Version/s: 12.5 Resolution: Fixed PR was merged; marking as fixed. > Various smaller LAF/HiDPI improvements in Windows LAF > - > > Key: NETBEANS-5697 > URL: https://issues.apache.org/jira/browse/NETBEANS-5697 > Project: NetBeans > Issue Type: Improvement > Environment: Windows LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Fix For: 12.5 > > Attachments: 210517 Menu Checkbox Bug.png, Smaller fixes.png > > Time Spent: 1h 50m > Remaining Estimate: 0h > > This issue was created for a Pull Request covering a number of smaller > improvements to the Windows LAF: > * Apply Windows LAF HiDPI bug workarounds from NETBEANS-3592 to > JCheckboxMenuItem and friends. > * Apply previous border tweaks for HiDPI screens in a few more places, > notably in tooltips and the quick search text field, and in the editor > toolbar. Improve JSpinner borders. > * Make the background color of tooltips consistent with that of other > Windows 10 apps. > * Add some pixels of left margin to the editor toolbar. > See attached screenshots. > (This work was done while working on modernized window system tabs on the > Windows LAF, see NETBEANS-5673.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5757) Compile-on-Save drops static initializer (vanilla javac)
[
https://issues.apache.org/jira/browse/NETBEANS-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382144#comment-17382144
]
Eirik Bakke commented on NETBEANS-5757:
---
I think this will be fixed by https://github.com/apache/netbeans/pull/3054 .
> Compile-on-Save drops static initializer (vanilla javac)
>
>
> Key: NETBEANS-5757
> URL: https://issues.apache.org/jira/browse/NETBEANS-5757
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.4
> Environment: NetBeans 12.4 _without_ nb-javac installed (started from
> clean user and cache directories to ensure no trace of nb-javac was left from
> my old installation). Java 11.0.11 or Java 17-ea+25. Windows 10.
>Reporter: Eirik Bakke
>Priority: Major
>
> Very great to see Compile-on-Save now working without the external nb-javac
> plugin! Here's the first bug I've found around this. To reproduce, create an
> empty maven-based Java project and add the following class:
> {code:java}
> public class StaticInitializerExample {
> private static final String SOME_CONSTANT;
> static {
> SOME_CONSTANT = "I am a constant.";
> }
> public static final void main(String args[]) {
> System.out.println(SOME_CONSTANT);
> }
> }
> {code}
> Do a clean build and run. The application will print, "I am a constant."
> Now do any trivial change to the code, such as adding a comment, and save.
> Run again. The application will now print "null", rather than the correct
> output.
> Tested on both Java 11.0.11 and Java 17-ea+25. I also tested with NetBeans
> 11.3 with nb-javac installed; in that case the output is correct (still "I am
> a constant."). In the latter case you can also change the constant in the
> static initializer, and CoS will apply the change correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5855) Closing unsaved editor tab from dropdown can put IDE in unusable state
Eirik Bakke created NETBEANS-5855: - Summary: Closing unsaved editor tab from dropdown can put IDE in unusable state Key: NETBEANS-5855 URL: https://issues.apache.org/jira/browse/NETBEANS-5855 Project: NetBeans Issue Type: Bug Components: platform - Window System Affects Versions: 12.4 Reporter: Eirik Bakke If the main editor area's dropdown menu is used to close an editor tab, and said tab has unsaved changes, a dialog will pop up to prompt the user to save their changes. At this point, the left mouse button will no longer work, however, and in fact the left mouse button will continue to not work if the dialog is closed by keyboard action (e.g. pressing Escape). On Windows, it is usually possible to get out of this state by opening a popup menu or other dialog, e.g. by right-clicking something in the Projects pane or clicking in the menu bar (in which mouse clicking does seem to work). On MacOS, however, the state seems persistent; I could not easily figure out how to get out of this state other than by restarting the IDE. The relevant component is org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also https://github.com/apache/netbeans/pull/2528 , which intends to make some changes to this component. And see also https://issues.apache.org/jira/browse/NETBEANS-5853 , which is a more cosmetic repaint bug in the same component. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5853) Repaint problems in tabcontrol ButtonPopupSwitcher
[ https://issues.apache.org/jira/browse/NETBEANS-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5853: -- Description: On the Windows LAF, when using the dropdown menu to select an editor tab, hovering over the "X" button and then moving the mouse cursor to the right outside the switcher popup will cause repaint problems. See the attached GIF, which was prepared by DevCharly (who found the bug during review of [another PR|https://github.com/apache/netbeans/pull/2967]). The component in question is org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also https://github.com/apache/netbeans/pull/2528 , which intends to make some changes in this area. The bug does not appear on MacOS/Aqua. It does appear on both the Windows LAF and FlatLAF Dark on Windows. was: On the Windows LAF, when using the dropdown menu to select an editor tab, hovering over the "X" button and then moving the mouse cursor to the right outside the switcher popup will cause repaint problems. See the attached GIF, which was prepared by DevCharly (who found the bug during review of another PR, see https://github.com/apache/netbeans/pull/2967 ). The component in question is org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also https://github.com/apache/netbeans/pull/2528 , which intends to make some changes in this area. The bug does not appear on MacOS. > Repaint problems in tabcontrol ButtonPopupSwitcher > -- > > Key: NETBEANS-5853 > URL: https://issues.apache.org/jira/browse/NETBEANS-5853 > Project: NetBeans > Issue Type: Bug > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans 12.4 on OpenJDK 11.0.11 on Windows, with > Windows LAF. >Reporter: Eirik Bakke >Priority: Minor > Attachments: Tab Switcher Bug.gif > > > On the Windows LAF, when using the dropdown menu to select an editor tab, > hovering over the "X" button and then moving the mouse cursor to the right > outside the switcher popup will cause repaint problems. See the attached GIF, > which was prepared by DevCharly (who found the bug during review of [another > PR|https://github.com/apache/netbeans/pull/2967]). > The component in question is > org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also > https://github.com/apache/netbeans/pull/2528 , which intends to make some > changes in this area. > The bug does not appear on MacOS/Aqua. It does appear on both the Windows LAF > and FlatLAF Dark on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5853) Repaint problems in tabcontrol ButtonPopupSwitcher
[ https://issues.apache.org/jira/browse/NETBEANS-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5853: -- Description: On the Windows LAF, when using the dropdown menu to select an editor tab, hovering over the "X" button and then moving the mouse cursor to the right outside the switcher popup will cause repaint problems. See the attached GIF, which was prepared by DevCharly (who found the bug during review of another PR, see https://github.com/apache/netbeans/pull/2967 ). The component in question is org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also https://github.com/apache/netbeans/pull/2528 , which intends to make some changes in this area. The bug does not appear on MacOS. was: On the Windows LAF, when using the dropdown menu to select an editor tab, hovering over the "X" button and then moving the mouse cursor to the right outside the switcher popup will cause repaint problems. See the attached GIF, which was prepared by DevCharly (who found the bug during review of another PR, see https://github.com/apache/netbeans/pull/2967 ). The component in question is org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also https://github.com/apache/netbeans/pull/2528 , which intends to make some changes in this area. > Repaint problems in tabcontrol ButtonPopupSwitcher > -- > > Key: NETBEANS-5853 > URL: https://issues.apache.org/jira/browse/NETBEANS-5853 > Project: NetBeans > Issue Type: Bug > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans 12.4 on OpenJDK 11.0.11 on Windows, with > Windows LAF. >Reporter: Eirik Bakke >Priority: Minor > Attachments: Tab Switcher Bug.gif > > > On the Windows LAF, when using the dropdown menu to select an editor tab, > hovering over the "X" button and then moving the mouse cursor to the right > outside the switcher popup will cause repaint problems. See the attached GIF, > which was prepared by DevCharly (who found the bug during review of another > PR, see https://github.com/apache/netbeans/pull/2967 ). > The component in question is > org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also > https://github.com/apache/netbeans/pull/2528 , which intends to make some > changes in this area. > The bug does not appear on MacOS. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5853) Repaint problems in tabcontrol ButtonPopupSwitcher
Eirik Bakke created NETBEANS-5853: - Summary: Repaint problems in tabcontrol ButtonPopupSwitcher Key: NETBEANS-5853 URL: https://issues.apache.org/jira/browse/NETBEANS-5853 Project: NetBeans Issue Type: Bug Components: platform - Window System Affects Versions: 12.4 Environment: NetBeans 12.4 on OpenJDK 11.0.11 on Windows, with Windows LAF. Reporter: Eirik Bakke Attachments: Tab Switcher Bug.gif On the Windows LAF, when using the dropdown menu to select an editor tab, hovering over the "X" button and then moving the mouse cursor to the right outside the switcher popup will cause repaint problems. See the attached GIF, which was prepared by DevCharly (who found the bug during review of another PR, see https://github.com/apache/netbeans/pull/2967 ). The component in question is org.netbeans.swing.tabcontrol.ButtonPopupSwitcher. See also https://github.com/apache/netbeans/pull/2528 , which intends to make some changes in this area. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5757) Compile-on-Save drops static initializer (vanilla javac)
[
https://issues.apache.org/jira/browse/NETBEANS-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5757:
--
Description:
Very great to see Compile-on-Save now working without the external nb-javac
plugin! Here's the first bug I've found around this. To reproduce, create an
empty maven-based Java project and add the following class:
{code:java}
public class StaticInitializerExample {
private static final String SOME_CONSTANT;
static {
SOME_CONSTANT = "I am a constant.";
}
public static final void main(String args[]) {
System.out.println(SOME_CONSTANT);
}
}
{code}
Do a clean build and run. The application will print, "I am a constant."
Now do any trivial change to the code, such as adding a comment, and save. Run
again. The application will now print "null", rather than the correct output.
Tested on both Java 11.0.11 and Java 17-ea+25. I also tested with NetBeans 11.3
with nb-javac installed; in that case the output is correct (still "I am a
constant."). In the latter case you can also change the constant in the static
initializer, and CoS will apply the change correctly.
was:
Very great to see Compile-on-Save now working without the external nb-javac
plugin! Here's the first bug I've found around this. To reproduce, create an
empty maven-based Java project and add the following class:
{code:java}
public class StaticInitializerExample {
private static final String SOME_CONSTANT;
static {
SOME_CONSTANT = "I am a constant.";
}
public static final void main(String args[]) {
System.out.println(SOME_CONSTANT);
}
}
{code}
Do a clean build and run. The application will print, "I am a constant."
Tested on both Java 11.0.11 and Java 17-ea+25.
Now do any trivial change to the code, such as adding a comment, and save. Run
again. The application will now print "null", rather than the correct output. I
tested this with an older NetBeans version with nb-javac as well, and in that
case the output is correct (still "I am a constant.").
> Compile-on-Save drops static initializer (vanilla javac)
>
>
> Key: NETBEANS-5757
> URL: https://issues.apache.org/jira/browse/NETBEANS-5757
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.4
> Environment: NetBeans 12.4 _without_ nb-javac installed (started from
> clean user and cache directories to ensure no trace of nb-javac was left from
> my old installation). Java 11.0.11 or Java 17-ea+25. Windows 10.
>Reporter: Eirik Bakke
>Priority: Major
>
> Very great to see Compile-on-Save now working without the external nb-javac
> plugin! Here's the first bug I've found around this. To reproduce, create an
> empty maven-based Java project and add the following class:
> {code:java}
> public class StaticInitializerExample {
> private static final String SOME_CONSTANT;
> static {
> SOME_CONSTANT = "I am a constant.";
> }
> public static final void main(String args[]) {
> System.out.println(SOME_CONSTANT);
> }
> }
> {code}
> Do a clean build and run. The application will print, "I am a constant."
> Now do any trivial change to the code, such as adding a comment, and save.
> Run again. The application will now print "null", rather than the correct
> output.
> Tested on both Java 11.0.11 and Java 17-ea+25. I also tested with NetBeans
> 11.3 with nb-javac installed; in that case the output is correct (still "I am
> a constant."). In the latter case you can also change the constant in the
> static initializer, and CoS will apply the change correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5757) Compile-on-Save drops static initializer (vanilla javac)
Eirik Bakke created NETBEANS-5757:
-
Summary: Compile-on-Save drops static initializer (vanilla javac)
Key: NETBEANS-5757
URL: https://issues.apache.org/jira/browse/NETBEANS-5757
Project: NetBeans
Issue Type: Bug
Components: java - Compiler
Affects Versions: 12.4
Environment: NetBeans 12.4 _without_ nb-javac installed (started from
clean user and cache directories to ensure no trace of nb-javac was left from
my old installation). Java 11.0.11 or Java 17-ea+25. Windows 10.
Reporter: Eirik Bakke
Very great to see Compile-on-Save now working without the external nb-javac
plugin! Here's the first bug I've found around this. To reproduce, create an
empty maven-based Java project and add the following class:
{code:java}
public class StaticInitializerExample {
private static final String SOME_CONSTANT;
static {
SOME_CONSTANT = "I am a constant.";
}
public static final void main(String args[]) {
System.out.println(SOME_CONSTANT);
}
}
{code}
Do a clean build and run. The application will print, "I am a constant."
Tested on both Java 11.0.11 and Java 17-ea+25.
Now do any trivial change to the code, such as adding a comment, and save. Run
again. The application will now print "null", rather than the correct output. I
tested this with an older NetBeans version with nb-javac as well, and in that
case the output is correct (still "I am a constant.").
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-3410) MIssing "Go to Implementation" keymap shortcut
[ https://issues.apache.org/jira/browse/NETBEANS-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357955#comment-17357955 ] Eirik Bakke edited comment on NETBEANS-3410 at 6/5/21, 10:17 PM: - Seems to be the same issue as NETBEANS-1950. I'm observing this for the "Go to Symbol" action as well. was (Author: ebakke): Seems to be the same issue as the other one. I'm observing this for the "Go to Symbol" action as well. > MIssing "Go to Implementation" keymap shortcut > --- > > Key: NETBEANS-3410 > URL: https://issues.apache.org/jira/browse/NETBEANS-3410 > Project: NetBeans > Issue Type: Improvement > Components: cnd - Navigation >Affects Versions: 11.2 > Environment: Linux Mint 18.3 Sylvia 64-bit > Kernel Linux 4.15.0-70-generic x86_64 > MATE 1.18.0 >Reporter: Jarek >Priority: Minor > Attachments: Screenshot at 2019-11-19 10-45-27.png > > > Missing helpfull "Go to Implementation" action on Options -> keymap in NB > 11.2 Profile NetBeans 5.5, Netbeans. Now it is only possible to call from > context (rmb) menu. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3410) MIssing "Go to Implementation" keymap shortcut
[ https://issues.apache.org/jira/browse/NETBEANS-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357955#comment-17357955 ] Eirik Bakke commented on NETBEANS-3410: --- Seems to be the same issue as the other one. I'm observing this for the "Go to Symbol" action as well. > MIssing "Go to Implementation" keymap shortcut > --- > > Key: NETBEANS-3410 > URL: https://issues.apache.org/jira/browse/NETBEANS-3410 > Project: NetBeans > Issue Type: Improvement > Components: cnd - Navigation >Affects Versions: 11.2 > Environment: Linux Mint 18.3 Sylvia 64-bit > Kernel Linux 4.15.0-70-generic x86_64 > MATE 1.18.0 >Reporter: Jarek >Priority: Minor > Attachments: Screenshot at 2019-11-19 10-45-27.png > > > Missing helpfull "Go to Implementation" action on Options -> keymap in NB > 11.2 Profile NetBeans 5.5, Netbeans. Now it is only possible to call from > context (rmb) menu. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-2617:
--
Attachment: (was: 210604 Icons Overview Cropped.png)
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: 210604 Icons Overview Cropped.png,
> ScreenshotExample.png, ide.editor.bookmarks.ai, ide.editor.macros.ai,
> ide.seperator.breadcrumbs.ai, netbeans_icons_illustrator_template.ai, style
> example (dark filter).png, style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is complex, it is fine to simplify it a bit when
> drawing vectorized versions.
> * Omit gradients, bevels, and unnecessary drop shadows. They take more time
> to draw, and with "flat design", they are now out of fashion in any case.
> * Use a stroke width of 1px around the main shapes in the icon, like in the
> existing bitmap icons. The new icons should look consistent with the existing
> bitmap icons, especially since we may see bitmap icons and vector icons
> side-by-side for a long time. Within shapes, 0.5px strokes can be used for
> finer details. (0.5p
[jira] [Comment Edited] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357413#comment-17357413
]
Eirik Bakke edited comment on NETBEANS-2617 at 6/4/21, 3:12 PM:
I've consolidated the previously drawn SVG icons into a single Illustrator
file, and organized the next batch to be drawn. I might draw an icon or two
here and there, but it won't happen in a single sitting.
!210604 Icons Overview Cropped.png!
was (Author: ebakke):
I've consolidated the previously drawn SVG icons into a single Illustrator
file, and organized the next batch to be drawn. I might draw an icon or two
here and there, but it won't happen in a single sitting.
!210604 Icons Overview Cropped.png!
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: 210604 Icons Overview Cropped.png,
> ScreenshotExample.png, ide.editor.bookmarks.ai, ide.editor.macros.ai,
> ide.seperator.breadcrumbs.ai, netbeans_icons_illustrator_template.ai, style
> example (dark filter).png, style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is co
[jira] [Updated] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-2617:
--
Attachment: (was: 210604 Icons Overview.png)
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: 210604 Icons Overview Cropped.png,
> ScreenshotExample.png, ide.editor.bookmarks.ai, ide.editor.macros.ai,
> ide.seperator.breadcrumbs.ai, netbeans_icons_illustrator_template.ai, style
> example (dark filter).png, style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is complex, it is fine to simplify it a bit when
> drawing vectorized versions.
> * Omit gradients, bevels, and unnecessary drop shadows. They take more time
> to draw, and with "flat design", they are now out of fashion in any case.
> * Use a stroke width of 1px around the main shapes in the icon, like in the
> existing bitmap icons. The new icons should look consistent with the existing
> bitmap icons, especially since we may see bitmap icons and vector icons
> side-by-side for a long time. Within shapes, 0.5px strokes can be used for
> finer details. (0.5px stroke
[jira] [Comment Edited] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357413#comment-17357413
]
Eirik Bakke edited comment on NETBEANS-2617 at 6/4/21, 3:12 PM:
I've consolidated the previously drawn SVG icons into a single Illustrator
file, and organized the next batch to be drawn. I might draw an icon or two
here and there, but it won't happen in a single sitting.
!210604 Icons Overview Cropped.png!
was (Author: ebakke):
I've consolidated the previously drawn SVG icons into a single Illustrator
file, and organized the next batch to be drawn. I might draw an icon or two
here and there, but it won't happen in a single sitting.
!210604 Icons Overview.png!
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: 210604 Icons Overview Cropped.png, 210604 Icons
> Overview.png, ScreenshotExample.png, ide.editor.bookmarks.ai,
> ide.editor.macros.ai, ide.seperator.breadcrumbs.ai,
> netbeans_icons_illustrator_template.ai, style example (dark filter).png,
> style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the
[jira] [Commented] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357413#comment-17357413
]
Eirik Bakke commented on NETBEANS-2617:
---
I've consolidated the previously drawn SVG icons into a single Illustrator
file, and organized the next batch to be drawn. I might draw an icon or two
here and there, but it won't happen in a single sitting.
!210604 Icons Overview.png!
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: 210604 Icons Overview.png, ScreenshotExample.png,
> batch.png, ide.editor.bookmarks.ai, ide.editor.macros.ai,
> ide.seperator.breadcrumbs.ai, netbeans_icons_illustrator_template.ai, style
> example (dark filter).png, style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is complex, it is fine to simplify it a bit when
> drawing vectorized versions.
> * Omit gradients, bevels, and unnecessary drop shadows. They take more time
> to draw, and with "flat design", they are now out of fashion in any case.
> * Use a stroke width of 1px around the main shapes in the icon, like in the
> existing bitma
[jira] [Updated] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-2617:
--
Attachment: 210604 Icons Overview.png
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: 210604 Icons Overview.png, ScreenshotExample.png,
> ide.editor.bookmarks.ai, ide.editor.macros.ai, ide.seperator.breadcrumbs.ai,
> netbeans_icons_illustrator_template.ai, style example (dark filter).png,
> style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is complex, it is fine to simplify it a bit when
> drawing vectorized versions.
> * Omit gradients, bevels, and unnecessary drop shadows. They take more time
> to draw, and with "flat design", they are now out of fashion in any case.
> * Use a stroke width of 1px around the main shapes in the icon, like in the
> existing bitmap icons. The new icons should look consistent with the existing
> bitmap icons, especially since we may see bitmap icons and vector icons
> side-by-side for a long time. Within shapes, 0.5px strokes can be used for
> finer details. (0.5px strokes become 1 device p
[jira] [Updated] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-2617:
--
Attachment: (was: batch.png)
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: 210604 Icons Overview.png, ScreenshotExample.png,
> ide.editor.bookmarks.ai, ide.editor.macros.ai, ide.seperator.breadcrumbs.ai,
> netbeans_icons_illustrator_template.ai, style example (dark filter).png,
> style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is complex, it is fine to simplify it a bit when
> drawing vectorized versions.
> * Omit gradients, bevels, and unnecessary drop shadows. They take more time
> to draw, and with "flat design", they are now out of fashion in any case.
> * Use a stroke width of 1px around the main shapes in the icon, like in the
> existing bitmap icons. The new icons should look consistent with the existing
> bitmap icons, especially since we may see bitmap icons and vector icons
> side-by-side for a long time. Within shapes, 0.5px strokes can be used for
> finer details. (0.5px strokes become 1 device pixel
[jira] [Updated] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-2617:
--
Attachment: batch.png
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: ScreenshotExample.png, batch.png,
> ide.editor.bookmarks.ai, ide.editor.macros.ai, ide.seperator.breadcrumbs.ai,
> netbeans_icons_illustrator_template.ai, style example (dark filter).png,
> style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is complex, it is fine to simplify it a bit when
> drawing vectorized versions.
> * Omit gradients, bevels, and unnecessary drop shadows. They take more time
> to draw, and with "flat design", they are now out of fashion in any case.
> * Use a stroke width of 1px around the main shapes in the icon, like in the
> existing bitmap icons. The new icons should look consistent with the existing
> bitmap icons, especially since we may see bitmap icons and vector icons
> side-by-side for a long time. Within shapes, 0.5px strokes can be used for
> finer details. (0.5px strokes become 1 device pixel on Retina screens, which
>
[jira] [Resolved] (NETBEANS-5723) Spurious "Set sun.java2d.noddraw=true to enable transparent windows" exception in IDE log
[
https://issues.apache.org/jira/browse/NETBEANS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke resolved NETBEANS-5723.
---
Fix Version/s: Next
Resolution: Fixed
PR was merged, marking issue resolved.
> Spurious "Set sun.java2d.noddraw=true to enable transparent windows"
> exception in IDE log
> -
>
> Key: NETBEANS-5723
> URL: https://issues.apache.org/jira/browse/NETBEANS-5723
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Window System
>Affects Versions: 12.2
> Environment: Windows 10 on OpenJDK 11.0.11.
>Reporter: Eirik Bakke
>Assignee: Eirik Bakke
>Priority: Minor
> Labels: pull-request-available
> Fix For: Next
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On Windows, when dragging window system tags with the mouse, the following
> spurious error message may appear on the console running the NetBeans IDE or
> a NetBeans Platform application:
> {noformat}
> INFO [org.netbeans.core.nativeaccess.NativeWindowSystemImpl]
> java.lang.UnsupportedOperationException: Set sun.java2d.noddraw=true to
> enable transparent windows
> at
> com.sun.jna.platform.WindowUtils$W32WindowUtils.setWindowAlpha(WindowUtils.java:796)
> at
> com.sun.jna.platform.WindowUtils.setWindowAlpha(WindowUtils.java:1940)
> [catch] at
> org.netbeans.core.nativeaccess.NativeWindowSystemImpl.setWindowAlpha(NativeWindowSystemImpl.java:88)
> at
> org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.createDragWindow(DragAndDropFeedbackVisualizer.java:89)
> at
> org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.start(DragAndDropFeedbackVisualizer.java:110)
> at
> org.netbeans.core.windows.view.dnd.TopComponentDragSupport.doStartDrag(TopComponentDragSupport.java:402)
> at
> org.netbeans.core.windows.view.dnd.TopComponentDragSupport.eventDispatched(TopComponentDragSupport.java:327)
> at
> java.desktop/java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2194)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2086)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2042)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4917)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4564)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.de
[jira] [Updated] (NETBEANS-5736) Clicking in "Projects" tree should work along entire row
[ https://issues.apache.org/jira/browse/NETBEANS-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5736: -- Description: In the TreeView component, which is used for the "Projects" tab in the NetBeans IDE, the user should be able to click anywhere along the width of the component to select a given node. (Or at least, in the empty space to the right of a component). Similarly, during drag-and-drop operations, the user should be able to drop anywhere to the right of the node's icon. This usability issue came up during user testing of a NetBeans Platform application. The user complained that files with a short filename were harder to click than files with long names. The user, a software engineer, pointed out that the equivalent tree component in IntelliJ allows the entire row to be clicked or dragged at to target a given node. TreeView's behavior is derived from its superclass JTree. The OutlineView component does not have the same problem, as it derives from ETable and in turn JTable. PR to follow... was: In the TreeView component, which is used for the "Projects" tab in the NetBeans IDE, the user should be able to click anywhere along the width of the component to select a given node. Or at least, in the empty space to the right of a component). Similarly, during drag-and-drop operations, the user should be able to drop anywhere to the right of the node's icon. This usability issue came up during user testing of a NetBeans Platform application. The user complained that files with a short filename were harder to click than files with long names. The user, a software engineer, pointed out that the equivalent tree component in IntelliJ allows the entire row to be clicked or dragged at to target a given node. TreeView's behavior is derived from its superclass JTree. The OutlineView component does not have the same problem, as it derives from ETable and in turn JTable. PR to follow... > Clicking in "Projects" tree should work along entire row > > > Key: NETBEANS-5736 > URL: https://issues.apache.org/jira/browse/NETBEANS-5736 > Project: NetBeans > Issue Type: Improvement > Components: platform - Explorer >Affects Versions: 12.2 > Environment: All LAFs (but tested on the Windows LAFs and MacOS/Aqua > LAFs). >Reporter: Eirik Bakke >Priority: Major > > In the TreeView component, which is used for the "Projects" tab in the > NetBeans IDE, the user should be able to click anywhere along the width of > the component to select a given node. (Or at least, in the empty space to the > right of a component). Similarly, during drag-and-drop operations, the user > should be able to drop anywhere to the right of the node's icon. > This usability issue came up during user testing of a NetBeans Platform > application. The user complained that files with a short filename were harder > to click than files with long names. The user, a software engineer, pointed > out that the equivalent tree component in IntelliJ allows the entire row to > be clicked or dragged at to target a given node. > TreeView's behavior is derived from its superclass JTree. The OutlineView > component does not have the same problem, as it derives from ETable and in > turn JTable. > PR to follow... -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5736) Clicking in "Projects" tree should work along entire row
Eirik Bakke created NETBEANS-5736: - Summary: Clicking in "Projects" tree should work along entire row Key: NETBEANS-5736 URL: https://issues.apache.org/jira/browse/NETBEANS-5736 Project: NetBeans Issue Type: Improvement Components: platform - Explorer Affects Versions: 12.2 Environment: All LAFs (but tested on the Windows LAFs and MacOS/Aqua LAFs). Reporter: Eirik Bakke In the TreeView component, which is used for the "Projects" tab in the NetBeans IDE, the user should be able to click anywhere along the width of the component to select a given node. Or at least, in the empty space to the right of a component). Similarly, during drag-and-drop operations, the user should be able to drop anywhere to the right of the node's icon. This usability issue came up during user testing of a NetBeans Platform application. The user complained that files with a short filename were harder to click than files with long names. The user, a software engineer, pointed out that the equivalent tree component in IntelliJ allows the entire row to be clicked or dragged at to target a given node. TreeView's behavior is derived from its superclass JTree. The OutlineView component does not have the same problem, as it derives from ETable and in turn JTable. PR to follow... -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5723) Spurious "Set sun.java2d.noddraw=true to enable transparent windows" exception in IDE log
[
https://issues.apache.org/jira/browse/NETBEANS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5723:
--
Description:
On Windows, when dragging window system tags with the mouse, the following
spurious error message may appear on the console running the NetBeans IDE or a
NetBeans Platform application:
{noformat}
INFO [org.netbeans.core.nativeaccess.NativeWindowSystemImpl]
java.lang.UnsupportedOperationException: Set sun.java2d.noddraw=true to enable
transparent windows
at
com.sun.jna.platform.WindowUtils$W32WindowUtils.setWindowAlpha(WindowUtils.java:796)
at
com.sun.jna.platform.WindowUtils.setWindowAlpha(WindowUtils.java:1940)
[catch] at
org.netbeans.core.nativeaccess.NativeWindowSystemImpl.setWindowAlpha(NativeWindowSystemImpl.java:88)
at
org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.createDragWindow(DragAndDropFeedbackVisualizer.java:89)
at
org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.start(DragAndDropFeedbackVisualizer.java:110)
at
org.netbeans.core.windows.view.dnd.TopComponentDragSupport.doStartDrag(TopComponentDragSupport.java:402)
at
org.netbeans.core.windows.view.dnd.TopComponentDragSupport.eventDispatched(TopComponentDragSupport.java:327)
at
java.desktop/java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2194)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2086)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2042)
at
java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4917)
at
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
at
java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
at
java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4564)
at
java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
at
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
at
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
at
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
{noformat}
The tab preview window that is shown next to the mouse cursor is actually
transparent as intended.
was:
On Windows, when dragging window system tags with the mouse, the following
spurious error message may appear on the console running the NetBeans IDE or a
NetBeans Platform application:
{noformat}
INFO [org.netbeans.core.nativeaccess.NativeWindowSystemImpl]
java.lang.UnsupportedOper
[jira] [Updated] (NETBEANS-5728) ETable/OutlineView drag-and-drop selects spurious nodes
[ https://issues.apache.org/jira/browse/NETBEANS-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5728: -- Summary: ETable/OutlineView drag-and-drop selects spurious nodes (was: OutlineView drag-and-drop selects spurious nodes) > ETable/OutlineView drag-and-drop selects spurious nodes > --- > > Key: NETBEANS-5728 > URL: https://issues.apache.org/jira/browse/NETBEANS-5728 > Project: NetBeans > Issue Type: Improvement > Components: platform - Outline&TreeTable >Affects Versions: 12.2 > Environment: Primarily MacOS, but also occasionally on Windows. >Reporter: Eirik Bakke >Priority: Major > > In an OutlineView with multiple selection enabled, if the user tries to drag > one row to a different position (e.g. to reorder rows when the underlying > nodes support it), additional rows will be selected as the mouse moves over > them during the drag operation. On MacOS, it happens 100% of the time. On > Windows, I've seen this bug happen in the past as well, though much less > frequently. On Windows the bug is merely annoying, but on MacOS the bug makes > OutlineView's drag-and-drop feature unusable. > To reproduce: > 1) One place in the IDE where the OutlineView is used is the "Search Results" > tab. While this node tree doesn't really support reordering results, the > OutlineView can still be used to exhibit the bug. Open some project, > right-click the project node, click "Find..." and search for something that > will bring up multiple (~5 or more) results. > 2) Drag the first result row a couple of rows down, holding the left mouse > button down to observe the bug. If the bug does not appear, let go and try > again until it does. On Windows, you may need to start dragging from the > lower part of the row you're trying to drag, and the dragged mouse cursor may > need to exit onto the next row within a certain time period from when the > left mouse button was pressed. On MacOS, the bug happens every time, > regardless of how long I wait hovering over the original row while holding > down the mouse button before beginning to drag across other rows. > Because the bug appears in both Windows and MacOS, albeit more rarely on > Windows, I suspect a fix that works in Windows would also fix the issue on > MacOS. Because of the timing aspect when reproducing the bug in Windows, > there appears to be some kind of race condition. Maybe there's some kind of > "selection rectangle" concept that doesn't get properly turned off in the > OutlineView. > The problem is in JTable (see > https://stackoverflow.com/questions/5969258/how-to-make-jtable-click-on-unselected-do-a-drag-instead-of-a-select > ), but can be worked around in OutlineView. > (This report is a revival of the old BugZilla issue > https://bz.apache.org/netbeans/show_bug.cgi?id=230690 ) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5729) Support HiDPI scaling in TreeView's long file name tooltip (e.g. in Projects pane)
[ https://issues.apache.org/jira/browse/NETBEANS-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5729: -- Description: When hovering over a long filename in the Projects pane, a tooltip is shown to show the entire filename as it extends beyond the edge of the scroll viewport. This tooltip needs to be updated to look good on HiDPI/Retina screens. This problem occurs on MacOS, but not on Windows 10. On Windows 10 it would be good to improve the alignment of the border, however. The relevant code is in org.openide.explorer.view.ViewTooltips.ImgComp. was: When hovering over a long filename in the Projects pane, a tooltip is shown to show the entire filename as it extends beyond the edge of the scroll viewport. This tooltip needs to be updated to look good on HiDPI/Retina screens. The relevant code is in org.openide.explorer.view.ViewTooltips.ImgComp. Environment: (was: All LAFs.) > Support HiDPI scaling in TreeView's long file name tooltip (e.g. in Projects > pane) > -- > > Key: NETBEANS-5729 > URL: https://issues.apache.org/jira/browse/NETBEANS-5729 > Project: NetBeans > Issue Type: Improvement > Components: platform - Outline&TreeTable >Affects Versions: 12.2 >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > > When hovering over a long filename in the Projects pane, a tooltip is shown > to show the entire filename as it extends beyond the edge of the scroll > viewport. This tooltip needs to be updated to look good on HiDPI/Retina > screens. > This problem occurs on MacOS, but not on Windows 10. On Windows 10 it would > be good to improve the alignment of the border, however. > The relevant code is in org.openide.explorer.view.ViewTooltips.ImgComp. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5729) Support HiDPI scaling in TreeView's long file name tooltip (e.g. in Projects pane)
Eirik Bakke created NETBEANS-5729: - Summary: Support HiDPI scaling in TreeView's long file name tooltip (e.g. in Projects pane) Key: NETBEANS-5729 URL: https://issues.apache.org/jira/browse/NETBEANS-5729 Project: NetBeans Issue Type: Improvement Components: platform - Outline&TreeTable Affects Versions: 12.2 Environment: All LAFs. Reporter: Eirik Bakke When hovering over a long filename in the Projects pane, a tooltip is shown to show the entire filename as it extends beyond the edge of the scroll viewport. This tooltip needs to be updated to look good on HiDPI/Retina screens. The relevant code is in org.openide.explorer.view.ViewTooltips.ImgComp. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5728) OutlineView drag-and-drop selects spurious nodes
Eirik Bakke created NETBEANS-5728: - Summary: OutlineView drag-and-drop selects spurious nodes Key: NETBEANS-5728 URL: https://issues.apache.org/jira/browse/NETBEANS-5728 Project: NetBeans Issue Type: Improvement Components: platform - Outline&TreeTable Affects Versions: 12.2 Environment: Primarily MacOS, but also occasionally on Windows. Reporter: Eirik Bakke In an OutlineView with multiple selection enabled, if the user tries to drag one row to a different position (e.g. to reorder rows when the underlying nodes support it), additional rows will be selected as the mouse moves over them during the drag operation. On MacOS, it happens 100% of the time. On Windows, I've seen this bug happen in the past as well, though much less frequently. On Windows the bug is merely annoying, but on MacOS the bug makes OutlineView's drag-and-drop feature unusable. To reproduce: 1) One place in the IDE where the OutlineView is used is the "Search Results" tab. While this node tree doesn't really support reordering results, the OutlineView can still be used to exhibit the bug. Open some project, right-click the project node, click "Find..." and search for something that will bring up multiple (~5 or more) results. 2) Drag the first result row a couple of rows down, holding the left mouse button down to observe the bug. If the bug does not appear, let go and try again until it does. On Windows, you may need to start dragging from the lower part of the row you're trying to drag, and the dragged mouse cursor may need to exit onto the next row within a certain time period from when the left mouse button was pressed. On MacOS, the bug happens every time, regardless of how long I wait hovering over the original row while holding down the mouse button before beginning to drag across other rows. Because the bug appears in both Windows and MacOS, albeit more rarely on Windows, I suspect a fix that works in Windows would also fix the issue on MacOS. Because of the timing aspect when reproducing the bug in Windows, there appears to be some kind of race condition. Maybe there's some kind of "selection rectangle" concept that doesn't get properly turned off in the OutlineView. The problem is in JTable (see https://stackoverflow.com/questions/5969258/how-to-make-jtable-click-on-unselected-do-a-drag-instead-of-a-select ), but can be worked around in OutlineView. (This report is a revival of the old BugZilla issue https://bz.apache.org/netbeans/show_bug.cgi?id=230690 ) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-5726) Checkmark next to "Show Editor Toolbar" menu item can get out of sync with actual setting
[ https://issues.apache.org/jira/browse/NETBEANS-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353440#comment-17353440 ] Eirik Bakke edited comment on NETBEANS-5726 at 5/28/21, 4:20 PM: - The bug also appears if the "Toggle Toolbar" (="Show Editor Toolbar" in the menu) action is assigned a keyboard shortcut and invoked using the shortcut. The menu item just doesn't respond to external changes to the preferences. This is due to the action being lazily initialized, which doesn't work for actions which need to track and show external state. Will submit a PR... was (Author: ebakke): The bug also appears if the "Toggle Toolbar" (="Show Editor Toolbar" in the menu) action is assigned a keyboard shortcut and invoked using the shortcut. The menu item just doesn't respond to external changes to the preferences. This is due to the action being lazily initialized, which doesn't work for actions which need to track external state. Will submit a PR... > Checkmark next to "Show Editor Toolbar" menu item can get out of sync with > actual setting > - > > Key: NETBEANS-5726 > URL: https://issues.apache.org/jira/browse/NETBEANS-5726 > Project: NetBeans > Issue Type: Improvement > Components: editor - Options >Affects Versions: 12.2 > Environment: All OSes. >Reporter: Eirik Bakke >Priority: Major > > The checkmark next to the "Show Editor Toolbar" menu item can get out of sync > with actual setting. > To reproduce: > 1) Open a file for editing in the NetBeans editor. > 2) Click View->"Show Only Editor" > 3) Click View->"Show Editor Toolbar" > 4) Click View->"Show Only Editor" > 5) Click View->"Show Editor Toolbar" > 6) There's now a checkmark next to View->"Show Editor Toolbar", even though > there is no editor toolbar showing. > It seems the checkbox in the menu is inverted on every click rather than > properly being bound to the underlying "toolbarVisible" preference from the > java.util.prefs.Preferences system, which is (rightly) modified by the "Show > Only Editor" action. > (This bug report is a copy of the old BugZilla bug > https://bz.apache.org/netbeans/show_bug.cgi?id=240513 .) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5726) Checkmark next to "Show Editor Toolbar" menu item can get out of sync with actual setting
[ https://issues.apache.org/jira/browse/NETBEANS-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353440#comment-17353440 ] Eirik Bakke commented on NETBEANS-5726: --- The bug also appears if the "Toggle Toolbar" (="Show Editor Toolbar" in the menu) action is assigned a keyboard shortcut and invoked using the shortcut. The menu item just doesn't respond to external changes to the preferences. This is due to the action being lazily initialized, which doesn't work for actions which need to track external state. Will submit a PR... > Checkmark next to "Show Editor Toolbar" menu item can get out of sync with > actual setting > - > > Key: NETBEANS-5726 > URL: https://issues.apache.org/jira/browse/NETBEANS-5726 > Project: NetBeans > Issue Type: Improvement > Components: editor - Options >Affects Versions: 12.2 > Environment: All OSes. >Reporter: Eirik Bakke >Priority: Major > > The checkmark next to the "Show Editor Toolbar" menu item can get out of sync > with actual setting. > To reproduce: > 1) Open a file for editing in the NetBeans editor. > 2) Click View->"Show Only Editor" > 3) Click View->"Show Editor Toolbar" > 4) Click View->"Show Only Editor" > 5) Click View->"Show Editor Toolbar" > 6) There's now a checkmark next to View->"Show Editor Toolbar", even though > there is no editor toolbar showing. > It seems the checkbox in the menu is inverted on every click rather than > properly being bound to the underlying "toolbarVisible" preference from the > java.util.prefs.Preferences system, which is (rightly) modified by the "Show > Only Editor" action. > (This bug report is a copy of the old BugZilla bug > https://bz.apache.org/netbeans/show_bug.cgi?id=240513 .) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5726) Checkmark next to "Show Editor Toolbar" menu item can get out of sync with actual setting
[ https://issues.apache.org/jira/browse/NETBEANS-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352898#comment-17352898 ] Eirik Bakke commented on NETBEANS-5726: --- Notes from looking into this: There are three implementations of this action in the NetBeans sources; only the ToggleAction in the editor.actions module is actually in use. The action is called toggle-toolbar, and it is an AbstractEditorAction wrapped in a WrapperEditorAction. The AbstractEditorAction seems to properly respond to external changes in the Preferences, setting Action.SELECTED_KEY to the appropriate value. But this is not picked up on by PresenterUpdater, presumably because it's listening to a WrapperAction rather than the AbstractEditorAction. > Checkmark next to "Show Editor Toolbar" menu item can get out of sync with > actual setting > - > > Key: NETBEANS-5726 > URL: https://issues.apache.org/jira/browse/NETBEANS-5726 > Project: NetBeans > Issue Type: Improvement > Components: editor - Options >Affects Versions: 12.2 > Environment: All OSes. >Reporter: Eirik Bakke >Priority: Major > > The checkmark next to the "Show Editor Toolbar" menu item can get out of sync > with actual setting. > To reproduce: > 1) Open a file for editing in the NetBeans editor. > 2) Click View->"Show Only Editor" > 3) Click View->"Show Editor Toolbar" > 4) Click View->"Show Only Editor" > 5) Click View->"Show Editor Toolbar" > 6) There's now a checkmark next to View->"Show Editor Toolbar", even though > there is no editor toolbar showing. > It seems the checkbox in the menu is inverted on every click rather than > properly being bound to the underlying "toolbarVisible" preference from the > java.util.prefs.Preferences system, which is (rightly) modified by the "Show > Only Editor" action. > (This bug report is a copy of the old BugZilla bug > https://bz.apache.org/netbeans/show_bug.cgi?id=240513 .) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5726) Checkmark next to "Show Editor Toolbar" menu item can get out of sync with actual setting
Eirik Bakke created NETBEANS-5726: - Summary: Checkmark next to "Show Editor Toolbar" menu item can get out of sync with actual setting Key: NETBEANS-5726 URL: https://issues.apache.org/jira/browse/NETBEANS-5726 Project: NetBeans Issue Type: Improvement Components: editor - Options Affects Versions: 12.2 Environment: All OSes. Reporter: Eirik Bakke The checkmark next to the "Show Editor Toolbar" menu item can get out of sync with actual setting. To reproduce: 1) Open a file for editing in the NetBeans editor. 2) Click View->"Show Only Editor" 3) Click View->"Show Editor Toolbar" 4) Click View->"Show Only Editor" 5) Click View->"Show Editor Toolbar" 6) There's now a checkmark next to View->"Show Editor Toolbar", even though there is no editor toolbar showing. It seems the checkbox in the menu is inverted on every click rather than properly being bound to the underlying "toolbarVisible" preference from the java.util.prefs.Preferences system, which is (rightly) modified by the "Show Only Editor" action. (This bug report is a copy of the old BugZilla bug https://bz.apache.org/netbeans/show_bug.cgi?id=240513 .) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5724) Preview image of dragged tabs need HiDPI quality
Eirik Bakke created NETBEANS-5724: - Summary: Preview image of dragged tabs need HiDPI quality Key: NETBEANS-5724 URL: https://issues.apache.org/jira/browse/NETBEANS-5724 Project: NetBeans Issue Type: Improvement Environment: Windows, Linux, and MacOS with Retina/HiDPI scaling enabled. Reporter: Eirik Bakke When window system tabs are dragged with the mouse for repositioning, a small preview image of the tab is shown next to the mouse cursor. This preview image needs to be rendered at a higher resolution when HiDPI scaling is active. (No work planned on this yet... just adding the issue so it shows up on the list of HiDPI issues at https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements .) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5723) Spurious "Set sun.java2d.noddraw=true to enable transparent windows" exception in IDE log
[
https://issues.apache.org/jira/browse/NETBEANS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5723:
--
Description:
On Windows, when dragging window system tags with the mouse, the following
spurious error message may appear on the console running the NetBeans IDE or a
NetBeans Platform application:
{noformat}
INFO [org.netbeans.core.nativeaccess.NativeWindowSystemImpl]
java.lang.UnsupportedOperationException: Set sun.java2d.noddraw=true to enable
transparent windows
at
com.sun.jna.platform.WindowUtils$W32WindowUtils.setWindowAlpha(WindowUtils.java:796)
at
com.sun.jna.platform.WindowUtils.setWindowAlpha(WindowUtils.java:1940)
[catch] at
org.netbeans.core.nativeaccess.NativeWindowSystemImpl.setWindowAlpha(NativeWindowSystemImpl.java:88)
at
org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.createDragWindow(DragAndDropFeedbackVisualizer.java:89)
at
org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.start(DragAndDropFeedbackVisualizer.java:110)
at
org.netbeans.core.windows.view.dnd.TopComponentDragSupport.doStartDrag(TopComponentDragSupport.java:402)
at
org.netbeans.core.windows.view.dnd.TopComponentDragSupport.eventDispatched(TopComponentDragSupport.java:327)
at
java.desktop/java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2194)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2086)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2042)
at
java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4917)
at
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
at
java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
at
java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4564)
at
java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
at
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
at
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
at
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
{noformat}
The tab preview window that is shown next to the mouse cursor is actually
transparent as intended.
At some point I'll get around to getting rid of this log message...
was:
On Windows, when dragging window system tags with the mouse, the following
spurious error message may appear on the console running the NetBeans IDE or a
NetBeans Platform application:
{noformat}
java.lang.Unsuppor
[jira] [Assigned] (NETBEANS-5723) Spurious "Set sun.java2d.noddraw=true to enable transparent windows" exception in IDE log
[
https://issues.apache.org/jira/browse/NETBEANS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke reassigned NETBEANS-5723:
-
Assignee: Eirik Bakke
> Spurious "Set sun.java2d.noddraw=true to enable transparent windows"
> exception in IDE log
> -
>
> Key: NETBEANS-5723
> URL: https://issues.apache.org/jira/browse/NETBEANS-5723
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Window System
>Affects Versions: 12.2
> Environment: Windows 10 on OpenJDK 11.0.11.
>Reporter: Eirik Bakke
>Assignee: Eirik Bakke
>Priority: Minor
>
> On Windows, when dragging window system tags with the mouse, the following
> spurious error message may appear on the console running the NetBeans IDE or
> a NetBeans Platform application:
> {noformat}
> INFO [org.netbeans.core.nativeaccess.NativeWindowSystemImpl]
> java.lang.UnsupportedOperationException: Set sun.java2d.noddraw=true to
> enable transparent windows
> at
> com.sun.jna.platform.WindowUtils$W32WindowUtils.setWindowAlpha(WindowUtils.java:796)
> at
> com.sun.jna.platform.WindowUtils.setWindowAlpha(WindowUtils.java:1940)
> [catch] at
> org.netbeans.core.nativeaccess.NativeWindowSystemImpl.setWindowAlpha(NativeWindowSystemImpl.java:88)
> at
> org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.createDragWindow(DragAndDropFeedbackVisualizer.java:89)
> at
> org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.start(DragAndDropFeedbackVisualizer.java:110)
> at
> org.netbeans.core.windows.view.dnd.TopComponentDragSupport.doStartDrag(TopComponentDragSupport.java:402)
> at
> org.netbeans.core.windows.view.dnd.TopComponentDragSupport.eventDispatched(TopComponentDragSupport.java:327)
> at
> java.desktop/java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2194)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2086)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
> at
> java.desktop/java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2042)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4917)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4564)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
[jira] [Created] (NETBEANS-5723) Spurious "Set sun.java2d.noddraw=true to enable transparent windows" exception in IDE log
Eirik Bakke created NETBEANS-5723:
-
Summary: Spurious "Set sun.java2d.noddraw=true to enable
transparent windows" exception in IDE log
Key: NETBEANS-5723
URL: https://issues.apache.org/jira/browse/NETBEANS-5723
Project: NetBeans
Issue Type: Improvement
Components: platform - Window System
Affects Versions: 12.2
Environment: Windows 10 on OpenJDK 11.0.11.
Reporter: Eirik Bakke
On Windows, when dragging window system tags with the mouse, the following
spurious error message may appear on the console running the NetBeans IDE or a
NetBeans Platform application:
{noformat}
java.lang.UnsupportedOperationException: Set sun.java2d.noddraw=true to enable
transparent windowsjava.lang.UnsupportedOperationException: Set
sun.java2d.noddraw=true to enable transparent windows at
com.sun.jna.platform.WindowUtils$W32WindowUtils.setWindowAlpha(WindowUtils.java:796)
at
com.sun.jna.platform.WindowUtils.setWindowAlpha(WindowUtils.java:1940)[catch]
at
org.netbeans.core.nativeaccess.NativeWindowSystemImpl.setWindowAlpha(NativeWindowSystemImpl.java:88)
at
org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.createDragWindow(DragAndDropFeedbackVisualizer.java:89)
at
org.netbeans.core.windows.view.dnd.DragAndDropFeedbackVisualizer.start(DragAndDropFeedbackVisualizer.java:110)
at
org.netbeans.core.windows.view.dnd.TopComponentDragSupport.doStartDrag(TopComponentDragSupport.java:402)
at
org.netbeans.core.windows.view.dnd.TopComponentDragSupport.eventDispatched(TopComponentDragSupport.java:327)
at
java.desktop/java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2194)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2086)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at
java.desktop/java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2085)
at java.desktop/java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2042) at
java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4917) at
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) at
java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) at
java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
at
java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4564)
at
java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) at
java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) at
java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) at
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) at
java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at
java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at
java.base/java.security.AccessController.doPrivileged(Native Method) at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) at
java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) at
java.base/java.security.AccessController.doPrivileged(Native Method) at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
at
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90){noformat}
The tab preview window that is shown next to the mouse cursor is actually
transparent as intended.
At some point I'll get around to getting rid of this log message...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netb
[jira] [Resolved] (NETBEANS-5658) Add remaining SVG icons in editor toolbar
[ https://issues.apache.org/jira/browse/NETBEANS-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke resolved NETBEANS-5658. --- Fix Version/s: Next Resolution: Fixed PR was merged; marking fixed. > Add remaining SVG icons in editor toolbar > - > > Key: NETBEANS-5658 > URL: https://issues.apache.org/jira/browse/NETBEANS-5658 > Project: NetBeans > Issue Type: Improvement > Components: editor - Other >Affects Versions: 12.2 >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Fix For: Next > > Attachments: MoreEditorToolbarIconsEirik.ai > > Time Spent: 40m > Remaining Estimate: 0h > > See the associated Pull Request, which adds 14 more SVG icons, adjusts two > existing ones, and reuses some existing ones for newly identified duplicates. > See NETBEANS-2617 for a more detailed description of this effort. > The Adobe Illustrator file that was used to produce the latest icons is > attached here. I haven't cleaned up the Illustrator file, so it may contain > some duplicates from previous Illustrator file in NETBEANS-2617. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-426) png file not viewed in scale in retina display
[ https://issues.apache.org/jira/browse/NETBEANS-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348682#comment-17348682 ] Eirik Bakke commented on NETBEANS-426: -- The right behavior here depends on the definition of "1:1" here. The current behavior maps one pixel in the image to one logical pixel (=two device pixels on retina) on the screen. But it's probably more useful to have the zoom rate be influenced by the HiDPI scaling factor of whichever screen the image is showing on when the "1:1" button is clicked, so that each pixel in the image maps to a device pixel on the screen. If you move the window to a different screen, with a different HiDPI scaling level, it'd be OK to require that the user presses the "1:1" button again. > png file not viewed in scale in retina display > -- > > Key: NETBEANS-426 > URL: https://issues.apache.org/jira/browse/NETBEANS-426 > Project: NetBeans > Issue Type: Bug > Components: ide - UI >Affects Versions: 8.2 >Reporter: Peter >Priority: Major > Labels: HiDPI > Attachments: icon is not one-to-one in scale if in retina.png > > > png file not viewed in scale in retina display -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Attachment: MacOS Catalina Border Style Example.png > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Attachments: Java 11 Tabs New.png, Java 11 Tabs Old.png, MacOS > Catalina Border Style Example.png, Summary.png > > Time Spent: 10m > Remaining Estimate: 0h > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of headaches. > The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with > the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style > has changed a bit, with either bright or dark colors depending on light/dark > mode (rather than midtone greys), and "glass pane" textures rather than > metallic surface gradients. It's probably best to keep the existing Aqua LAF > style for now, though perhaps some of the bevel effects could go away to make > it look more up-to-date. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Attachment: Summary.png Java 11 Tabs Old.png Java 11 Tabs New.png > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Attachments: Java 11 Tabs New.png, Java 11 Tabs Old.png, Summary.png > > Time Spent: 10m > Remaining Estimate: 0h > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of headaches. > The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with > the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style > has changed a bit, with either bright or dark colors depending on light/dark > mode (rather than midtone greys), and "glass pane" textures rather than > metallic surface gradients. It's probably best to keep the existing Aqua LAF > style for now, though perhaps some of the bevel effects could go away to make > it look more up-to-date. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Description: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of headaches. The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style has changed a bit, with either bright or dark colors depending on light/dark mode (rather than midtone greys), and "glass pane" textures rather than metallic surface gradients. It's probably best to keep the existing Aqua LAF style for now, though perhaps some of the bevel effects could go away to make it look more up-to-date. was: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style has changed a bit, with either bright or dark colors depending on light/dark mode (rather than midtone greys), and "glass pane" textures rather than metallic surface gradients. It's probably best to keep the existing Aqua LAF style for now, though perhaps some of the bevel effects could go away to make it look more up-to-date. > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of headaches. > The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with > the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style > has changed a bit, with either bright or dark colors depending on light/dark > mode (rather than midtone greys), and "glass pane" textures rather than > metallic surface gradients. It's probably best to keep the existing Aqua LAF > style for now, though perhaps some of the bevel effects could go away to make > it look more up-to-date. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Description: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style has changed a bit, with either bright or dark colors depending on light/dark mode (rather than midtone greys), and "glass pane" textures rather than metallic surface gradients. It's probably best to keep the existing Aqua LAF style for now, though perhaps some of the bevel effects could go away to make it look more up-to-date. was: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with the look of native apps on MacOS Catalina. On MacOS Big Sur, the style has changed a bit, with either bright or dark colors depending on light/dark mode (rather than midtone greys), and "glass panes" rather than metal gradients. It's probably best to keep the existing Aqua LAF style for now, though perhaps some of the bevel effects could go away to make it look more modern. > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of > additional headaches. > The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with > the look of native apps on MacOS Catalina. On MacOS Big Sur, the visual style > has changed a bit, with either bright or dark colors depending on light/dark > mode (rather than midtone greys), and "glass pane" textures rather than > metallic surface gradients. It's probably best to keep the existing Aqua LAF > style for now, though perhaps some of the bevel effects could go away to make > it look more up-to-date. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Description: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with the look of native apps on MacOS Catalina. On MacOS Big Sur, the style has changed a bit, with either bright or dark colors depending on light/dark mode (rather than midtone greys), and "glass panes" rather than metal gradients. It's probably best to keep the existing Aqua LAF style for now, though perhaps some of the bevel effects could go away to make it look more modern. was: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with the look of native apps on MacOS Catalina. Though MacOS Big Sur might change the style a bit; I haven't had a chance to check it out yet. > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of > additional headaches. > The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with > the look of native apps on MacOS Catalina. On MacOS Big Sur, the style has > changed a bit, with either bright or dark colors depending on light/dark mode > (rather than midtone greys), and "glass panes" rather than metal gradients. > It's probably best to keep the existing Aqua LAF style for now, though > perhaps some of the bevel effects could go away to make it look more modern. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Description: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with the look of native apps on MacOS Catalina. Though MacOS Big Sur might change the style a bit; I haven't had a chance to check it out yet. was: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern, and consistent with the look of native apps on MacOS (as of MacOS Catalina). > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of > additional headaches. > The Aqua LAF otherwise looks reasonably modern. It's fairly consistent with > the look of native apps on MacOS Catalina. Though MacOS Big Sur might change > the style a bit; I haven't had a chance to check it out yet. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Environment: MacOS with Aqua LAF (was: MacOS with Aqua LAF.) > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of > additional headaches. > The Aqua LAF otherwise looks reasonably modern, and consistent with the look > of native apps on MacOS (as of MacOS Catalina). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
[ https://issues.apache.org/jira/browse/NETBEANS-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5698: -- Description: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern, and consistent with the look of native apps on MacOS (as of MacOS Catalina). was: The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern, and consistent with the look of native apps (on MacOS Catalina the last time I checked). > Improve tab component appearance on Retina displays (MacOS/Aqua LAF) > > > Key: NETBEANS-5698 > URL: https://issues.apache.org/jira/browse/NETBEANS-5698 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: MacOS with Aqua LAF. >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > > The tab components used by the window system on the Aqua (MacOS) LAF have a > few visual imperfections when scaled up for Retina displays. It'll be good to > fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina > displays are always scaled at exactly 2x, this should be a lot easier than on > Windows, where fractional scalings like 150% tend to cause a lot of > additional headaches. > The Aqua LAF otherwise looks reasonably modern, and consistent with the look > of native apps on MacOS (as of MacOS Catalina). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5698) Improve tab component appearance on Retina displays (MacOS/Aqua LAF)
Eirik Bakke created NETBEANS-5698: - Summary: Improve tab component appearance on Retina displays (MacOS/Aqua LAF) Key: NETBEANS-5698 URL: https://issues.apache.org/jira/browse/NETBEANS-5698 Project: NetBeans Issue Type: Improvement Components: platform - Window System Affects Versions: 12.2 Environment: MacOS with Aqua LAF. Reporter: Eirik Bakke The tab components used by the window system on the Aqua (MacOS) LAF have a few visual imperfections when scaled up for Retina displays. It'll be good to fix these, as was done for the Windows LAF in NETBEANS-5673. Since Retina displays are always scaled at exactly 2x, this should be a lot easier than on Windows, where fractional scalings like 150% tend to cause a lot of additional headaches. The Aqua LAF otherwise looks reasonably modern, and consistent with the look of native apps (on MacOS Catalina the last time I checked). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5697) Various smaller LAF/HiDPI improvements in Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5697: -- Labels: HiDPI (was: ) > Various smaller LAF/HiDPI improvements in Windows LAF > - > > Key: NETBEANS-5697 > URL: https://issues.apache.org/jira/browse/NETBEANS-5697 > Project: NetBeans > Issue Type: Improvement > Environment: Windows LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: 210517 Menu Checkbox Bug.png, Smaller fixes.png > > > This issue was created for a Pull Request covering a number of smaller > improvements to the Windows LAF: > * Apply Windows LAF HiDPI bug workarounds from NETBEANS-3592 to > JCheckboxMenuItem and friends. > * Apply previous border tweaks for HiDPI screens in a few more places, > notably in tooltips and the quick search text field, and in the editor > toolbar. Improve JSpinner borders. > * Make the background color of tooltips consistent with that of other > Windows 10 apps. > * Add some pixels of left margin to the editor toolbar. > See attached screenshots. > (This work was done while working on modernized window system tabs on the > Windows LAF, see NETBEANS-5673.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5696) Replace animated spinner icon with HiDPI-scalable version
[ https://issues.apache.org/jira/browse/NETBEANS-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5696: -- Labels: HiDPI (was: ) > Replace animated spinner icon with HiDPI-scalable version > - > > Key: NETBEANS-5696 > URL: https://issues.apache.org/jira/browse/NETBEANS-5696 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.2 > Environment: All LAFs. >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: New Spinner Icon.png > > > The window system tabs component has a spinning "busy" icon which is > displayed e.g. while the Navigator is initially loading. This issue's Pull > Request replaces the current bitmap-based icon (busy_icon.png) with a > scalable spinner graphic (drawn with Java2D code) that looks better on HiDPI > and Retina screens. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5697) Various smaller LAF/HiDPI improvements in Windows LAF
Eirik Bakke created NETBEANS-5697: - Summary: Various smaller LAF/HiDPI improvements in Windows LAF Key: NETBEANS-5697 URL: https://issues.apache.org/jira/browse/NETBEANS-5697 Project: NetBeans Issue Type: Improvement Environment: Windows LAF Reporter: Eirik Bakke Attachments: 210517 Menu Checkbox Bug.png, Smaller fixes.png This issue was created for a Pull Request covering a number of smaller improvements to the Windows LAF: * Apply Windows LAF HiDPI bug workarounds from NETBEANS-3592 to JCheckboxMenuItem and friends. * Apply previous border tweaks for HiDPI screens in a few more places, notably in tooltips and the quick search text field, and in the editor toolbar. Improve JSpinner borders. * Make the background color of tooltips consistent with that of other Windows 10 apps. * Add some pixels of left margin to the editor toolbar. See attached screenshots. (This work was done while working on modernized window system tabs on the Windows LAF, see NETBEANS-5673.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5696) Replace animated spinner icon with HiDPI-scalable version
Eirik Bakke created NETBEANS-5696: - Summary: Replace animated spinner icon with HiDPI-scalable version Key: NETBEANS-5696 URL: https://issues.apache.org/jira/browse/NETBEANS-5696 Project: NetBeans Issue Type: Improvement Components: platform - Window System Affects Versions: 12.2 Environment: All LAFs. Reporter: Eirik Bakke Attachments: New Spinner Icon.png The window system tabs component has a spinning "busy" icon which is displayed e.g. while the Navigator is initially loading. This issue's Pull Request replaces the current bitmap-based icon (busy_icon.png) with a scalable spinner graphic (drawn with Java2D code) that looks better on HiDPI and Retina screens. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Assigned] (NETBEANS-5697) Various smaller LAF/HiDPI improvements in Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke reassigned NETBEANS-5697: - Assignee: Eirik Bakke > Various smaller LAF/HiDPI improvements in Windows LAF > - > > Key: NETBEANS-5697 > URL: https://issues.apache.org/jira/browse/NETBEANS-5697 > Project: NetBeans > Issue Type: Improvement > Environment: Windows LAF >Reporter: Eirik Bakke >Assignee: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: 210517 Menu Checkbox Bug.png, Smaller fixes.png > > > This issue was created for a Pull Request covering a number of smaller > improvements to the Windows LAF: > * Apply Windows LAF HiDPI bug workarounds from NETBEANS-3592 to > JCheckboxMenuItem and friends. > * Apply previous border tweaks for HiDPI screens in a few more places, > notably in tooltips and the quick search text field, and in the editor > toolbar. Improve JSpinner borders. > * Make the background color of tooltips consistent with that of other > Windows 10 apps. > * Add some pixels of left margin to the editor toolbar. > See attached screenshots. > (This work was done while working on modernized window system tabs on the > Windows LAF, see NETBEANS-5673.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Assigned] (NETBEANS-5697) Various smaller LAF/HiDPI improvements in Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke reassigned NETBEANS-5697: - Assignee: (was: Eirik Bakke) > Various smaller LAF/HiDPI improvements in Windows LAF > - > > Key: NETBEANS-5697 > URL: https://issues.apache.org/jira/browse/NETBEANS-5697 > Project: NetBeans > Issue Type: Improvement > Environment: Windows LAF >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: 210517 Menu Checkbox Bug.png, Smaller fixes.png > > > This issue was created for a Pull Request covering a number of smaller > improvements to the Windows LAF: > * Apply Windows LAF HiDPI bug workarounds from NETBEANS-3592 to > JCheckboxMenuItem and friends. > * Apply previous border tweaks for HiDPI screens in a few more places, > notably in tooltips and the quick search text field, and in the editor > toolbar. Improve JSpinner borders. > * Make the background color of tooltips consistent with that of other > Windows 10 apps. > * Add some pixels of left margin to the editor toolbar. > See attached screenshots. > (This work was done while working on modernized window system tabs on the > Windows LAF, see NETBEANS-5673.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5673: -- Description: The tab components used for TopComponents and the Project/Navigator sidebar look somewhat dated on the Windows LAF, and need improvements for HiDPI screens. I'll be making improvements on this for my NetBeans Platform-based application, and will likely be making an upstream PR for this in the future (which will benefit the IDE and other NetBeans Platform apps). Specific improvements planned: * Make the sidebar and TopComponent tabs consistent, and modernize the look of the tabs a bit. * Remove out-of-fashion gradients. * Remove out-of-fashion bevels. * Get rid of the extra borders in the sidebar (Projects/Files/Services in the IDE). * Make line thicknesses HiDPI-safe. * Make lines line up and connect on HiDPI scalings above 100%. HiDPI icons for the Windows LAF tab controls were previously added in NETBEANS-1238. Improvements to borders on HiDPI screens were done in NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in NETBEANS-3592. was: The tab components used for TopComponents and the Project/Navigator sidebar look somewhat dated on the Windows LAF, and need improvements for HiDPI screens. I'll be making improvements on this for my NetBeans Platform-based application, and will likely be making an upstream PR for this in the future (which will benefit the IDE and other NetBeans Platform apps). Specific improvements planned: * Make the sidebar and TopComponent tabs consistent, and modernize the look of the tabs a bit. * Remove out-of-fashion gradients. * Remove out-of-fashion bevels. * Get rid of the extra borders in the sidebar (Projects/Files/Services in the IDE). * Make line thicknesses DPI-safe. * Make lines line up and connect on DPI scalings above 100%. HiDPI icons for the Windows LAF tab controls were previously added in NETBEANS-1238. Improvements to borders on HiDPI screens were done in NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in NETBEANS-3592. > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: Planned Windows LAF improvements.png > > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and need improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses HiDPI-safe. > * Make lines line up and connect on HiDPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Assigned] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke reassigned NETBEANS-5673: - Assignee: Eirik Bakke > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Assignee: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: Planned Windows LAF improvements.png > > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and need improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses HiDPI-safe. > * Make lines line up and connect on HiDPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5673: -- Description: The tab components used for TopComponents and the Project/Navigator sidebar look somewhat dated on the Windows LAF, and need improvements for HiDPI screens. I'll be making improvements on this for my NetBeans Platform-based application, and will likely be making an upstream PR for this in the future (which will benefit the IDE and other NetBeans Platform apps). Specific improvements planned: * Make the sidebar and TopComponent tabs consistent, and modernize the look of the tabs a bit. * Remove out-of-fashion gradients. * Remove out-of-fashion bevels. * Get rid of the extra borders in the sidebar (Projects/Files/Services in the IDE). * Make line thicknesses DPI-safe. * Make lines line up and connect on DPI scalings above 100%. HiDPI icons for the Windows LAF tab controls were previously added in NETBEANS-1238. Improvements to borders on HiDPI screens were done in NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in NETBEANS-3592. was: The tab components used for TopComponents and the Project/Navigator sidebar look somewhat dated on the Windows LAF, and needs improvements for HiDPI screens. I'll be making improvements on this for my NetBeans Platform-based application, and will likely be making an upstream PR for this in the future (which will benefit the IDE and other NetBeans Platform apps). Specific improvements planned: * Make the sidebar and TopComponent tabs consistent, and modernize the look of the tabs a bit. * Remove out-of-fashion gradients. * Remove out-of-fashion bevels. * Get rid of the extra borders in the sidebar (Projects/Files/Services in the IDE). * Make line thicknesses DPI-safe. * Make lines line up and connect on DPI scalings above 100%. HiDPI icons for the Windows LAF tab controls were previously added in NETBEANS-1238. Improvements to borders on HiDPI screens were done in NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in NETBEANS-3592. > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: Planned Windows LAF improvements.png > > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and need improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses DPI-safe. > * Make lines line up and connect on DPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5673: -- Attachment: Planned Windows LAF improvements.png > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Attachments: Planned Windows LAF improvements.png > > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and needs improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses DPI-safe. > * Make lines line up and connect on DPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5673: -- Labels: HiDPI (was: ) > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI > Attachments: Planned Windows LAF improvements.png > > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and needs improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses DPI-safe. > * Make lines line up and connect on DPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5673: -- Attachment: Planned Windows LAF improvements.png > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and needs improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses DPI-safe. > * Make lines line up and connect on DPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5673: -- Attachment: (was: Planned Windows LAF improvements.png) > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and needs improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses DPI-safe. > * Make lines line up and connect on DPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
[ https://issues.apache.org/jira/browse/NETBEANS-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5673: -- Attachment: (was: Windows LAF improvements.png) > Modernize borders and tab controls in the Windows LAF > - > > Key: NETBEANS-5673 > URL: https://issues.apache.org/jira/browse/NETBEANS-5673 > Project: NetBeans > Issue Type: Improvement > Components: platform - Window System >Affects Versions: 12.4 > Environment: NetBeans IDE and NetBeans Platform applications on > Windows LAF on Windows 10. >Reporter: Eirik Bakke >Priority: Major > > The tab components used for TopComponents and the Project/Navigator sidebar > look somewhat dated on the Windows LAF, and needs improvements for HiDPI > screens. I'll be making improvements on this for my NetBeans Platform-based > application, and will likely be making an upstream PR for this in the future > (which will benefit the IDE and other NetBeans Platform apps). > Specific improvements planned: > * Make the sidebar and TopComponent tabs consistent, and modernize the look > of the tabs a bit. > * Remove out-of-fashion gradients. > * Remove out-of-fashion bevels. > * Get rid of the extra borders in the sidebar (Projects/Files/Services in > the IDE). > * Make line thicknesses DPI-safe. > * Make lines line up and connect on DPI scalings above 100%. > HiDPI icons for the Windows LAF tab controls were previously added in > NETBEANS-1238. Improvements to borders on HiDPI screens were done in > NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in > NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5673) Modernize borders and tab controls in the Windows LAF
Eirik Bakke created NETBEANS-5673: - Summary: Modernize borders and tab controls in the Windows LAF Key: NETBEANS-5673 URL: https://issues.apache.org/jira/browse/NETBEANS-5673 Project: NetBeans Issue Type: Improvement Components: platform - Window System Affects Versions: 12.4 Environment: NetBeans IDE and NetBeans Platform applications on Windows LAF on Windows 10. Reporter: Eirik Bakke The tab components used for TopComponents and the Project/Navigator sidebar look somewhat dated on the Windows LAF, and needs improvements for HiDPI screens. I'll be making improvements on this for my NetBeans Platform-based application, and will likely be making an upstream PR for this in the future (which will benefit the IDE and other NetBeans Platform apps). Specific improvements planned: * Make the sidebar and TopComponent tabs consistent, and modernize the look of the tabs a bit. * Remove out-of-fashion gradients. * Remove out-of-fashion bevels. * Get rid of the extra borders in the sidebar (Projects/Files/Services in the IDE). * Make line thicknesses DPI-safe. * Make lines line up and connect on DPI scalings above 100%. HiDPI icons for the Windows LAF tab controls were previously added in NETBEANS-1238. Improvements to borders on HiDPI screens were done in NETBEANS-2646. Various other HiDPI fixes in the Windows LAF were done in NETBEANS-3592. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5658) Add remaining SVG icons in editor toolbar
[ https://issues.apache.org/jira/browse/NETBEANS-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5658: -- Labels: HiDPI pull-request-available (was: pull-request-available) > Add remaining SVG icons in editor toolbar > - > > Key: NETBEANS-5658 > URL: https://issues.apache.org/jira/browse/NETBEANS-5658 > Project: NetBeans > Issue Type: Improvement > Components: editor - Other >Affects Versions: 12.2 >Reporter: Eirik Bakke >Priority: Major > Labels: HiDPI, pull-request-available > Attachments: MoreEditorToolbarIconsEirik.ai > > Time Spent: 10m > Remaining Estimate: 0h > > See the associated Pull Request, which adds 14 more SVG icons, adjusts two > existing ones, and reuses some existing ones for newly identified duplicates. > See NETBEANS-2617 for a more detailed description of this effort. > The Adobe Illustrator file that was used to produce the latest icons is > attached here. I haven't cleaned up the Illustrator file, so it may contain > some duplicates from previous Illustrator file in NETBEANS-2617. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5658) Add remaining SVG icons in editor toolbar
[ https://issues.apache.org/jira/browse/NETBEANS-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5658: -- Description: See the associated Pull Request, which adds 14 more SVG icons, adjusts two existing ones, and reuses some existing ones for newly identified duplicates. See NETBEANS-2617 for a more detailed description of this effort. The Adobe Illustrator file that was used to produce the latest icons is attached here. I haven't cleaned up the Illustrator file, so it may contain some duplicates from previous Illustrator file in NETBEANS-2617. was: See the associated Pull Request, which adds 14 more SVG icons, adjusts two existing ones, and reuses some existing ones for newly identified duplicates. The Adobe Illustrator file that was used to produce the latest icons is attached here. > Add remaining SVG icons in editor toolbar > - > > Key: NETBEANS-5658 > URL: https://issues.apache.org/jira/browse/NETBEANS-5658 > Project: NetBeans > Issue Type: Improvement > Components: editor - Other >Affects Versions: 12.2 >Reporter: Eirik Bakke >Priority: Major > Labels: pull-request-available > Attachments: MoreEditorToolbarIconsEirik.ai > > Time Spent: 10m > Remaining Estimate: 0h > > See the associated Pull Request, which adds 14 more SVG icons, adjusts two > existing ones, and reuses some existing ones for newly identified duplicates. > See NETBEANS-2617 for a more detailed description of this effort. > The Adobe Illustrator file that was used to produce the latest icons is > attached here. I haven't cleaned up the Illustrator file, so it may contain > some duplicates from previous Illustrator file in NETBEANS-2617. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5658) Add remaining SVG icons in editor toolbar
[ https://issues.apache.org/jira/browse/NETBEANS-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5658: -- Description: See the associated Pull Request, which adds 14 more SVG icons, adjusts two existing ones, and reuses some existing ones for newly identified duplicates. The Adobe Illustrator file that was used to produce the latest icons is attached here. was:Creating this issue for an upcoming Pull Request which will convert the rest of the icons in the editor toolbar to SVG. > Add remaining SVG icons in editor toolbar > - > > Key: NETBEANS-5658 > URL: https://issues.apache.org/jira/browse/NETBEANS-5658 > Project: NetBeans > Issue Type: Improvement > Components: editor - Other >Affects Versions: 12.2 >Reporter: Eirik Bakke >Priority: Major > Labels: pull-request-available > Attachments: MoreEditorToolbarIconsEirik.ai > > Time Spent: 10m > Remaining Estimate: 0h > > See the associated Pull Request, which adds 14 more SVG icons, adjusts two > existing ones, and reuses some existing ones for newly identified duplicates. > The Adobe Illustrator file that was used to produce the latest icons is > attached here. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5658) Add remaining SVG icons in editor toolbar
[ https://issues.apache.org/jira/browse/NETBEANS-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eirik Bakke updated NETBEANS-5658: -- Attachment: MoreEditorToolbarIconsEirik.ai > Add remaining SVG icons in editor toolbar > - > > Key: NETBEANS-5658 > URL: https://issues.apache.org/jira/browse/NETBEANS-5658 > Project: NetBeans > Issue Type: Improvement > Components: editor - Other >Affects Versions: 12.2 >Reporter: Eirik Bakke >Priority: Major > Labels: pull-request-available > Attachments: MoreEditorToolbarIconsEirik.ai > > Time Spent: 10m > Remaining Estimate: 0h > > Creating this issue for an upcoming Pull Request which will convert the rest > of the icons in the editor toolbar to SVG. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2617) Redraw common icons in SVG
[
https://issues.apache.org/jira/browse/NETBEANS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339167#comment-17339167
]
Eirik Bakke commented on NETBEANS-2617:
---
I've drawn the icons in the previous list above and will be incorporating them
shortly (NETBEANS-5658).
> Redraw common icons in SVG
> --
>
> Key: NETBEANS-2617
> URL: https://issues.apache.org/jira/browse/NETBEANS-2617
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Other
>Affects Versions: 11.0
> Environment: Windows, Linux, and MacOS
>Reporter: Eirik Bakke
>Priority: Major
> Labels: HiDPI
> Attachments: ScreenshotExample.png, ide.editor.bookmarks.ai,
> ide.editor.macros.ai, ide.seperator.breadcrumbs.ai,
> netbeans_icons_illustrator_template.ai, style example (dark filter).png,
> style example.png
>
>
> Once NETBEANS-2604 is done, we should start replacing commonly seen NetBeans
> icons with SVG versions, for improved appearance on Retina/HiDPI displays.
> h2. UPDATE:
> [Here|https://docs.google.com/spreadsheets/d/1U_pj-I3hk9Wj_7lvHcUDsZfFfBSyCkSGqBuv0qt_qXw/edit?usp=sharing]
> is a Google Sheet where we can track progress of contributions and
> prioritization of icons.
> With some practice, it takes on average 30 minutes to create an SVG version
> of a typical icon in Adobe Illustrator. See the attached illustration and
> Illustrator template. The Illustrator template includes a few icons which
> have already been converted.
> In NETBEANS-2605, a prioritized list of icons to convert was produced (now
> migrated to the Google Sheet above). By redrawing the most commonly seen
> icons first, we can get the greatest "bang for the buck" in terms of
> improving NetBeans' appearance on HiDPI displays. Note that in cases where an
> icon file has been copied around to various places in the NetBeans codebase,
> the spreadsheet includes only one location, picked arbitrarily. Once we have
> a batch of icons ready to integrate into the NetBeans repository, Eirik will
> redo the duplicate detection and ensure the SVGs end up in all relevant
> locations, and start creating pull requests.
> See also the overview page for HiDPI improvements on
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> .
> If you wish to contribute to this effort, comment here; Eirik will coordinate
> to make sure multiple people are not working on the same icons.
> h2. Proposed Style Guide for Vectorized Icons
> * Vector icons should be drawn in Adobe Illustrator, or alternatively
> Inkscape or another free tool. In Illustrator, each icon should be one named
> artboard, sized to the correct size in pixels. See the attached Illustrator
> template. (Adobe Illustrator comes with a free 7-day trial, after which it's
> $35/month. If cost is a problem but you want to contribute your time to draw
> icons, ask Eirik...)
> * If you prefer to use Inkscape instead, and want to contribute icons, that's
> fine; just make sure to follow the same consistent style as the other icons.
> If using Inkscape, perhaps pick another group of icons than the ones that are
> currently being drawn in Illustrator. It's best to draw all similar-looking
> icons in the same tool.
> * For each icon to be vectorized, place the old bitmap version of the icon in
> a separate layer ("Old Bitmap Icons" in the Illustrator template). You can
> then draw the vectorized version on top.
> * Since most of the existing NetBeans icons follow a quite consistent visual
> style, and to simplify the job of creating new icons, it is best to keep the
> shape of the new vectorized icons the same as in the old bitmap icons. For
> instance, a rectangle of size 5x4px in the bitmap icon should probably become
> a rectangle of 5x4px in the vector version.
> * Keep the same general colors in vectorized icons as in the corresponding
> old bitmap icons.
> * Some of the old bitmap icons use grays with a slightly blue tint (e.g. the
> [file
> icons|https://raw.githubusercontent.com/apache/netbeans/master/java/refactoring.java/src/org/netbeans/modules/refactoring/java/resources/newFile.png]).
> This style is out of fashion (resembling 1990s Solaris GUIs etc.); use
> neutral greys instead.
> * If the old bitmap icon is complex, it is fine to simplify it a bit when
> drawing vectorized versions.
> * Omit gradients, bevels, and unnecessary drop shadows. They take more time
> to draw, and with "flat design", they are now out of fashion in any case.
> * Use a stroke width of 1px around the main shapes in the icon, like in the
> existing bitmap icons. The new icons should look consistent with the existing
> bitmap icons, especially since we may see bitmap icons and vector icons
> side-by-side for a long time. W
[jira] [Created] (NETBEANS-5658) Add remaining SVG icons in editor toolbar
Eirik Bakke created NETBEANS-5658: - Summary: Add remaining SVG icons in editor toolbar Key: NETBEANS-5658 URL: https://issues.apache.org/jira/browse/NETBEANS-5658 Project: NetBeans Issue Type: Improvement Components: editor - Other Affects Versions: 12.2 Reporter: Eirik Bakke Creating this issue for an upcoming Pull Request which will convert the rest of the icons in the editor toolbar to SVG. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5656) Various smaller fixes in the database New Connection wizard
Eirik Bakke created NETBEANS-5656: - Summary: Various smaller fixes in the database New Connection wizard Key: NETBEANS-5656 URL: https://issues.apache.org/jira/browse/NETBEANS-5656 Project: NetBeans Issue Type: Improvement Components: db - DB schema Affects Versions: 12.2 Reporter: Eirik Bakke Issue for a PR with various small UI improvements to the database module's "New Connection" wizard. Details: * Refactor the 'Add Connection' wizard to avoid depending on hardcoded wizard panel indexes. * Improve two error messages in "New Connection" wizard. * Avoid a spurious 'Specified class is not a driver' warning in certain situations. * When detecting the Microsoft SQL Server JDBC driver, avoid showing an ancient version number. * Add a default port number for Microsoft SQL Server. * Tidy up presentation names in the JDBC URL format dropdown. * Decrease the timeout of the connection validation step. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5655) Invalid UTF-8 character when building on Windows
[
https://issues.apache.org/jira/browse/NETBEANS-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5655:
--
Affects Version/s: 12.4
> Invalid UTF-8 character when building on Windows
>
>
> Key: NETBEANS-5655
> URL: https://issues.apache.org/jira/browse/NETBEANS-5655
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.4
> Environment: Building NetBeans on Windows 10 from the Windows command
> line (not WSL).
>Reporter: Eirik Bakke
>Priority: Major
>
> Doing a build on Windows, the following error occurs:
> {{BUILD FAILED}}
> {{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
> following error occurred while executing this line:}}
> {{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
> The following error occurred while executing this line:}}
> {{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
> javax.xml.transform.TransformerException:
> javax.xml.transform.TransformerException:
> com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
> of 3-byte UTF-8 sequence.}}
> Examining build.xml:149, it points to the file
> nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
> UTF-8 character somewhere.
> Doing some further investigation...
> {{ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
> alldatas1.xml alldatas2.xml}}
> {{5139c5139}}
> {{< when running in “compile-on-save? mode}}
> {{---}}
> {{> when running in “compile-on-save�? mode}}
> Will submit a PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5655) Invalid UTF-8 character when building on Windows
[
https://issues.apache.org/jira/browse/NETBEANS-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5655:
--
Description:
Doing a build on Windows, the following error occurs:
{{BUILD FAILED}}
{{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
following error occurred while executing this line:}}
{{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
The following error occurred while executing this line:}}
{{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException:
com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
of 3-byte UTF-8 sequence.}}
Examining build.xml:149, it points to the file
nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
UTF-8 character somewhere.
Doing some further investigation...
{{ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
alldatas1.xml alldatas2.xml}}
{{5139c5139}}
{{< when running in “compile-on-save? mode}}
{{---}}
{{> when running in “compile-on-save�? mode}}
Will submit a PR.
was:
Doing a build on Windows, the following error occurs:
{{BUILD FAILED
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
The following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException:
com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
of 3-byte UTF-8 sequence.}}
Examining build.xml:149, it points to the file
nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
UTF-8 character somewhere.
Doing some further investigation...
{{ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
alldatas1.xml alldatas2.xml
5139c5139
< when running in “compile-on-save? mode
---
> when running in “compile-on-save�? mode}}
Will submit a PR.
> Invalid UTF-8 character when building on Windows
>
>
> Key: NETBEANS-5655
> URL: https://issues.apache.org/jira/browse/NETBEANS-5655
> Project: NetBeans
> Issue Type: Bug
> Environment: Building NetBeans on Windows 10 from the Windows command
> line (not WSL).
>Reporter: Eirik Bakke
>Priority: Major
>
> Doing a build on Windows, the following error occurs:
> {{BUILD FAILED}}
> {{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
> following error occurred while executing this line:}}
> {{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
> The following error occurred while executing this line:}}
> {{C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
> javax.xml.transform.TransformerException:
> javax.xml.transform.TransformerException:
> com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
> of 3-byte UTF-8 sequence.}}
> Examining build.xml:149, it points to the file
> nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
> UTF-8 character somewhere.
> Doing some further investigation...
> {{ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
> alldatas1.xml alldatas2.xml}}
> {{5139c5139}}
> {{< when running in “compile-on-save? mode}}
> {{---}}
> {{> when running in “compile-on-save�? mode}}
> Will submit a PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5655) Invalid UTF-8 character when building on Windows
[
https://issues.apache.org/jira/browse/NETBEANS-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5655:
--
Description:
Doing a build on Windows, the following error occurs:
{{BUILD FAILED
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
The following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException:
com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
of 3-byte UTF-8 sequence.}}
Examining build.xml:149, it points to the file
nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
UTF-8 character somewhere.
Doing some further investigation...
{{ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
alldatas1.xml alldatas2.xml
5139c5139
< when running in “compile-on-save? mode
---
> when running in “compile-on-save�? mode}}
Will submit a PR.
was:
Doing a build on Windows, the following error occurs:
{{BUILD FAILED
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
The following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException:
com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
of 3-byte UTF-8 sequence.
}}
Examining build.xml:149, it points to the file
nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
UTF-8 character somewhere.
Doing some further investigation...
{{
ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
alldatas1.xml alldatas2.xml
5139c5139
< when running in “compile-on-save? mode
---
> when running in “compile-on-save�? mode
}}
Will submit a PR.
> Invalid UTF-8 character when building on Windows
>
>
> Key: NETBEANS-5655
> URL: https://issues.apache.org/jira/browse/NETBEANS-5655
> Project: NetBeans
> Issue Type: Bug
> Environment: Building NetBeans on Windows 10 from the Windows command
> line (not WSL).
>Reporter: Eirik Bakke
>Priority: Major
>
> Doing a build on Windows, the following error occurs:
> {{BUILD FAILED
> C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
> following error occurred while executing this line:
> C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
> The following error occurred while executing this line:
> C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
> javax.xml.transform.TransformerException:
> javax.xml.transform.TransformerException:
> com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
> of 3-byte UTF-8 sequence.}}
> Examining build.xml:149, it points to the file
> nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
> UTF-8 character somewhere.
> Doing some further investigation...
> {{ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
> alldatas1.xml alldatas2.xml
> 5139c5139
> < when running in “compile-on-save? mode
> ---
> > when running in “compile-on-save�? mode}}
> Will submit a PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5655) Invalid UTF-8 character when building on Windows
[
https://issues.apache.org/jira/browse/NETBEANS-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eirik Bakke updated NETBEANS-5655:
--
Description:
Doing a build on Windows, the following error occurs:
{{BUILD FAILED
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
The following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException:
com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
of 3-byte UTF-8 sequence.
}}
Examining build.xml:149, it points to the file
nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
UTF-8 character somewhere.
Doing some further investigation...
{{
ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
alldatas1.xml alldatas2.xml
5139c5139
< when running in “compile-on-save? mode
---
> when running in “compile-on-save�? mode
}}
Will submit a PR.
was:
Doing a build on Windows, the following error occurs:
```
BUILD FAILED
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
The following error occurred while executing this line:
C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException:
com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
of 3-byte UTF-8 sequence.
```
Examining build.xml:149, it points to the file
nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
UTF-8 character somewhere.
Doing some further investigation...
```
ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
alldatas1.xml alldatas2.xml
5139c5139
< when running in “compile-on-save? mode
---
> when running in “compile-on-save�? mode
```
Will submit a PR.
> Invalid UTF-8 character when building on Windows
>
>
> Key: NETBEANS-5655
> URL: https://issues.apache.org/jira/browse/NETBEANS-5655
> Project: NetBeans
> Issue Type: Bug
> Environment: Building NetBeans on Windows 10 from the Windows command
> line (not WSL).
>Reporter: Eirik Bakke
>Priority: Major
>
> Doing a build on Windows, the following error occurs:
> {{BUILD FAILED
> C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The
> following error occurred while executing this line:
> C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48:
> The following error occurred while executing this line:
> C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149:
> javax.xml.transform.TransformerException:
> javax.xml.transform.TransformerException:
> com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3
> of 3-byte UTF-8 sequence.
> }}
> Examining build.xml:149, it points to the file
> nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed
> UTF-8 character somewhere.
> Doing some further investigation...
> {{
> ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff
> alldatas1.xml alldatas2.xml
> 5139c5139
> < when running in “compile-on-save? mode
> ---
> > when running in “compile-on-save�? mode
> }}
> Will submit a PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5655) Invalid UTF-8 character when building on Windows
Eirik Bakke created NETBEANS-5655: - Summary: Invalid UTF-8 character when building on Windows Key: NETBEANS-5655 URL: https://issues.apache.org/jira/browse/NETBEANS-5655 Project: NetBeans Issue Type: Bug Environment: Building NetBeans on Windows 10 from the Windows command line (not WSL). Reporter: Eirik Bakke Doing a build on Windows, the following error occurs: ``` BUILD FAILED C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\build.xml:395: The following error occurred while executing this line: C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:48: The following error occurred while executing this line: C:\Users\ebakke\ZRoot\nbsrc\incubator-netbeans\nbbuild\javadoctools\build.xml:149: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 3 of 3-byte UTF-8 sequence. ``` Examining build.xml:149, it points to the file nbbuild/build/javadoc/alldatas.xml, which indeed appears to have a malformed UTF-8 character somewhere. Doing some further investigation... ``` ebakke@EBLEN:/z/nbsrc/incubator-netbeans/nbbuild/build/javadoc$ diff alldatas1.xml alldatas2.xml 5139c5139 < when running in “compile-on-save? mode --- > when running in “compile-on-save�? mode ``` Will submit a PR. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5481) Netbeans 12.3 refuses to start on macOS 10.13.6
[
https://issues.apache.org/jira/browse/NETBEANS-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311864#comment-17311864
]
Eirik Bakke commented on NETBEANS-5481:
---
Given the description in https://support.apple.com/kb/dl1998, we might consider
adding
{noformat}
LSMinimumSystemVersion
10.14.4
{noformat}
to Info.plist in the MacOS application bundle, to ensure that users get a
user-friendly error message here. Though I wonder if the new Swift launcher
bundle could just be compiled with an older version of XCode that is capable of
linking in the libraries in question via "swift build
-c--static-swift-stdlib"...
Though after https://github.com/apache/netbeans/pull/2717, the launcher binary
becomes quite minimal. Perhaps it could just be rewritten in Objective C to
avoid this problem...
> Netbeans 12.3 refuses to start on macOS 10.13.6
> ---
>
> Key: NETBEANS-5481
> URL: https://issues.apache.org/jira/browse/NETBEANS-5481
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.3
>Reporter: Malte Müller
>Assignee: Christian Oyarzun
>Priority: Blocker
> Attachments: report-installed.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After successful installation via the macOS installer, Netbeans 12.3 refuses
> to start because of a problem. Nothing has been changed on the system
> recently and Netbeans 12.2 works as always. Here is the report macOS
> generates:
> Process: netbeans [4555]
> Path: /Applications/NetBeans/Apache NetBeans 12.3.app/Contents/MacOS/netbeans
> Identifier: org.netbeans.ide.nbide.12.3
> Version: 12.3 (12.3)
> Code Type: X86-64 (Native)
> Parent Process: ??? [1]
> Responsible: netbeans [4555]
> User ID: 501
> Date/Time: 2021-03-23 13:50:58.466 +0100
> OS Version: Mac OS X 10.13.6 (17G14042)
> Report Version: 12
> Anonymous UUID: FBFCE304-8AE4-5CEB-A2A5-E332E51F58CC
> Sleep/Wake UUID: 5468675E-19DD-4419-B58A-5BD3C96C0D7F
> Time Awake Since Boot: 19000 seconds
> Time Since Wake: 7100 seconds
> System Integrity Protection: enabled
> Crashed Thread: 0
> Exception Type: EXC_CRASH (SIGABRT)
> Exception Codes: 0x, 0x
> Exception Note: EXC_CORPSE_NOTIFY
> Termination Reason: DYLD, [0x1] Library missing
> Application Specific Information:
> dyld: launch, loading dependent libraries
> Dyld Error Message:
> Library not loaded: @rpath/libswiftCore.dylib
> Referenced from: /Applications/NetBeans/Apache NetBeans
> 12.3.app/Contents/MacOS/netbeans
> Reason: image not found
> Binary Images:
> 0x1084eb000 - 0x1084f1ff7 +org.netbeans.ide.nbide.12.3 (12.3 - 12.3)
> <72C28A65-4256-3EB6-B4A3-56D8F679C709> /Applications/NetBeans/Apache NetBeans
> 12.3.app/Contents/MacOS/netbeans
> 0x10edbf000 - 0x10ee09adf dyld (551.5)
> /usr/lib/dyld
> 0x7fff3ec2a000 - 0x7fff3eff1ffb com.apple.Foundation (6.9 - 1455.300)
> <0479E072-1DD0-3881-A9A2-EDAD3EE58C23>
> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
> 0x7fff627be000 - 0x7fff627bfffb libSystem.B.dylib (1252.50.4)
> <5A02016C-8F9D-3F47-8C39-AD2CD4F9F11D> /usr/lib/libSystem.B.dylib
> 0x7fff63ef9000 - 0x7fff642ea3b7 libobjc.A.dylib (723)
> <616AB826-9179-3924-AA61-AF760363A3F5> /usr/lib/libobjc.A.dylib
> Model: iMac12,1, BootROM 87.0.0.0.0, 4 processors, Intel Core i5, 2,5 GHz, 12
> GB, SMC 1.71f22
> Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe
> Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198,
> 0x393930353432382D3035312E4130304C4620
> Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198,
> 0x393930353432382D3035312E4130304C4620
> Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1333 MHz, 0x80CE,
> 0x4D34373142353737334448302D4348392020
> Memory Module: BANK 1/DIMM1, 2 GB, DDR3, 1333 MHz, 0x80CE,
> 0x4D34373142353737334448302D4348392020
> AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros
> 9380: 4.0.74.0-P2P
> Bluetooth: Version 6.0.7f22, 3 services, 27 devices, 1 incoming serial ports
> Network Service: Ethernet, Ethernet, en0
> Serial ATA Device: ST3500418AS, 500,11 GB
> Serial ATA Device: HL-DT-STDVDRW GA32N
> USB Device: USB 2.0 Bus
> USB Device: FaceTime HD Camera (Built-in)
> USB Device: Hub
> USB Device: USB 2.0 Hub
> USB Device: Elements 25A3
> USB Device: Ext HDD 1021
> USB Device: BRCM2046 Hub
> USB Device: Bluetooth USB Host Controller
> USB Device: USB 2.0 Bus
> USB Device: Hub
> USB Device: USB2.0 Hub
> USB Device: Wacom Intuos Pro M
> USB Device: Ext HDD 1021
> USB Device: IR Receiver
> USB Device: Internal Memory Card Reader
> Thunderbolt Bus: iMac, Apple Inc., 22.1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For addit
