issue-#99 Auto Upper Keywords

The features that we decide to not apply in the current time
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: issue-#99 Auto Upper Keywords

Post by Ivan Denisov »

In this form as Josef describing it exists. I am using it for a long time and it is good.

Two commands for menu:

Code: Select all

	SEPARATOR
	"#Cpc:&Capitalize"	"*F5"	"CpcEdit.Capitalize"	"TextCmds.FocusGuard"
	"#Cpc:&Capitalize & Expand"	"F5"	"CpcEdit.CapitalizeExpand"	"TextCmds.FocusGuard"
Attachments
CpcEdit.txt
(27.94 KiB) Downloaded 288 times
luowy
Posts: 234
Joined: Mon Oct 20, 2014 12:52 pm

Re: issue-#99 Auto Upper Keywords

Post by luowy »

this feature is not suitable for framework
Last edited by luowy on Wed Jan 27, 2016 3:37 pm, edited 1 time in total.
luowy
Posts: 234
Joined: Mon Oct 20, 2014 12:52 pm

Re: issue-#99 Auto Upper Keywords

Post by luowy »

this feature is not suitable for framework
Last edited by luowy on Wed Jan 27, 2016 3:38 pm, edited 1 time in total.
User avatar
Robert
Posts: 1024
Joined: Sat Sep 28, 2013 11:04 am
Location: Edinburgh, Scotland

Re: issue-#99 Auto Upper Keywords

Post by Robert »

luowy wrote:TextControllers {AutoIndent} Patch...
Thanks.

I had not meant this seriously, but as an example of the kind of automation I don't want too much of. There is always Visual Studio for people who like the other approach.

Actually I had no idea that the Framework already supports control of AutoIndent, which is why your patch is so simple.

But it raises some issues:

- Does it make sense to make AutoIndent a user option, but not AutoScroll (whatever that is)?
- Your proposal is not complete; there would also need to be some covering documentation written.
- If we respond to every suggested "I personally would like this little thing" how do we keep things as simple as possible, or ever get 1.7 released?


As a group I don't think we are very good at deciding if we want something before considering the details of how to implement it. I am not asking for more votes, but if more people said, early on, "I like this" or "I don't like this" I think some of our discussions would come to a consensus rather quicker.
luowy
Posts: 234
Joined: Mon Oct 20, 2014 12:52 pm

Re: issue-#99 Auto Upper Keywords

Post by luowy »

Robert wrote:
luowy wrote:TextControllers {AutoIndent} Patch...
Thanks.

I had not meant this seriously, but as an example of the kind of automation I don't want too much of. There is always Visual Studio for people who like the other approach.

Actually I had no idea that the Framework already supports control of AutoIndent, which is why your patch is so simple.

But it raises some issues:

- Does it make sense to make AutoIndent a user option, but not AutoScroll (whatever that is)?
- Your proposal is not complete; there would also need to be some covering documentation written.
- If we respond to every suggested "I personally would like this little thing" how do we keep things as simple as possible, or ever get 1.7 released?


As a group I don't think we are very good at deciding if we want something before considering the details of how to implement it. I am not asking for more votes, but if more people said, early on, "I like this" or "I don't like this" I think some of our discussions would come to a consensus rather quicker.
thanks you remind me.this feature is not suitable for the framework,so I will remove it.
let's stop it and work for other issue.
Ivan, please help me clean something about it.
luowy
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: issue-#99 Auto Upper Keywords

Post by Ivan Denisov »

LouWe, we can simply move it to Rejected subforum. That is normal case of Feature life-cycle:
1 somebody give an idea;
2 the demo was prepared;
3 during the discussion the author decide to not suggest it at the current moment;
4 topic is moving to the Rejected subforum to keep the discussion in our archive.
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: issue-#99 Auto Upper Keywords

Post by Josef Templ »

in addition, please clear the Target field in the Issue.
It should not contain "1.7" if it is rejected.

This is for avoiding any confusion when we later select
the issues related to 1.7.
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: issue-#99 Auto Upper Keywords

Post by Ivan Denisov »

Josef Templ wrote:in addition, please clear the Target field in the Issue.
It should not contain "1.7" if it is rejected.

This is for avoiding any confusion when we later select
the issues related to 1.7.
It was not set. Do not worry, Josef.
cfbsoftware
Posts: 204
Joined: Wed Sep 18, 2013 10:06 pm
Contact:

Re: issue-#99 Auto Upper Keywords

Post by cfbsoftware »

A note for whenever this feature request is reactivated: There has been a recent discussion of this issue on the ETH Oberon mailing list. Several existing solutions / alternative approaches have been proposed in the responses:

"[Oberon] Easier typing of capital letter keywords in Oberon"

http://lists.inf.ethz.ch/pipermail/oberon/2016/008771.html
Post Reply