Re: Calling all Gradle users!

[Peter Steele]

I am a big gradle user, I currently use the gradle plugin setup with a root
project and many sub projects. I am interested in helping. I'm currently on
netbeans 10 with jdk 11 (there is a minimum version of gradle required for
Jdk 11)

On Sat, 26 Jan 2019, 13:07 Geertjan Wielenga
 Hi all,
>
> If you're using Gradle in any way at all -- and especially if you have
> some Gradle projects of whatever kind lying around -- we need you!
>
> Thanks to Laszlo, we have integration with Gradle for the first time in
> the upcoming release scheduled to be released in March. We need as many as
> possible to try out the Gradle features, i.e., simply open your existing
> projects into the latest NetBeans builds and see if there are any problems
> so they can be fixed in time.
>
> Interested? Please respond to this e-mail indicating your intention to try
> out your existing Gradle projects in the upcoming release of Apache
> NetBeans and we'll work on this together from there initially via this mail
> thread.
>
> For example, without any problems at all, I was able to open and work with
> this random project I found on GitHub:
>
>

Re: java-agent to inject system properties on NetBeans startup

[Peter Steele]

+1

On Fri, 28 Sep 2018 01:37 Laszlo Kishalmi, 
wrote:

> Hi all,
>
> What do you think on the idea to create a simple Java agent which can
> insert system properties into the JVM before NetBeans starts?
>
> My motivation are the following:
>
>  1. Sometimes you need to change some properties to debug NetBeans
> behaviour. Copy and change netbeans.conf can be clumsy. (Ok, I know
> what I'm doing and it is fine for me, but we have other users.)
>  2. There can be a situation when some values needs to be computed, like
> Java 11 were messing up with font rendering on Linux and there is no
> proper default value for the antialiasing property which works on
> all platform. Also dpi awareness for HiDPI would requires some logic
> as well.
>
> Unfortunately this won't solve the currently quiet bloated command line
> in netbeans.conf (just probably reduce it a bit.)
> It would be good to be able to set the Memory and GC flags for the IDE
> as well (though memory would be sufficient)
>
> What do you think?
>
>
>

Re: SECURITY: plugins.netbeans.org domain not secure

[Peter Steele]

Kenneth

apache.netbeans.org supports https, so once everything redirects here we
should be good by default. There is a Jira to find a solution to the plugin
hosting question once we go fully move over but I think that's the still
TBD. Maybe find that Jira and add some comments to mention the new home for
plugins should be https compatible and people will take that in to
consideration

On Tue, 25 Sep 2018 18:47 Antonio,  wrote:

> Hi Kenneth,
>
> I fully agree with you. I'd add a JIRA so we can remember it, but I
> won't classify this as a security problem. For me security issues have
> special priority, I don't see that priority here.
>
> Kind regards,
> Antonio
>
> On 25/09/18 19:16, Kenneth Jaeger wrote:
> > I understand since there is no login information being sent to
> > plugins.netbeans.org, that security is less of a concern, but this is a
> > front facing website.  It is not just used by the IDE.  Browsers are
> going
> > to start yelling at us when we go to any http site (as I personally think
> > they should be).  Call me paranoid, but I think the trend toward 100% of
> > web traffic being TLS encrypted is a good one.  Also if
> plugins.netbeans.org
> > upgrades to HTTP2, it MUST be TLS then.
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: [LAZY CONSENSUS] Which NetBeans domains to keep?

[Peter Steele]

Gj

Apologies on the Jira mistake, I was browsing on mobile and it wasn't
obvious there was more description that what was shown by default. I see
the full list now.

On my comment, it was list independent. I can't see a rational decision for
having more than one domain. I'm totally surprised there ever were 17. I
would say most people only know of the one and that is the one search
engines will take you too. The netbeans.org gives you the ability to keep
the packages and maven deployments the same and also for continuity with
moving to apache.

On Mon, 24 Sep 2018 10:32 Geertjan Wielenga,
 wrote:

> On Mon, Sep 24, 2018 at 11:22 AM, Peter Steele 
> wrote:
>
> > The 17 aren't listed in the JIRA
>
>
>
> Yes, they are. Copied and pasted from the JIRA:
>
> netbeans.org
> netbeans.net
> netbeans.info
> netbeans.com
> netbeans.tv
> netbeans2.com
> netbeans2.org
> netbeans2.net
> testnetbeans.org
> testnetbeans.com
> testnetbeans.net
> devnetbeans.net
> devnetbeans.com
> devnetbeans.org
> devnetbeans.info
> stagenetbeans.org
> planetnetbeans.org
>
>
>
> > but I would argue
>
>
>
> Please argue only once you understand the discussion. I.e., you had not
> seen the list, please see the list first, here it is above now copied from
> the JIRA.
>
> Thanks,
>
> Gj
>
>
>
> > only netbeans.org is
> > required. You can host videos/aggregate a blog, have a staging area all
> on
> > one site
> >
> > On Mon, 24 Sep 2018 09:25 Geertjan Wielenga,
> >  wrote:
> >
> > > Hi all,
> > >
> > > Oracle donated 17 domains connected to NetBeans to Apache:
> > >
> > > https://issues.apache.org/jira/browse/INFRA-16946
> > >
> > > We don't need all of them, Apache shouldn't need to deal with those we
> > > don't want and should let those domains expire that we don't want.
> > >
> > > Of the 17 listed above, I propose we keep the following:
> > >
> > > - netbeans.org -- the standard home page
> > > - netbeans.tv -- a video/tutorial related domain
> > > - stagenetbeans.org -- a staging domain, good to have one of those
> > > - planetnetbeans.org -- the blog aggregator
> > >
> > > Following Apache lazy consensus (https://www.apache.org/founda
> > > tion/voting.html#LazyConsensu
> > > <https://www.apache.org/foundation/voting.html#LazyConsensus>), i.e.,
> no
> > > voting or responses of any kind are needed, except if you object. If no
> > one
> > > objects within 24 hours, we'll assume lazy consensus and implement the
> > > above proposal.
> > >
> > > Thanks,
> > >
> > > Gj
> > >
> >
>

Re: [LAZY CONSENSUS] Which NetBeans domains to keep?

[Peter Steele]

The 17 aren't listed in the JIRA but I would argue only netbeans.org is
required. You can host videos/aggregate a blog, have a staging area all on
one site

On Mon, 24 Sep 2018 09:25 Geertjan Wielenga,
 wrote:

> Hi all,
>
> Oracle donated 17 domains connected to NetBeans to Apache:
>
> https://issues.apache.org/jira/browse/INFRA-16946
>
> We don't need all of them, Apache shouldn't need to deal with those we
> don't want and should let those domains expire that we don't want.
>
> Of the 17 listed above, I propose we keep the following:
>
> - netbeans.org -- the standard home page
> - netbeans.tv -- a video/tutorial related domain
> - stagenetbeans.org -- a staging domain, good to have one of those
> - planetnetbeans.org -- the blog aggregator
>
> Following Apache lazy consensus (https://www.apache.org/founda
> tion/voting.html#LazyConsensu
> ), i.e., no
> voting or responses of any kind are needed, except if you object. If no one
> objects within 24 hours, we'll assume lazy consensus and implement the
> above proposal.
>
> Thanks,
>
> Gj
>

Re: Problems creating Javahelp project

[Peter Steele]

I believe in some other emails it was mentioned java help couldn't be
included due to license issues.

On Mon, 17 Sep 2018 11:41 Peter Nabbefeld,  wrote:

> After some changes (mainly in folder structure) which seemed to be
> necessary, help seems even not to be recognized.
>
> - P.
>
>
> Am 13.09.18 um 10:50 schrieb Peter Nabbefeld:
> >
> > Hello,
> >
> > I want to create some NetBeans Javahelp providing module, but I cannot
> > find out, how. It seems, the problem arises from JHIndexer not being
> > run. Project source code is available here:
> > https://github.com/pnabbefeld/NBWicketSupportDocs
> >
> > Kind regards
> > Peter
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Blurry font with NetBeans 9.0

[Peter Steele]

Here it is

-J-Dsun.java2d.dpiaware=false
-J-Dsun.java2d.uiScale=2

With these you don't need to set the -fontSize, icons and fonts work well.
These work well for a theme that is not native (for me that is GTK)


On Fri, Sep 7, 2018 at 7:21 PM Peter Steele  wrote:

> The theme you use will make a difference too, if it's a native laf theme
> then it will use the os scaling properties. If not it won't and you will
> need to set the ui scaling property and also set hdip property. There is a
> manifest solution too but you don't need this. If you need these -J-D
> command lines I can send them to you.
>
>
>
> On Fri, 7 Sep 2018 18:48 Tim Boudreau,  wrote:
>
>> Add --fontsize 24 (or whatever size works) to your netbeans.conf and turn
>> off zoom.
>>
>> Of course fonts will look fuzzy when zoomed - you are making the logical
>> pixels take up more than one physical pixel.
>>
>> There are a couple of system properties that may be useful to tell AWT as
>> well.
>>
>> I have been running NetBeans for years on a high dpi screen. Zoom is not
>> the solution.
>>
>> -Tim
>>
>> On Fri, Sep 7, 2018 at 10:21 AM Eirik Bakke  wrote:
>>
>> > I have added https://issues.apache.org/jira/browse/NETBEANS-1227 to
>> > indicate that the NetBeans launcher should eventually declare itself as
>> > DPI-aware, like JDKs javaw.exe already does.
>> >
>> > -- Eirik
>> >
>> > -Original Message-
>> > From: Eirik Bakke 
>> > Sent: Friday, September 7, 2018 9:48 AM
>> > To: dev@netbeans.incubator.apache.org
>> > Subject: RE: Blurry font with NetBeans 9.0
>> >
>> > Hi, Christian.
>> >
>> > I have NetBeans 9.0 running very well on a Windows 10 HiDPI screen at
>> > either 150% or 200% scaling. It's essential to use the latest Java--I
>> use
>> > 10.0.2. You also need to right click the "bin\netbeans64.exe" file, or
>> > whichever shortcut you're using to open NetBeans, go to the
>> "Compatibility"
>> > tab, click "Change high DPI settings", "Override high DPI scaling
>> > behavior", and select scaling performed by "Application". (This should
>> > probably be built into the launcher at some point.)
>> >
>> > -- Eirik
>> >
>> > -Original Message-
>> > From: Christian Lenz 
>> > Sent: Friday, September 7, 2018 4:45 AM
>> > To: dev@netbeans.incubator.apache.org
>> > Subject: Blurry font with NetBeans 9.0
>> >
>> > Hey All,
>> >
>> > I wanted to test out NetBeans 9.0 and I must say, that I have a blurry
>> > font. Please see the attached screenshot of comparing NetBeans 8.2 and
>> > NetBeans 9.0:
>> > https://netbeans.slack.com/files/U2BLJ28NA/FCJC0D1C5/image.png
>> >
>> > It doesn’t matter of the LaF so I have it w/ or w/o the dacrula theme.
>> >
>> > My Enviroment is:
>> > Windows 10 (64 bit, latest release) with a zoom factor of 200% because I
>> > have a HiDPI Surface book and I can’t set it to 100% because it is far
>> to
>> > small so this is not an Option.
>> >
>> > Here are the Infos from the About Dialog:
>> >
>> > Product Version: Apache NetBeans IDE 9.0 (Build
>> > incubator-netbeans-release-334-on-20180708)
>> > Updates: Updates available to version NetBeans 8.2 Patch 2 (weird but
>> has
>> > Nothing todo with my problem)
>> > Java: 10.0.1; Java HotSpot(TM) 64-Bit Server VM 10.0.1+10
>> > Runtime: Java(TM) SE Runtime Environment 10.0.1+10
>> > System: Windows 10 version 10.0 running on amd64; Cp1252; de_DE (nb)
>> User
>> > directory: C:\Users\Chrl\AppData\Roaming\NetBeans\9.0
>> > Cache directory: C:\Users\Chrl\AppData\Local\NetBeans\Cache\9.0
>> >
>> > Here is the thread in slack, where the guys tried to helped me, but
>> > Nothing worked out:
>> > https://netbeans.slack.com/archives/C2BJDQ77A/p1535635507000100
>> >
>> > Do you Need smth more to help here? Did I miss smth About the blurry
>> font?
>> >
>> >
>> > Cheers
>> >
>> > Chris
>> >
>> >
>> >
>> B�CB�
>> > � [��X��ܚX�K  K[XZ[
>> > �  ]�][��X��ܚX�P �] �X[�˚[��X�] ܋�\ X� K�ܙ�B��܈ Y  ] [ۘ[  ��[X[� �
>> K[XZ[
>> > �  ]�Z [   �] �X[�˚[��X�] ܋�\ X� K�ܙ�B�B��܈ �\�  \� [��ܛX] [ۈ X��]H
>> �]
>> > �X[�� XZ[ [��  \� �  �\�]
>> > �B�΋Z�K�\ X� K�ܙ���ۙ� Y[��K� \�  ^KӑU �PS���XZ[ [��� \� �B�B�B
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>> >
>> > For further information about the NetBeans mailing lists, visit:
>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> >
>> >
>> > --
>> http://timboudreau.com
>>
>

Re: Blurry font with NetBeans 9.0

[Peter Steele]

The theme you use will make a difference too, if it's a native laf theme
then it will use the os scaling properties. If not it won't and you will
need to set the ui scaling property and also set hdip property. There is a
manifest solution too but you don't need this. If you need these -J-D
command lines I can send them to you.



On Fri, 7 Sep 2018 18:48 Tim Boudreau,  wrote:

> Add --fontsize 24 (or whatever size works) to your netbeans.conf and turn
> off zoom.
>
> Of course fonts will look fuzzy when zoomed - you are making the logical
> pixels take up more than one physical pixel.
>
> There are a couple of system properties that may be useful to tell AWT as
> well.
>
> I have been running NetBeans for years on a high dpi screen. Zoom is not
> the solution.
>
> -Tim
>
> On Fri, Sep 7, 2018 at 10:21 AM Eirik Bakke  wrote:
>
> > I have added https://issues.apache.org/jira/browse/NETBEANS-1227 to
> > indicate that the NetBeans launcher should eventually declare itself as
> > DPI-aware, like JDKs javaw.exe already does.
> >
> > -- Eirik
> >
> > -Original Message-
> > From: Eirik Bakke 
> > Sent: Friday, September 7, 2018 9:48 AM
> > To: dev@netbeans.incubator.apache.org
> > Subject: RE: Blurry font with NetBeans 9.0
> >
> > Hi, Christian.
> >
> > I have NetBeans 9.0 running very well on a Windows 10 HiDPI screen at
> > either 150% or 200% scaling. It's essential to use the latest Java--I use
> > 10.0.2. You also need to right click the "bin\netbeans64.exe" file, or
> > whichever shortcut you're using to open NetBeans, go to the
> "Compatibility"
> > tab, click "Change high DPI settings", "Override high DPI scaling
> > behavior", and select scaling performed by "Application". (This should
> > probably be built into the launcher at some point.)
> >
> > -- Eirik
> >
> > -Original Message-
> > From: Christian Lenz 
> > Sent: Friday, September 7, 2018 4:45 AM
> > To: dev@netbeans.incubator.apache.org
> > Subject: Blurry font with NetBeans 9.0
> >
> > Hey All,
> >
> > I wanted to test out NetBeans 9.0 and I must say, that I have a blurry
> > font. Please see the attached screenshot of comparing NetBeans 8.2 and
> > NetBeans 9.0:
> > https://netbeans.slack.com/files/U2BLJ28NA/FCJC0D1C5/image.png
> >
> > It doesn’t matter of the LaF so I have it w/ or w/o the dacrula theme.
> >
> > My Enviroment is:
> > Windows 10 (64 bit, latest release) with a zoom factor of 200% because I
> > have a HiDPI Surface book and I can’t set it to 100% because it is far to
> > small so this is not an Option.
> >
> > Here are the Infos from the About Dialog:
> >
> > Product Version: Apache NetBeans IDE 9.0 (Build
> > incubator-netbeans-release-334-on-20180708)
> > Updates: Updates available to version NetBeans 8.2 Patch 2 (weird but has
> > Nothing todo with my problem)
> > Java: 10.0.1; Java HotSpot(TM) 64-Bit Server VM 10.0.1+10
> > Runtime: Java(TM) SE Runtime Environment 10.0.1+10
> > System: Windows 10 version 10.0 running on amd64; Cp1252; de_DE (nb) User
> > directory: C:\Users\Chrl\AppData\Roaming\NetBeans\9.0
> > Cache directory: C:\Users\Chrl\AppData\Local\NetBeans\Cache\9.0
> >
> > Here is the thread in slack, where the guys tried to helped me, but
> > Nothing worked out:
> > https://netbeans.slack.com/archives/C2BJDQ77A/p1535635507000100
> >
> > Do you Need smth more to help here? Did I miss smth About the blurry
> font?
> >
> >
> > Cheers
> >
> > Chris
> >
> >
> >
> B�CB�
> > � [��X��ܚX�K  K[XZ[
> > �  ]�][��X��ܚX�P �] �X[�˚[��X�] ܋�\ X� K�ܙ�B��܈ Y  ] [ۘ[  ��[X[� �  K[XZ[
> > �  ]�Z [   �] �X[�˚[��X�] ܋�\ X� K�ܙ�B�B��܈ �\�  \� [��ܛX] [ۈ X��]H
> �]
> > �X[�� XZ[ [��  \� �  �\�]
> > �B�΋Z�K�\ X� K�ܙ���ۙ� Y[��K� \�  ^KӑU �PS���XZ[ [��� \� �B�B�B
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> > --
> http://timboudreau.com
>

Issue with latest jdk 11 on Linux and work around solution

[Peter Steele]

Hi

I recently upgraded my java on ubuntu and on startup I get this error

java.awt.AWTError: Assistive Technology not found:
org.GNOME.Accessibility.AtkWrapper
at java.desktop/java.awt.Toolkit.newAWTError(Toolkit.java:472)
at java.desktop/java.awt.Toolkit.fallbackToLoadClassForAT(Toolkit.java:488)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
at
java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1608)

Caused by: java.lang.ClassNotFoundException:
org.GNOME.Accessibility.AtkWrapper
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at java.base/java.lang.Class.forName0(Native Method)
...

The work around for this until they fix it is

Comment out line with 'assistive_technologies=org.GNOME.Accessibility.
AtkWrapper' in /etc/java-11-openjdk/accessibility.properties

Peter

Re: Cleanup of old pending PRs

[Peter Steele]

Looks like CONTRIBUTOR.md is "standard place" to put information on how to
contribute. Should be easy to add this to the root folder in GitHub.

On Fri, 17 Aug 2018 09:00 Peter Steele,  wrote:

> What is the process / criteria for approving a PR and what is the process
> / criteria for closing a PR?
>
> On the one hand everyone is encouraging people to contribute, on another
> hand you are suggesting to throw away contributions.
>
> Publish some PR submitter guidelines saying what people need to do to get
> a PR approved and what to do if their particular reviewer doesnt want to
> commit the changes and what to do if you have no comments at all on your
> PR.
>
> Once the process is clear then auto closing can be a valid action because
> the PR submitter is aware that this will happen.
>
>
>
>
> On Fri, 17 Aug 2018 07:35 Jaroslav Tulach, 
> wrote:
>
>> Dne Pá 17. srpna 2018 06:30:28, Peter Steele napsal(a):
>> > So my thoughts on this would be to decide on a more formal PR approach
>> and
>> > apply it to this situation
>>
>> Great, that is what I am calling for!
>>
>> Let's automatically close PRs that are silent for 60 days and more.
>>
>> Simple. Formal. Well defined. Easy to understand and implement approach.
>> -jt
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>

Re: Cleanup of old pending PRs

[Peter Steele]

What is the process / criteria for approving a PR and what is the process /
criteria for closing a PR?

On the one hand everyone is encouraging people to contribute, on another
hand you are suggesting to throw away contributions.

Publish some PR submitter guidelines saying what people need to do to get a
PR approved and what to do if their particular reviewer doesnt want to
commit the changes and what to do if you have no comments at all on your
PR.

Once the process is clear then auto closing can be a valid action because
the PR submitter is aware that this will happen.




On Fri, 17 Aug 2018 07:35 Jaroslav Tulach, 
wrote:

> Dne Pá 17. srpna 2018 06:30:28, Peter Steele napsal(a):
> > So my thoughts on this would be to decide on a more formal PR approach
> and
> > apply it to this situation
>
> Great, that is what I am calling for!
>
> Let's automatically close PRs that are silent for 60 days and more.
>
> Simple. Formal. Well defined. Easy to understand and implement approach.
> -jt
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Cleanup of old pending PRs

[Peter Steele]

The fact that there are so many open PR's is an issue in itself, we either
have lots of amazing code that isn't being integrated, or lots on
unsuitable requests that should be formally closed down or something in the
middle of these two (most likely).

Closing them just hides the fact we don't have a better process

- The issue for a lot them are conversations happen which are very
productive then they suddenly stop. If these are things we want to have in
netbeans then a better process needs to be in place so these great
submissions don't get lost.
- One assignes a reviewer and then the PR goes silent, again people are
busy but there needs to be a process to help speed this along
- People seem to be working on issues they want to fix (*yayy*), but this
isn't always the best thing for netbeans. But we don't have a way to
formally deal with these.

So my thoughts on this would be to decide on a more formal PR approach and
apply it to this situation

Peter


On Fri, 17 Aug 2018, 06:10 Mario Schroeder,  wrote:

> Hi,
>
> I would not close all. At least one PR is missing a second reviewer and
> could be merged then. So it depends.
> The rest, where is no activity for several months, could be closed.
>
>
>
> Jaroslav Tulach  schrieb am Fr., 17. Aug. 2018,
> 06:55:
>
> > Hi.
> > I've noticed that there is few pull requests that haven't seen any
> > activity in
> > last forty seven days:
> >
> >
> >
> https://github.com/apache/incubator-netbeans/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aopen+updated%3A%3C2018-06-01+-label%3Awork-in-progress+
> >
> > Shouldn't there be some policy to close them automatically? Assuming
> there
> > is
> > a way to reopen them again, it should do no harm and would keep the list
> > of
> > open PR actual.
> >
> > Best regards.
> > -jt
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>

Re: Apache NetBeans Release Cycle

[Peter Steele]

Badly worded by me, module update issue is where the update center will be
located

On Tue, 7 Aug 2018 15:54 Oliver Rettig,  wrote:

> > Phycologically people feel they have a more modern system if it updates
> > more frequently. There should be no reason why minor items can't be
> > released quickly in a more agile way. I suspect though we need to move
> out
> > of incubator status for that because there are a lot of rounds of
> approval
> > before code gets released.
> > You could have large core releases once or twice a year and many minor
> > updates imbetween.
> +1
>
> > This is a personal thing but I would like to get the updates without
> > downloading a new version of the ide every time. Letting the ide auto
> > update would be nice. I guess that could only happen when the module
> update
> > issue is resolved
> Please point me to that module update issue?
>
> > On Tue, 7 Aug 2018 15:24 Geertjan Wielenga,
> >
> >  wrote:
> > > Also, Apache NetBeans is more than Java-focused, and the question is
> also
> > > whether such prominence for Java should be given to the extent that the
> > > JDK
> > > releases should be followed at all, i.e., whether this should be an
> aim of
> > > the project. It's certainly open to discussion but definitely not a
> given.
> > >
> > > Gj
> > >
> > > On Tue, Aug 7, 2018 at 4:22 PM, Geertjan Wielenga <
> > >
> > > geertjan.wiele...@googlemail.com> wrote:
> > > > Just as a quick FYI: Both JDK 9 and JDK 10 are supported in Apache
> > > > NetBeans 9, i.e., no, we've not skipped JDK 10.
> > > >
> > > > Gj
> > > >
> > > > On Tue, Aug 7, 2018 at 4:11 PM, Chuck Davis 
> wrote:
> > > >> To me it makes sense to have NB reflect the level of Java
> implemented.
> > > >> For
> > > >> example, features of JDK 11 can be added incrementally to NB 9.1,
> 9.2,
> > > >> etc.
> > > >> (schedule is irrelevant to me -- every 3 months is fine)  but when
> the
> > > >> full
> > > >> function of JDK 11 is included then NB 11 should be released.  I
> assume
> > > >> we're going to skip JDK 10 at this point.  Releases like 2018.3
> tell me
> > > >> nothing about what the product includes.  But if Java moves to that
> > >
> > > naming
> > >
> > > >> scheme then NB should move to that scheme to indicate what is
> > >
> > > implemented.
> > >
> > > >> On Tue, Aug 7, 2018 at 1:46 AM, Geertjan Wielenga <
> > > >>
> > > >> geertjan.wiele...@googlemail.com.invalid> wrote:
> > > >> > Hi all,
> > > >> >
> > > >> > We've discussed this informally, i.e., the topic of the release
> > > >> > cycle/cadence, a few times over the past months.
> > > >> >
> > > >> > Let's nail it down as far as possible so that we can give clarity
> to
> > >
> > > our
> > >
> > > >> > users about our intentions and also to enable us to organize
> features
> > > >> > coming in through donations and otherwise into releases.
> > > >> >
> > > >> > https://cwiki.apache.org/confluence/display/NETBEANS/
> > > >> > Apache+NetBeans+Release+Cycle
> > > >> >
> > > >> > Right now, we have a clear suggestion around in which month of the
> > >
> > > year
> > >
> > > >> we
> > > >>

Re: Using 8.2 plugins in 9.0

[Peter Steele]

Useful tip for those editing confluence, you can select dates for the table
by typing // to bring up the date selector. The dates in the table are then
sortable.

On Tue, Aug 7, 2018 at 12:35 PM Oliver Rettig  wrote:

> +1 and thanks
> > Hi all,
> >
> > On the Slack channel and elsewhere there's been discussion around the
> need
> > for everyone to know which 8.2 plugins actually work in 9.0.
> >
> > So, here's a page where we can document that:
> >
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Using+8.2+Plugins+in+9
> .
> > 0
> >
> > If you don't have access to the page, create a Confluence user account if
> > you don't have one, and send the user name to me, and I will give you
> > permission to access the NetBeans Confluence pages.
> >
> > The above is a very simple and lowkey way to support Apache NetBeans at
> > this stage of the process.
> >
> > Comments to the above are welcome.
> >
> > Thanks,
> >
> > Gj
>
>
>

Re: Apache NetBeans Release Cycle

[Peter Steele]

Phycologically people feel they have a more modern system if it updates
more frequently. There should be no reason why minor items can't be
released quickly in a more agile way. I suspect though we need to move out
of incubator status for that because there are a lot of rounds of approval
before code gets released.

You could have large core releases once or twice a year and many minor
updates imbetween.

This is a personal thing but I would like to get the updates without
downloading a new version of the ide every time. Letting the ide auto
update would be nice. I guess that could only happen when the module update
issue is resolved

On Tue, 7 Aug 2018 15:24 Geertjan Wielenga,
 wrote:

> Also, Apache NetBeans is more than Java-focused, and the question is also
> whether such prominence for Java should be given to the extent that the JDK
> releases should be followed at all, i.e., whether this should be an aim of
> the project. It's certainly open to discussion but definitely not a given.
>
> Gj
>
> On Tue, Aug 7, 2018 at 4:22 PM, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
> > Just as a quick FYI: Both JDK 9 and JDK 10 are supported in Apache
> > NetBeans 9, i.e., no, we've not skipped JDK 10.
> >
> > Gj
> >
> > On Tue, Aug 7, 2018 at 4:11 PM, Chuck Davis  wrote:
> >
> >> To me it makes sense to have NB reflect the level of Java implemented.
> >> For
> >> example, features of JDK 11 can be added incrementally to NB 9.1, 9.2,
> >> etc.
> >> (schedule is irrelevant to me -- every 3 months is fine)  but when the
> >> full
> >> function of JDK 11 is included then NB 11 should be released.  I assume
> >> we're going to skip JDK 10 at this point.  Releases like 2018.3 tell me
> >> nothing about what the product includes.  But if Java moves to that
> naming
> >> scheme then NB should move to that scheme to indicate what is
> implemented.
> >>
> >> On Tue, Aug 7, 2018 at 1:46 AM, Geertjan Wielenga <
> >> geertjan.wiele...@googlemail.com.invalid> wrote:
> >>
> >> > Hi all,
> >> >
> >> > We've discussed this informally, i.e., the topic of the release
> >> > cycle/cadence, a few times over the past months.
> >> >
> >> > Let's nail it down as far as possible so that we can give clarity to
> our
> >> > users about our intentions and also to enable us to organize features
> >> > coming in through donations and otherwise into releases.
> >> >
> >> > https://cwiki.apache.org/confluence/display/NETBEANS/
> >> > Apache+NetBeans+Release+Cycle
> >> >
> >> > Right now, we have a clear suggestion around in which month of the
> year
> >> we
> >> > will release. I.e., the Apache NetBeans (incubating) 9.0 release was
> our
> >> > August release (and we even managed to release it a few days early, in
> >> > July, hurray!). So, this year, we will have another release in
> November,
> >> > that's our next big target, if we agree with the above proposal.
> >> >
> >> > However, a separate discussion is about release numbers. Our current
> >> > release is 9.0. How do we decide to number the other releases? A
> simple
> >> > proposal might be to have our major release in August of each year and
> >> then
> >> > all then make all the other releases minor. However, that's just a
> >> thought,
> >> > another one could be that we should simply consider how large the
> >> features
> >> > are that we have added and base major/minor on that. Or we could try
> to
> >> > follow the JDK release numbering more or less.
> >> >
> >> > Anyway, thoughts welcome,
> >> >
> >> > Gj
> >> >
> >>
> >
> >
>

Re: [DISCUSS] Integration of 2nd donation

[Peter Steele]

Gj

I'm not sure I fully understand what the issue is. I suspect it's not a
clear direction on what the branching strategy is for this project. There
are also conflicting ideas which makes it hard to comment.

If you just want to merge everything in to master then the way to do this
has been discussed already. This is a very standard thing to do in git.

I personally don't agree with this approach because master should contain
everything that has been signed off and this code has not been signed off.
You have a branch so use that branch for approving everything then merge in
to master once donation 2 is signed off. Remember you can cherry pick
commits to the master branch back to the donation2 branch to keep them in
sync.

The donation2 branch should be a copy of master with the additional
modules. Does it?

The rat report should be run from this new branch

The new modules should be added to the rate report if they need to be
configured.

The committers need to agree on the branching strategy then the to-do list
falls in to place easily.





On Wed, 1 Aug 2018 10:50 Geertjan Wielenga,
 wrote:

> OK. There are 430 people registered on this mailing list.
>
> Until someone responds to this thread or simply uses their existing
> knowledge to bring the 2nd donation into master probably in the way
> suggested by Jan Lahoda above in this thread, integration of the 2nd
> donation is effectvely dead. Want Java EE in Apache NetBeans? Want PHP?
> Groovy? JavaScript? Then answer the open questions here or please do the
> merge in one way or another yourself. :-)
>
> Gj
>
>
> On Wednesday, August 1, 2018, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
> > My fork's master is now merged into my fork's 2ndDonation branch:
> >
> > https://github.com/geertjanw/incubator-netbeans/tree/2ndDonation
> >
> > Using:
> >
> > git clone -b 2ndDonation https://github.com/geertjanw/
> > incubator-netbeans.git
> >
> > git pull https://github.com/apache/incubator-netbeans.git
> > --allow-unrelated-histories
> >
> > From my 2ndDonation branch, I could do a PR for the origin repo's
> > 2ndDonation branch.
> >
> > Is that the next step or something else (or does someone who knows what
> > needs to be done want to do it)?
> >
> > Gj
> >
> >
> >
> > On Wed, Aug 1, 2018 at 7:57 AM, Geertjan Wielenga <
> > geertjan.wiele...@googlemail.com> wrote:
> >
> >> OK.
> >>
> >> What are the PR checks exactly, i.e., how will we know this approach is
> >> successful?
> >>
> >> Should I do this in my fork first? Or straight into the 2ndDonation
> >> branch at https://github.com/apache/incubator-netbeans/tree/2ndDonation
> ?
> >>
> >> Gj
> >>
> >> On Tue, Jul 31, 2018 at 7:04 PM, Jan Lahoda  wrote:
> >>
> >>> On Tue, Jul 31, 2018 at 5:19 PM, Geertjan Wielenga <
> >>> geertjan.wiele...@googlemail.com.invalid> wrote:
> >>>
> >>> > Did the above (including --allow-unrelated-histories), ran Ant Rat,
> >>> and was
> >>> > encouraged to find 'only' 1223 unknown licenses identified:
> >>> >
> >>> > https://cwiki.apache.org/confluence/display/NETBEANS/
> >>> > Initial+Rat+Report+for+2nd+Donation
> >>> >
> >>> > I believe that if I were to do a push, the Ant Rat that is run
> >>> > automatically needs to be tweaked to include the new clusters.
> >>> >
> >>> > Jan Lahoda, I think you can tell more about this and explain what
> >>> needs to
> >>> > be done re Rat and then someone can do that.
> >>> >
> >>>
> >>> I think it might be good to merge master into the 2ndDonation  branch
> >>> (and
> >>> push to 2ndDonation). Then it might(?) be possible to create a PR from
> >>> 2ndDonation to master (which would run all the PR checks for us
> >>> automatically). I though rat wouldn't need need tweaks in travis
> config,
> >>> but apparently it will need some - I can try to do that, but having
> >>> master
> >>> merged into the 2ndDonation branch would help.
> >>>
> >>> Thanks,
> >>>  Jan
> >>>
> >>>
> >>> > Thanks,
> >>> >
> >>> > Gj
> >>> >
> >>> >
> >>> > On Tue, Jul 31, 2018 at 5:02 PM, Peter Steele 
> >>> > wrote:
> >>> >
> >>> > > You do it locally on

Re: [DISCUSS] Integration of 2nd donation

[Peter Steele]

You do it locally on your own PC, clone master, pull in chosen branch,
commit and push. I don't know of a way to do it on the GitHub site, using
git commands is easiest. There is probably a gui to do this too

On Tue, 31 Jul 2018 15:58 Geertjan Wielenga,
 wrote:

> Apologies for my ignorance, but should someone do this in their own clone
> or should it be done directly in
> https://github.com/apache/incubator-netbeans?
>
> Gj
>
> On Tue, Jul 31, 2018 at 4:45 PM, Peter Steele 
> wrote:
>
> > https://help.github.com/articles/merging-an-upstream-
> > repository-into-your-fork/
> >
> > On Tue, 31 Jul 2018 15:41 Geertjan Wielenga,
> >  wrote:
> >
> > > Is there a way to merge the branch into master on GitHub?
> > >
> > > Or is there someone who can recommend best practices for doing this?
> > >
> > > Thanks,
> > >
> > > Gj
> > >
> > >
> > > On Tue, Jul 31, 2018 at 4:16 PM, Josh Juneau 
> > wrote:
> > >
> > > > Looking forward to getting started with the work on this 2nd
> donation.
> > > >
> > > > On Tue, Jul 31, 2018 at 3:09 AM Geertjan Wielenga
> > > >  wrote:
> > > >
> > > > > Is there any objection to merging the 2nddonation branch into
> master
> > > > today?
> > > > >
> > > > > https://github.com/apache/incubator-netbeans/tree/2ndDonation
> > > > >
> > > > > Gj
> > > > >
> > > > > On Sun, Jul 29, 2018 at 9:44 PM, Geertjan Wielenga <
> > > > > geertjan.wiele...@googlemail.com> wrote:
> > > > >
> > > > > > Is there anything stopping us from merging the 2nd donation
> branch
> > > into
> > > > > > master?
> > > > > >
> > > > > > If not, let's do it, then take a look at the Rat report after the
> > > first
> > > > > > build that includes the branch, and see what kind and how many
> > > problems
> > > > > are
> > > > > > identified and how to solve them.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Gj
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, Jul 26, 2018 at 11:00 PM, Antonio 
> > > wrote:
> > > > > >
> > > > > >> That's easy: I still own one of the NetBeans Day in 2004
> > > somewhere...
> > > > > >>
> > > > > >> El 26/07/2018 a las 22:58, Emilian Bold escribió:
> > > > > >>
> > > > > >>> We just need some tshirts to gift people :-)
> > > > > >>>
> > > > > >>> --emi
> > > > > >>>
> > > > > >>> ‐‐‐ Original Message ‐‐‐
> > > > > >>> On 26 July 2018 11:57 PM, Antonio  wrote:
> > > > > >>>
> > > > > >>> Yep, but on august. Let's call it Hacktaugustfest or something
> > :-)
> > > > > >>>>
> > > > > >>>> El 26/07/2018 a las 22:40, Emilian Bold escribió:
> > > > > >>>>
> > > > > >>>> Isn't this what we did with #Hacktoberfest 2017?
> > > > > >>>>> --emi
> > > > > >>>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>
> > > -
> > > > > >> To unsubscribe, e-mail:
> > > dev-unsubscr...@netbeans.incubator.apache.org
> > > > > >> For additional commands, e-mail: dev-help@netbeans.incubator.
> > > > apache.org
> > > > > >>
> > > > > >> For further information about the NetBeans mailing lists, visit:
> > > > > >> https://cwiki.apache.org/confluence/display/NETBEANS/
> > Mailing+lists
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > > --
> > > > Josh Juneau
> > > > juneau...@gmail.com
> > > > http://jj-blogger.blogspot.com
> > > > https://www.apress.com/index.php/author/author/view/id/1866
> > > >
> > >
> >
>

Re: [DISCUSS] Integration of 2nd donation

[Peter Steele]

https://help.github.com/articles/merging-an-upstream-repository-into-your-fork/

On Tue, 31 Jul 2018 15:41 Geertjan Wielenga,
 wrote:

> Is there a way to merge the branch into master on GitHub?
>
> Or is there someone who can recommend best practices for doing this?
>
> Thanks,
>
> Gj
>
>
> On Tue, Jul 31, 2018 at 4:16 PM, Josh Juneau  wrote:
>
> > Looking forward to getting started with the work on this 2nd donation.
> >
> > On Tue, Jul 31, 2018 at 3:09 AM Geertjan Wielenga
> >  wrote:
> >
> > > Is there any objection to merging the 2nddonation branch into master
> > today?
> > >
> > > https://github.com/apache/incubator-netbeans/tree/2ndDonation
> > >
> > > Gj
> > >
> > > On Sun, Jul 29, 2018 at 9:44 PM, Geertjan Wielenga <
> > > geertjan.wiele...@googlemail.com> wrote:
> > >
> > > > Is there anything stopping us from merging the 2nd donation branch
> into
> > > > master?
> > > >
> > > > If not, let's do it, then take a look at the Rat report after the
> first
> > > > build that includes the branch, and see what kind and how many
> problems
> > > are
> > > > identified and how to solve them.
> > > >
> > > > Thanks,
> > > >
> > > > Gj
> > > >
> > > >
> > > >
> > > > On Thu, Jul 26, 2018 at 11:00 PM, Antonio 
> wrote:
> > > >
> > > >> That's easy: I still own one of the NetBeans Day in 2004
> somewhere...
> > > >>
> > > >> El 26/07/2018 a las 22:58, Emilian Bold escribió:
> > > >>
> > > >>> We just need some tshirts to gift people :-)
> > > >>>
> > > >>> --emi
> > > >>>
> > > >>> ‐‐‐ Original Message ‐‐‐
> > > >>> On 26 July 2018 11:57 PM, Antonio  wrote:
> > > >>>
> > > >>> Yep, but on august. Let's call it Hacktaugustfest or something :-)
> > > 
> > >  El 26/07/2018 a las 22:40, Emilian Bold escribió:
> > > 
> > >  Isn't this what we did with #Hacktoberfest 2017?
> > > > --emi
> > > >
> > > 
> > > 
> > > >>
> -
> > > >> To unsubscribe, e-mail:
> dev-unsubscr...@netbeans.incubator.apache.org
> > > >> For additional commands, e-mail: dev-help@netbeans.incubator.
> > apache.org
> > > >>
> > > >> For further information about the NetBeans mailing lists, visit:
> > > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > >
> > --
> > Josh Juneau
> > juneau...@gmail.com
> > http://jj-blogger.blogspot.com
> > https://www.apress.com/index.php/author/author/view/id/1866
> >
>

Re: Snap - Linux packaging

[Peter Steele]

Thanks, looks like the INFRA ticket is progressing

On Mon, Jul 30, 2018 at 6:36 PM Laszlo Kishalmi 
wrote:

> Well, we need to figure out how can we build the Snap package on Apache
> infra.
>
> https://issues.apache.org/jira/browse/NETBEANS-341
>
> https://issues.apache.org/jira/browse/INFRA-16728
>
> Till it happens:
> wget
>
> https://s3-us-west-2.amazonaws.com/lkishalmi-us-west-2-public/snaps/netbeans_9.0_amd64.snap
> sudo snap install netbeans_9.0_amd64.snap --dangerous --classic
>
> On 07/30/2018 09:49 AM, Peter Steele wrote:
> > Hi
> >
> > What's the latest of getting Netbeans 9 packaged up as a snap? I saw some
> > emails a while back but nothing seemed to indicate if anything was going
> to
> > happen or not.
> >
> > Having a snap would make it very easy to install on Linux. I see some
> > discussions on Mac packaging, would be good to close the Linux
> discussions
> > too.
> >
> > Peter
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Snap - Linux packaging

[Peter Steele]

Hi

What's the latest of getting Netbeans 9 packaged up as a snap? I saw some
emails a while back but nothing seemed to indicate if anything was going to
happen or not.

Having a snap would make it very easy to install on Linux. I see some
discussions on Mac packaging, would be good to close the Linux discussions
too.

Peter

Re: Public vs. Friend API?

[Peter Steele]

Could Netbeans implement something similar in his stack overflow?

https://stackoverflow.com/q/3297/2999563

Let it be flagged as unstable or experimental in the javadoc but let the
user decide (how ever stupid it maybe)

On Mon, 23 Jul 2018 10:12 Neil C Smith,  wrote:

> On Mon, 23 Jul 2018, 00:12 Emilian Bold,  .invalid>
> wrote:
>
> > How do you get more input about the API if the consumer can unilaterally
> > ask for access?
> >
>
> Because people have a tendency to input when things are broken or don't
> work as expected / required! ;-)
>
> Best wishes,
>
> Neil
>
> >
>

Re: Apache NetBeans Apress Book

[Peter Steele]

I had a look at Apress and there are quite a few books on netbeans (one
already that uses Netbeans 9 for its demos!). They all cost money
(unsurprisingly), I was wondering how that would fit in to a community
written book?

I don't have any expertise to add myself (I'm kind of waiting till things
stabilise to a standard development life cycle before investing some time
in to adding enhancements) but was interested in how it would work.

Is it better to actually just write a free book? Or do Apress bring a lot
to the venture?

On Wed, 18 Jul 2018 17:22 Mario Schroeder,  wrote:

> Hi Miloš,
>
> that what you describe is what I also thought about. I got an book about NB
> too, but the samples there don't use the annotations and some classes are
> even deprecated. So an update to the latest version of the platform would
> be great. I could be your copilot if you need help in reviews and
> correction.
>
> Regards,
> Mario
>
> Miloš Šilhánek  schrieb am Mi., 18. Juli 2018,
> 17:54:
>
> > Hi,
> > I was been interested some years ago in NetBeans Platform. I organized
> > translation from English to Czech and cowrote a NetBeans Platform
> > Cookbook
> > which were not realized - it is on NB wiki pages.
> >
> > So I leaved it - because of time and the need of application based on NB
> > Platform disappears in my work.
> > Now is all by browser. :-(. But NBP is suitable for many application as
> > the
> > showcase shows.
> >
> >
> >
> >
> > The book was made for NB 6.9.1 and tested for 7.1. Many features were
> > moved
> > to annotations in this time. We both had no time to upgrade it.
> >
> >
> >
> >
> > My English is poor so I could upgrade these examples or test new
> examples.
> >
> > Milos
> >
> >
> >
> >
> >
> > -- Původní e-mail --
> > Od: Delfi Ramirez 
> > Komu: dev@netbeans.incubator.apache.org <
> dev@netbeans.incubator.apache.org
> > >
> > Datum: 16. 7. 2018 13:56:18
> > Předmět: RE: Apache NetBeans Apress Book
> > "Hi All:
> >
> > Agreed there is the need of a chapter-by-chapter community written book.
> >
> > Count me in. Even if there is the need for the book, once written, of a
> > single translator for the whole community content.
> >
> > Even everyone of us has English as a mother tongue or second tongue, we
> > may
> > able to reach and target new markets and new loyal fellows in this world
> > wide world we live in
> >
> > Cheers
> >
> >
> > Delfi Ramirez
> >
> > Segonquart Studio
> >
> > https://segonquart.net
> >
> > From: Oliver Rettig
> > Sent: 16 July 2018 13:47
> > To: dev@netbeans.incubator.apache.org
> > Subject: Re: Apache NetBeans Apress Book
> >
> > Hi all,
> >
> > I like the idea of a community-written book very much. This can encourage
> > people to join
> > our great community and it show that netbeans is now a apache project ...
> > For me the
> > community is one of the most important facts to work with netbeans and
> > rarely with eclipse.
> >
> > I have some experience with writing a book for Tomcat 5:
> >
> > https://www.rheinwerk-verlag.de/tomcat-5_700/
> >
> > and the most important thing I have learned from this book project is:
> > better not to write
> > such books alone.
> >
> > It would be a pleasure for me to write a chapter for a community-written
> > Netbeans book, or
> > may be to translate from english to german some parts, if we want to have
> > a
> > german
> > version.
> >
> > But I have less experience in organzing such things. In scientific
> > communities typically you
> > have an editor or a small team of editors. Their job is often really a
> lot
> > of work: to defines the
> > chapters/articles, to find people who can write the articles and to push
> > the
> > authors to deliver
> > in the timeline.
> >
> > An other question is where and how to publish the book. My experience
> with
> > the Tomcat
> > book was that the publisher was a really great help in formatting and
> > proofreading. And a
> > publisher can be a very big help in invertising for apache netbeans.
> >
> > But it should be also possible to write the book without a publisher at
> > our
> > own. In this case
> > we can have an open-pdf-Version of the book. Maye we can have this too
> > with
> > a publisher?
> >
> > best regards
> > Oliver
> >
> >
> > > I've been approached by Apress regarding interest in a book on Apache
> > > NetBeans. I personally do not have enough time to devote to another
> book
> > > right now, so I wanted to send a note to the Apache NetBeans developer
> > > group to see if there are any developers interested in authoring a book
> > > (perhaps a collaborative effort).
> > >
> > > I know things are very busy right now, and I've already told Apress
> that
> > > the main focus is the release of Apache NetBeans 9 right now, but maybe
> > a
> > > book project could start this fall. There are no timelines right
> > > now...just interest in a book on the new open Apache NetBeans IDE.
> > >
> > > If anyone is interested then reply to this message and I can get 

Re: Apache NetBeans Apress Book

[Peter Steele]

Can someone link the current book to netbeans.apache.org? Would've good to
reference it in the documentation page and when /if the new book comes the
link can be updated.

On Tue, 17 Jul 2018 09:40 Delfi Ramirez,  wrote:

> +1 Huang Kai 
>
> A wonder of myself to the community. Is there exist any intention or
> interest to include JSF in the topics -- chapters, subchapters -- of the
> book?
>
> Cheers
>
> Delfi Ramirez
>
> Segonquart Studio
>
> https://segonquart.net
>
> From: huang kai
> Sent: 17 July 2018 10:30
> To: dev@netbeans.incubator.apache.org
> Subject: Re: Apache NetBeans Apress Book
>
> Hi, all
>
> I live in china and have been using netbeans for swing and java ee dev
> for about 10 years. I think I can help translate the book to chinese,
> let's make this great platform speading more faster.
>
> cheers.
>
> Kain Huang
>
>
> On 7/16/2018 7:53 PM, Delfi Ramirez wrote:
> > Hi All:
> >
> > Agreed there is the  need of a chapter-by-chapter community written book.
> >
> > Count me in. Even if there is the need for the book, once written,  of a
> single translator for the whole community content.
> >
> > Even everyone of us has English as a mother tongue or second tongue, we
> may able to reach and target new markets and new loyal fellows in this
> world wide world we live in
> >
> > Cheers
> >
> >
> > Delfi Ramirez
> >
> > Segonquart Studio
> >
> > https://segonquart.net
> >
> > From: Oliver Rettig
> > Sent: 16 July 2018 13:47
> > To: dev@netbeans.incubator.apache.org
> > Subject: Re: Apache NetBeans Apress Book
> >
> > Hi all,
> >
> > I like the idea of a  community-written book very much. This can
> encourage people to join
> > our great community and it show that netbeans is now a apache project
> ... For me the
> > community is one of the most important facts to work with netbeans and
> rarely with eclipse.
> >
> > I have some experience with writing a book for Tomcat 5:
> >
> > https://www.rheinwerk-verlag.de/tomcat-5_700/
> >
> > and the most important thing I have learned from this book project is:
> better not to write
> > such books alone.
> >
> > It would be a pleasure for me to write a chapter for a community-written
> Netbeans book, or
> > may be to translate from english to german some parts, if we want to
> have a german
> > version.
> >
> > But I have less experience in organzing such things. In scientific
> communities typically you
> > have an editor or a small team of editors. Their job is often really a
> lot of work: to defines the
> > chapters/articles, to find people who can write the articles and to push
> the authors to deliver
> > in the timeline.
> >
> > An other question is where and how to publish the book. My experience
> with the Tomcat
> > book was that the publisher was a really great help in formatting and
> proofreading. And a
> > publisher can be a very big help in invertising for apache netbeans.
> >
> > But it should be also possible to write the book without a publisher at
> our own. In this case
> > we can have an open-pdf-Version of the book. Maye we can have this too
> with a publisher?
> >
> > best regards
> > Oliver
> >
> >
> >> I've been approached by Apress regarding interest in a book on Apache
> >> NetBeans.  I personally do not have enough time to devote to another
> book
> >> right now, so I wanted to send a note to the Apache NetBeans developer
> >> group to see if there are any developers interested in authoring a book
> >> (perhaps a collaborative effort).
> >>
> >> I know things are very busy right now, and I've already told Apress that
> >> the main focus is the release of Apache NetBeans 9 right now, but maybe
> a
> >> book project could start this fall.  There are no timelines right
> >> now...just interest in a book on the new open Apache NetBeans IDE.
> >>
> >> If anyone is interested then reply to this message and I can get a list
> of
> >> names together to send along to Apress.
> >>
> >> Thanks
> >>
> >> Josh Juneau
> >> juneau...@gmail.com
> >> http://jj-blogger.blogspot.com
> >> https://www.apress.com/index.php/author/author/view/id/1866
> >
> >
> >
>
>
>

Re: Updater branding

[Peter Steele]

There is a nice little animated gif of stack overflow which shows you how
to do this.

https://stackoverflow.com/a/24159161/2999563



On Mon, 25 Jun 2018 17:27 Geertjan Wielenga,
 wrote:

> https://github.com/apache/incubator-netbeans/pull/601
>
> That's a PR for 'main'. How do I get it into 'release90' branch?
>
> Gj
>
> On Mon, Jun 25, 2018 at 5:08 PM, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
> > Here they are:
> >
> > core.startup/src/org/netbeans/core/startup/splash.gif
> > core.startup/src/org/netbeans/core/startup/splash_dark.gif
> >
> > Thanks,
> >
> > Gj
> >
> >
> >
> >
> > On Mon, Jun 25, 2018 at 5:04 PM, Geertjan Wielenga <
> > geertjan.wiele...@googlemail.com> wrote:
> >
> >>
> >> Here's the location of the updater image, I believe:
> >>
> >> ide.branding/autoupdate.services/libsrc/org/netbeans/updater
> >> /resources/updatersplash_nb.gif
> >>
> >> The other one I haven't found yet, i.e., the one for the NetBeans
> >> Platform application.
> >>
> >> Gj
> >>
> >>
> >>
> >>
> >> On Sun, Jun 24, 2018 at 11:36 PM, Laszlo Kishalmi <
> >> laszlo.kisha...@gmail.com> wrote:
> >>
> >>> And if we get a chance the branding when you create a new platform
> >>> application project is still the old branding.
> >>>
> >>> (https://issues.apache.org/jira/browse/NETBEANS-990) I could not find
> >>> the code responsible for that at the first scan.
> >>>
> >>>
> >>>
> >>>
> >>> On 06/24/2018 12:16 PM, Geertjan Wielenga wrote:
> >>>
>  Yes.
> 
>  Gj
> 
>  On Sun, Jun 24, 2018 at 8:56 PM, Sven Reimers  >
>  wrote:
> 
>  So we still need to update the updater as well for NetBeans 9.0
> release?
> >
> > -Sven
> >
> > Geertjan Wielenga  schrieb
> > am
> > So., 24. Juni 2018, 19:25:
> >
> > I don't believe the update dialog has been updated -- I only updated
> >> the
> >> splash screen and the About box.
> >>
> >> Those new images are in 'ide.branding'.
> >>
> >> Gj
> >>
> >> On Sun, Jun 24, 2018 at 6:36 PM, Sven Reimers <
> sven.reim...@gmail.com
> >> >
> >> wrote:
> >>
> >> Hi all,
> >>>
> >>> can anyone confirm that the branding of the update dialog has been
> >>>
> >> updated?
> >>
> >>> I just tried with a local build of the latest 90release branch and
> >>> saw
> >>>
> >> the
> >>
> >>> old blue updater splash (this is on mac os).
> >>>
> >>> Just trying to figure out if this is just me seeing this..
> >>>
> >>> Thanks
> >>>
> >>> -Sven
> >>>
> >>> --
> >>> Sven Reimers
> >>>
> >>> * Senior Expert Software Architect
> >>> * Java Champion
> >>> * NetBeans Dream Team Member: http://dreamteam.netbeans.org
> >>> * JUG Leader JUG Bodensee: http://www.jug-bodensee.de
> >>> * Duke's Choice Award Winner 2009
> >>>
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> >>> For additional commands, e-mail:
> dev-h...@netbeans.incubator.apache.org
> >>>
> >>> For further information about the NetBeans mailing lists, visit:
> >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>
> >>>
> >>>
> >>>
> >>
> >
>

Re: Questions about contributing code and developing on top of Platform 9.0

[Peter Steele]

Geertjan

I've seen that link but running ant from netbeans is not the same as
actually running the actual java code where you can step through code and
inspect variables etc.

Regards

Peter

On Fri, 15 Jun 2018 19:59 Geertjan Wielenga,
 wrote:

> Here it is:
>
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Development+Environment
>
> Gj
>
> On Fri, Jun 15, 2018 at 8:58 PM, Peter Steele 
> wrote:
>
> > Is there a guide any where for building netbeans in the netbeans ide so
> you
> > can use netbeans to debug things?
> >
> > On Fri, 15 Jun 2018, 19:48 Dmitry Avtonomov, <
> dmitriy.avtono...@gmail.com>
> > wrote:
> >
> > > Thanks Matthias and Gj!
> > >
> > > I've added the extra Debug line to confluence wiki:
> > >
> > > https://cwiki.apache.org/confluence/display/NETBEANS/
> > Development+Environment
> > >
> > > On Fri, Jun 15, 2018 at 11:33 AM Matthias Bläsing <
> > > mblaes...@doppel-helix.eu>
> > > wrote:
> > >
> > > > Hi Dmitry,
> > > >
> > > > Am Freitag, den 15.06.2018, 11:02 -0700 schrieb Dmitry Avtonomov:
> > > > > Just wanted to point out that:
> > > > > 1) The Netbeans project is potentially loosing lots of people who
> > would
> > > > > have liked to contribute, but can't find a way how.
> > > >
> > > > the insight is good, so you obvisually went through this and could
> > > > improve the documentation. That would help the project and you.
> > > >
> > > > Remember: Many current contributors are around for a long time, so
> they
> > > > now the places to look and the thinks to do.
> > > >
> > > > > 2) 10 minute turnaround time for fix-build-run-test cycle is too
> > much.
> > > >
> > > > This will require some one to step up and look through the build
> where
> > > > the time is spend. But normally you don't need to rebuild the whole
> > > > IDE. You build once and if you need to modify a set of modules, you
> > > > just rebuild these.
> > > >
> > > > > 3) Most importantly I don't know how to start the whole thing in
> > debug
> > > > > mode. Do I need to modify the ant script to make it wait for
> debugger
> > > > > connection?
> > > >
> > > > You can pass java options through the netbeans launcher via
> > > > "-J". This will run netbeans with debugging enabled:
> > > >
> > > > /bin/netbeans
> > > > -J-agentlib:jdwp=transport=dt_socket,suspend=y,server=y,address=9009
> > > >
> > > > To run a freshly build netbeans you can invoke:
> > > >
> > > > ant -Ddebug.port=9009 tryme
> > > >
> > > > This will start the build IDE with a test userdir and it will wait on
> > > > tcp port 9009 for debugger connections.
> > > >
> > > > > 4) Just people fiddling around in debugger can lead to some fixes
> and
> > > > > contributions as we're observing system's behavior.
> > > >
> > > > Sure.
> > > >
> > > > I hope you stay and improve the situation.
> > > >
> > > > Matthias
> > > >
> > > > -
> > > > To unsubscribe, e-mail:
> dev-unsubscr...@netbeans.incubator.apache.org
> > > > For additional commands, e-mail: dev-help@netbeans.incubator.
> > apache.org
> > > >
> > > > For further information about the NetBeans mailing lists, visit:
> > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Re: Questions about contributing code and developing on top of Platform 9.0

[Peter Steele]

Is there a guide any where for building netbeans in the netbeans ide so you
can use netbeans to debug things?

On Fri, 15 Jun 2018, 19:48 Dmitry Avtonomov, 
wrote:

> Thanks Matthias and Gj!
>
> I've added the extra Debug line to confluence wiki:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Development+Environment
>
> On Fri, Jun 15, 2018 at 11:33 AM Matthias Bläsing <
> mblaes...@doppel-helix.eu>
> wrote:
>
> > Hi Dmitry,
> >
> > Am Freitag, den 15.06.2018, 11:02 -0700 schrieb Dmitry Avtonomov:
> > > Just wanted to point out that:
> > > 1) The Netbeans project is potentially loosing lots of people who would
> > > have liked to contribute, but can't find a way how.
> >
> > the insight is good, so you obvisually went through this and could
> > improve the documentation. That would help the project and you.
> >
> > Remember: Many current contributors are around for a long time, so they
> > now the places to look and the thinks to do.
> >
> > > 2) 10 minute turnaround time for fix-build-run-test cycle is too much.
> >
> > This will require some one to step up and look through the build where
> > the time is spend. But normally you don't need to rebuild the whole
> > IDE. You build once and if you need to modify a set of modules, you
> > just rebuild these.
> >
> > > 3) Most importantly I don't know how to start the whole thing in debug
> > > mode. Do I need to modify the ant script to make it wait for debugger
> > > connection?
> >
> > You can pass java options through the netbeans launcher via
> > "-J". This will run netbeans with debugging enabled:
> >
> > /bin/netbeans
> > -J-agentlib:jdwp=transport=dt_socket,suspend=y,server=y,address=9009
> >
> > To run a freshly build netbeans you can invoke:
> >
> > ant -Ddebug.port=9009 tryme
> >
> > This will start the build IDE with a test userdir and it will wait on
> > tcp port 9009 for debugger connections.
> >
> > > 4) Just people fiddling around in debugger can lead to some fixes and
> > > contributions as we're observing system's behavior.
> >
> > Sure.
> >
> > I hope you stay and improve the situation.
> >
> > Matthias
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>

Re: Microsoft buys GitHub

[Peter Steele]

Encouraging read

https://www.reddit.com/r/AMA/comments/8pc8mf/im_nat_friedman_future_ceo_of_github_ama/?limit=500



On Thu, 7 Jun 2018, 19:46 Stephen Parry,  wrote:

> Just my tuppence worth (being British) regarding Micro$oft being evil:
> companies do change. I remember when IBM was the byword for restrictive
> practice and vendor lock-in.  Nowadays they are a really positive force in
> the open source arena. They contribute a huge amount (too much if Xenix
> were to be believed) to open source development, use and popularity. You
> can run Linux as standard on a IBM supercomputer. 25 years ago, running a
> non-IBM OS on such would have been considered "crazy talk".
> Going the other way, Google, the company that pioneered "not being evil"?
> They have tarnished that more than a little.
> The industry is so full of wreckers and weasels it is easy to become
> cynical. If you want to see a consistent wrecker in the community, Oracle
> wins hands down, I agree. However, the  people who put MS where they are?
> Ironically that is Apple. They taught Microsoft the lesson, "if they are an
> enemy, sue them, if they are a friend sue them first" and "If in doubt, if
> any new technology appears,  patent it, stick your logo on it, and pretend
> like you invented it".
> I think we need to be a little more positive and the really positive
> success story of the last two decades is the fact that, no matter how hard
> everyone else tried too, only one player managed to dominate the Internet -
> us, the open source community. Linux, Apache, MySQL, Firefox, and a
> bazillion other projects mean it is possible to both have software that is
> diverse and open but that works and does not cost you internal organs,
> while people are still able to make a mostly adequate and mostly honest
> dollar, rupee or pound out of it all. That's a big thing.
> In other words, for the most part, we won. That is something to both
> celebrate and protect damn hard. Microsoft is just trying to hack out the
> biggest chunk they can of the new order, which is why they have the CEO
> they do now. That does mean though tgat we need to be vigilant. Let's watch
> and see, but be prepared - be friends and let them ride in the car;  just
> don't give them the keys.
> Regards to all
> Stephen
>
> On 7 June 2018 16:55:33 BST, Kirk Pepperdine  wrote:
> >What GitHub brings to the table are the review and collaboration tools.
> >If you don’t need them, then you don’t need GitHub.
> >
> >Kind regards,
> >Kirk
> >
> >> On Jun 7, 2018, at 4:23 PM, Geertjan Wielenga
> > wrote:
> >>
> >> We’re using GitHub as a convenience, thanks to GitBox. But there’s no
> >> requirement to use GitHub except that since it’s possible it’s
> >popular
> >> because everyone knows GitHub. But we could use whatever Apache
> >enables us
> >> to use.
> >>
> >> Gj
> >>
> >> On Thursday, June 7, 2018, Emilian Bold 
> >wrote:
> >>
> >>> In theory. In practice we never saw a patch being discussed on the
> >mailing
> >>> list.
> >>>
> >>> Without GitHub you cannot comment on PRs, you cannot +1. You cannot
> >create
> >>> a new PR.
> >>>
> >>> --emi
> >>>
> >>> ‐‐‐ Original Message ‐‐‐
> >>>
> >>> On 7 June 2018 3:45 PM, Mark Struberg 
> >wrote:
> >>>
>  To be honest I don't get why someone would require a github
> >account.
> 
>  Just clone our ASF git repo. Technically it makes no difference
> >where
> >>> from. Might be from ASF, github or even your neighbour,..
> 
>  The sha1 are everywhere the same anyway (if the clone is up2date).
> 
>  Then you do your changes, create a patch etc. And send a pull
> >request. I
> >>> personally even prefer creating the patch via git-format-patch and
> >then
> >>> attaching it to either JIRA or send it directly to the mailing list
> >for
> >>> review. That's how we always did work in the past and it still works
> >like a
> >>> charm!
> 
>  In many cases it's even way cleaner than via github (no spread
> >channels
> >>> etc).
> 
>  You could also just point to your repo (hosted on bitbucket,
> >>> sourceforge, your private server, whatever) and the maintainer could
> >>> git-fetch+merge from there. That's how GIT was intended to be used
> >even.
> 
>  LieGrue,
> 
>  strub
> 
> > Am 07.06.2018 um 09:20 schrieb Jan Lahoda lah...@gmail.com:
> >
> > Hi Emilian,
> >
> > On Thu, Jun 7, 2018 at 8:33 AM, Emilian Bold
> >>> emilian.b...@protonmail.ch
> >
> > wrote:
> >
> >> I think we need to plan a separate contribution workflow without
> >>> GitHub
> >>
> >> (see my other thread 'How to participate in Apache NetBeans
> >without a
> >>
> >> GitHub account?').
> >>
> >> Right now we are tied to GitHub and it's impossible to be
> >involved in
> >>
> >> anything without jumping onto GitHub.
> >
> > Not sure if (or why) it is impossible to be involved without
> >GitHub.
> >>> AFAIK
> >
> > anyone can 

Re: AW: (Git) Diff Window horizontal space rescue

[Peter Steele]

If there are configurable options to change it why do you care? You can
just keep the settings how you like it and you will be happy. From what I
read in the chain it sounds like this was a suggestion a while back.

On Thu, 10 May 2018, 15:17 Matthias Bläsing, 
wrote:

> Am Donnerstag, den 10.05.2018, 09:25 -0400 schrieb Emilian Bold:
> > Not sure why you have to be so adamant about this.
>
> Because you try to force your use-case down my throat. Yes I choose my
> hardware to get my work done and this worked good with netbeans. All I
> heard till now torpedes this. This is why I'm speaking out against it.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: NetBeans has rendering problems with GTK look and feel on Java 10

[Peter Steele]

The issue I had with GTK on java 10 on Ubuntu was that it had wierd
behaviour for hidpi screens. If I used the UI Scaling property to match the
os I would get images all scaled correctly but fonts would be twice the
size. If I set the UI Scaling property to 1 the font would now look nice
but the images would be far too small.

I guess GTK takes the font size from the OS which already takes scaling in
to consideration so it is out of sync with java when you ask it to
compensate.

On Tue, 8 May 2018, 16:53 Martin Weißhaupt, 
wrote:

> Oops, I didn't notice this.
>
> I hope this works better:
> https://imgur.com/a/VrLq4Rx
>
> The problem is not the font rendering but the gui components.
>
> Am 08.05.2018 um 17:28 schrieb Laszlo Kishalmi:
> > Well, Apache kindly removes the images from mails. So I just suspect
> > it is more like a font rendering issue.
> >
> > Somehow Java 10 reintroduced the fontconfig.Ubuntu.properties* under
> > $JAVA_HOME/lib
> >
> > That file is really old and comes from the pre-Ubuntu font ages.
> > Itmakes the IDE really ugly as forcing it to render not available fonts.
> >
> > Just get rid of that file and Netbeans will look good again on GTK.
> >
> >
> > On 05/08/2018 05:33 AM, Martin Weißhaupt wrote:
> >> I have noticed something strange when I tried the NetBeans 9 Beta. I
> >> wanted to create a ticket in Jira but noticed that NetBeans 9 was
> >> running with Java 10 which seems to produce rendering issues. So this
> >> is propably not a problem of NetBeans but the GTK look and feel.
> >>
> >> The first image shows how it should look like and the second shows
> >> multiple problems that exist with the GTK3 look and feel which seems
> >> to be used by Java 10.
> >>
> >> Is there anything that can be done by NetBeans to prevent this?
> >> Forcing Java 8 or using a different look and feel fixes the issue for
> >> me but this is only a workaround. This also happens with my own Swing
> >> apps so should I create a ticket for OpenJDK?
> >>
> >> I'm running Ubuntu 18.04 and the GTK Theme used does not seem to matter.
> >>
> >> NetBeans 8.2 running on Java 8 with the GTK2 Theme:
> >>
> >>
> >> NetBeans 9 running on Java 10 with parts of the GTK3 Theme:
> >>
> >> ​
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: AW: (Git) Diff Window horizontal space rescue

[Peter Steele]

+1 separate window

I'd like to also suggest having the separate window track selection events
in the windows that generated it so that you only have one window up. An
example of this would be the commit window, clicking of different files
would load the diff for that file and changing the selection would
automatically update the same window with the diff from the new file.

On Fri, 4 May 2018, 09:05 Christian Lenz,  wrote:

> As we see some discussion like, we want a separate Dialog and some doesn’t
> want it, we Need an Option for changing this. Because I’m also for using
> the separated window. So Default should be as it is, as a tab Maybe and
> with anoption, we can switch to a more lightweight (w/o the tab stuff
> inside etc.). So please don’t decide to do it only in one way. We have
> multiple situations for that. To fix the most for all, use an Option to let
> the user decide how to use it.
>
>
> Cheers
>
> Chris
>
> Von: cowwoc
> Gesendet: Donnerstag, 3. Mai 2018 17:53
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: AW: (Git) Diff Window horizontal space rescue
>
> I'd be okay with "reuse diff topcomponent for identical diff". It seems
> like a reasonable default seeing as opening the same source file in the
> editor reuses the same tab. It would be consistent.
>
> Gili
>
> On 2018-05-03 6:07 AM, Sven Reimers wrote:
> > Hi,
> >
> > idea for solving this via configuration:
> > - reuse diff topcomponent
> > - reuse diff topcomponent for identical diff
> >
> > I like the simple navigation between topcomponents, but having the same
> > diff open multiple times is annoying.
> >
> > Sven
> >
> > John McDonnell  schrieb am Do., 3. Mai 2018,
> > 08:18:
> >
> >> I'd be the same as you Emilian,  I often end up with multiple
> >> editor windows of the same diff, which is annoying. Maybe a separate
> >> dialog makes
> >> sense?
> >>
> >>
> >>
> >> Could this be a preference thing?   I.e. allow this as an editor
> component
> >> or as a separate dialog? or is that a lot of effort?
> >>
> >> John
> >>
> >>
> >>
> >> On 3 May 2018 at 03:14, cowwoc  wrote:
> >>
> >>> Multiple diffs, probably not. But I don't like IDEA-style separate
> >> dialog.
> >>> I like being able to treat the diff as just another editor tab so I can
> >>> casually move back and forth between it and the code.
> >>>
> >>> Gili
> >>>
> >>>
> >>> On 2018-05-02 9:25 PM, Emilian Bold wrote:
> >>>
>  Now that you mention it, there is something odd about the diff window
>  being another editor-like topcomponent.
> 
>  I sometimes find myself having the same diff open multiple times
>  (generally after I've excluded some file manually in the Git bottom
>  topcomponent).
> 
>  So, do people really need multiple diffs open at once? Because it's
>  starting to make sense having this as a separate dialog.
> 
>  --emi
> 
>  ‐‐‐ Original Message ‐‐‐
> 
>  On 2 May 2018 2:39 PM, Christian Lenz  wrote:
> 
>  As I compared it with intelliJ e.g. (only to see how intelliJ does it)
> > they open the diff window as a standalone window to remove everything
> >> which
> > is not needed. NetBeans only opens that diff for a file as a new tab.
> >> Sure
> > you can make it floatable by your own but it is not a file, so it
> >> could be
> > treated as a separate window which can be floatable via Option (not
> as
> > Default, because it could be disturbing some other users). So I like
> >> the
> > Approach to get more space. Maybe the drop downs can be placed close
> >> to the
> > Icons, in the same line. If this make sense. See my screenshot how
> >> WebStorm
> > handles this: https://ibb.co/jV9YW7 Only as an idea.
> >
> > It doesn’t Need the tab section and the other Icons. I added a secion
> > screenshot: https://ibb.co/bsLe4S Here you can see, what I mean. The
> > red section is not needed in my opinion. So we can remove it w/o
> >> having an
> > Option for this. And the blue section should be optional and
> >> redesigned as
> > Emilian said (textual/visual via DropDown e.g.)
> >
> > Cheers
> >
> > Chris
> >
> > Von: Emilian Bold
> >
> > Gesendet: Mittwoch, 2. Mai 2018 07:35
> >
> > An: dev@netbeans.incubator.apache.org
> >
> > Betreff: Re: (Git) Diff Window horizontal space rescue
> >
> > I wonder if it would be a good intermediate solution to just
> introduce
> >> a
> >> System property that disables the enhanced flag in
> >> DefaultDiffControllerProvider. Then users can just gain some more
> >> pixels by
> >> editing the .conf file.
> >>
> > Createdhttps://github.com/apache/incubator-netbeans/pull/531
> >
> > With both PRs I get to see 32 lines of code for the diff vs 28 lines
> of
> > code previously.
> >
> > This becomes even more 

Re: Time to branch for the release candidate?

[Peter Steele]

Just for my interest, which types of people can approve Pull Requests? As
we are now open source the community is deciding what's important by
providing the PR's but we have quite a few stacked up. It has previously
been mentioned in someone else request to get one approved that they should
just sent a message to dev but that's not really a process, it's just
hiding the fact there isn't really one.

Also who gets to flag an issue as 9.0, I guess in general what makes an
issue relevant to a particular version or not.

As we move to integrating the next code donation, there will now be two
parallel streams running. Bug fixing/enhancing the current code base and
integrating the new modules. What is the strategy here, branching seems
like best approach here but it looks like aren't doing this. What is the
plan to effectively manage the two streams?

On Thu, 26 Apr 2018, 18:56 Laszlo Kishalmi, 
wrote:

> Well,
>
> I'm trying to collect the remaining things to do for 9.0 release for a
> week now, from GitHub PR-s, JIRA and this mailing list. Regarding 9.0 in
> numbers are the following (none may be accurate, though):
>
> We have 31 open PR-s in GitHub (not necessary 9.0 related)
>
> We have 44 open issues with PR-s.
>
> We have 32 open issues marked for 9.0
>
> We also have 5 open issues with PR-s for 9.0
>
> The issues and PRs are not really aligned.
>
> Well this does not necessarily means that we should not branch for
> release. I just would like to say, we probably need to be more focused
> on what we are doing.
>
> I could promise to go over the open issues and the PR-s and close those
> which have merged PRs-.
>
> Also I feel the number of open PRs is quite high, though it might really
> mean that changes that we do not want to include into 9.0 are piling up
> (indicates the need of the release branch).
>
> Also those 5 issues with PR-s might just go into master in the following
> days and we could make the release branch after that.
>
> So If I would vote for release branch now it would be 0/-1 right now as
> we (or maybe just me) can't really see clearly on 9.0.
>
>
>
> On 04/17/2018 05:52 AM, Neil C Smith wrote:
> > On Tue, 17 Apr 2018 at 12:10 Jaroslav Tulach 
> > wrote:
> >
> >> Yeah, there are changes in the queue for the master branch that could be
> >> too destabilizing. To avoid something like that to negatively influence
> the
> >> 9.0 release, I'd suggest to create a branch release/9.0 and put only the
> >> safe fixes ready for 9.0 there. The wild development would continue in
> the
> >> master branch.
> >>
> > +1 to branching and that.  Longer term perhaps a more gitflow-like system
> > where PR's come into a develop branch too?
> >
> >   A question, though - I assume this will branch off master now, not from
> > the beta tag?  Given that in NetCAT we were testing the beta, I assume
> > there is nothing you'd consider "too destabilizing"  between then and
> now?
> >
> > Best wishes,
> >
> > Neil
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Time to branch for the release candidate?

[Peter Steele]

+1 to Chris / Neil

You shouldn't be developing in master, ideally

On Tue, 17 Apr 2018, 15:10 Christian Lenz,  wrote:

> Master shouldn’t be that one, where the wild development is going on.
> Master should be that one which is already live.
> In General, what gitflow does. Wild development is going on on the dev
> branch, for the next release. If whatever is finished, there is a release
> branch. After that, it will merged into master and created a tag.
>
> If this is not possible, then an other solution is that develop stays
> clean and always releasable. You only work on Feature branches. After the
> Feature is finished and ready to go, it will merged into develop. Someday
> you can create a release branch of develop.
>
>
> Cheer
>
> Chris
>
> Von: Neil C Smith
> Gesendet: Dienstag, 17. April 2018 14:53
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Time to branch for the release candidate?
>
> On Tue, 17 Apr 2018 at 12:10 Jaroslav Tulach 
> wrote:
>
> > Yeah, there are changes in the queue for the master branch that could be
> > too destabilizing. To avoid something like that to negatively influence
> the
> > 9.0 release, I'd suggest to create a branch release/9.0 and put only the
> > safe fixes ready for 9.0 there. The wild development would continue in
> the
> > master branch.
> >
>
> +1 to branching and that.  Longer term perhaps a more gitflow-like system
> where PR's come into a develop branch too?
>
>  A question, though - I assume this will branch off master now, not from
> the beta tag?  Given that in NetCAT we were testing the beta, I assume
> there is nothing you'd consider "too destabilizing"  between then and now?
>
> Best wishes,
>
> Neil
> --
> Neil C Smith
> Artist & Technologist
> www.neilcsmith.net
>
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>
>

Re: Modules included in 2nd donation.

[Peter Steele]

That averages 2.74 lines of code per file, must be a mistake there
somewhere 

On Fri, 13 Apr 2018, 13:13 Geertjan Wielenga, <
geertjan.wiele...@googlemail.com> wrote:

> Number of files in 2nd donation: 38338 -- after running this: find . -print
> | wc -l
>
> Number of lines of code in 2nd donation: 104965 -- after running this: find
> . -name '*' | xargs wc -l
>
> Thanks,
>
> Gj
>
> On Fri, Apr 13, 2018 at 2:03 PM, Antonio  wrote:
>
> > This is great news! Congratulations everybody! :-)
> >
> >
> > On 13/04/18 14:00, Geertjan Wielenga wrote:
> >
> >> Hi all,
> >>
> >> At the end of this page, look at 5e, i.e., that is the generic
> description
> >> of what the 2nd code donation consists of:
> >>
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
> >>
> >> I.e., the clusters are listed there.
> >>
> >> We now have the ZIP file ready that contains those clusters, which have
> >> been audited over the past months on the donation_review branch, i.e.,
> >> here
> >> you can see what's been removed/changed:
> >>
> >> https://hg.netbeans.org/releases/shortlog/donation_review
> >>
> >> Now that the ZIP file is ready, and we're working on the legal
> documents,
> >> the exact content of the 2nd code donation in terms of the NetBeans
> >> modules
> >> constituting the donation, are clearly defined.
> >>
> >> I.e., in short, be happy if you're interested in these areas of tooling:
> >> - Java EE
> >> - JavaScript
> >> - Groovy
> >> - PHP
> >>
> >> In detail, see the list of module names below that will be in the ZIP to
> >> be
> >> donated to Apache, i.e., the below defines the 2nd code donation:
> >>
> >> api.knockout
> >> api.web.webmodule
> >> cloud.amazon
> >> cloud.common
> >> cordova
> >> cordova.platforms
> >> cordova.platforms.android
> >> cordova.platforms.ios
> >> el.lexer
> >> extbrowser.chrome
> >> glassfish.common
> >> glassfish.eecommon
> >> glassfish.javaee
> >> glassfish.tooling
> >> groovy.antproject
> >> groovy.editor
> >> groovy.grails
> >> groovy.grailsproject
> >> groovy.gsp
> >> groovy.kit
> >> groovy.refactoring
> >> groovy.samples
> >> groovy.support
> >> hibernateweb
> >> html.angular
> >> html.knockout
> >> html.ojet
> >> hudson.php
> >> ide.ergonomics
> >> j2ee.ant
> >> j2ee.api.ejbmodule
> >> j2ee.clientproject
> >> j2ee.common
> >> j2ee.core
> >> j2ee.dd
> >> j2ee.dd.webservice
> >> j2ee.ddloaders
> >> j2ee.earproject
> >> j2ee.ejbcore
> >> j2ee.ejbjarproject
> >> j2ee.ejbrefactoring
> >> j2ee.ejbverification
> >> j2ee.genericserver
> >> j2ee.jboss4
> >> j2ee.kit
> >> j2ee.platform
> >> j2ee.sun.appsrv
> >> j2ee.sun.dd
> >> j2ee.sun.ddui
> >> j2ee.weblogic9
> >> j2eeapis
> >> j2eeserver
> >> javaee.api
> >> javaee.beanvalidation
> >> javaee.project
> >> javaee.resources
> >> javaee.specs.support
> >> javaee.wildfly
> >> javaee7.api
> >> javascript.bower
> >> javascript.cdnjs
> >> javascript.grunt
> >> javascript.gulp
> >> javascript.jstestdriver
> >> javascript.karma
> >> javascript.nodejs
> >> javascript.v8debug
> >> javascript.v8debug.ui
> >> javascript2.doc
> >> javascript2.editor
> >> javascript2.extdoc
> >> javascript2.extjs
> >> javascript2.jade
> >> javascript2.jquery
> >> javascript2.jsdoc
> >> javascript2.json
> >> javascript2.kit
> >> javascript2.knockout
> >> javascript2.lexer
> >> javascript2.model
> >> javascript2.nodejs
> >> javascript2.prototypejs
> >> javascript2.react
> >> javascript2.requirejs
> >> javascript2.sdoc
> >> javascript2.source.query
> >> javascript2.types
> >> jellytools.enterprise
> >> jsp.lexer
> >> ko4j.debugging
> >> languages.apacheconf
> >> languages.ini
> >> languages.neon
> >> lib.v8debug
> >> libs.amazon
> >> libs.commons_fileupload
> >> libs.elimpl
> >> libs.glassfish_logging
> >> libs.groovy
> >> libs.javacup
> >> libs.jstestdriver
> >> libs.jstl
> >> libs.nashorn
> >> libs.plist
> >> maven.groovy
> >> maven.j2ee
> >> maven.jaxws
> >> nbbuild
> >> netserver
> >> performance.ergonomics
> >> performance.javaee
> >> performance.scripting
> >> performance.web
> >> php.api.annotation
> >> php.api.documentation
> >> php.api.editor
> >> php.api.executable
> >> php.api.framework
> >> php.api.phpmodule
> >> php.api.templates
> >> php.api.testing
> >> php.apigen
> >> php.atoum
> >> php.code.analysis
> >> php.codeception
> >> php.composer
> >> php.dbgp
> >> php.doctrine2
> >> php.editor
> >> php.kit
> >> php.latte
> >> php.nette.tester
> >> php.nette2
> >> php.phing
> >> php.phpdoc
> >> php.phpdoc.documentation
> >> php.phpunit
> >> php.project
> >> php.refactoring
> >> php.samples
> >> php.smarty
> >> php.symfony
> >> php.symfony2
> >> php.twig
> >> php.zend
> >> php.zend2
> >> profiler.j2ee
> >> projectimport.eclipse.web
> >> selenium2.php
> >> selenium2.webclient
> >> selenium2.webclient.mocha
> >> selenium2.webclient.protractor
> >> servletjspapi
> >> spellchecker.bindings.php
> >> spring.webmvc
> >> tomcat5
> >> web.beans
> >> web.client.kit
> >> web.client.rest
> >> web.client.samples
> >> 

Re: Reporting errors

[Peter Steele]

Thanks all, I have done, will add them when I get back from work

On Fri, 23 Mar 2018, 08:58 Hermien Pellissier,  wrote:

> >
> > Anyone can create an account.
> >
>
> That is indeed correct. Click on Log In (top right), and on the login
> screen click Sign up. Anyone with an account can report new bugs.
>
> ~ Hermien
>

Reporting errors

[Peter Steele]

Hi

I am not part of NETCAT but I have started using netbeans 9 incubator beta
as my primary idea (the gradle plugin is no longer updated for 8.2 and it's
much more stable in 9).

I have had a few scenarios where ide errors have occured, I have saved the
stack traces for these and when they occured. What should I do with these
stack traces? Shall I email them to this group or send them some where
else?

Regards

Peter

Re: Usability study was: Think Java, not Electron! was: Apache HTML/Java UI

[Peter Steele]

On Thu, 15 Mar 2018, 20:08 Jaroslav Tulach, 
wrote:

> Hello Dmitry,
> thanks a lot for trying it out!
>
> 2018-03-15 2:50 GMT+01:00 Dmitry Avtonomov :
>
> > I find it incredible that Jaroslav is saying "... people aren't willing
> to
> > dedicate 10minutes of their personal time to try HTML/Java API in action
> > ...". How are they supposed to discover that?
> >
>
> To be fair, I also mentioned "... do you have recent version of NetBeans
> 9.0..." - e.g. the build time doesn't count.
>
> Let's try it out with time logging:
> >
> > 15:33 - Setting out to search for NetBeans on google, landed on
> > https://netbeans.org/, latest version 8.2
> > 15:34 - Search for "netbeans apache" (only did this because I knew what
> to
> > search for), landed on https://netbeans.apache.org/
> > 15:34 - Go to downloads (https://netbeans.apache.org/download/index.html
> )
> > - no binaries
> > 15:35 - I've already built v9 once, just deleting it took several minutes
> > 15:41 - Start clone `git clone https://github.com/apache/
> > incubator-netbeans.git` <
> https://github.com/apache/incubator-netbeans.git>
> > 15:44 - Clone + checkout done
> > 15:44 - `ant` (i had ant 1.10 installed, jdk - oracle 1.8, core i7
> 6700hq)
> > ...
> > compilation took 24 minutes 29 seconds
> > ...
> > `ant tryme`. Popup message:
> >
> > "Java features limited":
> > - install nb-javac library (highly recommended)
> > - run NetBeans on JDK 9 or later
> >
> > Click button to install nb-javac plugin.
> > Warnings about unsigned plugins.
> > Restart IDE.
> >
>
> Alas, this is the nb-javac licensing problem, that will be hard to mitigate
> anytime soon.
>
>
> > That's already quite some trouble that would stop 99.5% of people who
> > might have wanted to try it out.
> >
> >
> > Select: File -> New Project -> JavaFX -> Java HTML5 Application (again,
> > only because I knew from this thread where to click)
> > Read description: "Generates a WebView based DukeScript application".
> >
> > DukeScript? WebView based?... huh...
> >
>
> Geertjan also suggested to make the wizard more prominent. I noticed that
> Toni is currently thinking of some adjustments... personally I would split
> the wizard into few: "Java Desktop App", "Java iOS App", "Java Android
> App", "Java SPA App", etc. That would promote that NetBeans does support
> development/deployment to all important platforms of these days.
>
>
> > Click, wizard opens. Font is different, project type selector radio
> > buttons not aligned to text (image):
> >
> > Select "Visual HTML/Java example", project opens, immediately get warning
> > about project problems (Export-Package/Provate-Package contains packages
> > from dependencies) (image):
> >
> > It did run, but not that I understand the structure of 5 projects that
> got
> > created or how to use it. I can start "... Client for Web" project from
> the
> > IDE, but how do I build a runnable application? (image)
> >
>
> This is a great usability study. Toni has written a [getting started
> tutorial and a book](https://dukescript.com/documentation.html), but yes,
> it would be better if the system was usable without reading anything. I
> always advocate supporting "cluelessness" (and I hope I did support it when
> designing the HTML/Java API), but I never verified whether people building
> on top of it (e.g. Toni and his projects and wizards) do the same thing.
>
>
> > So yeah, I totally understand people googling for "Java Vaadin Electron
> > tutorial". As a matter of fact I was one of those people just 2 weeks
> ago,
> > even though I have built NB 9 previously.
> >
> > The samples I was able to run were running either in my default browser
> > (so it depends on system browser) or in, presumably, javafx webview
> > window(?), which lacked significantly in performance (the examples ran,
> > judging visually, at 10-20fps, while in the browser it was smooth, so I
> > couldn't tell the frame rate). I guess something like electron can be
> used,
> > but I have no idea how to achieve this.
> >
> > It needs:
> > - basic documentation
> >
>
> I am trying to make the Javadoc entertaining
> http://bits.netbeans.org/html+java/, but +1 - more is needed
>
> - geertjan style tutorials
> >
>
> +10, Geertjan, do you hear it?
>
> It needs examples of:
> > - how to feed large amounts of data from Java to JS running the view
> >
>
> Yes, this is often needed and I and Toni did some experiments with it. In
> fact we even proposed a paper about it to ManLang conference. The trick to
> improve throughput of Java -> JS communication would be:
>
> http://bits.netbeans.org/html+java/1.5/net/java/html/js/JavaScriptBody.html#wait4js()
>
> Btw. how much data you are talking about?
>
>
> > - how to communicate data back from the view into the java program
> >
>
> The low level API is here:
>
> http://bits.netbeans.org/html+java/1.5/net/java/html/js/package-summary.html
>
>
> > - how to build and run the application 

Re: AW: AW: Apache HTML/Java UI instead of ... Oracle will remove JavaFXfromOracle JDK

[Peter Steele]

Toni

Apologies, I didn't mean to offend. I'm just frustrated with a lot of the
conversations here. If I miss interpreted you "selling" dukescript to the
group I apologies. There are, what looks to be, so many intermingled
conversations here.

People are trying to solve a problem which doesn't currently need solving,
I'd rather people concentrate on the current product and make that better
rather than waste time working out how replace swing.


On 15 Mar 2018 16:17, <toni.ep...@eppleton.de> wrote:

Peter,

Did I say MVVM is a technology? Are we using MVVM with Swing? HTML/Java
uses it, so it would be new (and in my opinion) better way from what we've
got.

Running the IDE in a Browser means, at least in my interpretation, that the
program logic is executed in the browser. With HTML/Java the logic is
running in the JVM, only the view is rendered in HTML. That is the
difference.

Where did I propose to use DukeScript Presenters or DukeScript proprietary
stuff for any of this? I only mentioned it as an example to show it's
possible to use other renderers than JavaFX WebView.

I'm beginning to feel Jaroslav's pain.

--Toni

-Ursprüngliche Nachricht-
Von: Peter Steele <steeleh...@gmail.com>
Gesendet: Donnerstag, 15. März 2018 17:01
An: dev@netbeans.incubator.apache.org
Betreff: Re: AW: Apache HTML/Java UI instead of ... Oracle will remove
JavaFXfromOracle JDK

Toni

MVVM is an architecture, not a technology. You can use any technology to
implement it (there are even some that use swing).

If you want the whole ui rendered in HTML 5, you need something to parse
html, CSS and JavaScript. Which, despite what you say, needs a browser like
rendering engine. Which brings us back to running an ide in a browser. If
there was no javafx, swing or awt what would dukescript use as the
rendering engine?

Netbeans already has good support for web technologies, and already has the
ability to run those in the browser of your choice. I see no reason for
other people to add more including your dukescript, the product is open
source and there is no reason not to create a module if you want to promote
your own project

And lastly because Dukescript is a commercial product (if you want no ads,
nag screen) i would say we should not even consider it as a potential risk
long term alternative to swing. There are other free alternatives and these
should be considered as and when there is actually a need to do.

This conversation has gone on long enough, can we please re focus on
netbeans.

On 15 Mar 2018 14:59, <toni.ep...@eppleton.de> wrote:

> These things can happen in parallel. I for my part cannot help much
> with Python or Groovy features, but I can help with the POCs to
> improve NB UI and make it future proof. If for example we manage to
> replace JavaFX WebView with something better, contributors like Chris
> Lenz will be able to use more HTML5 features for writing their plugins
> and the performance of HTML-based plugins will improve.
>
> Maybe some of the Swing/JavaFX developers will also try it out and
> realize that developing with modern ui patterns like MVVM can
> dramatically speed up development, and lead to more testable and
> stable code while reducing the LOC. This would have the immediate
> effect of better code that needs less maintenance.
>
> But we can also offer them a way to still run their ( in my opinion
> horribly archaic  ) Swing code.
>
> As a side effect we could also replace the embedded Browser for
> debugging web applications with a real browser and make Web
> Development in NB even more attractive. Projects like the Oracle JET
> support in NetBeans, but also EE projects could directly benefit from
that.
>
> You're right these changes are driven by longer term goals, but they
> will also create huge short term improvements.
>
> And since there's a lot of confusion here between "web technologies"
> and "web applications": I for my part don't want to run NetBeans in a
Browser.
> I want NetBeans to remain a traditional Desktop application, which can
> use modern HTML5 UIs and is prepared for the end of Swing.
>
> --Toni
>
>
>
> -Ursprüngliche Nachricht-
> Von: Wade Chandler <wadechand...@apache.org>
> Gesendet: Donnerstag, 15. März 2018 14:40
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Apache HTML/Java UI instead of ... Oracle will remove
> JavaFXfromOracle JDK
>
>
> > On Mar 15, 2018, at 8:54 AM, Neil C Smith <neilcsm...@apache.org> wrote:
> >
> > Anyway, this whole thing is going a bit in circles. We need to look
> > at improving the POCs in NetBeans to be able to show where (and
> > where
> > not) this approach is viable and useful.
> >
>
> Agreed, but I think, so IMO, those just take us off the things that
> will actually have direct and i

Re: AW: Apache HTML/Java UI instead of ... Oracle will remove JavaFXfromOracle JDK

[Peter Steele]

Toni

MVVM is an architecture, not a technology. You can use any technology to
implement it (there are even some that use swing).

If you want the whole ui rendered in HTML 5, you need something to parse
html, CSS and JavaScript. Which, despite what you say, needs a browser like
rendering engine. Which brings us back to running an ide in a browser. If
there was no javafx, swing or awt what would dukescript use as the
rendering engine?

Netbeans already has good support for web technologies, and already has the
ability to run those in the browser of your choice. I see no reason for
other people to add more including your dukescript, the product is open
source and there is no reason not to create a module if you want to promote
your own project

And lastly because Dukescript is a commercial product (if you want no ads,
nag screen) i would say we should not even consider it as a potential risk
long term alternative to swing. There are other free alternatives and these
should be considered as and when there is actually a need to do.

This conversation has gone on long enough, can we please re focus on
netbeans.

On 15 Mar 2018 14:59,  wrote:

> These things can happen in parallel. I for my part cannot help much with
> Python or Groovy features, but I can help with the POCs to improve NB UI
> and make it future proof. If for example we manage to replace JavaFX
> WebView with something better, contributors like Chris Lenz will be able to
> use more HTML5 features for writing their plugins and the performance of
> HTML-based plugins will improve.
>
> Maybe some of the Swing/JavaFX developers will also try it out and realize
> that developing with modern ui patterns like MVVM can dramatically speed up
> development, and lead to more testable and stable code while reducing the
> LOC. This would have the immediate effect of better code that needs less
> maintenance.
>
> But we can also offer them a way to still run their ( in my opinion
> horribly archaic  ) Swing code.
>
> As a side effect we could also replace the embedded Browser for debugging
> web applications with a real browser and make Web Development in NB even
> more attractive. Projects like the Oracle JET support in NetBeans, but also
> EE projects could directly benefit from that.
>
> You're right these changes are driven by longer term goals, but they will
> also create huge short term improvements.
>
> And since there's a lot of confusion here between "web technologies" and
> "web applications": I for my part don't want to run NetBeans in a Browser.
> I want NetBeans to remain a traditional Desktop application, which can use
> modern HTML5 UIs and is prepared for the end of Swing.
>
> --Toni
>
>
>
> -Ursprüngliche Nachricht-
> Von: Wade Chandler 
> Gesendet: Donnerstag, 15. März 2018 14:40
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Apache HTML/Java UI instead of ... Oracle will remove
> JavaFXfromOracle JDK
>
>
> > On Mar 15, 2018, at 8:54 AM, Neil C Smith  wrote:
> >
> > Anyway, this whole thing is going a bit in circles. We need to look at
> > improving the POCs in NetBeans to be able to show where (and where
> > not) this approach is viable and useful.
> >
>
> Agreed, but I think, so IMO, those just take us off the things that will
> actually have direct and immediate impacts. We can work on NB just as it
> is, and work to fix the index lock issues, add new Java parsing, add better
> language and feature support for some things like Groovy and Python, and
> generally move ahead, even while fixing some issues in Swing/AWT, or bog
> down in all this talk of web UIs which starts to make a lot of work which
> in the end didn’t really move the needle because we’ll still have a desktop
> IDE, but a lot of time would have been spent to just get further behind.
>
> Wade
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: AW: AW: Apache HTML/Java UI instead of ... Oracle will remove JavaFXfromOracle JDK

[Peter Steele]

One of the biggest limitations is the fact everything is single threaded.
This isn't related to vaadin and gwt.

I have used vaadin and like it alot, and to build certain types of
applications it is a great candidate if you are used to java. I have also
used GWT alot and have extended it for areas which it doesn't cover.
(Vaadin uses GWT too)

Another js pet hate for me is the fact it is not OO based, people have
tried to put wrappers around us but they inevitably have issues because
they are wrappers.

Chrome has a good debugger but compared to debugging support from desktop
languages it is inferior

The language is too visual basic like for my taste, it's nice and easy to
use but if you want to do anything complicated you are in trouble. Thumbs
up for closure support, thumbs down for the complete over use of closures.

Btw these are only my opinions, you may disagree with everything i say and
that is ok. I am in the camp of "i will never use a web based ide" but i
have no issues building apps that are designed for the web and work well on
the web (like for thin clients). Forcing everything in to the browser is
not they way forward.


On 14 Mar 2018 10:26, "Christian Lenz" <christian.l...@gmx.net> wrote:

Peter,

can you tell me which limitations you mean? As I wrote in an other thread,
the limitations came from GWT. The Problem is that a Java developer doesn’t
want to write HTML, CSS and JS so they are looking for an alternative. GWT
or Vaadin or kotlin to js, I can’t understand that, but ok. So please don’t
compare GWT or Vaadin with native JS.


Cheers

Chris

Von: Peter Steele
Gesendet: Montag, 12. März 2018 17:50
An: dev@netbeans.incubator.apache.org
Betreff: Re: AW: Apache HTML/Java UI instead of ... Oracle will remove
JavaFXfromOracle JDK

Christian

I am sure electron is good, but my personal preference is to not use a web
ide. Javascript as a language has a lot of limitations. I have written gwt
code to export java to html and you are limited a lot in how you design
your apps.

On 12 Mar 2018 16:40, "Christian Lenz" <christian.l...@gmx.net> wrote:

> Have a look into electron apps. A lot of apps are written with this
> Framework like VS Code and I think this is a big Player and you can see,
> that it performs very well and it is performant as hell. Only to say one
of
> those apps.
>
>
> Cheers
>
> Chris
> Von: Peter Steele
> Gesendet: Montag, 12. März 2018 17:37
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX
> fromOracle JDK
>
> What about the eclipse RCP framework which uses swt? This would seem to be
> a much better solution than having a html front end.
>
> On 12 Mar 2018 16:25, "Neil C Smith" <neilcsm...@apache.org> wrote:
>
> > On Mon, 12 Mar 2018 at 15:59 Jaroslav Tulach <jaroslav.tul...@gmail.com>
> > wrote:
> >
> > > Forget about AWT, Swing and JavaFX - the future is HTML. In case you
> > still
> > > care about Java, then your future should be Apache HTML/Java API!
> > >
> >
> > Generally inclined to agree with you - definitely on forgetting JavaFX,
> and
> > probably on forgetting AWT/Swing (intrigued to see what actually happens
> > there).  I don't think HTML is the only game in town, but for a lot of
> > things it's probably the right way forward.
> >
> > But, if we start turning to Apache HTML/Java way, what does it run in?
> >
> > Out of interest, I was looking at an example project using Vaadin
running
> > inside Electron recently.  Have you tried this approach with HTML/Java?
> >
> > Best wishes,
> >
> > Neil
> > --
> > Neil C Smith
> > Artist & Technologist
> > www.neilcsmith.net
> >
> > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
> >
>
>

Re: AW: Apache HTML/Java UI instead of ... Oracle will remove JavaFX fromOracle JDK

[Peter Steele]

Christian

I am sure electron is good, but my personal preference is to not use a web
ide. Javascript as a language has a lot of limitations. I have written gwt
code to export java to html and you are limited a lot in how you design
your apps.

On 12 Mar 2018 16:40, "Christian Lenz" <christian.l...@gmx.net> wrote:

> Have a look into electron apps. A lot of apps are written with this
> Framework like VS Code and I think this is a big Player and you can see,
> that it performs very well and it is performant as hell. Only to say one of
> those apps.
>
>
> Cheers
>
> Chris
> Von: Peter Steele
> Gesendet: Montag, 12. März 2018 17:37
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX
> fromOracle JDK
>
> What about the eclipse RCP framework which uses swt? This would seem to be
> a much better solution than having a html front end.
>
> On 12 Mar 2018 16:25, "Neil C Smith" <neilcsm...@apache.org> wrote:
>
> > On Mon, 12 Mar 2018 at 15:59 Jaroslav Tulach <jaroslav.tul...@gmail.com>
> > wrote:
> >
> > > Forget about AWT, Swing and JavaFX - the future is HTML. In case you
> > still
> > > care about Java, then your future should be Apache HTML/Java API!
> > >
> >
> > Generally inclined to agree with you - definitely on forgetting JavaFX,
> and
> > probably on forgetting AWT/Swing (intrigued to see what actually happens
> > there).  I don't think HTML is the only game in town, but for a lot of
> > things it's probably the right way forward.
> >
> > But, if we start turning to Apache HTML/Java way, what does it run in?
> >
> > Out of interest, I was looking at an example project using Vaadin running
> > inside Electron recently.  Have you tried this approach with HTML/Java?
> >
> > Best wishes,
> >
> > Neil
> > --
> > Neil C Smith
> > Artist & Technologist
> > www.neilcsmith.net
> >
> > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
> >
>
>

Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX from Oracle JDK

[Peter Steele]

And there is Apache pivot, being Apache maybe we could get help in any
migration if that was the path chosen

On 12 Mar 2018 16:39, "Peter Steele" <steeleh...@gmail.com> wrote:

> To be clear (which i wasn't) i meant eclipse RCP is pretty popular, it
> uses swt as it's foundation. Could netbeans use swt as it's foundations too?
>
> On 12 Mar 2018 16:36, "Peter Steele" <steeleh...@gmail.com> wrote:
>
>> What about the eclipse RCP framework which uses swt? This would seem to
>> be a much better solution than having a html front end.
>>
>> On 12 Mar 2018 16:25, "Neil C Smith" <neilcsm...@apache.org> wrote:
>>
>>> On Mon, 12 Mar 2018 at 15:59 Jaroslav Tulach <jaroslav.tul...@gmail.com>
>>> wrote:
>>>
>>> > Forget about AWT, Swing and JavaFX - the future is HTML. In case you
>>> still
>>> > care about Java, then your future should be Apache HTML/Java API!
>>> >
>>>
>>> Generally inclined to agree with you - definitely on forgetting JavaFX,
>>> and
>>> probably on forgetting AWT/Swing (intrigued to see what actually happens
>>> there).  I don't think HTML is the only game in town, but for a lot of
>>> things it's probably the right way forward.
>>>
>>> But, if we start turning to Apache HTML/Java way, what does it run in?
>>>
>>> Out of interest, I was looking at an example project using Vaadin running
>>> inside Electron recently.  Have you tried this approach with HTML/Java?
>>>
>>> Best wishes,
>>>
>>> Neil
>>> --
>>> Neil C Smith
>>> Artist & Technologist
>>> www.neilcsmith.net
>>>
>>> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>>>
>>

Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX from Oracle JDK

[Peter Steele]

To be clear (which i wasn't) i meant eclipse RCP is pretty popular, it uses
swt as it's foundation. Could netbeans use swt as it's foundations too?

On 12 Mar 2018 16:36, "Peter Steele" <steeleh...@gmail.com> wrote:

> What about the eclipse RCP framework which uses swt? This would seem to be
> a much better solution than having a html front end.
>
> On 12 Mar 2018 16:25, "Neil C Smith" <neilcsm...@apache.org> wrote:
>
>> On Mon, 12 Mar 2018 at 15:59 Jaroslav Tulach <jaroslav.tul...@gmail.com>
>> wrote:
>>
>> > Forget about AWT, Swing and JavaFX - the future is HTML. In case you
>> still
>> > care about Java, then your future should be Apache HTML/Java API!
>> >
>>
>> Generally inclined to agree with you - definitely on forgetting JavaFX,
>> and
>> probably on forgetting AWT/Swing (intrigued to see what actually happens
>> there).  I don't think HTML is the only game in town, but for a lot of
>> things it's probably the right way forward.
>>
>> But, if we start turning to Apache HTML/Java way, what does it run in?
>>
>> Out of interest, I was looking at an example project using Vaadin running
>> inside Electron recently.  Have you tried this approach with HTML/Java?
>>
>> Best wishes,
>>
>> Neil
>> --
>> Neil C Smith
>> Artist & Technologist
>> www.neilcsmith.net
>>
>> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>>
>

Re: Apache HTML/Java UI instead of ... Oracle will remove JavaFX from Oracle JDK

[Peter Steele]

What about the eclipse RCP framework which uses swt? This would seem to be
a much better solution than having a html front end.

On 12 Mar 2018 16:25, "Neil C Smith"  wrote:

> On Mon, 12 Mar 2018 at 15:59 Jaroslav Tulach 
> wrote:
>
> > Forget about AWT, Swing and JavaFX - the future is HTML. In case you
> still
> > care about Java, then your future should be Apache HTML/Java API!
> >
>
> Generally inclined to agree with you - definitely on forgetting JavaFX, and
> probably on forgetting AWT/Swing (intrigued to see what actually happens
> there).  I don't think HTML is the only game in town, but for a lot of
> things it's probably the right way forward.
>
> But, if we start turning to Apache HTML/Java way, what does it run in?
>
> Out of interest, I was looking at an example project using Vaadin running
> inside Electron recently.  Have you tried this approach with HTML/Java?
>
> Best wishes,
>
> Neil
> --
> Neil C Smith
> Artist & Technologist
> www.neilcsmith.net
>
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>

Re: [VOTE] Apache NetBeans Logo (NETBEANS-145)

[Peter Steele]

Logo Id 2 : +1

On 1 Mar 2018 12:38, "Neil C Smith"  wrote:

> Logo ID 1 : +1
>
> Thanks,
>
> Neil
> --
> Neil C Smith
> Artist & Technologist
> www.neilcsmith.net
>
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>

Re: [ANN] Closing the NetBeans Logo Contest

[Peter Steele]

I take it it's only really between 1 and 2 as 3,4,5,6,7,8 is typography.

+1 to number 2 the colored SVG icon.

On 1 Mar 2018 07:36, "Eduard Karel de Jong"  wrote:

> Great!
> Another step forward for NetBeans.
>
> How do I cast a vote on [2}?
>
> It says 'cast ypur vote below,' howvere only the, as yet empty, result is
> shown. ( I am logged in)
>
> Cheers
> Eduard
>
> Antonio wrote:
>
>> Hi all,
>>
>> We now have nine proposals for the Apache NetBeans Logo (see [2]), the
>> most recent ones were received through the mailing list and through JIRA
>> during february, 2018.
>>
>> (Note this is about the icon, and not the typography.)
>>
>> If nobody opposes, I thought we could close NETBEANS-145 [1] and cast our
>> votes at [2] during 72h (so this should be closed by next sunday). Or
>> should we do this voting through the mailing list? Or both?
>>
>> Kind regards,
>> Antonio
>>
>> [1]
>> The contest
>> https://issues.apache.org/jira/browse/NETBEANS-145
>>
>> [2]
>> The votes
>> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+
>> NetBeans+Logo+Contest
>>
>>
>> On 26/02/18 12:57, Antonio wrote:
>>
>>> Hi all,
>>>
>>> We'll be closing the First Apache NetBeans Logo Contest [1] by March the
>>> 1st, to proceed with voting during March the 2nd, 3rd and 4th.
>>>
>>> If you would like to submit a proposal for the Apache NetBeans Logo
>>> please do so before March the 2nd. Note that we're focusing in the icon
>>> design (not typography at the moment).
>>>
>>> Refer to [1] for more details.
>>>
>>> Thanks and best of luck,
>>> Antonio
>>>
>>> [1]
>>> https://issues.apache.org/jira/browse/NETBEANS-145
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Merged to master (was Re: A NetBeans website proposal)

[Peter Steele]

Apologies if i may have missed it, but where in the
incubator-netbeans-website github repository is the delete/clean code in
build.gradle?

On 26 Feb 2018 11:52, "Neil C Smith" <neilcsm...@apache.org> wrote:

> On Mon, 26 Feb 2018 at 11:38 Peter Steele <steeleh...@gmail.com> wrote:
>
> > Although the easiest way is to actually move the clean code from the
> > scripts to gradle because gradle will then have a complete view on things
> >
>
> Everything is already gradle though!
>
> Best wishes,
>
> Neil
> --
> Neil C Smith
> Artist & Technologist
> www.neilcsmith.net
>
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>

Re: Merged to master (was Re: A NetBeans website proposal)

[Peter Steele]

It could be that because you have cleaned them outside of gradle, gradle
still thinks they are there and they haven't changed. The .gradle/caches
contains the cached data, you can tell gradle to refresh the dependencies
using ./gradle build --refresh-dependencies.

Although the easiest way is to actually move the clean code from the
scripts to gradle because gradle will then have a complete view on things

On 26 Feb 2018 11:07, "Neil C Smith" <neilcsm...@apache.org> wrote:

On Mon, 26 Feb 2018 at 10:57 Peter Steele <steeleh...@gmail.com> wrote:

> Gradle clean basically cleans the build directory used in java
compilation.
> In the task compileContentSass for instance you source from $contentDir
and
> write to $generatedAssetDir and these are not part of the java eco system.
>
> What you should do is create a new task which deletes all the directories
> you use and then do a clean.dependsOn(myCleanTask) so that is is run when
> clean is run.
>

Thanks!  Wade's build scripts do clean out all the generated files,
presumably because they're under /build anyway?  However, the sass plugin
still thinks it's up-to-date.  I'm assuming we need to link the sass plugin
into clean somehow, but the problem appears to be more than just deleting
the output directories, because they already are deleted?  Unless it's the
way that they're deleted that matters?

Best wishes,

Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net

Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org

Re: Merged to master (was Re: A NetBeans website proposal)

[Peter Steele]

Gradle clean basically cleans the build directory used in java compilation.
In the task compileContentSass for instance you source from $contentDir and
write to $generatedAssetDir and these are not part of the java eco system.

What you should do is create a new task which deletes all the directories
you use and then do a clean.dependsOn(myCleanTask) so that is is run when
clean is run.

Another thing is noticed was you have a task to stop and start tomcat,
there is a nice plugin on github (bmuschko/gradle-tomcat-plugin) which
allows you to redeploy core easily.

On 26 Feb 2018 10:42, "Neil C Smith"  wrote:

> On Mon, 26 Feb 2018 at 07:54 Antonio  wrote:
>
> > This has now been merged to master, we think we comply with ASF's
> > podling website requirements.
>
>
> Woot! :-)
>
> Some other enhancements & to-dos as seen in the thread & elsewhere:
> > ...
> > - The README at
> >
> > https://github.com/apache/incubator-netbeans-website/
> tree/master/netbeans.apache.org
> > explains how Wade's script work, how to run a preview site yourself, etc.
> >
> >
> Note (for others) that you might need to run these commands to get the
> correct output -
>
> ./gradlew clean
> ./gradlew preprocessContent --rerun-tasks
> ./gradlew bake
>
> One other useful task would be for someone who understands Gradle better
> than Antonio or I to have a look at why the build (or sass plugin in
> particular) is incorrectly caching even after cleaning.
>
> Best wishes,
>
> Neil
> --
> Neil C Smith
> Artist & Technologist
> www.neilcsmith.net
>
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>

Re: A NetBeans website proposal

[Peter Steele]

Looks good, what timelines do you have for the migration?

On 23 Feb 2018 12:11, "Josh Juneau"  wrote:

> Great work!
>
> Josh Juneau
> j
>
> > On Feb 23, 2018, at 1:19 AM, Antonio  wrote:
> >
> > Hi all,
> >
> > Wade, Tim, Neil, Jirka, Geertjan and I have been doing some experiments
> regarding the NetBeans website.
> >
> > As you probably know, the current NetBeans website comprises many
> different webs: we have "bits.netbeans.org" for APIs, "netbeans.org" for
> main content, "plugins.netbeans.org" for the Plugin Portal, "
> wiki.netbeans.org" for the wiki, and there're a few more subdomains.
> >
> > The current "netbeans.org" website is quite big. As you already know,
> Wade consolidated it in github's "apache/incubator-netbeans-website-cleanup"
> [1] repo, and added a Gradle build system that uses JBake to generate
> static content, where content is markdown/asciidoc/html with some
> additional files.
> >
> > As the migration is going to take time, and will require Oracle
> reviewing IP clearance for the content, we thought we could start a simpler
> "netbeans.apache.org" website that uses the same Wade's scripts. We then
> could add content gradually, as Oracle passes the IP clearance procedures.
> >
> > So we came out with a basic "multisite-test" _branch_ at Github's
> "incubator-netbeans-website" [2].
> >
> > The idea of this branch is to be able to consolidate different NetBeans
> subdomains as different directories (currently "bits.netbeans.org" and "
> netbeans.apache.org"), and create scripts for generating _static_ content
> for those different websites. Currently we have:
> >
> > - bits.netbeans.org
> >Currently builds the javadoc from sources.
> >
> > - netbeans.apache.org
> >- Has some basic content from current Confluence pages.
> >- As posted to the list in december we chose the Foundation 6
> framework as a, well, foundation, and Neil modified it with some proper
> SCSS structure [3] to fit our needs.
> >- We've also added the wiki pages. We may set up a different repo for
> these in the future, though.
> >- We've uploaded the result of this static site to
> https://netbeans.vieiro.net for you to see live (note: the "see this page
> in github" won't work until/if this branch merges to master).
> >
> > So to summarize, the objectives are:
> >
> > 1. Have all NetBeans websites in a single repo, with different folders
> for each. Maybe we want to share stuff among them in the future.
> > 2. Have some scripts to build static content for those websites.
> > 3. For web sites, make them comply with Apache's guidelines for web
> sites [4]
> >
> > If you think the idea is good enough then we may merge that branch into
> master and start migrating content, and/or creating different
> subdirectories for other websites (such as the plugin portal, for instance).
> >
> > So, please, say yes or no to keep this path of work. Some other ideas
> would also we welcome.
> >
> > Kind regards,
> > Antonio
> >
> >
> > [1]
> > https://github.com/apache/incubator-netbeans-website-cleanup
> >
> > [2]
> > https://github.com/apache/incubator-netbeans-website/tree/multisite-test
> >
> > We've used asciidoc, but Wade's script supports markdown and html as
> well. An example asciidoc file, as rendered by github, can be seen here:
> >
> > https://github.com/apache/incubator-netbeans-website/
> blob/multisite-test/netbeans.apache.org/src/content/
> download/index.asciidoc
> >
> > [3]
> > Neil's impressive SCSS organization is here:
> > https://github.com/apache/incubator-netbeans-website/
> tree/multisite-test/netbeans.apache.org/src/content/scss
> >
> > (note: some low quality scss stuff in there is my fault, not Neil's)
> >
> > [4]
> >
> > Apache Navigation Links Policy
> > https://www.apache.org/foundation/marks/pmcs#navigation
> >
> > Incubator Branding Guide
> > http://incubator.apache.org/guides/branding.html
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>

Re: www.netbeans.org not working

[Peter Steele]

Is there a reason why netbeans.org is not redirecting to netbeans.apache.org?
The new front page looks so much better than the existing one. It's just
missing the download to the 8.2 version


On 20 Feb 2018 15:11, "cowwoc"  wrote:

> I am seeing the same thing as Rik but here is the interesting bit...
> http://www.netbeans.org/ returns "The connection was connection"
> intermittently. If I hit the page 10 times in a row, sometimes it'll work
> one out of 10 times and sometimes it'll work nine out of 10 times. It keeps
> on alternating. Assuming there is a load balancer in front of this website
> it indicates that one of the nodes is down/bad.
>
> Once you successfully hit http://www.netbeans.org/ you are redirected to
> https://netbeans.org/ which always works, so simply reloading the page is
> not sufficient to reproduce this problem. You need to explicitly point
> paste http://www.netbeans.org/ in the address bar over and over again.
>
> PS: I'm using Chrome.
>
> Gili
>
> On 2018-02-20 9:46 AM, Geertjan Wielenga wrote:
>
>> That link works fine for me.
>>
>> Gj
>>
>> On Tue, Feb 20, 2018 at 3:44 PM, Riktam  wrote:
>>
>> Hallo Gili,
>>>
>>> it's still not working. In detail:
>>>
>>> a) https://netbeans.org/  OK(the final URL)
>>> b) https://www.netbeans.org/OK--> redirects to (a)
>>> c) http://netbeans.org/OK--> redirects to (a)
>>> d) http://www.netbeans.org/  Error(site not available)
>>>
>>> Maybe there is a problem to redirect protocol and path at the same time.
>>> My idea:
>>> redirect (d) --> (c), which in a second step redirect (c) --> (d)
>>>
>>> Who can arrange this ?
>>>
>>> Rik
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Wiki Edit Permissions

[Peter Steele]

Antonio

I beleive Vano wants wiki access not help on subscribing to the emails.

On 19 Jan 2018 08:38, "Antonio"  wrote:

Hi Vano,

Instructions on how to subscribe and unsubscribe from mailing lists (either
digests or not) are at https://cwiki.apache.org/confl
uence/display/NETBEANS/Mailing+lists

Mailing lists are managed by ezmlm, so all standard ezmlm commands (
http://untroubled.org/ezmlm/manual/) are supported.

Kind regards,
Antonio


On 19/01/18 09:06, Vano Beridze wrote:

> Hello,
>
> I've been using NetBeans since 2001, participated in several NetCAT events,
> contributed NetBeans welcome page translation in Georgian.
>
> I would like to contribute to the success of my favorite IDE.
>
> Please grant me the permission to edit Wiki (https://cwiki.apache.org/)
>
> Kind regards,
> Vano Beridze
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Java editor

[Peter Steele]

Is there anything anywhere saying why netbeans needs its own java compiler
(nb-javac) What features require this? I'm just surprised that netbeans was
ever built with a custom javac.

On 17 Dec 2017 11:03, "Geertjan Wielenga" 
wrote:

It's great and works for me and complies with the instructions we have
received re nb-javac, i.e., users must explicitly choose to install it and
agree to its licensing terms.

I have updated the Beta planning page to show the solution via the most
important dialog boxes:

https://cwiki.apache.org/confluence/display/NETBEANS/
Apache+NetBeans+9.0+Beta

But why the "highly recommended" in bold for nb-javac? I'd omit this, I
think it's up to the user and could be confusing.

Gj


On Sun, Dec 17, 2017 at 9:20 AM, Jan Lahoda  wrote:

> Hi,
>
> I've updated the jdk-javac branch (in the incubator-netbeans repository)
to
> run on JDK 8 even without nb-javac, and show a dialog (on the first run)
or
> a notification to install nb-javac (or run on JDK 9). My plan is to make a
> pass through the patch and send a pull request. But it would be helpful if
> someone would be willing to try the branch and provide feedback if needed.
>
> Thanks,
> Jan
>
>
> On Tue, Dec 12, 2017 at 7:20 PM, Jan Lahoda  wrote:
>
> > Hello,
> >
> > Today, we were talking with Jarda (jtulach) and Geertjan about what do
we
> > do with the Java support for the beta release.
> >
> > I think the proposal is roughly like this:
> > -the jdk-javac branch will be updated to
> > --allow the IDE to start on JDK 8, with javac based Java features
> disabled
> > (as best as we can, some exceptions might still happen, which we will
> > resolve as we find them).
> > --when running on JDK 8, there will be a notification/popup/dialog that
> > the Java features are disabled and that the IDE either needs to run on
> JDK
> > 9 or later, or the additional nb-javac module must be installed (the
> latter
> > being preferred, a "link" to perform the action included)
> > --when running on JDK 9, show (once?) a notification/popup that the
IDE's
> > behavior may improve by installing the additional nb-javac module.
> > -critical problems with the jdk-javac branch that we find should be
fixed
> > -a pull request to merge the jdk-javac branch into master will be sent
> >
> > (Jarda, please correct me if I missed something.)
> >
> > Are there any comments/objections/help offers to this proposal?
> >
> > I'd like to get to this later this week.
> >
> > Thanks,
> > Jan
> >
> >
>

Re: NetBeans 9 release date

[Peter Steele]

>Have you tried this plugin:
>plugins.netbeans.org/plugin/62424/darcula-laf-for-netbeans
>
>Would be great to have that as part of Apache NetBeans.

I use this, it's definitely the best look and feel that you can choose
from. But the font used is something that puts me off.


On 13 Oct 2017 10:18, "Geertjan Wielenga" <geertjan.wiele...@googlemail.com>
wrote:

On Fri, Oct 13, 2017 at 10:49 AM, Peter Steele <steeleh...@gmail.com> wrote:

> The Apache integration should be very prominent on the main page, it
should
> link to all the relevant Apache pages and should ask for volunteers etc.
> The Apache wiki is ok, but most people know about netbeans.org.
>
> In terms of my comments on "modern" and small things. I can't think of too
> many specific things off hand but what I would say is
>
> - I think a subset of the modules you can download should become core
> - the look at feel of netbeans puts me off a bit, I like the intellij dark
> look and feel (the font is much nicer to work with)
>

Have you tried this plugin:
plugins.netbeans.org/plugin/62424/darcula-laf-for-netbeans

Would be great to have that as part of Apache NetBeans.



> - having moved over to gradle I find the gradle integration in netbeans
not
> as good good as it's competitors. I think netbeans should divorce the
build
> system from the project choice so I could (as a basic example) choose
maven
> html5 or gradle html5 or maven basic java as a project choice.
>

I think the Gradle plugin should be a standard part of Apache NetBeans,
though that is a decision that Attila Kelemen, the creator of the plugin,
needs to make:

https://github.com/kelemen/netbeans-gradle-project



> - android integration is important to me, would be good to have some
> standard support.
>

Yes, https://bitbucket.org/nbandroid/nbandroid/wiki/Installation is another
one that could be part of Apache NetBeans, depending on the developer who
created it, so that everyone can get involved in getting it to the next
level.



>
> Btw I like the fact netbeans has moved to Apache, netbeans has a lot going
> for it that is better than other ides. Hopefully the Apache integration
> will help it move quickly to a better place.
>


Yup.



> Step one though is making it clearer to users of netbeans that the
> integration is happening and progress is being made to get a new release
> out.
>
>
Well, step one was making sure we would succeed in getting the code out of
Oracle into Apache. That has recently succeeded, only over the past month
or so, with at least half more still to come.

So, we really needed there to be code in the Apache NetBeans Git repo
before we could start actively thinking about moving NetBeans users over to
Apache NetBeans.

Gj

Re: NetBeans 9 release date

[Peter Steele]

As one of those "netbeans users" I would agree with both sides of what
people have been saying.

I joined this and the user mailing list to find out a bit more about what
is happening, I would love to contribute at some point but because of the
little time I can give currently I wanted to wait for the Apache migration
to stabilise first.

As a current neutral observer I would say a few things.

- netbeans.org is totally void of any Apache information, if you want more
people involved then communication should be updated there.

- without seeing the project updates here, it looks to be a "dead"  project
to the outside world so again, communication is key. To be fair netbeans.org
was never really good at this either.

- some sort of date or regularly updated checklist to show what needs to be
done before the next release is sorely being missed

- I am a big netbeans fan but moved over to the intellij community edition
because I didn't see oracle really investing much in making netbeans
"modern". I'd love to move back because I think as a community driven
project it can bridge the difference in feature gaps that exist. I far
prefer core netbeans as an ide to intellij or eclipse but it's the many
small things that are missing that makes it hard to beat those other
platforms in terms of every day usability.

I'm definitely looking forward to the integration in to Apache to be more
complete and for the project to continue moving in a positive way forwards.

On 13 Oct 2017 02:15, "Javier Ortiz"  wrote:

NetBeans is a huge scary code to most people including myself. Others just
don't feel or plain lack the skill/knowledge to help, or at least that's
what they feel.

Takes lots of time just to get used to the concepts, structure and
peculiarities of it.

As with many other open source tools I contribute to it comes down to need,
and effort needed.

If NetBeans was unique there would be more help since there were no other
options. But if your time is limited and not available or buggy on NetBeans
you just look around and there are other options.

Personally the open source project I got deeply evolved were unique in one
way or another or I created myself due to the same reason. That's why I
believe we don't see the other millions of users.

On Oct 12, 2017 6:26 PM, "Geertjan Wielenga" <
geertjan.wiele...@googlemail.com> wrote:

> Agree completely. And note that the NetBeans Governance is everyone here
on
> the mailing list, i.e., we decide together what should be in a release of
> NetBeans.
>
> There's something in Apache called the PMC (
> http://www.apache.org/dev/pmc.html#what-is-a-pmc) which in its simplest
> form is everyone who is a committer of an Apache project.
>
> Together, the committers, in discussion with the community at large,
> decides what each release should consist of, its roadmap, etc.
>
> Gj
>
> On Fri, Oct 13, 2017 at 1:21 AM, Antonio Vieiro 
> wrote:
>
> >
> > > El 12 oct 2017, a las 23:56, Emilian Bold 
> > escribió:
> > >
> > >> I think, though this is just my opinion, that people simply using
> > NetBeans
> > > and not giving anything back at all, is something we need to actively
> > move
> > > away from.
> > >
> > > As a counterpart to this, I don't know where the millions of NetBeans
> > users
> > > are.
> >
> > Those millions of users are waiting for you to ask them what they want.
> > It’s exactly the same Emilian did with yameter.com a few days after the
> > release:
> >
> > https://twitter.com/emilianbold/status/916775452714336256
> >
> > Should NetBeans support Apache Spark? Tomcat? The Go programming
> language?
> > R? Whatever? Just find a big pool of developers and ask them what to do
> > next, what they need, what they want. There’s no Oracle direction now
(or
> > if there’s then it’s just a direction, not all direction), nobody is
> > deciding what the future will be. So the NetBeans CEO (CEOs) must start
> > asking customers what they want.
> >
> > Hint: Apache has a big pool of developers.
> > Hint 2: Ernie’s vi emulator should be included in NetBeans 9.
> >
> > >
> > > On Fri, Oct 13, 2017 at 12:46 AM, Geertjan Wielenga <
> > > geertjan.wiele...@googlemail.com> wrote:
> > >
> > >>
> > >> We could then focus on releasing that -- i.e., the first release
would
> > >> consist of all the new JDK 9 features (Jigsaw, JShell, etc), together
> > with
> > >> then relicensed source code.
> >
> > There’re no Oracle deadlines now. So the NetBeans Governance (or
whatever
> > is called, why am I asking this? Not clear enough?) should set a roadmap
> > ASAP and start blogging about it in the net. Many users will appreciate
a
> > public roadmap. It gives us a sense of confidence on what to expect.
> >
> > And if this roadmap is decided by the NetBeans Governance _and_ the
> users,
> > the better.
> >
> > In fact a lack of roadmap can be seen as a competitive advantage, a
blank
> > sheet for users deciding the NetBeans