date:20180226




On 26/02/18 23:18, Neil C Smith wrote:

There is support for modals in general though which might work for this -
https://foundation.zurb.com/sites/docs/reveal.html


Ahh, that's the piece I was missing!

Maybe that path is worth exploring, Neil, instead of using this ColorBox 
plugin.


If you submit a more sensible PR I'll close the previous one!

Thanks,
Antonio



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: launcher for windows and building c file

2018-02-26 Thread Jan Lahoda

Hi Scott,

On Mon, Feb 26, 2018 at 11:54 PM, Scott Palmer  wrote:

> That is of course the “correct” way to do this. But I still wonder, why
> doesn’t NetBeans use the standard java launcher that is produced by
> javapackager?
>

I am not sure what exactly is the proposal - could you please share some
more details?

Looking at the current launchers, they seem to provide at least these
services:
-run the updater before or after the IDE/application is run, and possibly
restart the IDE/application after running the updater
-find a viable JDK (or read the path from etc/netbeans.conf)
-read extra options (including VM options) from etc/netbeans.conf
-detect userdir and cache dir locations
-for Windows, the launcher itself probably has an icon

Also, our builds are currently multiplatform (esp. Linux build can run on
Windows), and I think it would be good to keep this.

It we can maintain less platform-specific code, that would be nice, but I
think I'd need a more complete proposal on how to exactly do that without
loosing too many of the above features.

Jan


>
> (If it isn’t good enough, it should be. We should file an issue with the
> JDK if it is inadequate.)
>
> Scott
>
> > On Feb 25, 2018, at 10:00 PM, John Muczynski 
> wrote:
> >
> > Hi guys,
> >
> > At work we commit binaries (products of a build) into a binary repository
> > (Artifactory).
> >
> > In order to bundle them along with the jar files, a Java build then
> fetches
> > these hard-to-build pieces, made by the other build. They are specified
> > with a specific version number by using Maven coordinates.
> >
> > Kind regards,
> > Johnny
> >
> >
> >
> >> On Feb 25, 2018 12:51 AM, "Jan Lahoda"  wrote:
> >>
> >>> On Fri, Feb 23, 2018 at 5:09 PM, Eric Barboni 
> wrote:
> >>>
> >>> Hi Jan,
> >>>
> >>> I try to  make it concrete to me (as I am not sure to understand
> >>> completely the workflow).
> >>>
> >>> We may add a folder to nbbuild/buildnatives that contains all the make
> c
> >>> stuff to compile and release (linked to the source we need for example
> in
> >>> o.n.bootstrap and ide/native)
> >>>
> >>> Phase 1  (optional)
> >>> clone netbeans-incubator and execute the nbbuild/buildnatives
> >>>
> >>
> >> As Emilian noted, not sure if we need another directory. Maybe we could
> >> just have a few special targets in nbbuild/build.xml, that would
> delegate
> >> to appropriate Makefiles.
> >>
> >>
> >>> Phase 2
> >>> clone netbeans-incubator ,ant and use the released native
> >>>
> >>
> >> Yes.
> >>
> >> Overall, I think there are two important things:
> >> -folks building NetBeans shouldn't need to have a C/C++ compiler
> installed
> >> -NetBeans builds should be multi-platform (so that doing a build on
> Linux
> >> gets a binary that can run on Windows)
> >>
> >> There are only very few native components, so overall, this should be
> >> doable.
> >>
> >> Traditionally, we had the launchers checked-in directly in the
> repository,
> >> but that's not allowed in ASF. Hence the idea with releasing launchers
> >> separately. But if there's a better solution, I'm for it.
> >>
> >> Jan
> >>
> >>
> >>> Is it a "possible" workflow ?
> >>>
> >>> Regards
> >>> Eric
> >>>
> >>>
> >>> -Message d'origine-
> >>> De : Jan Lahoda [mailto:lah...@gmail.com]
> >>> Envoyé : vendredi 23 février 2018 13:10
> >>> À : dev@netbeans.incubator.apache.org
> >>> Objet : Re: launcher for windows and building c file
> >>>
>  On Fri, Feb 23, 2018 at 1:02 PM, Eric Barboni 
> wrote:
> 
>  Hi,
>  I know that Apache Openoffice use buildbot[1,2] with cygwin on it.
> 
>  We need ask Apache Infra for that. We also need a new repository.
> 
> >>>
> >>> We can definitely ask for a new repository, but do we need one? I.e.
> why
> >>> can't the sources be part of the main repo, and just produce a release
> >> as a
> >>> subset of that repo? (We already do that with the NB platform.)
> >>>
> >>> Jan
> >>>
> >>>
>  Regards
>  Eric
>  [1]
>  https://ci.apache.org/builders/aoo-w741x
>  [2]
>  https://ci.apache.org/buildbot.html
> 
>  -Message d'origine-
>  De : Jan Lahoda [mailto:lah...@gmail.com] Envoyé : vendredi 23
> février
>  2018 12:02 À : dev@netbeans.incubator.apache.org Objet : Re: launcher
>  for windows and building c file
> 
>  On Thu, Feb 22, 2018 at 4:59 PM, Eric Barboni 
> >> wrote:
> 
> > Hi,
> > I setup cygwin64 on windows 10. Thanks to your tips I update to
> > i686* tools chain.
> > I add to static link libgcc, libstdc++ and also add -static
> > lpthread to get it works.
> >
> > Artefact are huge now but I was able test some code to check for
> > jdk9 compatibility.
> >
> > The remaining issue are:
> > how  to generate the platform-launcher-9.0beta.zip and
> > launcher.zip, how to populate the external binaries repository with
> > those artefact
> >
> 
>  When I was thinking of this, I was thinking it would be i

Re: launcher for windows and building c file

2018-02-26 Thread Wade Chandler

On Feb 26, 2018 17:54, "Scott Palmer"  wrote:

But I still wonder, why doesn’t NetBeans use the standard java launcher
that is produced by javapackager?


NetBeans launcher has been around well before that. NB is in itself an
entire platform with a module management infrastructure. It supports
specific command line arguments etc. Java Packager may be able to do it
now, but someone would need to hash all that out.


(If it isn’t good enough, it should be. We should file an issue with the
JDK if it is inadequate.)


Probably true, but the devil is always in the details. The launchers for NB
work with the specifics of NetBeans, and do some special magic. So, the
java launcher class to do that magic would need to be provided, but too, NB
uses a pluggable JDK, and requires one be provided right now. I think if
you want to put together a PR for what that could look like with
javapackager, nobody will argue with a working solution.

Wade

Re: launcher for windows and building c file

2018-02-26 Thread Jan Lahoda

Hi Eric,

Not sure about the current status: should I try to look at how to update
the launchers? Do you have a working commandline for build?

Thanks,
 Jan

On Mon, Feb 26, 2018 at 5:27 PM, Eric Barboni  wrote:

> Hi,
>
>  Sorry I can answer all issue but make file is incomplete in this
> location[1] it need a mk file generated by c support in NetBeans. It the
> same for ide. It means we cannot build from 'scratch'. Kind of" chicken or
> egg" issue.
>
> And on the other hand, it is cool to have a c NetBeans project configured
> to quick test of new exe file.
>
> Eric
>
> [1]
> https://github.com/apache/incubator-netbeans/tree/
> master/o.n.bootstrap/launcher/windows/
>
> Eric BARBONI | Research Assistant | T : 33.561.55.6964
> ICS Team | IRIT | 118 route de Narbonne | 31062 Toulouse | France
> eric.barb...@irit.fr
>
> -Message d'origine-
> De : Emilian Bold [mailto:emilian.b...@protonmail.ch]
> Envoyé : samedi 24 février 2018 23:09
> À : dev@netbeans.incubator.apache.org
> Objet : RE: launcher for windows and building c file
>
> I would also like for us to have a 'from scratch' build possible,
> including native launchers.
>
> -1 on another repo just for this.
>
> I also don't believe we need new folders, we could have a ./build/ in
> o.n.bootstrap/launcher/windows/ just like we have for any other module.
>
> I see there's a Makefile in there and the sources. So, what's missing is
> perhaps a task in nbbuild/build.xml?
>
> Also agree that we can have launcher 'releases' with convenience binaries
> which we re-use in Platform releases, etc.
>
> --emi
>
> ‐‐‐ Original Message ‐‐‐
>
> On 23 February 2018 6:09 PM, Eric Barboni  wrote:
>
> > Hi Jan,
> >
> > I try to make it concrete to me (as I am not sure to understand
> completely the workflow).
> >
> > We may add a folder to nbbuild/buildnatives that contains all the make c
> stuff to compile and release (linked to the source we need for example in
> o.n.bootstrap and ide/native)
> >
> > Phase 1 (optional)
> >
> > clone netbeans-incubator and execute the nbbuild/buildnatives
> >
> > Phase 2
> >
> > clone netbeans-incubator ,ant and use the released native
> >
> > Is it a "possible" workflow ?
> >
> > Regards
> >
> > Eric
> >
> > -Message d'origine-
> >
> > De : Jan Lahoda \[mailto:lah...@gmail.com\]
> >
> > Envoyé : vendredi 23 février 2018 13:10
> >
> > À : dev@netbeans.incubator.apache.org
> >
> > Objet : Re: launcher for windows and building c file
> >
> > On Fri, Feb 23, 2018 at 1:02 PM, Eric Barboni sk...@apache.org wrote:
> >
> > > Hi,
> > >
> > > I know that Apache Openoffice use buildbot\[1,2\] with cygwin on it.
> > >
> > > We need ask Apache Infra for that. We also need a new repository.
> >
> > We can definitely ask for a new repository, but do we need one? I.e. why
> can't the sources be part of the main repo, and just produce a release as a
> subset of that repo? (We already do that with the NB platform.)
> >
> > Jan
> >
> > > Regards
> > >
> > > Eric
> > >
> > > \[1\]
> > >
> > > https://ci.apache.org/builders/aoo-w741x
> > >
> > > \[2\]
> > >
> > > https://ci.apache.org/buildbot.html
> > >
> > > -Message d'origine-
> > >
> > > De : Jan Lahoda \[mailto:lah...@gmail.com\] Envoyé : vendredi 23
> février
> > >
> > > 2018 12:02 À : dev@netbeans.incubator.apache.org Objet : Re: launcher
> > >
> > > for windows and building c file
> > >
> > > On Thu, Feb 22, 2018 at 4:59 PM, Eric Barboni sk...@apache.org wrote:
> > >
> > > > Hi,
> > > >
> > > > I setup cygwin64 on windows 10. Thanks to your tips I update to
> > > >
> > > > i686* tools chain.
> > > >
> > > > I add to static link libgcc, libstdc++ and also add -static
> > > >
> > > > lpthread to get it works.
> > > >
> > > > Artefact are huge now but I was able test some code to check for
> > > >
> > > > jdk9 compatibility.
> > > >
> > > > The remaining issue are:
> > > >
> > > > how to generate the platform-launcher-9.0beta.zip and
> > > >
> > > > launcher.zip, how to populate the external binaries repository with
> > > >
> > > > those artefact
> > >
> > > When I was thinking of this, I was thinking it would be in line with
> > >
> > > the Apache approach to create a separate release with just the
> > >
> > > launchers (this wouldn't quite require moving that ouside of the repo,
> > >
> > > it could be a task to simply pack a piece of the big repo). That would
> > >
> > > be sources and convenience binaries. Should be reasonably small. And
> > >
> > > when building the IDE, the convenience binaries for launchers would be
> > >
> > > downloaded and incorporated to the built IDE. I assume some work will
> > >
> > > be needed to setup such a release. It would be ideal if the
> > >
> > > convenience binaries would be uploaded to Maven. Upload to the legacy
> > >
> > > binary repository requires commit rights to hg.netbeans.org.
> > >
> > > Are there build machines at Apache that have mingw? It would be
> > >
> > > definitely good to have an "official" build.
> > >
> >

Re: launcher for windows and building c file

2018-02-26 Thread Scott Palmer

That is of course the “correct” way to do this. But I still wonder, why doesn’t 
NetBeans use the standard java launcher that is produced by javapackager?

(If it isn’t good enough, it should be. We should file an issue with the JDK if 
it is inadequate.)

Scott

> On Feb 25, 2018, at 10:00 PM, John Muczynski  wrote:
> 
> Hi guys,
> 
> At work we commit binaries (products of a build) into a binary repository
> (Artifactory).
> 
> In order to bundle them along with the jar files, a Java build then fetches
> these hard-to-build pieces, made by the other build. They are specified
> with a specific version number by using Maven coordinates.
> 
> Kind regards,
> Johnny
> 
> 
> 
>> On Feb 25, 2018 12:51 AM, "Jan Lahoda"  wrote:
>> 
>>> On Fri, Feb 23, 2018 at 5:09 PM, Eric Barboni  wrote:
>>> 
>>> Hi Jan,
>>> 
>>> I try to  make it concrete to me (as I am not sure to understand
>>> completely the workflow).
>>> 
>>> We may add a folder to nbbuild/buildnatives that contains all the make c
>>> stuff to compile and release (linked to the source we need for example in
>>> o.n.bootstrap and ide/native)
>>> 
>>> Phase 1  (optional)
>>> clone netbeans-incubator and execute the nbbuild/buildnatives
>>> 
>> 
>> As Emilian noted, not sure if we need another directory. Maybe we could
>> just have a few special targets in nbbuild/build.xml, that would delegate
>> to appropriate Makefiles.
>> 
>> 
>>> Phase 2
>>> clone netbeans-incubator ,ant and use the released native
>>> 
>> 
>> Yes.
>> 
>> Overall, I think there are two important things:
>> -folks building NetBeans shouldn't need to have a C/C++ compiler installed
>> -NetBeans builds should be multi-platform (so that doing a build on Linux
>> gets a binary that can run on Windows)
>> 
>> There are only very few native components, so overall, this should be
>> doable.
>> 
>> Traditionally, we had the launchers checked-in directly in the repository,
>> but that's not allowed in ASF. Hence the idea with releasing launchers
>> separately. But if there's a better solution, I'm for it.
>> 
>> Jan
>> 
>> 
>>> Is it a "possible" workflow ?
>>> 
>>> Regards
>>> Eric
>>> 
>>> 
>>> -Message d'origine-
>>> De : Jan Lahoda [mailto:lah...@gmail.com]
>>> Envoyé : vendredi 23 février 2018 13:10
>>> À : dev@netbeans.incubator.apache.org
>>> Objet : Re: launcher for windows and building c file
>>> 
 On Fri, Feb 23, 2018 at 1:02 PM, Eric Barboni  wrote:
 
 Hi,
 I know that Apache Openoffice use buildbot[1,2] with cygwin on it.
 
 We need ask Apache Infra for that. We also need a new repository.
 
>>> 
>>> We can definitely ask for a new repository, but do we need one? I.e. why
>>> can't the sources be part of the main repo, and just produce a release
>> as a
>>> subset of that repo? (We already do that with the NB platform.)
>>> 
>>> Jan
>>> 
>>> 
 Regards
 Eric
 [1]
 https://ci.apache.org/builders/aoo-w741x
 [2]
 https://ci.apache.org/buildbot.html
 
 -Message d'origine-
 De : Jan Lahoda [mailto:lah...@gmail.com] Envoyé : vendredi 23 février
 2018 12:02 À : dev@netbeans.incubator.apache.org Objet : Re: launcher
 for windows and building c file
 
 On Thu, Feb 22, 2018 at 4:59 PM, Eric Barboni 
>> wrote:
 
> Hi,
> I setup cygwin64 on windows 10. Thanks to your tips I update to
> i686* tools chain.
> I add to static link libgcc, libstdc++ and also add -static
> lpthread to get it works.
> 
> Artefact are huge now but I was able test some code to check for
> jdk9 compatibility.
> 
> The remaining issue are:
> how  to generate the platform-launcher-9.0beta.zip and
> launcher.zip, how to populate the external binaries repository with
> those artefact
> 
 
 When I was thinking of this, I was thinking it would be in line with
 the Apache approach to create a separate release with just the
 launchers (this wouldn't quite require moving that ouside of the repo,
 it could be a task to simply pack a piece of the big repo). That would
 be sources and convenience binaries. Should be reasonably small. And
 when building the IDE, the convenience binaries for launchers would be
 downloaded and incorporated to the built IDE. I assume some work will
 be needed to setup such a release. It would be ideal if the
 convenience binaries would be uploaded to Maven. Upload to the legacy
 binary repository requires commit rights to hg.netbeans.org.
 
 Are there build machines at Apache that have mingw? It would be
 definitely good to have an "official" build.
 
 Thanks,
 Jan
 
 
 
> 
> Regards
> Eric
> 
> 
> -Message d'origine-
> De : John Muczynski [mailto:johnst...@gmail.com] Envoyé : mercredi
> 21 février 2018 19:10 À : dev@netbeans.incubator.apache.org Objet :
>>> Re:
> launcher for windows and building c file
> 
> Hi Eric,
>

Re: incubator-netbeans-website, lightbox and issues


Hi Neil,

D'oh! I'm afraid I'm in the mood or something, I hate having things 
hanging on me. We have now


https://github.com/apache/incubator-netbeans-website/pull/9

with this colorbox stuff. Seems to we working fine
https://netbeans.vieiro.net/download/nb90/ (requires reload).

Anyway feel free to do enhancements or request modifications to the PR 
or discard it completely. I haven't tried with "retina" images yet.


I'm not very good at this Javascript stuff, so for sure there's room for 
improvement there. I just hope I didn't break anything.


Kind regards,
Antonio


On 26/02/18 23:18, Neil C Smith wrote:

Hi,

On Mon, 26 Feb 2018 at 20:54 Antonio  wrote:



http://www.jacklmoore.com/colorbox/

Which is MIT licensed. That could be a good choice. I'll try to
integrate it as transparently as possible, so as not to have to write
any HTML-specifics in the pages.



I was going to have a look at this, but can't for a few days so no problem
if you want to look into it.  I've used Colorbox in the past on a few
client sites, although am using Lightbox2 on my own for now.

However, the one thing I was going to look at first was what Foundation has
out of the box.  I think 5 had a Lightbox that hasn't made it into 6? -
https://foundation.zurb.com/sites/docs/v/5.5.3/components/clearing.html

There is support for modals in general though which might work for this -
https://foundation.zurb.com/sites/docs/reveal.html

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: incubator-netbeans-website, lightbox and issues

Hi,

On Mon, 26 Feb 2018 at 20:54 Antonio  wrote:

>
> http://www.jacklmoore.com/colorbox/
>
> Which is MIT licensed. That could be a good choice. I'll try to
> integrate it as transparently as possible, so as not to have to write
> any HTML-specifics in the pages.
>
>
I was going to have a look at this, but can't for a few days so no problem
if you want to look into it.  I've used Colorbox in the past on a few
client sites, although am using Lightbox2 on my own for now.

However, the one thing I was going to look at first was what Foundation has
out of the box.  I think 5 had a Lightbox that hasn't made it into 6? -
https://foundation.zurb.com/sites/docs/v/5.5.3/components/clearing.html

There is support for modals in general though which might work for this -
https://foundation.zurb.com/sites/docs/reveal.html

Best wishes,

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

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

Re: AW: incubator-netbeans-website, lightbox and issues

Hi,

So do I: I love removing unrequired dependencies everywhere!

But Foundation 6 requires jQuery, I'm afraid.

Cheers,
Antonio

On 26/02/18 21:57, Christian Lenz wrote:

I would like to reamove jQuery as good as possible, because it is not needed in
my eyes and my opinion anymore. The Colorbox is a plugin as I understand it
right for jQuery.

Cheers

Chris

Von: Antonio
Gesendet: Montag, 26. Februar 2018 21:54
An: dev@netbeans.incubator.apache.org
Betreff: Re: incubator-netbeans-website, lightbox and issues

On 26/02/18 21:41, Wade Chandler wrote:

On Feb 26, 2018, at 1:55 PM, Antonio wrote:

Hi all,

I was wondering if anybody is working on the "lightbox" support for the website
features page, I may have some spare time during the week and may tackle if, if nobody is
already working on that.

Not I.

I'll take it then. That'd be NETBEANS-429

https://issues.apache.org/jira/browse/NETBEANS-429?jql=project%20%3D%20NETBEANS%20AND%20component%20%3D%20website

By looking at incubator-netbeans-website-cleanup it seems netbeans.org
was using "colorbox"

https://github.com/apache/incubator-netbeans-website-cleanup/blob/master/src/content/features/index.html

http://www.jacklmoore.com/colorbox/

Which is MIT licensed. That could be a good choice. I'll try to
integrate it as transparently as possible, so as not to have to write
any HTML-specifics in the pages.

Also I thought we could open JIRA tickets for the web as well

There are some tickets already there for some bits of the site. Do you see
them? Those should use the same component to be accurate. But, yes I favor
issues in Jira to help track them, and give visibility into who is doing what;
IMO.

We're using the "website" component in JIRA.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20NETBEANS%20AND%20component%20%3D%20website

I'll try to close some of those as things evolve.

, and was wondering if we want git<->JIRA integration in the
"incubator-netbeans-website" repository, so JIRA issues are related with that
repository commits.

I don't know if it's possible to connect JIRA to two different repos, but I'd
be happy to either ask or make a request to INFRA, if you want.

Seems like it does, and it links them by the issue key which contains the
project code, so it should just work when a repository is added:
https://confluence.atlassian.com/adminjiraserver072/linking-a-bitbucket-or-github-repository-with-jira-828787604.html

Great news.

They may already be doing this automatically, but can’t hurt to ask.

I chatted with them a while back, it seems all NetBeans repos can be
integrated with JIRA, even different repos.

I just didn't know we had this already set up. These guys at infra do
really rock!

Cheers,
Antonio

Thanks,

Wade

===

Wade Chandler
e: cons...@wadechandler.com
t: @wadechandler
https://www.linkedin.com/in/wade-chandler

-
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

AW: incubator-netbeans-website, lightbox and issues

I would like to reamove jQuery as good as possible, because it is not needed in 
my eyes and my opinion anymore. The Colorbox is a plugin as I understand it 
right for jQuery.


Cheers

Chris

Von: Antonio
Gesendet: Montag, 26. Februar 2018 21:54
An: dev@netbeans.incubator.apache.org
Betreff: Re: incubator-netbeans-website, lightbox and issues



On 26/02/18 21:41, Wade Chandler wrote:
> 
>> On Feb 26, 2018, at 1:55 PM, Antonio  wrote:
>>
>> Hi all,
>>
>> I was wondering if anybody is working on the "lightbox" support for the 
>> website features page, I may have some spare time during the week and may 
>> tackle if, if nobody is already working on that.
> 
> Not I.

I'll take it then. That'd be NETBEANS-429

https://issues.apache.org/jira/browse/NETBEANS-429?jql=project%20%3D%20NETBEANS%20AND%20component%20%3D%20website

By looking at incubator-netbeans-website-cleanup it seems netbeans.org 
was using "colorbox"

https://github.com/apache/incubator-netbeans-website-cleanup/blob/master/src/content/features/index.html

http://www.jacklmoore.com/colorbox/

Which is MIT licensed. That could be a good choice. I'll try to 
integrate it as transparently as possible, so as not to have to write 
any HTML-specifics in the pages.


> 
>>
>> Also I thought we could open JIRA tickets for the web as well
> 
> There are some tickets already there for some bits of the site. Do you see 
> them? Those should use the same component to be accurate. But, yes I favor 
> issues in Jira to help track them, and give visibility into who is doing 
> what; IMO.

We're using the "website" component in JIRA.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20NETBEANS%20AND%20component%20%3D%20website

I'll try to close some of those as things evolve.

> 
>> , and was wondering if we want git<->JIRA integration in the 
>> "incubator-netbeans-website" repository, so JIRA issues are related with 
>> that repository commits.
>>
>> I don't know if it's possible to connect JIRA to two different repos, but 
>> I'd be happy to either ask or make a request to INFRA, if you want.
> 
> Seems like it does, and it links them by the issue key which contains the 
> project code, so it should just work when a repository is added:
> https://confluence.atlassian.com/adminjiraserver072/linking-a-bitbucket-or-github-repository-with-jira-828787604.html
>  
> 

Great news.

> 
> They may already be doing this automatically, but can’t hurt to ask.

I chatted with them a while back, it seems all NetBeans repos can be 
integrated with JIRA, even different repos.

I just didn't know we had this already set up. These guys at infra do 
really rock!

Cheers,
Antonio

> 
> Thanks,
> 
> Wade
> 
> 
> ===
> 
> Wade Chandler
> e: cons...@wadechandler.com
> t: @wadechandler
> https://www.linkedin.com/in/wade-chandler
> 
> 

-
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: incubator-netbeans-website, lightbox and issues

On 26/02/18 21:41, Wade Chandler wrote:

On Feb 26, 2018, at 1:55 PM, Antonio wrote:

Hi all,

I was wondering if anybody is working on the "lightbox" support for the website
features page, I may have some spare time during the week and may tackle if, if nobody is
already working on that.

Not I.

I'll take it then. That'd be NETBEANS-429

https://issues.apache.org/jira/browse/NETBEANS-429?jql=project%20%3D%20NETBEANS%20AND%20component%20%3D%20website

By looking at incubator-netbeans-website-cleanup it seems netbeans.org
was using "colorbox"

https://github.com/apache/incubator-netbeans-website-cleanup/blob/master/src/content/features/index.html

http://www.jacklmoore.com/colorbox/

Which is MIT licensed. That could be a good choice. I'll try to
integrate it as transparently as possible, so as not to have to write
any HTML-specifics in the pages.

Also I thought we could open JIRA tickets for the web as well

We're using the "website" component in JIRA.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20NETBEANS%20AND%20component%20%3D%20website

I'll try to close some of those as things evolve.

, and was wondering if we want git<->JIRA integration in the
"incubator-netbeans-website" repository, so JIRA issues are related with that
repository commits.

I don't know if it's possible to connect JIRA to two different repos, but I'd
be happy to either ask or make a request to INFRA, if you want.

Great news.

They may already be doing this automatically, but can’t hurt to ask.

I chatted with them a while back, it seems all NetBeans repos can be
integrated with JIRA, even different repos.

I just didn't know we had this already set up. These guys at infra do
really rock!

Cheers,
Antonio

Thanks,

Wade

===

Wade Chandler
e: cons...@wadechandler.com
t: @wadechandler
https://www.linkedin.com/in/wade-chandler

-
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

AW: Platform API: Context-sensitive keyboard accelerators

I figured out that problem too, but I don’t know whether this is window 
specific or not.
Sure I think you can add a shortcut to your Code, which is already taken. You 
got a warning after NetBeans started that says: „there is a duplicate“.
Maybe it overrides it or not, I don’t know atm. But if not and you created an 
Action, where you can Change the shortcut via KeyMap Options, you sometimes 
overrides existing ones (Which Shows you a warning or error that another one 
has the same etc.), but yes they should work context sensitve, and some are 
still working context sensitive, afaik.

I set ctrl + b to Show the git browser for branches etc. This shortcut only 
Woks, when I select a Project. If I’m in the Editor, it will set a bookmark or 
open the bookmark window. So there is smth like a context sensitive way to 
implement shortcuts but I don’t know the logic at all.

My 2 cents

Cheers

Chris

Von: Tim Boudreau
Gesendet: Montag, 26. Februar 2018 19:59
An: dev@netbeans.incubator.apache.org
Betreff: Re: Platform API: Context-sensitive keyboard accelerators

It's been a long time since I worked on the code involved, so my
recollection may be a little fuzzy, but this may help point you in a
direction or two:

There is a general problem that NetBeans supports, or at least used to
support, both single window pseudo-SDI mode and a multiple windows mode.
And keyboard shortcuts propagate down to the InputMap/KeyMap of the window
in question.  My recollection is that this was originally handled with an
AWTEventListener, because that was the one way to guarantee shortcuts
worked globally, no matter the windowing layout.  I *think* we migrated
that to something using InputMap/KeyMap around 2003 or so, but there may
still be workarounds to ensure things work globally.

What I'd suggest to try is an experiment - create a dialog with the dialogs
API and try binding a key you know is bound as a global shortcut.  Use
InputMap/KeyMap and attach it to, most likely, the root pane of the dialog.

If it works, then it's just a matter of implementing shortcuts in the right
places (make sure to call consume() on the event to stop it propagating
further).  If it doesn't, then some more fundamental work that's likely to
touch how key bindings work globally may be needed.

Also bear in mind that key bindings are different for different platforms -
on Mac OS, the alt key is a compose key for international characters and
cannot have shortcuts bound to it (ctrl is used instead), and some
keybindings are mapped to different keys for consistency with other Mac OS
apps (there's a syntax for defining keybindings in OS-neutral ways, for
declarative bindings).

HTH,

Tim

On Mon, Feb 26, 2018 at 9:11 AM, cowwoc  wrote:

> Hi,
>
> Netbeans has an extremely long (and getting longer) list of keyboard
> shortcuts. Part of the problem is that (for the most part) keyboard
> shortcuts are not context-sensitive nor are they able to be
> context-sensitive. I'll give you a simple example I raised a few years back:
>
> When the editor Find & Replace dialog is focused, we have "Replace" and
> "Replace All" buttons. It would be nice if we could map ALT+A to "Replace
> All" as many other applications do. Unfortunately, ALT+A is already mapped
> to the Refactor pulldown menu. The platform API does not allow mapping the
> same keyboard accelerator to different UI actions depending on the context.
> As a result, we end up with akward combinations like ALT+P for Replace All.
>
> Please see https://netbeans.org/bugzilla/show_bug.cgi?id=222843 for
> additional context.
>
> Is anyone else interested in this issue? Is anyone interested in working
> on it?
>
> Thank you,
> Gili
>
>
> -
> 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: incubator-netbeans-website, lightbox and issues

2018-02-26 Thread Wade Chandler


> On Feb 26, 2018, at 1:55 PM, Antonio  wrote:
> 
> Hi all,
> 
> I was wondering if anybody is working on the "lightbox" support for the 
> website features page, I may have some spare time during the week and may 
> tackle if, if nobody is already working on that.

Not I.

> 
> Also I thought we could open JIRA tickets for the web as well

There are some tickets already there for some bits of the site. Do you see 
them? Those should use the same component to be accurate. But, yes I favor 
issues in Jira to help track them, and give visibility into who is doing what; 
IMO.

> , and was wondering if we want git<->JIRA integration in the 
> "incubator-netbeans-website" repository, so JIRA issues are related with that 
> repository commits.
> 
> I don't know if it's possible to connect JIRA to two different repos, but I'd 
> be happy to either ask or make a request to INFRA, if you want.

Seems like it does, and it links them by the issue key which contains the 
project code, so it should just work when a repository is added:
https://confluence.atlassian.com/adminjiraserver072/linking-a-bitbucket-or-github-repository-with-jira-828787604.html
 


They may already be doing this automatically, but can’t hurt to ask.

Thanks,

Wade


===

Wade Chandler
e: cons...@wadechandler.com
t: @wadechandler
https://www.linkedin.com/in/wade-chandler

AW: incubator-netbeans-website, lightbox and issues

What exactly do you mean with lightbox for the Features page?
Please keep in mind, that all pages, should work mobile friendly too BUT only 
that they should looking good to navigate and not to zoom etc.

Please be Aware of this.


Cheers

Chris
Von: Antonio
Gesendet: Montag, 26. Februar 2018 19:56
An: dev@netbeans.incubator.apache.org
Betreff: incubator-netbeans-website, lightbox and issues

Hi all,

I was wondering if anybody is working on the "lightbox" support for the 
website features page, I may have some spare time during the week and 
may tackle if, if nobody is already working on that.

Also I thought we could open JIRA tickets for the web as well, and was 
wondering if we want git<->JIRA integration in the 
"incubator-netbeans-website" repository, so JIRA issues are related with 
that repository commits.

I don't know if it's possible to connect JIRA to two different repos, 
but I'd be happy to either ask or make a request to INFRA, if you want.

Thanks,
Antonio

-
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: Platform API: Context-sensitive keyboard accelerators

2018-02-26 Thread Tim Boudreau

It's been a long time since I worked on the code involved, so my
recollection may be a little fuzzy, but this may help point you in a
direction or two:

There is a general problem that NetBeans supports, or at least used to
support, both single window pseudo-SDI mode and a multiple windows mode.
And keyboard shortcuts propagate down to the InputMap/KeyMap of the window
in question.  My recollection is that this was originally handled with an
AWTEventListener, because that was the one way to guarantee shortcuts
worked globally, no matter the windowing layout.  I *think* we migrated
that to something using InputMap/KeyMap around 2003 or so, but there may
still be workarounds to ensure things work globally.

What I'd suggest to try is an experiment - create a dialog with the dialogs
API and try binding a key you know is bound as a global shortcut.  Use
InputMap/KeyMap and attach it to, most likely, the root pane of the dialog.

If it works, then it's just a matter of implementing shortcuts in the right
places (make sure to call consume() on the event to stop it propagating
further).  If it doesn't, then some more fundamental work that's likely to
touch how key bindings work globally may be needed.

Also bear in mind that key bindings are different for different platforms -
on Mac OS, the alt key is a compose key for international characters and
cannot have shortcuts bound to it (ctrl is used instead), and some
keybindings are mapped to different keys for consistency with other Mac OS
apps (there's a syntax for defining keybindings in OS-neutral ways, for
declarative bindings).

HTH,

Tim

On Mon, Feb 26, 2018 at 9:11 AM, cowwoc  wrote:

> Hi,
>
> Netbeans has an extremely long (and getting longer) list of keyboard
> shortcuts. Part of the problem is that (for the most part) keyboard
> shortcuts are not context-sensitive nor are they able to be
> context-sensitive. I'll give you a simple example I raised a few years back:
>
> When the editor Find & Replace dialog is focused, we have "Replace" and
> "Replace All" buttons. It would be nice if we could map ALT+A to "Replace
> All" as many other applications do. Unfortunately, ALT+A is already mapped
> to the Refactor pulldown menu. The platform API does not allow mapping the
> same keyboard accelerator to different UI actions depending on the context.
> As a result, we end up with akward combinations like ALT+P for Replace All.
>
> Please see https://netbeans.org/bugzilla/show_bug.cgi?id=222843 for
> additional context.
>
> Is anyone else interested in this issue? Is anyone interested in working
> on it?
>
> Thank you,
> Gili
>
>
> -
> 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

incubator-netbeans-website, lightbox and issues


Hi all,

I was wondering if anybody is working on the "lightbox" support for the 
website features page, I may have some spare time during the week and 
may tackle if, if nobody is already working on that.


Also I thought we could open JIRA tickets for the web as well, and was 
wondering if we want git<->JIRA integration in the 
"incubator-netbeans-website" repository, so JIRA issues are related with 
that repository commits.


I don't know if it's possible to connect JIRA to two different repos, 
but I'd be happy to either ask or make a request to INFRA, if you want.


Thanks,
Antonio

-
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: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))

2018-02-26 Thread Eduard

Indeed, the icon without typgraphy should be the item to vote upon this 
time.
The next discussion and a subsequent vote should be on the elements that 
we want to present in the typography, for instance:

-the word "apache"
-the feather
-a 'badge' with "IDE"  (with a possible alternate badge for the 
framework, like "AFW".
An other question is if the words "Net" and "Beans" should be with 
distinct typography.


Cheers
Eduard



Antonio wrote:

I'd say the icon without the typography.

Cheers,
Antonio

On 26/02/18 12:16, Neil C Smith wrote:

On Mon, 26 Feb 2018 at 11:06 Antonio  wrote:


To end up the logo discussion once and for all I propose:

- Announcing closing the contest within a few days.
- Announce a voting in the mailing list, as per the Apache way.



Sounds good!

Can we also clarify what we mean by logo though?  Are we at this stage
literally looking for the replacement for the cube icon, without any 
text /

typography?

Because currently the blue logo has 6 or 8 votes depending on what we 
mean.


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







-
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: First draft of netbeans quick outline plugin

let me think and thanks Chris

From: Christian Lenz 
Sent: Monday, February 26, 2018 5:56 PM
To: dev@netbeans.incubator.apache.org
Subject: AW: First draft of netbeans quick outline plugin

Hey Peter,

I wanted to comment, but smth with Twitter and/or fb is not working. Anyway, I 
do it here:

➢ The tree (AST) view is needed, because it shows the hierachical view and the 
association of the code. IntelliJ does the same, the navigator in NetBeans too. 
It represents the Abstract Syntax Tree, which is a tree. If you show it like 
this, there is no association between vars and/or functions and whatever, as 
you can see your comparsion of your plugin and the result from Eclipse.

➢ For me, I would like to see the same information from the navigator for 
example. If I have a filter function, there is nothing wrong with a tree and it 
will not hurting the eyes. The only difference between your plugin and the 
navigator, should be, that this is a lightweight dialog and with a filter 
functionality.

Cheers

Chris

Von: Peter Cheung
Gesendet: Montag, 26. Februar 2018 10:06
An: d...@platform.netbeans.org
Cc: dev@netbeans.incubator.apache.org
Betreff: First draft of netbeans quick outline plugin

Welcome to NetBeans
netbeans.org
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 
2018, Oracle Corporation and/or its affiliates. Sponsored by

First draft of netbeans quick outline plugin

http://peter.quantr.hk/2018/02/first-draft-of-netbeans-quick-outline-plugin/

RE: launcher for windows and building c file

2018-02-26 Thread Eric Barboni

Hi, 

 Sorry I can answer all issue but make file is incomplete in this location[1] 
it need a mk file generated by c support in NetBeans. It the same for ide. It 
means we cannot build from 'scratch'. Kind of" chicken or egg" issue.

And on the other hand, it is cool to have a c NetBeans project configured to 
quick test of new exe file.

Eric

[1]
https://github.com/apache/incubator-netbeans/tree/master/o.n.bootstrap/launcher/windows/

Eric BARBONI | Research Assistant | T : 33.561.55.6964
ICS Team | IRIT | 118 route de Narbonne | 31062 Toulouse | France
eric.barb...@irit.fr

-Message d'origine-
De : Emilian Bold [mailto:emilian.b...@protonmail.ch] 
Envoyé : samedi 24 février 2018 23:09
À : dev@netbeans.incubator.apache.org
Objet : RE: launcher for windows and building c file

I would also like for us to have a 'from scratch' build possible, including 
native launchers.

-1 on another repo just for this.

I also don't believe we need new folders, we could have a ./build/ in  
o.n.bootstrap/launcher/windows/ just like we have for any other module.

I see there's a Makefile in there and the sources. So, what's missing is 
perhaps a task in nbbuild/build.xml?

Also agree that we can have launcher 'releases' with convenience binaries which 
we re-use in Platform releases, etc.

--emi

‐‐‐ Original Message ‐‐‐

On 23 February 2018 6:09 PM, Eric Barboni  wrote:

> Hi Jan,
> 
> I try to make it concrete to me (as I am not sure to understand completely 
> the workflow).
> 
> We may add a folder to nbbuild/buildnatives that contains all the make c 
> stuff to compile and release (linked to the source we need for example in 
> o.n.bootstrap and ide/native)
> 
> Phase 1 (optional)
> 
> clone netbeans-incubator and execute the nbbuild/buildnatives
> 
> Phase 2
> 
> clone netbeans-incubator ,ant and use the released native
> 
> Is it a "possible" workflow ?
> 
> Regards
> 
> Eric
> 
> -Message d'origine-
> 
> De : Jan Lahoda \[mailto:lah...@gmail.com\]
> 
> Envoyé : vendredi 23 février 2018 13:10
> 
> À : dev@netbeans.incubator.apache.org
> 
> Objet : Re: launcher for windows and building c file
> 
> On Fri, Feb 23, 2018 at 1:02 PM, Eric Barboni sk...@apache.org wrote:
> 
> > Hi,
> > 
> > I know that Apache Openoffice use buildbot\[1,2\] with cygwin on it.
> > 
> > We need ask Apache Infra for that. We also need a new repository.
> 
> We can definitely ask for a new repository, but do we need one? I.e. why 
> can't the sources be part of the main repo, and just produce a release as a 
> subset of that repo? (We already do that with the NB platform.)
> 
> Jan
> 
> > Regards
> > 
> > Eric
> > 
> > \[1\]
> > 
> > https://ci.apache.org/builders/aoo-w741x
> > 
> > \[2\]
> > 
> > https://ci.apache.org/buildbot.html
> > 
> > -Message d'origine-
> > 
> > De : Jan Lahoda \[mailto:lah...@gmail.com\] Envoyé : vendredi 23 février
> > 
> > 2018 12:02 À : dev@netbeans.incubator.apache.org Objet : Re: launcher
> > 
> > for windows and building c file
> > 
> > On Thu, Feb 22, 2018 at 4:59 PM, Eric Barboni sk...@apache.org wrote:
> > 
> > > Hi,
> > > 
> > > I setup cygwin64 on windows 10. Thanks to your tips I update to
> > > 
> > > i686* tools chain.
> > > 
> > > I add to static link libgcc, libstdc++ and also add -static
> > > 
> > > lpthread to get it works.
> > > 
> > > Artefact are huge now but I was able test some code to check for
> > > 
> > > jdk9 compatibility.
> > > 
> > > The remaining issue are:
> > > 
> > > how to generate the platform-launcher-9.0beta.zip and
> > > 
> > > launcher.zip, how to populate the external binaries repository with
> > > 
> > > those artefact
> > 
> > When I was thinking of this, I was thinking it would be in line with
> > 
> > the Apache approach to create a separate release with just the
> > 
> > launchers (this wouldn't quite require moving that ouside of the repo,
> > 
> > it could be a task to simply pack a piece of the big repo). That would
> > 
> > be sources and convenience binaries. Should be reasonably small. And
> > 
> > when building the IDE, the convenience binaries for launchers would be
> > 
> > downloaded and incorporated to the built IDE. I assume some work will
> > 
> > be needed to setup such a release. It would be ideal if the
> > 
> > convenience binaries would be uploaded to Maven. Upload to the legacy
> > 
> > binary repository requires commit rights to hg.netbeans.org.
> > 
> > Are there build machines at Apache that have mingw? It would be
> > 
> > definitely good to have an "official" build.
> > 
> > Thanks,
> > 
> > Jan
> > 
> > > Regards
> > > 
> > > Eric
> > > 
> > > -Message d'origine-
> > > 
> > > De : John Muczynski \[mailto:johnst...@gmail.com\] Envoyé : mercredi
> > > 
> > > 21 février 2018 19:10 À : dev@netbeans.incubator.apache.org Objet : Re:
> > > 
> > > launcher for windows and building c file
> > > 
> > > Hi Eric,
> > > 
> > > These are excellent issues to unearth.
> > > 
> > > I like the idea of creating a setup to b

Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))

2018-02-26 Thread Eduard Karel de Jong

Indeed, the icon without typgraphy should be the item to vote upon this 
time.
The next discussion and a subsequent vote should be on the elements that 
we want to present in the typography, for instance:

-the word "apache"
-the feather
-a 'badge' with "IDE"  (with a possible alternate badge for the 
framework, like "AFW".
An other question is if the words "Net" and "Beans" should be with 
distinct typography.


Cheers
Eduard



Antonio wrote:

I'd say the icon without the typography.

Cheers,
Antonio

On 26/02/18 12:16, Neil C Smith wrote:

On Mon, 26 Feb 2018 at 11:06 Antonio  wrote:


To end up the logo discussion once and for all I propose:

- Announcing closing the contest within a few days.
- Announce a voting in the mailing list, as per the Apache way.



Sounds good!

Can we also clarify what we mean by logo though?  Are we at this stage
literally looking for the replacement for the cube icon, without any 
text /

typography?

Because currently the blue logo has 6 or 8 votes depending on what we 
mean.


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







-
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: openide annotation processors and StandardLocation.SOURCE_PATH

2018-02-26 Thread Basin Ilya

Hi Neil.


On 26.02.2018 16:27, Neil C Smith wrote:
> :-)  But, do you have to use the Eclipse compiler?

There's no easy way to switch to another compiler in Eclipse.


> I was looking at the bundle processor the other week when I needed to write
> my own processor using SOURCE_PATH.   In this case, is that fix really
> trivial?  Won't it miss merging pre-existing entries?

Perhaps there's another way to access source files. Not sure whether 
CLASS_OUTPUT gets populated with resources before the processor is called.


-
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

Platform API: Context-sensitive keyboard accelerators

2018-02-26 Thread cowwoc


Hi,

Netbeans has an extremely long (and getting longer) list of keyboard 
shortcuts. Part of the problem is that (for the most part) keyboard 
shortcuts are not context-sensitive nor are they able to be 
context-sensitive. I'll give you a simple example I raised a few years back:


When the editor Find & Replace dialog is focused, we have "Replace" and 
"Replace All" buttons. It would be nice if we could map ALT+A to 
"Replace All" as many other applications do. Unfortunately, ALT+A is 
already mapped to the Refactor pulldown menu. The platform API does not 
allow mapping the same keyboard accelerator to different UI actions 
depending on the context. As a result, we end up with akward 
combinations like ALT+P for Replace All.


Please see https://netbeans.org/bugzilla/show_bug.cgi?id=222843 for 
additional context.


Is anyone else interested in this issue? Is anyone interested in working 
on it?


Thank you,
Gili


-
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)

On Mon, 26 Feb 2018 at 13:27 Peter Steele  wrote:

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

I have no idea!  Maybe one for Wade.  What I do know is that clean deletes
the build dir, so the assets get removed.

Maybe we need to explicitly clean up the asset dirs too?

Seems possibly related to comments here
https://github.com/gradle/gradle/issues/1168

Best wishes,

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

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

Re: openide annotation processors and StandardLocation.SOURCE_PATH

Hi,

On Mon, 26 Feb 2018 at 12:36 Basin Ilya  wrote:

> This may sound like a heresy, but I tried to build some Netbeans
> components with Eclipse.

:-)  But, do you have to use the Eclipse compiler?

> Eclipse can't generate Bundle.java because of the error thrown by an
> annotation processor used.
>
> The error is "Unsupported location: SOURCE_PATH" and the reason is that it
> expects IOException while Eclipse throws IllegalArgumentException. The fix
> is trivial: catch a
> more generic exception.
>

I was looking at the bundle processor the other week when I needed to write
my own processor using SOURCE_PATH.   In this case, is that fix really
trivial?  Won't it miss merging pre-existing entries?

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)

2018-02-26 Thread 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"  wrote:

> On Mon, 26 Feb 2018 at 11:38 Peter Steele  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
>

openide annotation processors and StandardLocation.SOURCE_PATH

2018-02-26 Thread Basin Ilya

Hi.

This may sound like a heresy, but I tried to build some Netbeans components 
with Eclipse. Namely, openide.util.ui/test and its dependencies. Almost 
everything works except
Eclipse can't generate Bundle.java because of the error thrown by an annotation 
processor used.

The error is "Unsupported location: SOURCE_PATH" and the reason is that it 
expects IOException while Eclipse throws IllegalArgumentException. The fix is 
trivial: catch a
more generic exception.

At least, NbBundleProcessor and AbstractServiceProviderProcessor are affected.

https://github.com/apache/incubator-netbeans/blob/15bc442a91fa2be81488725b15c61386bf1d0b9b/openide.util.lookup/src/org/openide/util/lookup/implspi/AbstractServiceProviderProcessor.java#L203

https://github.com/apache/incubator-netbeans/blob/15bc442a91fa2be81488725b15c61386bf1d0b9b/openide.util.ui/src/org/netbeans/modules/openide/util/NbBundleProcessor.java#L156

https://github.com/apache/incubator-netbeans/blob/15bc442a91fa2be81488725b15c61386bf1d0b9b/openide.util/src/org/netbeans/modules/openide/util/NbBundleProcessor.java#L156


I faced this issue on Oxygen 2 and on some older Eclipse:

    eclipse.buildId=4.4.2.M20150204-1700
    java.version=1.8.0_40
    java.vendor=Oracle Corporation
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
    Framework arguments:  -product org.eclipse.epp.package.jee.product
    Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product 
org.eclipse.epp.package.jee.product -data c:\keep\eclipse\4.4\workspace
   
    org.eclipse.jdt.apt.pluggable.core
    Error
    Mon Feb 26 12:22:16 MSK 2018
    Exception thrown by Java annotation processor 
org.netbeans.modules.openide.util.NbBundleProcessor@15df658b
   
    java.lang.IllegalArgumentException: Unsupported location: SOURCE_PATH
        at 
org.eclipse.jdt.internal.apt.pluggable.core.filer.IdeFilerImpl.getFileFromOutputLocation(IdeFilerImpl.java:188)
        at 
org.eclipse.jdt.internal.apt.pluggable.core.filer.IdeFilerImpl.getResource(IdeFilerImpl.java:154)
        at 
org.netbeans.modules.openide.util.NbBundleProcessor.process(NbBundleProcessor.java:173)
        at 
org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.handleProcessor(RoundDispatcher.java:139)
        at 
org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.round(RoundDispatcher.java:121)
        at 
org.eclipse.jdt.internal.compiler.apt.dispatch.BaseAnnotationProcessorManager.processAnnotations(BaseAnnotationProcessorManager.java:159)
        at 
org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.processAnnotations(IdeAnnotationProcessorManager.java:134)
        at 
org.eclipse.jdt.internal.compiler.Compiler.processAnnotations(Compiler.java:818)
        at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:434)
        at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:367)
        at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.compile(BatchImageBuilder.java:179)
        at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:304)
        at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:61)
        at 
org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:256)
        at 
org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:175)
        at 
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
        at 
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
        at 
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
        at 
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
        at 
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
        at 
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

AW: [ANN] Closing the NetBeans Logo Contest

Thx for the announcement and work 😊 Great to see it going the right way.


Cheers

Chris

Von: Antonio
Gesendet: Montag, 26. Februar 2018 12:57
An: dev@netbeans.incubator.apache.org
Betreff: [ANN] Closing the NetBeans Logo Contest

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

AW: The logo, once and for all? (was AW: Merged to master (was Re: ANetBeans website proposal))

I know all of that, the page in the wiki was from me, because I didn’t know the 
real voting process for that. Now we have a ticket, someone created it in Q4 
last year I think. But there was no Progress until now. So no real announcement 
that someone should create logos and adding stuff. Junichi was one of 2 I think 
who created a logo proposal. So for now there is no contest that can closed, or 
do we accept that, what we already have? Then I’m really fine with that.

I only wanted to give a hint, that we should choose the SVG variant of the logo 
on the new draft, not the png file, because on my Screen it Looks blurry. I 
only wanted to mention, that I use the SVG variant, of the other, colorful 
logo. I don’t wanted to Change it. Only using SVG instead of PNG.

So great that we have a vote soon, I thought it is Apache way to have the vote 
in JIRA, as someone other said that to me. But Mailing list is also ok, if this 
is going to happen.


Cheers

Chris

Von: Antonio
Gesendet: Montag, 26. Februar 2018 12:06
An: dev@netbeans.incubator.apache.org
Betreff: The logo, once and for all? (was AW: Merged to master (was Re: 
ANetBeans website proposal))

Hi Chris, all,

The situation with the logo is that there was a voting at [1] somewhere 
in 2016, the most voted logo is not the one with colors, so using the 
one you suggest (with colors) instead of the most voted one does not 
seem to be very Apache compliant, as it would be against a voting result.

Also in late 2017 we opened an Apache NetBeans logo contest at [2], 
which has not been closed yet. There has been a submission in early 
february 2018 (i.e., a few days ago) from Junichi (see [3]), which is 
also pretty cool, IMHO, and also deserves our consideration.

To end up the logo discussion once and for all I propose:

- Announcing closing the contest within a few days.
- Announce a voting in the mailing list, as per the Apache way.

I know this is probably lots of bureaucracy, but that's how things are 
expected to work in this Apache world, AFAIK (and please correct me if 
I'm wrong).

Kind regards,
Antonio

[1]
https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo

[2]
https://issues.apache.org/jira/browse/NETBEANS-145

[3]
https://issues.apache.org/jira/secure/attachment/12909573/apache-netbeans-logo.png

 Forwarded Message 
Subject: AW: Merged to master (was Re: A NetBeans website proposal)
Date: Mon, 26 Feb 2018 10:58:53 +0100
From: Christian Lenz 
Reply-To: dev@netbeans.incubator.apache.org
To: dev@netbeans.incubator.apache.org 

I would like to Change the logo to the SVG file, because it scales 
better and we don’t have any Problems with Retina and whatever, as you 
can see it here: http://netbeans.apache.org/. I added the SVG too.


Cheers

Chris



-
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

[ANN] Closing the NetBeans Logo Contest


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

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

On Mon, 26 Feb 2018 at 11:38 Peter Steele  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)

2018-02-26 Thread 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"  wrote:

On Mon, 26 Feb 2018 at 10:57 Peter Steele  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: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))

On Mon, 26 Feb 2018 at 11:24 Antonio  wrote:

> I'd say the icon without the typography.
>

Agreed, so +1 from me to that and your schedule.

Given the necessarily short schedule, etc., and as we find our feet at
Apache, it might be good to keep in mind that any decision could get
reviewed around either next major release or when we become a top-level
project - ie. it's not a vote on something that will be fixed for all
eternity! ;-)

Best wishes,

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

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

Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))


I'd say the icon without the typography.

Cheers,
Antonio

On 26/02/18 12:16, Neil C Smith wrote:

On Mon, 26 Feb 2018 at 11:06 Antonio  wrote:


To end up the logo discussion once and for all I propose:

- Announcing closing the contest within a few days.
- Announce a voting in the mailing list, as per the Apache way.



Sounds good!

Can we also clarify what we mean by logo though?  Are we at this stage
literally looking for the replacement for the cube icon, without any text /
typography?

Because currently the blue logo has 6 or 8 votes depending on what we mean.

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: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))


Hi again,

So, to keep things moving, shall we announce closing the contest by, 
say, until March the 1st?


And start the voting during March 2nd, 3rd and 4th?

Or is that too fast? ;-)

Cheers,
Antonio

On 26/02/18 12:09, Geertjan Wielenga wrote:

That sounds good. Thanks for persevering with this, Antonio.

Gj

On Mon, Feb 26, 2018 at 12:06 PM, Antonio  wrote:


Hi Chris, all,

The situation with the logo is that there was a voting at [1] somewhere in
2016, the most voted logo is not the one with colors, so using the one you
suggest (with colors) instead of the most voted one does not seem to be
very Apache compliant, as it would be against a voting result.

Also in late 2017 we opened an Apache NetBeans logo contest at [2], which
has not been closed yet. There has been a submission in early february 2018
(i.e., a few days ago) from Junichi (see [3]), which is also pretty cool,
IMHO, and also deserves our consideration.

To end up the logo discussion once and for all I propose:

- Announcing closing the contest within a few days.
- Announce a voting in the mailing list, as per the Apache way.

I know this is probably lots of bureaucracy, but that's how things are
expected to work in this Apache world, AFAIK (and please correct me if I'm
wrong).

Kind regards,
Antonio

[1]
https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo

[2]
https://issues.apache.org/jira/browse/NETBEANS-145

[3]
https://issues.apache.org/jira/secure/attachment/12909573/
apache-netbeans-logo.png

 Forwarded Message 
Subject: AW: Merged to master (was Re: A NetBeans website proposal)
Date: Mon, 26 Feb 2018 10:58:53 +0100
From: Christian Lenz 
Reply-To: dev@netbeans.incubator.apache.org
To: dev@netbeans.incubator.apache.org 

I would like to Change the logo to the SVG file, because it scales better
and we don’t have any Problems with Retina and whatever, as you can see it
here: http://netbeans.apache.org/. I added the SVG too.


Cheers

Chris



-
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: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))

On Mon, 26 Feb 2018 at 11:06 Antonio  wrote:

> To end up the logo discussion once and for all I propose:
>
> - Announcing closing the contest within a few days.
> - Announce a voting in the mailing list, as per the Apache way.
>

Sounds good!

Can we also clarify what we mean by logo though?  Are we at this stage
literally looking for the replacement for the cube icon, without any text /
typography?

Because currently the blue logo has 6 or 8 votes depending on what we mean.

Best wishes,

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

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

Re: The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))

2018-02-26 Thread Geertjan Wielenga

That sounds good. Thanks for persevering with this, Antonio.

Gj

On Mon, Feb 26, 2018 at 12:06 PM, Antonio  wrote:

> Hi Chris, all,
>
> The situation with the logo is that there was a voting at [1] somewhere in
> 2016, the most voted logo is not the one with colors, so using the one you
> suggest (with colors) instead of the most voted one does not seem to be
> very Apache compliant, as it would be against a voting result.
>
> Also in late 2017 we opened an Apache NetBeans logo contest at [2], which
> has not been closed yet. There has been a submission in early february 2018
> (i.e., a few days ago) from Junichi (see [3]), which is also pretty cool,
> IMHO, and also deserves our consideration.
>
> To end up the logo discussion once and for all I propose:
>
> - Announcing closing the contest within a few days.
> - Announce a voting in the mailing list, as per the Apache way.
>
> I know this is probably lots of bureaucracy, but that's how things are
> expected to work in this Apache world, AFAIK (and please correct me if I'm
> wrong).
>
> Kind regards,
> Antonio
>
> [1]
> https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo
>
> [2]
> https://issues.apache.org/jira/browse/NETBEANS-145
>
> [3]
> https://issues.apache.org/jira/secure/attachment/12909573/
> apache-netbeans-logo.png
>
>  Forwarded Message 
> Subject: AW: Merged to master (was Re: A NetBeans website proposal)
> Date: Mon, 26 Feb 2018 10:58:53 +0100
> From: Christian Lenz 
> Reply-To: dev@netbeans.incubator.apache.org
> To: dev@netbeans.incubator.apache.org 
>
> I would like to Change the logo to the SVG file, because it scales better
> and we don’t have any Problems with Retina and whatever, as you can see it
> here: http://netbeans.apache.org/. I added the SVG too.
>
>
> Cheers
>
> Chris
>
>
>
> -
> 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)

On Mon, 26 Feb 2018 at 10:57 Peter Steele  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

The logo, once and for all? (was AW: Merged to master (was Re: A NetBeans website proposal))


Hi Chris, all,

The situation with the logo is that there was a voting at [1] somewhere 
in 2016, the most voted logo is not the one with colors, so using the 
one you suggest (with colors) instead of the most voted one does not 
seem to be very Apache compliant, as it would be against a voting result.


Also in late 2017 we opened an Apache NetBeans logo contest at [2], 
which has not been closed yet. There has been a submission in early 
february 2018 (i.e., a few days ago) from Junichi (see [3]), which is 
also pretty cool, IMHO, and also deserves our consideration.


To end up the logo discussion once and for all I propose:

- Announcing closing the contest within a few days.
- Announce a voting in the mailing list, as per the Apache way.

I know this is probably lots of bureaucracy, but that's how things are 
expected to work in this Apache world, AFAIK (and please correct me if 
I'm wrong).


Kind regards,
Antonio

[1]
https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+Logo

[2]
https://issues.apache.org/jira/browse/NETBEANS-145

[3]
https://issues.apache.org/jira/secure/attachment/12909573/apache-netbeans-logo.png

 Forwarded Message 
Subject: AW: Merged to master (was Re: A NetBeans website proposal)
Date: Mon, 26 Feb 2018 10:58:53 +0100
From: Christian Lenz 
Reply-To: dev@netbeans.incubator.apache.org
To: dev@netbeans.incubator.apache.org 

I would like to Change the logo to the SVG file, because it scales 
better and we don’t have any Problems with Retina and whatever, as you 
can see it here: http://netbeans.apache.org/. I added the SVG too.



Cheers

Chris



-
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)

2018-02-26 Thread 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: Merged to master (was Re: A NetBeans website proposal)

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: Netbeans quick outline plugin

On Mon, 26 Feb 2018 at 09:50 Christian Lenz  wrote:

> ... this was only possible to add the plugin as a friend which is only a
> Workaround.
>

There was a discussion on a PR recently about stopping using friend
relationships for "unstable" API's in favour of another approach -
something that would be good not to let slide IMO.

Best wishes,

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

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

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

I would like to Change the logo to the SVG file, because it scales better and 
we don’t have any Problems with Retina and whatever, as you can see it here: 
http://netbeans.apache.org/. I added the SVG too.

Cheers

Chris

Von: Antonio
Gesendet: Montag, 26. Februar 2018 08:54
An: dev@netbeans.incubator.apache.org
Betreff: Merged to master (was Re: A NetBeans website proposal)

Hi all,

This has now been merged to master, we think we comply with ASF's 
podling website requirements. Feel free to submit PRs as you see fit.

I've uploaded the bits at https://netbeans.vieiro.net temporarily, to 
verify that the "see this page in github" links work properly. This 
won't track master, and may dissappear within a few days.

Thanks all involved and those giving comments and ideas.

Have fun,
Antonio

== Main goals

As Geertjan outlined in the mailing list thread the main goals for the 
netbeans.apache.org website are, in order of importance:

1- Have a proper IDE features page.
2- Port the IDE tutorials.
3- Have a platform specific page.

Some other enhancements & to-dos as seen in the thread & elsewhere:

- Improve image visualization (lightbox, for instance).
- Add proper retina images (including the NetBeans logo).
- The wiki pages should be reviewed, after review the bottom of the page 
should contain the review date.

== Going live

AFAIK the website won't go live until we update the content to the 
"asf-site" branch (i.e., until we copy the generated HTML into that 
branch), as I think this branch is currently connected with the web 
server through Apache's gitpubsub.

I'll try to find out the details.

== netbeans.apache.org help materials

- 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.

- The templates directory README
https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org/src/content/templates
has information about building templates as "Groovy Server Pages" files, 
as well as the initial templates we're using.

- The scss directory at
https://github.com/apache/incubator-netbeans-website/tree/master/netbeans.apache.org/src/content/scss
Contains the initial SCSS files from Foundation adapted to netbeans.

Other useful links:

- jbake http://jbake.org/docs/2.5.1/
- foundation 6 for sites https://foundation.zurb.com/sites/docs/
- for those using asciidoc the AsciiDoc Writer's Guide at 
https://asciidoctor.org/docs/asciidoc-writers-guide/

== bits.netbeans.org

The ant script at bits.netbeans.org needs some love to properly generate 
NetBeans javadoc files + arch stuff (properly tagged with release 
information, etc.). The directory structure from current 
"bits.netbeans.org" does not match the existing one.

AFAIK we haven't set up a webserver for this domain, I imagine we can do 
this later on (probably using gitpubsub too in another "api" branch).

On 23/02/18 08:19, 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

AW: First draft of netbeans quick outline plugin

Hey Peter,

I wanted to comment, but smth with Twitter and/or fb is not working. Anyway, I 
do it here:


➢ The tree (AST) view is needed, because it shows the hierachical view and the 
association of the code. IntelliJ does the same, the navigator in NetBeans too. 
It represents the Abstract Syntax Tree, which is a tree. If you show it like 
this, there is no association between vars and/or functions and whatever, as 
you can see your comparsion of your plugin and the result from Eclipse.

➢ For me, I would like to see the same information from the navigator for 
example. If I have a filter function, there is nothing wrong with a tree and it 
will not hurting the eyes. The only difference between your plugin and the 
navigator, should be, that this is a lightweight dialog and with a filter 
functionality.


Cheers

Chris

Von: Peter Cheung
Gesendet: Montag, 26. Februar 2018 10:06
An: d...@platform.netbeans.org
Cc: dev@netbeans.incubator.apache.org
Betreff: First draft of netbeans quick outline plugin



First draft of netbeans quick outline plugin

http://peter.quantr.hk/2018/02/first-draft-of-netbeans-quick-outline-plugin/

AW: Netbeans quick outline plugin

The Thing is, that you can extends the Java Editor to add new Hints for 
example, this is not possible for JS, HTML, CSS or PHP, because it is not open 
to extend those stuff. As you can see a plugin from NetBeans to adding KendoUI, 
this was only possible to add the plugin as a friend which is only a 
Workaround. Now it is not a friend anymore, so you can’t Access some JS stuff 
like JSTokens or SQLTokens or PHPTokens to work with that. Those Tokens are 
used for adding embedding languages to another language like SQL or HTML into 
JS Code which is not possible (AFAIK) with 3rd Party Plugins.


Cheers

Chris
Von: Peter Cheung
Gesendet: Montag, 26. Februar 2018 10:44
An: dev@netbeans.incubator.apache.org
Betreff: Re: Netbeans quick outline plugin

  1.  Let me try out the javascript grammar in the coming few days 
https://github.com/antlr/grammars-v4/tree/master/javascript
  2.  Why netbeans just let everyone to access every api/class/functions ?


Thanks
>From Peter



From: Christian Lenz 
Sent: Monday, February 26, 2018 5:39 PM
To: dev@netbeans.incubator.apache.org
Subject: AW: Netbeans quick outline plugin

Sure, plugin makes sense. So for this, you are parsing the JS grammar again? I 
only wanted to say, that this is not needed, because NetBeans already does it 
for you, but you can’t acces the Tokens for example other than Java, because it 
is not public from the outside. Sure there is the CSL but it is not working. 
But if you do it by your own, you will not have any Problems.

Gesendet von Mail für Windows 10

Von: Peter Cheung
Gesendet: Montag, 26. Februar 2018 10:13
An: dev@netbeans.incubator.apache.org
Betreff: Re: Netbeans quick outline plugin

Dear Chris


That would be great. I thought on such a plugin too, please Keep in mind, that 
we Need it for C/C++, Java, JavaScript, PHP and what NetBeans also Support. 
Maybe HTML XML too but could be optional.

Easy, Antlr already support those grammars

If this is not possible, with a 3rd Party plugin, because you have to get the 
JS, PHP C/C++ Parser Tokens to identify private, public, functions, members, 
classes etc. (This is, AFAIK, only possible for Java). You can implement it 
into the NetBeans core, instead of a plugin.

I have no experience to implement anything in core, don't even know how to 
submit my code for review and the team seems very busy on migrating the project 
to apache. not sure it is a good approach or not. Please suggest.

Cheers

Chris

Von: Peter Cheung
Gesendet: Sonntag, 25. Februar 2018 19:32
An: d...@platform.netbeans.org
Cc: dev@netbeans.incubator.apache.org
Betreff: Netbeans quick outline plugin

http://peter.quantr.hk/2018/02/netbeans-quick-outline/

Re: Netbeans quick outline plugin

  1.  Let me try out the javascript grammar in the coming few days 
https://github.com/antlr/grammars-v4/tree/master/javascript
  2.  Why netbeans just let everyone to access every api/class/functions ?


Thanks
>From Peter



From: Christian Lenz 
Sent: Monday, February 26, 2018 5:39 PM
To: dev@netbeans.incubator.apache.org
Subject: AW: Netbeans quick outline plugin

Sure, plugin makes sense. So for this, you are parsing the JS grammar again? I 
only wanted to say, that this is not needed, because NetBeans already does it 
for you, but you can’t acces the Tokens for example other than Java, because it 
is not public from the outside. Sure there is the CSL but it is not working. 
But if you do it by your own, you will not have any Problems.

Gesendet von Mail für Windows 10

Von: Peter Cheung
Gesendet: Montag, 26. Februar 2018 10:13
An: dev@netbeans.incubator.apache.org
Betreff: Re: Netbeans quick outline plugin

Dear Chris


That would be great. I thought on such a plugin too, please Keep in mind, that 
we Need it for C/C++, Java, JavaScript, PHP and what NetBeans also Support. 
Maybe HTML XML too but could be optional.

Easy, Antlr already support those grammars

If this is not possible, with a 3rd Party plugin, because you have to get the 
JS, PHP C/C++ Parser Tokens to identify private, public, functions, members, 
classes etc. (This is, AFAIK, only possible for Java). You can implement it 
into the NetBeans core, instead of a plugin.

I have no experience to implement anything in core, don't even know how to 
submit my code for review and the team seems very busy on migrating the project 
to apache. not sure it is a good approach or not. Please suggest.

Cheers

Chris

Von: Peter Cheung
Gesendet: Sonntag, 25. Februar 2018 19:32
An: d...@platform.netbeans.org
Cc: dev@netbeans.incubator.apache.org
Betreff: Netbeans quick outline plugin

http://peter.quantr.hk/2018/02/netbeans-quick-outline/

AW: Netbeans quick outline plugin

Sure, plugin makes sense. So for this, you are parsing the JS grammar again? I 
only wanted to say, that this is not needed, because NetBeans already does it 
for you, but you can’t acces the Tokens for example other than Java, because it 
is not public from the outside. Sure there is the CSL but it is not working. 
But if you do it by your own, you will not have any Problems.

Gesendet von Mail für Windows 10

Von: Peter Cheung
Gesendet: Montag, 26. Februar 2018 10:13
An: dev@netbeans.incubator.apache.org
Betreff: Re: Netbeans quick outline plugin

Dear Chris


That would be great. I thought on such a plugin too, please Keep in mind, that 
we Need it for C/C++, Java, JavaScript, PHP and what NetBeans also Support. 
Maybe HTML XML too but could be optional.

Easy, Antlr already support those grammars

If this is not possible, with a 3rd Party plugin, because you have to get the 
JS, PHP C/C++ Parser Tokens to identify private, public, functions, members, 
classes etc. (This is, AFAIK, only possible for Java). You can implement it 
into the NetBeans core, instead of a plugin.

I have no experience to implement anything in core, don't even know how to 
submit my code for review and the team seems very busy on migrating the project 
to apache. not sure it is a good approach or not. Please suggest.

Cheers

Chris

Von: Peter Cheung
Gesendet: Sonntag, 25. Februar 2018 19:32
An: d...@platform.netbeans.org
Cc: dev@netbeans.incubator.apache.org
Betreff: Netbeans quick outline plugin

http://peter.quantr.hk/2018/02/netbeans-quick-outline/

Re: ActionReference has bug ?

OK, thanks


Thanks
>From Peter



From: Geertjan Wielenga 
Sent: Monday, February 26, 2018 1:13 AM
To: dev@netbeans.incubator.apache.org
Cc: d...@platform.netbeans.org
Subject: Re: ActionReference has bug ?

Programmatic name is probably not Navigate. Maybe it is GoTo.

Gj

On Sunday, February 25, 2018, Peter Cheung  wrote:

> Hi All
>
>  Why "Menu/Navigate" will put my action into another Navigate menu
> rather than the existing one? Why i press the shortcut key, i only see the
> menu is blinking but the actionPerformed() hasn't run?
>
>
> Thanks
>
>
>
> package hk.quantr.netbeansquickoutline;
>
>
> import java.awt.event.ActionEvent;
>
> import java.awt.event.ActionListener;
>
> import javax.swing.JOptionPane;
>
> import org.openide.awt.ActionID;
>
> import org.openide.awt.ActionReference;
>
> import org.openide.awt.ActionReferences;
>
> import org.openide.awt.ActionRegistration;
>
> import org.openide.util.NbBundle.Messages;
>
>
> @ActionID(
>
> category = "Navigate",
>
> id = "hk.quantr.netbeansquickoutline.SomeAction"
>
> )
>
> @ActionRegistration(
>
> displayName = "#CTL_SomeAction"
>
> )
>
> @ActionReferences({
>
> @ActionReference(path = "Menu/Navigate", position = )
>
> ,
>
> @ActionReference(path = "Shortcuts", name = "M-P")
>
> })
>
> @Messages("CTL_SomeAction=MyMenu")
>
> public final class SomeAction implements ActionListener {
>
>
> @Override
>
> public void actionPerformed(ActionEvent e) {
>
> JOptionPane.showMessageDialog(null, "hey");
>
> }
>
> }
>

Re: Netbeans quick outline plugin

Dear Chris


That would be great. I thought on such a plugin too, please Keep in mind, that 
we Need it for C/C++, Java, JavaScript, PHP and what NetBeans also Support. 
Maybe HTML XML too but could be optional.

Easy, Antlr already support those grammars

If this is not possible, with a 3rd Party plugin, because you have to get the 
JS, PHP C/C++ Parser Tokens to identify private, public, functions, members, 
classes etc. (This is, AFAIK, only possible for Java). You can implement it 
into the NetBeans core, instead of a plugin.

I have no experience to implement anything in core, don't even know how to 
submit my code for review and the team seems very busy on migrating the project 
to apache. not sure it is a good approach or not. Please suggest.

Cheers

Chris

Von: Peter Cheung
Gesendet: Sonntag, 25. Februar 2018 19:32
An: d...@platform.netbeans.org
Cc: dev@netbeans.incubator.apache.org
Betreff: Netbeans quick outline plugin

http://peter.quantr.hk/2018/02/netbeans-quick-outline/

First draft of netbeans quick outline plugin