[jira] [Created] (NETBEANS-264) Project names are cut off in the Projects tab
Gili created NETBEANS-264: - Summary: Project names are cut off in the Projects tab Key: NETBEANS-264 URL: https://issues.apache.org/jira/browse/NETBEANS-264 Project: NetBeans Issue Type: Bug Components: platform - Window System Environment: Product Version: Apache NetBeans IDE Dev (Build 20180106-unknown-revn) Updates: Updates available Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11 Runtime: Java(TM) SE Runtime Environment 9.0.1+11 System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb) User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev Reporter: Gili Attachments: screenshot.png Sometimes I see project names getting cut off in the Projects tab, even though there is plenty of space left for them to render. For example, see the attached screenshot for project name "mmmMMM". This seems specific to certain letters because other project names render just fine. This issue is specific to JDK9. JDK 1.8.0_141-b15 renders the text just fine. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - 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
[incubator-netbeans] annotated tag 9.0-beta-rc1 created (now 5dafb3f)
This is an automated email from the ASF dual-hosted git repository. jlahoda pushed a change to annotated tag 9.0-beta-rc1 in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git. at 5dafb3f (tag) tagging dd5eb868ec5e8037c77118dbd5e2c53103f1c30e (commit) replaces 9.0-alpha-rc2 by Jan Lahoda on Wed Jan 10 23:52:52 2018 +0100 - Log - RC1 of 9.0-beta. --- No new revisions were added by this update. -- To stop receiving notification emails like this one, please contact ['"commits@netbeans.apache.org"']. - 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
svn commit: r24119 - in /dev/incubator/netbeans: incubating-netbeans-java/ incubating-netbeans-java/incubating-9.0-beta/ incubating-netbeans-platform/ incubating-netbeans-platform/incubating-9.0-beta/
Author: jlahoda Date: Wed Jan 10 22:46:53 2018 New Revision: 24119 Log: Apache NetBeans 9.0-beta RC1. Added: dev/incubator/netbeans/incubating-netbeans-java/ dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/ dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip (with props) dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.asc dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.md5 dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.sha1 dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-source.zip (with props) dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-source.zip.asc dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-source.zip.md5 dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-source.zip.sha1 dev/incubator/netbeans/incubating-netbeans-platform/ dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/ dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-bin.zip (with props) dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-bin.zip.asc dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-bin.zip.md5 dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-bin.zip.sha1 dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-source.zip (with props) dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-source.zip.asc dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-source.zip.md5 dev/incubator/netbeans/incubating-netbeans-platform/incubating-9.0-beta/incubating-netbeans-platform-9.0-beta-source.zip.sha1 Added: dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip == Binary file - no diff available. Propchange: dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip -- svn:mime-type = application/octet-stream Added: dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.asc == --- dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.asc (added) +++ dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.asc Wed Jan 10 22:46:53 2018 @@ -0,0 +1,17 @@ +-BEGIN PGP SIGNATURE- +Version: GnuPG v1 + +iQIcBAABAgAGBQJaVpabAAoJELTBlA/qk2TxWIUP/Rc5HuMP77DaGJq9p+RQXSdo +n98Btv/N1xDMYLUhz9LeEXFj7V6SeGgB/dEG7C+9R1EbktOo3xPTdE9r8YoEUUIv +LiudrW1lHXVEDvhzk3DmXm/cp1ob/QTpjx8p1YfaqnBcKqOhVyX68hGQJGytwool +oENcGUdYidMAEdJU5aj+Yjy9WWALnsejVtLgc5lu0CUQ4CInZpemPxFnYOyDoKjT +DPtJhPUxZ1jcFV0LObLux++nlc0Rhp7m0LQarrxKdlcb5/gtTvXjXAAlkAGGDayZ +ZDD9MdkvtKBRGf6oq3uEy3HY7AAgPsjilKzl4AAFWmwPgKqaLX8vDLqUbVdxLoER +IdGJKBhPfF5Zh+wDNh/ALDH8LN/TTpEM1ZrRxUEWzmQmzaekQRPTGllo8+HFPTZY +4vx7RIT77r9L00eACpdPjQ5sRinih8IgXUVh79Ty/1LMTgLWTt7Pq1S0nu9sv3Ua +uogCfA3bTeRlPBP3uG9yAZbsy7ag9UAHox0RMaRdrS6Y7kol8r0Uj83+TwcR2KPg +jkDrzZTqUi1apvwtnD5ns2g0PWFfjMTEGV4YH0xW+ZHDNkFIgKzaNd0qIAAt7Xc+ +hDa96KmeEYicmmzYJiBBWCFuzKCTeOLsA52jL32SxBvG8tgOMeVoEoRrEbbPY+Xk +gncCluxPS9HTo3cvZOFr +=7WbO +-END PGP SIGNATURE- Added: dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.md5 == --- dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.md5 (added) +++ dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.md5 Wed Jan 10 22:46:53 2018 @@ -0,0 +1 @@ +8e450ab47bc204fdf17463621f3448bc incubating-netbeans-java-9.0-beta-bin.zip Added: dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/incubating-netbeans-java-9.0-beta-bin.zip.sha1 == ---
[incubator-netbeans] branch master updated: [NetBeans-259] Consolidate README in Apache NetBeans src distros (#359)
This is an automated email from the ASF dual-hosted git repository. geertjan pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git The following commit(s) were added to refs/heads/master by this push: new f0e591d [NetBeans-259] Consolidate README in Apache NetBeans src distros (#359) f0e591d is described below commit f0e591d135d304d47ccdb7a41e46aba16e4fc21d Author: Geertjan WielengaAuthorDate: Wed Jan 10 16:29:36 2018 +0100 [NetBeans-259] Consolidate README in Apache NetBeans src distros (#359) * Updating shortcuts document to 9.0. * Revert "Updating shortcuts document to 9.0." This reverts commit adc15f559952f1a5259d6f27a628b964eb0fed2b. * Removing this file, which is now generated automatically as DEPENDENCIES file. * [NETBEANS-259] Consolidate README in Apache NetBeans src distros --- ide.branding/README-src.txt | 3 --- nbbuild/build.xml | 7 +++ o.n.bootstrap/readme/README-src.txt | 3 --- 3 files changed, 3 insertions(+), 10 deletions(-) diff --git a/ide.branding/README-src.txt b/ide.branding/README-src.txt deleted file mode 100644 index 1f7a9b0..000 --- a/ide.branding/README-src.txt +++ /dev/null @@ -1,3 +0,0 @@ -This is a NetBeans IDE source zip. - -To build the NetBeans IDE, run "ant". The IDE will be into nbbuild/netbeans. diff --git a/nbbuild/build.xml b/nbbuild/build.xml index 722be15..e77a266 100644 --- a/nbbuild/build.xml +++ b/nbbuild/build.xml @@ -1605,8 +1605,8 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y to start the system in d - + @@ -1623,7 +1623,7 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y to start the system in d - + @@ -2138,7 +2138,6 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y to start the system in d - diff --git a/o.n.bootstrap/readme/README-src.txt b/o.n.bootstrap/readme/README-src.txt deleted file mode 100644 index 96573da..000 --- a/o.n.bootstrap/readme/README-src.txt +++ /dev/null @@ -1,3 +0,0 @@ -This is a NetBeans Platform source zip. - -To build the NetBeans Platform, run "ant". The built platform will be in nbbuild/netbeans. -- To stop receiving notification emails like this one, please contact ['"commits@netbeans.apache.org" ']. - 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-261) Better code completion for JS with typescript type definition files
[ https://issues.apache.org/jira/browse/NETBEANS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-261: Description: I read an article about the new Salsa feature in Visual Studio 2016: https://github.com/Microsoft/TypeScript/wiki/Salsa MS tried to implement a better intellisense support for javascript again. Same procedure as every year. But it's not that easy because of the dynamically type system of js as we know. The new idea is to use typescript type definitions files ALSO you don't want to write in TypeScript. The definitions are only helper during the development time in Visual Studio to support the code completion/intellisense. It's based on a new language service called "salsa". Maybe this could be a good enhancement too for supporting a better code completion and go to whatever if netbeans could use TS typedefinition files too? I think VS Code and WebStorm did the same thing and it will make the whole code completion of JS much much better. Cheers Chris P.S. the other thing to resolve better and maybe have type checking while writing plain js code is to use JsDoc as I wrote it here: https://issues.apache.org/jira/browse/NETBEANS-184 was: I read an article about the new Salsa feature in Visual Studio 2016: https://github.com/Microsoft/TypeScript/wiki/Salsa MS tried to implement a better intellisense support for javascript again. Same procedure as every year. But it's not that easy because of the dynamically type system of js as we know. The new idea is to use typescript type definitions files ALSO you don't want to write in TypeScript. The definitions are only helper during the development time in Visual Studio to support the code completion/intellisense. It's based on a new language service called "salsa". Maybe this could be a good enhancement too for supporting a better code completion and go to whatever if netbeans could use TS typedefinition files too? I think VS Code and WebStorm did the same thing and it will make the whole code completion of JS much much better. Cheers Chris P.S. the other thing to resolve better and maybe have type checking while writing plain js code is to use JsDoc as I wrote it here: https://netbeans.org/bugzilla/show_bug.cgi?id=249892 > Better code completion for JS with typescript type definition files > --- > > Key: NETBEANS-261 > URL: https://issues.apache.org/jira/browse/NETBEANS-261 > Project: NetBeans > Issue Type: Improvement > Components: javascript - Documentation, javascript - Editor >Affects Versions: Next >Reporter: Christian Lenz > > I read an article about the new Salsa feature in Visual Studio 2016: > https://github.com/Microsoft/TypeScript/wiki/Salsa > MS tried to implement a better intellisense support for javascript again. > Same procedure as every year. But it's not that easy because of the > dynamically type system of js as we know. The new idea is to use typescript > type definitions files ALSO you don't want to write in TypeScript. The > definitions are only helper during the development time in Visual Studio to > support the code completion/intellisense. It's based on a new language > service called "salsa". > Maybe this could be a good enhancement too for supporting a better code > completion and go to whatever if netbeans could use TS typedefinition files > too? > I think VS Code and WebStorm did the same thing and it will make the whole > code completion of JS much much better. > Cheers > Chris > P.S. the other thing to resolve better and maybe have type checking while > writing plain js code is to use JsDoc as I wrote it here: > https://issues.apache.org/jira/browse/NETBEANS-184 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - 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-261) Better code completion for JS with typescript type definition files
Christian Lenz created NETBEANS-261: --- Summary: Better code completion for JS with typescript type definition files Key: NETBEANS-261 URL: https://issues.apache.org/jira/browse/NETBEANS-261 Project: NetBeans Issue Type: Improvement Components: javascript - Documentation, javascript - Editor Affects Versions: Next Reporter: Christian Lenz I read an article about the new Salsa feature in Visual Studio 2016: https://github.com/Microsoft/TypeScript/wiki/Salsa MS tried to implement a better intellisense support for javascript again. Same procedure as every year. But it's not that easy because of the dynamically type system of js as we know. The new idea is to use typescript type definitions files ALSO you don't want to write in TypeScript. The definitions are only helper during the development time in Visual Studio to support the code completion/intellisense. It's based on a new language service called "salsa". Maybe this could be a good enhancement too for supporting a better code completion and go to whatever if netbeans could use TS typedefinition files too? I think VS Code and WebStorm did the same thing and it will make the whole code completion of JS much much better. Cheers Chris P.S. the other thing to resolve better and maybe have type checking while writing plain js code is to use JsDoc as I wrote it here: https://netbeans.org/bugzilla/show_bug.cgi?id=249892 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - 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-260) Don't make the code coverage so prominent
[ https://issues.apache.org/jira/browse/NETBEANS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-260: Issue Type: Improvement (was: Bug) > Don't make the code coverage so prominent > - > > Key: NETBEANS-260 > URL: https://issues.apache.org/jira/browse/NETBEANS-260 > Project: NetBeans > Issue Type: Improvement > Components: java - TestNG, javascript - Testing, utilities - Test > Runner >Affects Versions: Next >Reporter: Christian Lenz > Labels: CodeCoverage, UnitTest > Attachments: code-coverage-nb.png > > > I think I will create sub tasks for this, because it affects all supported > languages, but I figured it out on JS. > Atm if you use code coverage like with karma and the coverage plugin or > istanbul or whatever, the whole line, which will turn green or red. That > makes the code unreadable, if you use an other theme than light. I use > darcula laf and the darcula theme and of course, the plugin should fix this, > but to avoid such things, it would be better to have a not that big prominent > indicator in e.g. only the line number should be colored. Thats enough and > this is what other IDEs and editors do. > So it will not be in conflict, with the git coloring inside the editor, > because it is behind the line numbers. > See my attachment for what I mean. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - 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-260) Don't make the code coverage so prominent
[ https://issues.apache.org/jira/browse/NETBEANS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320002#comment-16320002 ] Christian Lenz commented on NETBEANS-260: - Such icons would be cool/enough and if you hover on it, you can see a bit more info, > Don't make the code coverage so prominent > - > > Key: NETBEANS-260 > URL: https://issues.apache.org/jira/browse/NETBEANS-260 > Project: NetBeans > Issue Type: Bug > Components: java - TestNG, javascript - Testing, utilities - Test > Runner >Affects Versions: Next >Reporter: Christian Lenz > Labels: CodeCoverage, UnitTest > Attachments: code-coverage-nb.png > > > I think I will create sub tasks for this, because it affects all supported > languages, but I figured it out on JS. > Atm if you use code coverage like with karma and the coverage plugin or > istanbul or whatever, the whole line, which will turn green or red. That > makes the code unreadable, if you use an other theme than light. I use > darcula laf and the darcula theme and of course, the plugin should fix this, > but to avoid such things, it would be better to have a not that big prominent > indicator in e.g. only the line number should be colored. Thats enough and > this is what other IDEs and editors do. > So it will not be in conflict, with the git coloring inside the editor, > because it is behind the line numbers. > See my attachment for what I mean. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - 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-260) Don't make the code coverage so prominent
[ https://issues.apache.org/jira/browse/NETBEANS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320001#comment-16320001 ] Christian Lenz commented on NETBEANS-260: - Here are some links of alternative IDEs and editors: VS (Wallaby.js plugin): https://wallabyjs.com/assets/img/main.png VS Code: https://wallabyjs.com/assets/img/vscode_inline.gif WebStorm: https://blog.jetbrains.com/webide/files/2012/04/editor-covered-lines-2.png This is much better than that what we have. It is prominent enough to see/know what happens there, but it is not disturbing. Maybe a circle or the whole line for the line numbers would be great and maybe with a (/) or (x). Cheers Chris > Don't make the code coverage so prominent > - > > Key: NETBEANS-260 > URL: https://issues.apache.org/jira/browse/NETBEANS-260 > Project: NetBeans > Issue Type: Bug > Components: java - TestNG, javascript - Testing, utilities - Test > Runner >Affects Versions: Next >Reporter: Christian Lenz > Labels: CodeCoverage, UnitTest > Attachments: code-coverage-nb.png > > > I think I will create sub tasks for this, because it affects all supported > languages, but I figured it out on JS. > Atm if you use code coverage like with karma and the coverage plugin or > istanbul or whatever, the whole line, which will turn green or red. That > makes the code unreadable, if you use an other theme than light. I use > darcula laf and the darcula theme and of course, the plugin should fix this, > but to avoid such things, it would be better to have a not that big prominent > indicator in e.g. only the line number should be colored. Thats enough and > this is what other IDEs and editors do. > So it will not be in conflict, with the git coloring inside the editor, > because it is behind the line numbers. > See my attachment for what I mean. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - 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