You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Laszlo Kishalmi <la...@gmail.com> on 2018/05/12 16:52:10 UTC
Expose Caret Settings in Editor Options
Dear all,
We have a new feature request:
https://issues.apache.org/jira/browse/NETBEANS-762 about changing the
Caret blinking speed.
AFAIK NetBeans has 3 caret settings available in its editor which can't
be set in the new (post 3.x maybe) NetBeans Options UI. The caret blink
rate and caret shape in insert and overwrite mode.
What do you think about having a Caret tab in Editor Options in order to
expose these properties? Or place those somewhere else? Or not place
them at all or implement that as a custom plugin? So I'd like to hear
the voice of the community. I fell myself confident enough to implement
the required code.
Personally I was fan of the non blinking block Caret.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
AW: Expose Caret Settings in Editor Options
Posted by Christian Lenz <ch...@gmx.net>.
The Options window, should similar and consistent to the Project properties. This is not only to make it consistent, it is a UX Thing, because now you can’t see the Options and Sub Options of each Option. But sure this is an other Topic. But I saw this discussion here and wanted to jump in.
Cheers
Chris
Von: Christian Lenz
Gesendet: Sonntag, 13. Mai 2018 12:16
An: dev@netbeans.incubator.apache.org
Betreff: AW: Expose Caret Settings in Editor Options
There can’t be enough Options to customize to your Needs. There are lot of Options missing (Change Code completion dleay e.g.). So we can’t fit any Needs, but we can customize a lot of Features via Options, but the current Option window is not good to have this. This is where we should care About. Look at other IDEs or Editors, they have a lot of Options to customize your stuff.
Cheers
Chris
Von: Geertjan Wielenga
Gesendet: Sonntag, 13. Mai 2018 12:11
An: dev@netbeans.incubator.apache.org
Betreff: Re: Expose Caret Settings in Editor Options
I get your point and I think it's a very difficult balance to make. We
don't want to overload the IDE with UI. However, at the same time, I don't
see there being hundreds of requests for new configuration options,
instead, I have seen about three or four coming up again and again, really,
in total, in all the time I have been working on NetBeans since 2004. And
this caret thing is one of them. So, it's not that bad, we're not being
asked for much more than we already have, though this caret thing is one of
them, I think it would be handy to have this one somewhere in the Options
window, maybe within an existing panel rather than a whole new one which I
think would be adding too much for this.
Gj
On Sun, May 13, 2018 at 11:54 AM, Emilian Bold <em...@protonmail.ch>
wrote:
> -0.5
>
> This seems like something a plugin could easily provide.
>
> Normal users would just use NetBeans and have a clean UI while users that
> search for more customisations just use the plugin.
>
> The important part is having the API support for this (which we do), not
> adding more and more UI.
>
> I feel the current Options window provides too much configuration.
>
> Otoh, people regularly seem to discover something they assumed impossible
> has a preference somewhere deep down. So, discoverability is quite bad.
>
> --emi
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On 12 May 2018 7:52 PM, Laszlo Kishalmi <la...@gmail.com> wrote:
>
> > Dear all,
> >
> > We have a new feature request:
> >
> > https://issues.apache.org/jira/browse/NETBEANS-762 about changing the
> >
> > Caret blinking speed.
> >
> > AFAIK NetBeans has 3 caret settings available in its editor which can't
> >
> > be set in the new (post 3.x maybe) NetBeans Options UI. The caret blink
> >
> > rate and caret shape in insert and overwrite mode.
> >
> > What do you think about having a Caret tab in Editor Options in order to
> >
> > expose these properties? Or place those somewhere else? Or not place
> >
> > them at all or implement that as a custom plugin? So I'd like to hear
> >
> > the voice of the community. I fell myself confident enough to implement
> >
> > the required code.
> >
> > Personally I was fan of the non blinking block Caret.
> >
> >
> > ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> -----------------------------------------
> >
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> >
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
AW: Expose Caret Settings in Editor Options
Posted by Christian Lenz <ch...@gmx.net>.
There can’t be enough Options to customize to your Needs. There are lot of Options missing (Change Code completion dleay e.g.). So we can’t fit any Needs, but we can customize a lot of Features via Options, but the current Option window is not good to have this. This is where we should care About. Look at other IDEs or Editors, they have a lot of Options to customize your stuff.
Cheers
Chris
Von: Geertjan Wielenga
Gesendet: Sonntag, 13. Mai 2018 12:11
An: dev@netbeans.incubator.apache.org
Betreff: Re: Expose Caret Settings in Editor Options
I get your point and I think it's a very difficult balance to make. We
don't want to overload the IDE with UI. However, at the same time, I don't
see there being hundreds of requests for new configuration options,
instead, I have seen about three or four coming up again and again, really,
in total, in all the time I have been working on NetBeans since 2004. And
this caret thing is one of them. So, it's not that bad, we're not being
asked for much more than we already have, though this caret thing is one of
them, I think it would be handy to have this one somewhere in the Options
window, maybe within an existing panel rather than a whole new one which I
think would be adding too much for this.
Gj
On Sun, May 13, 2018 at 11:54 AM, Emilian Bold <em...@protonmail.ch>
wrote:
> -0.5
>
> This seems like something a plugin could easily provide.
>
> Normal users would just use NetBeans and have a clean UI while users that
> search for more customisations just use the plugin.
>
> The important part is having the API support for this (which we do), not
> adding more and more UI.
>
> I feel the current Options window provides too much configuration.
>
> Otoh, people regularly seem to discover something they assumed impossible
> has a preference somewhere deep down. So, discoverability is quite bad.
>
> --emi
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On 12 May 2018 7:52 PM, Laszlo Kishalmi <la...@gmail.com> wrote:
>
> > Dear all,
> >
> > We have a new feature request:
> >
> > https://issues.apache.org/jira/browse/NETBEANS-762 about changing the
> >
> > Caret blinking speed.
> >
> > AFAIK NetBeans has 3 caret settings available in its editor which can't
> >
> > be set in the new (post 3.x maybe) NetBeans Options UI. The caret blink
> >
> > rate and caret shape in insert and overwrite mode.
> >
> > What do you think about having a Caret tab in Editor Options in order to
> >
> > expose these properties? Or place those somewhere else? Or not place
> >
> > them at all or implement that as a custom plugin? So I'd like to hear
> >
> > the voice of the community. I fell myself confident enough to implement
> >
> > the required code.
> >
> > Personally I was fan of the non blinking block Caret.
> >
> >
> > ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> -----------------------------------------
> >
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> >
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Expose Caret Settings in Editor Options
Posted by Emilian Bold <em...@protonmail.ch>.
> Everybody has some little thing they'd like to be able to tweak. And for
> many of them, there are two people in the universe that will ever tweak
> them. The overwhelming lesson of the data about what options people
> actually used that we gathered was that most people customize nothing.
>
> Don't open Pandora's box. Today it's caret blink rate. What will it be
> tomorrow?
+100
--emi
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 14 May 2018 10:07 AM, Tim Boudreau <ni...@gmail.com> wrote:
> On Mon, May 14, 2018 at 2:15 AM, Christian Lenz christian.lenz@gmx.net
>
> wrote:
>
> > Of Course, it will increase a bit of the complexity but it is as it is.
> >
> > This shouldn’t really not a reason why not doing this.
>
> IMO, maybe it should. From an oldie but a goodie:
>
> Pull up the Tools | Options dialog box and you will see a history ofarguments that the software designers had about the design of the product.
>
> - Joel Spolsky - https://www.joelonsoftware.com/2000/04/12/choices/
>
> I was around for the original rewrite of the options window - the
>
> BeanTreeView with a property sheet that somebody mentioned used to be
>
> around as the "advanced" view. Now, part of that was the fact that, as we
>
> learned the hard way with videotaped usability studies, the tree + property
>
> sheet interface was completely baffling to a lot of users. But a lot of it
>
> was the sheer volume of options - who actually wants to customize "Editor
>
> scroll jump insets"? You could.
>
> The job, in creating usable software, is to make good choices about
>
> defaults, so nobody wants to customize them. The way to abdicate that
>
> responsibility is to avoid choosing "let's make that an option".
>
> Everybody has some little thing they'd like to be able to tweak. And for
>
> many of them, there are two people in the universe that will ever tweak
>
> them. The overwhelming lesson of the data about what options people
>
> actually used that we gathered was that most people customize nothing.
>
> Don't open Pandora's box. Today it's caret blink rate. What will it be
>
> tomorrow?
>
> If someone simply must have a non-blinking caret, it would be trivial to
>
> write a plugin that sets that one setting via its layer.xml - and given
>
> that in 19 years of working on NetBeans or being involved with it, this is
>
> the only request I have ever seen for that, a downloadable plugin seems
>
> like the right level of discoverability. People who search the web for
>
> "netbeans caret blink" will find it, but we don't pollute the UI with a
>
> setting for something almost nobody on earth is going to care about.
>
> And I say that, thinking, I'd probably actually like a non-blinking caret
>
> and install that plugin. But I am also, as one of its developers, not the
>
> target audience, and what makes me happy can drive others away.
>
> -Tim
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Expose Caret Settings in Editor Options
Posted by Laszlo Kishalmi <la...@gmail.com>.
Dear all,
Thank you for all the valuable feedback. Upon that I think that the best
way to implement this is to create a separate plugin.
On 05/14/2018 12:07 AM, Tim Boudreau wrote:
> On Mon, May 14, 2018 at 2:15 AM, Christian Lenz <ch...@gmx.net>
> wrote:
>
>> Of Course, it will increase a bit of the complexity but it is as it is.
>> This shouldn’t really not a reason why not doing this.
>>
> IMO, maybe it should. From an oldie but a goodie:
>
> *Pull up the Tools | Options dialog box and you will see a history of
> arguments that the software designers had about the design of the product.*
> - Joel Spolsky - https://www.joelonsoftware.com/2000/04/12/choices/
>
> I was around for the original rewrite of the options window - the
> BeanTreeView with a property sheet that somebody mentioned used to be
> around as the "advanced" view. Now, part of that was the fact that, as we
> learned the hard way with videotaped usability studies, the tree + property
> sheet interface was completely baffling to a lot of users. But a lot of it
> was the sheer volume of options - who actually wants to customize "Editor
> scroll jump insets"? You could.
>
> The *job*, in creating usable software, is to make good choices about
> defaults, so nobody wants to customize them. The way to abdicate that
> responsibility is to avoid choosing "let's make that an option".
>
> Everybody has some little thing they'd like to be able to tweak. And for
> many of them, there are two people in the universe that will ever tweak
> them. The overwhelming lesson of the data about what options people
> actually used that we gathered was that most people customize nothing.
>
> Don't open Pandora's box. Today it's caret blink rate. What will it be
> tomorrow?
>
> If someone simply *must* have a non-blinking caret, it would be trivial to
> write a plugin that sets that one setting via its layer.xml - and given
> that in 19 years of working on NetBeans or being involved with it, this is
> the only request I have ever seen for that, a downloadable plugin seems
> like the right level of discoverability. People who search the web for
> "netbeans caret blink" will find it, but we don't pollute the UI with a
> setting for something almost nobody on earth is going to care about.
>
> And I say that, thinking, I'd probably actually like a non-blinking caret
> and install that plugin. But I am also, as one of its developers, not the
> target audience, and what makes me happy can drive others away.
>
> -Tim
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
AW: Expose Caret Settings in Editor Options
Posted by Christian Lenz <ch...@gmx.net>.
A blinking Cursor is an eye catcher for those who are searching for the Cursor in a file of lot of lines. So this Thing is reasonable for some users. Sure we can’t handle all Little tweaks and Options and we shouldn’t but we should have a look what are the big cases for those users. One case, that I can Image is the delay of the Code completion. Me I don’t want a delay time, some others want them like not seeing the completion while typing, etc. This Thing is configuratble, but not via Options, only inside the files. This is one case where users want that delay customizable. There is a ticket for this too.
Yes there are good reasons for almost everything like do or don’t and we should think About it and let the user choose what they want. But if we have a ticket like, please do this and it will be implemented and some other creates a ticket with please do this, what is the complete opposite, this goes into differnet directions and then you only make one user happy with it. Sure 1 user could be 100 and the other user could be 200 but we should think about that. You can’t make everything good and everything Default. And if you have a Default, it should be changeable. Maybe not everything but most of them.
Yes today it is the blinking Cursor and tomorrow it could be some other stuff. I’m for advanced Settings too, for such Settings. If the user is willing to click on that advanced Settings button, he should be able to Change whatever he wants and thinks, which could be inside of it. To give Defaults only to one user groul instead of a lot of more People, is not a good Point, in my opinion.
Things can Change so let the user/developer decide.
Cheers
Chris
Von: Tim Boudreau
Gesendet: Montag, 14. Mai 2018 09:07
An: dev@netbeans.incubator.apache.org
Betreff: Re: Expose Caret Settings in Editor Options
On Mon, May 14, 2018 at 2:15 AM, Christian Lenz <ch...@gmx.net>
wrote:
> Of Course, it will increase a bit of the complexity but it is as it is.
> This shouldn’t really not a reason why not doing this.
>
IMO, maybe it should. From an oldie but a goodie:
*Pull up the Tools | Options dialog box and you will see a history of
arguments that the software designers had about the design of the product.*
- Joel Spolsky - https://www.joelonsoftware.com/2000/04/12/choices/
I was around for the original rewrite of the options window - the
BeanTreeView with a property sheet that somebody mentioned used to be
around as the "advanced" view. Now, part of that was the fact that, as we
learned the hard way with videotaped usability studies, the tree + property
sheet interface was completely baffling to a lot of users. But a lot of it
was the sheer volume of options - who actually wants to customize "Editor
scroll jump insets"? You could.
The *job*, in creating usable software, is to make good choices about
defaults, so nobody wants to customize them. The way to abdicate that
responsibility is to avoid choosing "let's make that an option".
Everybody has some little thing they'd like to be able to tweak. And for
many of them, there are two people in the universe that will ever tweak
them. The overwhelming lesson of the data about what options people
actually used that we gathered was that most people customize nothing.
Don't open Pandora's box. Today it's caret blink rate. What will it be
tomorrow?
If someone simply *must* have a non-blinking caret, it would be trivial to
write a plugin that sets that one setting via its layer.xml - and given
that in 19 years of working on NetBeans or being involved with it, this is
the only request I have ever seen for that, a downloadable plugin seems
like the right level of discoverability. People who search the web for
"netbeans caret blink" will find it, but we don't pollute the UI with a
setting for something almost nobody on earth is going to care about.
And I say that, thinking, I'd probably actually like a non-blinking caret
and install that plugin. But I am also, as one of its developers, not the
target audience, and what makes me happy can drive others away.
-Tim
Re: Expose Caret Settings in Editor Options
Posted by Tim Boudreau <ni...@gmail.com>.
On Mon, May 14, 2018 at 2:15 AM, Christian Lenz <ch...@gmx.net>
wrote:
> Of Course, it will increase a bit of the complexity but it is as it is.
> This shouldn’t really not a reason why not doing this.
>
IMO, maybe it should. From an oldie but a goodie:
*Pull up the Tools | Options dialog box and you will see a history of
arguments that the software designers had about the design of the product.*
- Joel Spolsky - https://www.joelonsoftware.com/2000/04/12/choices/
I was around for the original rewrite of the options window - the
BeanTreeView with a property sheet that somebody mentioned used to be
around as the "advanced" view. Now, part of that was the fact that, as we
learned the hard way with videotaped usability studies, the tree + property
sheet interface was completely baffling to a lot of users. But a lot of it
was the sheer volume of options - who actually wants to customize "Editor
scroll jump insets"? You could.
The *job*, in creating usable software, is to make good choices about
defaults, so nobody wants to customize them. The way to abdicate that
responsibility is to avoid choosing "let's make that an option".
Everybody has some little thing they'd like to be able to tweak. And for
many of them, there are two people in the universe that will ever tweak
them. The overwhelming lesson of the data about what options people
actually used that we gathered was that most people customize nothing.
Don't open Pandora's box. Today it's caret blink rate. What will it be
tomorrow?
If someone simply *must* have a non-blinking caret, it would be trivial to
write a plugin that sets that one setting via its layer.xml - and given
that in 19 years of working on NetBeans or being involved with it, this is
the only request I have ever seen for that, a downloadable plugin seems
like the right level of discoverability. People who search the web for
"netbeans caret blink" will find it, but we don't pollute the UI with a
setting for something almost nobody on earth is going to care about.
And I say that, thinking, I'd probably actually like a non-blinking caret
and install that plugin. But I am also, as one of its developers, not the
target audience, and what makes me happy can drive others away.
-Tim
AW: Expose Caret Settings in Editor Options
Posted by Christian Lenz <ch...@gmx.net>.
Of Course, it will increase a bit of the complexity but it is as it is. This shouldn’t really not a reason why not doing this.
Cheers
Chris
Von: Emilian Bold
Gesendet: Sonntag, 13. Mai 2018 13:05
An: dev@netbeans.incubator.apache.org
Betreff: Re: Expose Caret Settings in Editor Options
I dunno, I can't really compare -- last I heard about caret blink rate was years ago. I guess we could look at votes in the old Bugzilla to see the most requested features and such?
Anyhow, I'm not really bothered by this config being added, but the idea is not to add UI for everything.
> There can’t be enough Options to customize to your Needs.
Options increase the code complexity. The combinatorial explosion also makes testing complicated.
From an UI standpoint a noisy Options window will be hard to use.
I remember NetBeans used to have an 'Advanced' button which opened a bean tree view with basic Java beans settings. I guess something like that would make more sense for something as the cursor blink rate instead of a custom Swing panel. https://ui.netbeans.org/docs/hi/options/advancedOptions.html
--emi
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 13 May 2018 1:11 PM, Geertjan Wielenga <ge...@googlemail.com> wrote:
> I get your point and I think it's a very difficult balance to make. We
>
> don't want to overload the IDE with UI. However, at the same time, I don't
>
> see there being hundreds of requests for new configuration options,
>
> instead, I have seen about three or four coming up again and again, really,
>
> in total, in all the time I have been working on NetBeans since 2004. And
>
> this caret thing is one of them. So, it's not that bad, we're not being
>
> asked for much more than we already have, though this caret thing is one of
>
> them, I think it would be handy to have this one somewhere in the Options
>
> window, maybe within an existing panel rather than a whole new one which I
>
> think would be adding too much for this.
>
> Gj
>
> On Sun, May 13, 2018 at 11:54 AM, Emilian Bold emilian.bold@protonmail.ch
>
> wrote:
>
> > -0.5
> >
> > This seems like something a plugin could easily provide.
> >
> > Normal users would just use NetBeans and have a clean UI while users that
> >
> > search for more customisations just use the plugin.
> >
> > The important part is having the API support for this (which we do), not
> >
> > adding more and more UI.
> >
> > I feel the current Options window provides too much configuration.
> >
> > Otoh, people regularly seem to discover something they assumed impossible
> >
> > has a preference somewhere deep down. So, discoverability is quite bad.
> >
> > --emi
> >
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >
> > On 12 May 2018 7:52 PM, Laszlo Kishalmi laszlo.kishalmi@gmail.com wrote:
> >
> > > Dear all,
> > >
> > > We have a new feature request:
> > >
> > > https://issues.apache.org/jira/browse/NETBEANS-762 about changing the
> > >
> > > Caret blinking speed.
> > >
> > > AFAIK NetBeans has 3 caret settings available in its editor which can't
> > >
> > > be set in the new (post 3.x maybe) NetBeans Options UI. The caret blink
> > >
> > > rate and caret shape in insert and overwrite mode.
> > >
> > > What do you think about having a Caret tab in Editor Options in order to
> > >
> > > expose these properties? Or place those somewhere else? Or not place
> > >
> > > them at all or implement that as a custom plugin? So I'd like to hear
> > >
> > > the voice of the community. I fell myself confident enough to implement
> > >
> > > the required code.
> > >
> > > Personally I was fan of the non blinking block Caret.
> >
> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > >
> > > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > >
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> >
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Expose Caret Settings in Editor Options
Posted by Emilian Bold <em...@protonmail.ch>.
I dunno, I can't really compare -- last I heard about caret blink rate was years ago. I guess we could look at votes in the old Bugzilla to see the most requested features and such?
Anyhow, I'm not really bothered by this config being added, but the idea is not to add UI for everything.
> There can’t be enough Options to customize to your Needs.
Options increase the code complexity. The combinatorial explosion also makes testing complicated.
From an UI standpoint a noisy Options window will be hard to use.
I remember NetBeans used to have an 'Advanced' button which opened a bean tree view with basic Java beans settings. I guess something like that would make more sense for something as the cursor blink rate instead of a custom Swing panel. https://ui.netbeans.org/docs/hi/options/advancedOptions.html
--emi
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 13 May 2018 1:11 PM, Geertjan Wielenga <ge...@googlemail.com> wrote:
> I get your point and I think it's a very difficult balance to make. We
>
> don't want to overload the IDE with UI. However, at the same time, I don't
>
> see there being hundreds of requests for new configuration options,
>
> instead, I have seen about three or four coming up again and again, really,
>
> in total, in all the time I have been working on NetBeans since 2004. And
>
> this caret thing is one of them. So, it's not that bad, we're not being
>
> asked for much more than we already have, though this caret thing is one of
>
> them, I think it would be handy to have this one somewhere in the Options
>
> window, maybe within an existing panel rather than a whole new one which I
>
> think would be adding too much for this.
>
> Gj
>
> On Sun, May 13, 2018 at 11:54 AM, Emilian Bold emilian.bold@protonmail.ch
>
> wrote:
>
> > -0.5
> >
> > This seems like something a plugin could easily provide.
> >
> > Normal users would just use NetBeans and have a clean UI while users that
> >
> > search for more customisations just use the plugin.
> >
> > The important part is having the API support for this (which we do), not
> >
> > adding more and more UI.
> >
> > I feel the current Options window provides too much configuration.
> >
> > Otoh, people regularly seem to discover something they assumed impossible
> >
> > has a preference somewhere deep down. So, discoverability is quite bad.
> >
> > --emi
> >
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >
> > On 12 May 2018 7:52 PM, Laszlo Kishalmi laszlo.kishalmi@gmail.com wrote:
> >
> > > Dear all,
> > >
> > > We have a new feature request:
> > >
> > > https://issues.apache.org/jira/browse/NETBEANS-762 about changing the
> > >
> > > Caret blinking speed.
> > >
> > > AFAIK NetBeans has 3 caret settings available in its editor which can't
> > >
> > > be set in the new (post 3.x maybe) NetBeans Options UI. The caret blink
> > >
> > > rate and caret shape in insert and overwrite mode.
> > >
> > > What do you think about having a Caret tab in Editor Options in order to
> > >
> > > expose these properties? Or place those somewhere else? Or not place
> > >
> > > them at all or implement that as a custom plugin? So I'd like to hear
> > >
> > > the voice of the community. I fell myself confident enough to implement
> > >
> > > the required code.
> > >
> > > Personally I was fan of the non blinking block Caret.
> >
> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > >
> > > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > >
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> >
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Expose Caret Settings in Editor Options
Posted by Geertjan Wielenga <ge...@googlemail.com>.
I get your point and I think it's a very difficult balance to make. We
don't want to overload the IDE with UI. However, at the same time, I don't
see there being hundreds of requests for new configuration options,
instead, I have seen about three or four coming up again and again, really,
in total, in all the time I have been working on NetBeans since 2004. And
this caret thing is one of them. So, it's not that bad, we're not being
asked for much more than we already have, though this caret thing is one of
them, I think it would be handy to have this one somewhere in the Options
window, maybe within an existing panel rather than a whole new one which I
think would be adding too much for this.
Gj
On Sun, May 13, 2018 at 11:54 AM, Emilian Bold <em...@protonmail.ch>
wrote:
> -0.5
>
> This seems like something a plugin could easily provide.
>
> Normal users would just use NetBeans and have a clean UI while users that
> search for more customisations just use the plugin.
>
> The important part is having the API support for this (which we do), not
> adding more and more UI.
>
> I feel the current Options window provides too much configuration.
>
> Otoh, people regularly seem to discover something they assumed impossible
> has a preference somewhere deep down. So, discoverability is quite bad.
>
> --emi
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On 12 May 2018 7:52 PM, Laszlo Kishalmi <la...@gmail.com> wrote:
>
> > Dear all,
> >
> > We have a new feature request:
> >
> > https://issues.apache.org/jira/browse/NETBEANS-762 about changing the
> >
> > Caret blinking speed.
> >
> > AFAIK NetBeans has 3 caret settings available in its editor which can't
> >
> > be set in the new (post 3.x maybe) NetBeans Options UI. The caret blink
> >
> > rate and caret shape in insert and overwrite mode.
> >
> > What do you think about having a Caret tab in Editor Options in order to
> >
> > expose these properties? Or place those somewhere else? Or not place
> >
> > them at all or implement that as a custom plugin? So I'd like to hear
> >
> > the voice of the community. I fell myself confident enough to implement
> >
> > the required code.
> >
> > Personally I was fan of the non blinking block Caret.
> >
> >
> > ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> -----------------------------------------
> >
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> >
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Expose Caret Settings in Editor Options
Posted by Emilian Bold <em...@protonmail.ch>.
-0.5
This seems like something a plugin could easily provide.
Normal users would just use NetBeans and have a clean UI while users that search for more customisations just use the plugin.
The important part is having the API support for this (which we do), not adding more and more UI.
I feel the current Options window provides too much configuration.
Otoh, people regularly seem to discover something they assumed impossible has a preference somewhere deep down. So, discoverability is quite bad.
--emi
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 12 May 2018 7:52 PM, Laszlo Kishalmi <la...@gmail.com> wrote:
> Dear all,
>
> We have a new feature request:
>
> https://issues.apache.org/jira/browse/NETBEANS-762 about changing the
>
> Caret blinking speed.
>
> AFAIK NetBeans has 3 caret settings available in its editor which can't
>
> be set in the new (post 3.x maybe) NetBeans Options UI. The caret blink
>
> rate and caret shape in insert and overwrite mode.
>
> What do you think about having a Caret tab in Editor Options in order to
>
> expose these properties? Or place those somewhere else? Or not place
>
> them at all or implement that as a custom plugin? So I'd like to hear
>
> the voice of the community. I fell myself confident enough to implement
>
> the required code.
>
> Personally I was fan of the non blinking block Caret.
>
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Expose Caret Settings in Editor Options
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Yes, I think this would be a very useful enhancement and also really great
that you're confident to provide the related pull request!
Gj
On Sat, May 12, 2018 at 6:52 PM, Laszlo Kishalmi <la...@gmail.com>
wrote:
> Dear all,
>
> We have a new feature request: https://issues.apache.org/jira
> /browse/NETBEANS-762 about changing the Caret blinking speed.
>
> AFAIK NetBeans has 3 caret settings available in its editor which can't be
> set in the new (post 3.x maybe) NetBeans Options UI. The caret blink rate
> and caret shape in insert and overwrite mode.
>
> What do you think about having a Caret tab in Editor Options in order to
> expose these properties? Or place those somewhere else? Or not place them
> at all or implement that as a custom plugin? So I'd like to hear the voice
> of the community. I fell myself confident enough to implement the required
> code.
>
> Personally I was fan of the non blinking block Caret.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>