Move to Region
It would be nice if you could highlight any block of code and choose a
command such as "Move to Region" and you can see a list of all the regions
in your code and it will append that block inside of said region. Just a
thought.
Please sign in to leave a comment.
Derek,
do you mean that you'd like to select a member (field, method etc), choose
region in the
containing class and append the member to the region?
"Derek" <derek@btacinc.com> wrote in message
news:c5p4bj$8tj$1@is.intellij.net...
>
>
Yeah.It's just another means of refactoring. Like, I like to have all of my
Properties in a region, so when I make them, I usually make them there, but
when a property is made using the "Generate" Command in the Context Menu, it
doesn't put it there, so I've got to expand the Properties Region, Highlight
the Property, and move it down there. it's a simple task ,and it just looks
like being able to point and click would be a handy automation.
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c5p4ht$aad$1@is.intellij.net...
>
>
>> It would be nice if you could highlight any block of code and choose a
>> command such as "Move to Region" and you can see a list of all the
>> regions
>> in your code and it will append that block inside of said region. Just a
>> thought.
>>
>>
>
Generate will work better since build 78 and will place generated members
into a region if invoked inside one.
--
Andrey Simanovsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Derek" <derek@btacinc.com> wrote in message
news:c5p4lq$b0e$1@is.intellij.net...
my
but
it
Highlight
looks
>
choose
a
>
>
That's good. Or it would be nice to be able to set a region to automatically
generate things into in the settings.
"Andrey Simanovsky (JetBrains)" <ands@jetbrains.com> wrote in message
news:c5p51e$dem$1@is.intellij.net...
>
>
>
>> Yeah.It's just another means of refactoring. Like, I like to have all of
>> Properties in a region, so when I make them, I usually make them there,
>> when a property is made using the "Generate" Command in the Context Menu,
>> doesn't put it there, so I've got to expand the Properties Region,
>> the Property, and move it down there. it's a simple task ,and it just
>> like being able to point and click would be a handy automation.
>>
>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
>> news:c5p4ht$aad$1@is.intellij.net...
>> > Derek,
>> >
>> > do you mean that you'd like to select a member (field, method etc),
>> > region in the
>> > containing class and append the member to the region?
>> >
>> > "Derek" <derek@btacinc.com> wrote in message
>> > news:c5p4bj$8tj$1@is.intellij.net...
>> >> It would be nice if you could highlight any block of code and choose a
>> >> command such as "Move to Region" and you can see a list of all the
>> >> regions
>> >> in your code and it will append that block inside of said region. Just
>> >> thought.
>> >>
>> >>
>> >
>> >
>>
>>
>
Hello Derek,
I like that suggestion. Perhaps have a config page that will allow you to name default regions for members, properties, methods, and set the order in which they appear...
-Michael
>> Generate will work better since build 78 and will place generated
>> members
>> into a region if invoked inside one.
>> --
>> Andrey Simanovsky
>> Software Developer
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>> "Derek" <derek@btacinc.com> wrote in message
>> news:c5p4lq$b0e$1@is.intellij.net...
>>> Yeah.It's just another means of refactoring. Like, I like to have
>>> all of
>>>
>> my
>>
>>> Properties in a region, so when I make them, I usually make them
>>> there,
>>>
>> but
>>
>>> when a property is made using the "Generate" Command in the Context
>>> Menu,
>>>
>> it
>>
>>> doesn't put it there, so I've got to expand the Properties Region,
>>>
>> Highlight
>>
>>> the Property, and move it down there. it's a simple task ,and it
>>> just
>>>
>> looks
>>
>>> like being able to point and click would be a handy automation.
>>>
>>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in
>>> message news:c5p4ht$aad$1@is.intellij.net...
>>>
>>>> Derek,
>>>>
>>>> do you mean that you'd like to select a member (field, method etc),
>>>>
>> choose
>>
>>>> region in the
>>>> containing class and append the member to the region?
>>>> "Derek" <derek@btacinc.com> wrote in message
>>>> news:c5p4bj$8tj$1@is.intellij.net...
>>>>> It would be nice if you could highlight any block of code and
>>>>> choose a
>>>>> command such as "Move to Region" and you can see a list of all the
>>>>> regions
>>>>> in your code and it will append that block inside of said region.
>>>>> Just
>> a
>>
>>>>> thought.
>>>>>
automatically
It wouldn't be used by Alt-Insert anyway. It generates all members at the
position of the caret.
--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Derek" <derek@btacinc.com> wrote in message
news:c5p539$ehr$1@is.intellij.net...
automatically
>
members
of
Menu,
a
Just
>
>
The suggestion is feasible if and only if you group things by their kind, instead of grouping logically. I used to organized regions around the task they perform. E.g. for a control, I have a drawing region, behaviour region, layout region and sometimes implementation details region. From the Re#er point of view you can't decide region from the preconfigured data in this case.
Of course. I like to group, like, all my fields together, all my methods
together, my constructors together, and properties together. ..
"Ilya Ryzhenkov" <no_mail@jetbrains.com> wrote in message
news:31608413.1082406986942.JavaMail.javamailuser@localhost...
Well, for Re#er team we seem to be a good pair of C# developers with opposite point view :) We may be widening their "typical C# developer" profile, which is GREAT.
Well, I never group things like you. Different fields, constructors, methods and properties serve different purposes, and when I'm reviewing class in specific case I would like things to be grouped logically rather than physically. If I have a problem with painting, I want to expand the Painting region and see all the fields, methods and properties, that is anything to do with drawing. And why should I see ForeColor property if I'm dealing with expand/collapse behaviour of a TreeView-like control? It's just irrelevant.