mirror of
https://gitflic.ru/project/openide/openide.git
synced 2026-01-08 15:09:39 +07:00
[IFT] Apply simple proofreading changes
GitOrigin-RevId: 1139165559fcbe3c6c243a1b25036f32e9378938
This commit is contained in:
committed by
intellij-monorepo-bot
parent
00609098d7
commit
e4fbb03a2a
@@ -4,20 +4,20 @@ java.basic.completion.choose.first=You can choose the first item from the Lookup
|
||||
java.basic.completion.activate=To activate Basic Completion, press {0} and you will see the lookup menu again.
|
||||
java.basic.completion.choose.item=Select {0} inside the lookup menu and press {1}.
|
||||
java.basic.completion.complete=Press {0} to complete this statement.
|
||||
java.basic.completion.deeper.level=Sometimes you need to see suggestions for static constants or methods. \
|
||||
Press {0} twice to access extended Code Completion.
|
||||
java.basic.completion.deeper.level=Sometimes, you need to see suggestions for static constants or methods. \
|
||||
Press {0} twice to get them in the lookup.
|
||||
java.basic.completion.module.promotion=You will find more about refactorings in the {0} module.
|
||||
|
||||
java.run.configuration.lets.run=Any code marked with {0} can be run. Let''s run our simple example with {1}. \
|
||||
Alternatively, you can click {0} and select the {2} item.
|
||||
|
||||
java.postfix.completion.apply=Postfix Completion helps reduce backward caret jumps as you write code. \
|
||||
java.postfix.completion.apply=Postfix Completion helps you reduce backward caret jumps as you write code. \
|
||||
It lets you transform an already typed expression into another one based on the postfix you add, the type of expression, and its context. \
|
||||
Type {0} after the parenthesis to see the list of postfix completion suggestions. \
|
||||
Select {1} from the list, or type it in the editor, and then press {2} to complete the statement.
|
||||
Select {1} from the list or type it in the editor and then press {2} to complete the statement.
|
||||
|
||||
java.smart.type.completion.lesson.name=Smart type completion
|
||||
java.smart.type.completion.apply=Smart Type Completion filters the list of suggestion to include only those types that are applicable \
|
||||
java.smart.type.completion.apply=Smart Type Completion filters the list of suggestions to include only the types applicable \
|
||||
within the current context. Press {0} to see the list of matching suggestions. Choose the first one by pressing {1}.
|
||||
java.smart.type.completion.return=Smart Type Completion can also suggest code for a return statement. \
|
||||
Press {0} twice to see the Lookup menu for a return. Choose the first one by pressing {1}
|
||||
@@ -25,50 +25,50 @@ java.smart.type.completion.return=Smart Type Completion can also suggest code fo
|
||||
java.statement.completion.lesson.name=Statement completion
|
||||
java.statement.completion.complete.for=Press {0} to complete the {1} statement.
|
||||
java.statement.completion.complete.if=Type {0} and press {1} to generate the statement.
|
||||
java.statement.completion.complete.condition=Add a condition inside parentheses {0} and press {1} to jump inside the {2} statement.
|
||||
java.statement.completion.complete.finish.body=Type on one line: {0} and then press {1} to complete the entered statement and apply formatting.
|
||||
java.statement.completion.complete.condition=Add a condition inside the parentheses {0} and press {1} to jump into the {2} statement.
|
||||
java.statement.completion.complete.finish.body=Type a line of code: {0} and then press {1} to complete the statement and apply formatting.
|
||||
|
||||
java.rename.press.rename=Press {0} to rename field {1}.
|
||||
java.rename.type.new.name=Type the new name for this field (e.g., {0}) and press {1}.
|
||||
java.rename.confirm.accessors.rename=<ide/> is detecting corresponding getters/setters and proposes to rename them accordingly.\
|
||||
java.rename.type.new.name=Type a new name for this field (for example, {0}) and press {1}.
|
||||
java.rename.confirm.accessors.rename=<ide/> is detecting the corresponding getters/setters and suggests renaming them accordingly.\
|
||||
Now just press {0} or click {1}
|
||||
|
||||
java.refactoring.menu.inline.variable=Now let''s inline variable {0} into the only use. You can press {1} and filter the refactoring menu by \
|
||||
<strong>iv</strong> (<strong>i</strong>nline <strong>v</strong>ariable). Choose this item. Or just press {2}.
|
||||
java.refactoring.menu.introduce.constant=In the end, let''s extract extension from file name. \
|
||||
Again, you can press {0} and filter by <strong>ic</strong> (<strong>i</strong>ntroduce <strong>c</strong>onstant). Or just press {1}.
|
||||
java.refactoring.menu.confirm.constant=In this dialog you can choose the name, the parent and visibility for the new constant. \
|
||||
You can leave proposed defaults and press {0} or click {1}.
|
||||
java.refactoring.menu.inline.variable=Now let''s inline a variable {0} to reduce it to a single usage. You can press {1} and filter the refactoring menu by \
|
||||
<strong>iv</strong> (<strong>i</strong>nline <strong>v</strong>ariable). Choose this item or press {2}.
|
||||
java.refactoring.menu.introduce.constant=Finally, let''s extract an extension from the file name. \
|
||||
Again, you can press {0} and filter by <strong>ic</strong> (<strong>i</strong>ntroduce <strong>c</strong>onstant) or press {1}.
|
||||
java.refactoring.menu.confirm.constant=In this dialog, you can choose the new constant\u2019s type, name, parent class and visibility. \
|
||||
You can leave the defaults and press {0} or click {1}.
|
||||
|
||||
java.inheritance.hierarchy.lesson.name=Inheritance hierarchy
|
||||
java.inheritance.hierarchy.goto.implementation=Press {0} to look for implementations of {1}.
|
||||
java.inheritance.hierarchy.choose.any.implementation=Choose any implementation and press {0} (or click it by mouse).
|
||||
java.inheritance.hierarchy.navigate.to.base=You can navigate to a super method from derived. Press {0} or click icon {1} in the editor gutter.
|
||||
java.inheritance.hierarchy.choose.any.implementation=Choose any implementation and press {0} or click it.
|
||||
java.inheritance.hierarchy.navigate.to.base=You can navigate to a super method from derived. Press {0} or click the {1} icon in the editor gutter.
|
||||
java.inheritance.hierarchy.invoke.implementations.again=The declaration of the base method has its own gutter icon {0}. \
|
||||
Click it or press {1} again.
|
||||
java.inheritance.hierarchy.open.in.find.tool.window=For big hierarchies you may want to look for implementations in the {0} tool window. \
|
||||
Click at {1}.
|
||||
java.inheritance.hierarchy.open.in.find.tool.window=For big hierarchies, you might want to look for implementations in the {0} tool window. \
|
||||
Click {1}.
|
||||
java.inheritance.hierarchy.hide.find.tool.window=Press {0} to hide the {1} tool window.
|
||||
java.inheritance.hierarchy.open.method.hierarchy=You may want to explore the whole hierarchy for this method. Press {0}.
|
||||
java.inheritance.hierarchy.hide.method.hierarchy=Let''s hide {0} also. Press {1} again.
|
||||
java.inheritance.hierarchy.open.class.hierarchy=To overview the class hierarchy press {0}.
|
||||
java.inheritance.hierarchy.last.note=<strong>Note:</strong> Actions {0} and {1} can be applied to classes also. \
|
||||
Actions {2} and {3} may be used rarely but you always can find them with {4} by the {5} filter.
|
||||
java.inheritance.hierarchy.open.method.hierarchy=You might want to explore the whole hierarchy for this method. Press {0}.
|
||||
java.inheritance.hierarchy.hide.method.hierarchy=Let''s (also) hide {0} too. Press {1} again.
|
||||
java.inheritance.hierarchy.open.class.hierarchy=To view the class hierarchy, press {0}.
|
||||
java.inheritance.hierarchy.last.note=<strong>Note:</strong> Actions {0} and {1} can be also applied to classes. \
|
||||
Actions {2} and {3} are rarely used, but you can always find them with {4} using the {5} filter.
|
||||
|
||||
java.find.occurrences.lesson.name=Next/previous occurrences
|
||||
java.find.occurrences.invoke.find=For this lesson, we selected {0}. Press {1} to start the textual search through the current file.
|
||||
java.find.occurrences.find.previous=For previous occurrences, press {0}.
|
||||
java.find.occurrences.lesson.name=Next/previous occurrence
|
||||
java.find.occurrences.invoke.find=For this lesson, we selected {0}. Press {1} to start full-text search through the current file.
|
||||
java.find.occurrences.find.previous=To jump to the previous occurrence, press {0}.
|
||||
java.find.occurrences.find.next=<ide/> automatically copies the selected text into the search field. Let''s find the next occurrence. \
|
||||
Press {0} or {1}.
|
||||
java.find.occurrences.close.search.tool=With the search panel closed, you can still use these shortcuts to navigate between occurrences \
|
||||
of the item being searched for earlier. Let''s close the search panel by pressing {0}.
|
||||
java.find.occurrences.find.next.in.editor=Try to find the next occurrence with {0}.
|
||||
java.find.occurrences.find.previous.in.editor=And {0} in a back way.
|
||||
java.find.occurrences.note.about.cyclic=<strong>Note:</strong> The search is cyclic and pressing twice {0} at the last occurrence will set \
|
||||
the selection for the last occurrence. {1} is cyclic also.
|
||||
java.find.occurrences.close.search.tool=With the search panel closed, you can still use these shortcuts to navigate between \
|
||||
the recently found occurrences. Let''s close the search panel by pressing {0}.
|
||||
java.find.occurrences.find.next.in.editor=Locate the next occurrence with {0}.
|
||||
java.find.occurrences.find.previous.in.editor=And {0} to go backwards.
|
||||
java.find.occurrences.note.about.cyclic=<strong>Note:</strong> The search is cyclic and pressing {0} twice at the last occurrence will set \
|
||||
the selection for the last occurrence. {1} is cyclic too.
|
||||
|
||||
java.debug.workflow.rebuild=For big programs rerun can take much time. When you find some mistake in pure method you can just rebuild \
|
||||
the project and apply <strong>Hot Swap</strong> JVM feature. Let''s build project: {0} or {1}.
|
||||
java.debug.workflow.confirm.hot.swap=Confirm <strong>Hot Swap</strong> replacement.
|
||||
java.debug.workflow.drop.frame=We patched our method, but right now we are still executing old obsolete {0} and it will throw the \
|
||||
exception again. Let''s drop the frame and return to the state before {1} call. Click {2} at the debug panel or press {3}.
|
||||
java.debug.workflow.rebuild=For big programs, rerun can take a long time. When you find a mistake in a pure method, you can just rebuild \
|
||||
the project and apply the <strong>Hot Swap</strong> JVM feature. Let''s build the project: {0} or {1}.
|
||||
java.debug.workflow.confirm.hot.swap=Confirm the <strong>Hot Swap</strong> replacement.
|
||||
java.debug.workflow.drop.frame=We patched our method, but right now we are still executing obsolete {0}, and it will throw the \
|
||||
exception again. Let''s drop the frame and return to the state before the {1} call. Click {2} the debug panel or press {3}.
|
||||
|
||||
@@ -1,20 +1,23 @@
|
||||
### Dialog messages ###
|
||||
dialog.noSdk.title=Project SDK Problem
|
||||
dialog.noSdk.message=Cannot start learning: no SDK is specified for the current project.\nPlease specify the SDK for {0} in the Project Structure dialog.
|
||||
dialog.noSdk.message=Cannot start the course: no SDK is specified for the current project.\n\
|
||||
Specify an SDK for {0} in the Project Structure dialog.
|
||||
|
||||
dialog.learnProjectWarning.title=Open a Learning Project
|
||||
dialog.learnProjectWarning.message={0} will now create and open a new Learning Project.
|
||||
dialog.learnProjectWarning.message={0} will now create and open a new learning project.
|
||||
dialog.learnProjectWarning.ok=Open
|
||||
|
||||
dialog.askToSwitchToLearnProject.title=Learning Project Warning
|
||||
dialog.askToSwitchToLearnProject.message=<html>This lesson/module should be opened in {0} project. <br>Please switch to {0} project manually and start this lesson again.</html>
|
||||
dialog.askToSwitchToLearnProject.message=<html>This lesson/module should be opened in the {0} project. <br>\
|
||||
Switch to the {0} project manually and start this lesson again.</html>
|
||||
|
||||
learn.project.initializing.process=Prepare Learning Project
|
||||
learn.project.initializing.python.sdk.finding.progress.title=Finding Python SDKs
|
||||
learn.project.initializing.process=Prepare a Learning Project
|
||||
learn.project.initializing.python.sdk.finding.progress.title=Searching for Python SDKs
|
||||
learn.project.initializing.jdk.download.title=JDK Not Found
|
||||
learn.project.initializing.jdk.download.message=Not found already installed JDK. Download and install {0}?
|
||||
learn.project.initializing.jdk.download.message=Cannot find any installed JDK. Download and install {0}?
|
||||
learn.project.initializing.jdk.download.notification.title=Initialization
|
||||
learn.project.initializing.jdk.download.notification.message=The lesson will begin after the downloading and indexing of the SDK. It may take some time.
|
||||
learn.project.initializing.jdk.download.notification.message=The lesson will begin after the downloading and indexing of the SDK. \
|
||||
It may take some time.
|
||||
|
||||
learn.project.initializing.choose.place=Choose a Parent Directory for {0}
|
||||
learn.project.initializing.cannot.create.message=Cannot create a learning demo project. See the LOG files for more details.
|
||||
@@ -40,26 +43,28 @@ learn.new.ui.button.back=Back
|
||||
|
||||
### Congratulations panel ###
|
||||
learn.ui.course.completed.caption=Course completed
|
||||
learn.ui.course.completed.description=Congratulations, you've completed the course!\nStay tuned for new lessons helping you to be more productive with the IDE.
|
||||
learn.ui.course.completed.description=Congratulations, you've completed the course!\n\
|
||||
Stay tuned for new lessons helping you to be more productive with the IDE.
|
||||
|
||||
indexing.message=Please, wait for the indexing to be finished
|
||||
indexing.message=Wait for the indexing to be finished
|
||||
|
||||
learn.WelcomeScreen.StartLearn.text=Learn {0}
|
||||
learn.WelcomeScreen.StartLearn.description=Learn the shortcuts, actions and user interface of the IDE
|
||||
learn.WelcomeScreen.StartLearn.description=Learn shortcuts, actions, and elements of the user interface
|
||||
|
||||
### WELCOME_SCREEN ###
|
||||
learn.choose.language.caption=Choose a language to study
|
||||
learn.choose.language.description=We've found more than one language suitable for learning. Please select one to continue.
|
||||
learn.choose.language.caption=Choose a language to learn
|
||||
learn.choose.language.description=We've found more than one language suitable for learning. Select a language to continue.
|
||||
learn.choose.language.button=Start Learning
|
||||
learn.choose.language.dialog.title = Choose Study Language
|
||||
learn.choose.language.dialog.title = Choose a Learing Language
|
||||
### TOOL_WINDOW (these keys are used by LanguageChoosePanel dynamically, see training.learn.LearnBundle#messageInPlace) ###
|
||||
# suppress inspection "UnusedProperty"
|
||||
learn.choose.language.caption.tool.window=Choose a language to study
|
||||
learn.choose.language.caption.tool.window=Choose a language to learn
|
||||
# suppress inspection "UnusedProperty"
|
||||
learn.choose.language.description.tool.window=Select language for learning. All the result will be saved for a current language. To reset the result please click the Clear Results button.
|
||||
learn.choose.language.description.tool.window=Select a language for learning. All the results will be saved for the current language. \
|
||||
To reset the result, click the Clear Results button.
|
||||
# suppress inspection "UnusedProperty"
|
||||
learn.choose.language.button.tool.window=Continue Learning
|
||||
learn.choose.language.description.combo.box=Select language to learn about IDE features for it
|
||||
learn.choose.language.description.combo.box=Select a language to learn about the IDE features
|
||||
learn.choose.language.button.reset.tool.window=Clear Results
|
||||
|
||||
learn.project.read.only.hint=Demo project modification is disabled.
|
||||
@@ -69,10 +74,10 @@ learn.options.panel.name=Features Trainer
|
||||
learn.option.main.language=Learning main programming language
|
||||
learn.option.reset.progress=Reset Lessons Progress
|
||||
learn.option.reset.progress.dialog=Reset Lessons Progress
|
||||
learn.option.reset.progress.confirm=Do you want to forget all the learning progress?
|
||||
learn.option.reset.progress.confirm=Do you want to restart the course?
|
||||
|
||||
learn.restore.notification.modification.message=Unexpected sample modification
|
||||
learn.restore.notification.caret.message=The caret is in unexpected place
|
||||
learn.restore.notification.caret.message=The caret is in an unexpected place
|
||||
learn.restore.notification.editor.closed=The editor has been closed
|
||||
|
||||
action.learn.next.lesson.text=Next Non-Passed Lesson
|
||||
@@ -90,8 +95,8 @@ action.SetCurrentLessonAsPassed.text=Set Current Lesson as Passed
|
||||
|
||||
|
||||
dialog.message.jdk.ruby.required=Selected SDK should be Ruby SDK
|
||||
dialog.message.jdk.ruby.version.missed=SDK should have a version
|
||||
dialog.message.jdk.ruby.version.required=Ruby version should be at least 2.3
|
||||
dialog.message.jdk.ruby.version.missed=The SDK version is missing
|
||||
dialog.message.jdk.ruby.version.required=Ruby 2.3 or later is required
|
||||
|
||||
# Should be rarely used
|
||||
no.supported.languages.found=No supported languages found
|
||||
@@ -117,4 +122,4 @@ usages.tab.name=Usages of
|
||||
|
||||
welcome.tab.start.learning.button=Start Learning
|
||||
welcome.tab.header.learn.ide.features=Learn IDE Features
|
||||
welcome.tab.description.learn.ide.features=Learn basic shortcuts and essential features interactively with IDE Training Course.
|
||||
welcome.tab.description.learn.ide.features=Learn basic shortcuts and essential features interactively with the IDE Training Course.
|
||||
@@ -1,4 +1,4 @@
|
||||
### Ths file contains strings from lessons.
|
||||
### This file contains strings from lessons.
|
||||
|
||||
###############################################################################
|
||||
## Common lessons
|
||||
@@ -6,33 +6,33 @@
|
||||
|
||||
## Essential module
|
||||
essential.module.name=Essential
|
||||
essential.module.description=Catch the most essential capabilities of {0}
|
||||
essential.module.description=Discover the most essential capabilities of {0}
|
||||
|
||||
context.actions.lesson.name=Context actions
|
||||
context.actions.invoke.intentions.for.warning=In many cases, <ide/> can guess your <strong>intention</strong> or suggest you a fix for a \
|
||||
warning or an error. Let''s invoke one of the most useful actions, {0}. Press {1}.
|
||||
context.actions.invoke.intentions.for.warning=In many cases, <ide/> can guess your <strong>intention</strong> or propose a fix for a \
|
||||
warning or an error. Let''s invoke one of the most useful actions, {0}. Press {1}.
|
||||
context.actions.fix.warning=Let''s apply the first quick-fix to this warning: {0}.
|
||||
context.actions.invoke.general.intentions=<ide/> knows a lot about intentions! Try to invoke {0} every time you think there might be a \
|
||||
good solution or intention. You will save a lot of time and make the coding process much more fun! Now let''s look what we can apply to \
|
||||
the piece of code where the caret is. Press {1} again.
|
||||
context.actions.invoke.general.intentions=<ide/> has a lot of intentions! Try to invoke {0} every time you think there might be a \
|
||||
good solution or intention. You will save a lot of time and make the coding process much more fun! Now let''s look what we can apply to \
|
||||
the piece of code where the caret is. Press {1} again.
|
||||
context.actions.apply.intention=Let''s apply the {0} intention.
|
||||
context.actions.refactorings.promotion=Note that a lot of useful refactorings are not available with the help of {0}. \
|
||||
Go to the {1} module to learn how to invoke and use them.
|
||||
context.actions.refactorings.promotion=Note that a lot of useful refactorings are not available via {0}. \
|
||||
Go to the {1} module to learn how to invoke and use them.
|
||||
|
||||
## Editor basics module
|
||||
editor.basics.module.name=Editor basics
|
||||
editor.basics.module.description=Add, delete, select, move, and duplicate your code with smart shortcuts.
|
||||
|
||||
goto.action.lesson.name=Search for actions
|
||||
goto.action.mac.workaround=\nIf <strong>Terminal</strong> search opens instead of {0}, refer to <a href="{1}">this article</a>.
|
||||
goto.action.mac.workaround=\nIf the <strong>Terminal</strong> search opens instead of {0}, refer to <a href="{1}">this article</a>.
|
||||
goto.action.use.find.action=One of the most useful shortcuts is {0}. It lets you search through all available \
|
||||
actions without having to know their individual shortcuts. Try it now with {1}.\n\
|
||||
Alternatively, you can invoke {2} by pressing {3} two times in a row. By using {2}, you can look for your project code entities \
|
||||
Alternatively, you can invoke {2} by pressing {3} twice. By using {2}, you can look for your project code entities \
|
||||
<strong>and</strong> other IDE objects at the same time. It is up to you what to use.
|
||||
goto.action.invoke.about.action=Let''s say you want to learn about <ide/>, type {0} and press {1}.
|
||||
goto.action.invoke.about.action=For example, if you want to learn about <ide/>, type {0} and press {1}.
|
||||
goto.action.to.return.to.the.editor=Press {0} to return to the editor.
|
||||
goto.action.invoke.again=Also, you can use {0} or double {1} to change the settings. Try to invoke it again.
|
||||
goto.action.show.line.numbers.request=Type {0} to see {1} selector.
|
||||
goto.action.show.line.numbers.request=Type {0} to see the {1} selector.
|
||||
goto.action.first.lines.toggle=Switch the line numbers {0, choice, 0#off|1#on}.
|
||||
goto.action.second.lines.toggle=Now switch the line numbers back {0, choice, 0#on|1#off}.
|
||||
goto.action.propose.to.go.next.new.ui=Awesome! Just press {0} or click the button below to start the next lesson.
|
||||
@@ -47,13 +47,13 @@ collapse.all.expand=Similarly, press {0} to expand all available regions.
|
||||
|
||||
duplicate.and.delete.lines.lesson.name=Duplicate and delete lines
|
||||
duplicate.and.delete.lines.duplicate.line=Duplicate any line with {0}.
|
||||
duplicate.and.delete.lines.duplicate.several.lines=You can apply the same action to multiple lines too. \
|
||||
duplicate.and.delete.lines.duplicate.several.lines=You can apply the same action to multiple lines. \
|
||||
Simply select two or more lines and duplicate them with {0}.
|
||||
duplicate.and.delete.lines.delete.line=To delete the current line you can use action {0}.
|
||||
duplicate.and.delete.lines.delete.line=To delete the current line, you can use action {0}.
|
||||
|
||||
move.lesson.name=Move
|
||||
move.pull.down=Rearranging lines usually involves two actions: cut and paste. \
|
||||
With <ide/>, you can do it with just one. Press {0} to pull down the current line.
|
||||
With <ide/>, you can do it with just one action. Press {0} to pull down the current line.
|
||||
move.pull.up=Similarly, to pull a line up, press {0}.
|
||||
move.whole.method.up=Now try to move the whole method up with {0}.
|
||||
move.whole.method.down=Now move it down with {0}.
|
||||
@@ -68,19 +68,19 @@ multiple.selections.replace=Type {0} to replace all occurrences of {1} with {0}.
|
||||
selection.lesson.name=Expand and shrink the code selection
|
||||
selection.select.word=Place the caret before any word. Press {0} to move the caret to the next word and select everything in between.
|
||||
selection.extend.selection=Press {0} to extend the selection to the next code block.
|
||||
selection.extend.until.whole.file=Try to increase your selection with {0} until your whole file is selected.
|
||||
selection.shrink.selection={0} shrinks the selection. Try pressing it.
|
||||
selection.extend.until.whole.file=Try to increase your selection with {0} until the whole file is selected.
|
||||
selection.shrink.selection={0} shrinks the selection. Try it.
|
||||
|
||||
comment.line.lesson.name=Comment line
|
||||
comment.line.comment.any.line=Comment out any line with {0}.
|
||||
comment.line.uncomment.that.line=Uncomment the commented line with the same shortcut, {0}.
|
||||
comment.line.comment.several.lines=Select several lines and then comment them with {0}.
|
||||
comment.line.uncomment.that.line=Uncomment the commented line with the same shortcut. Press {0}.
|
||||
comment.line.comment.several.lines=Select several lines and then comment them out with {0}.
|
||||
|
||||
surround.and.unwrap.lesson.name=Surround and unwrap
|
||||
surround.and.unwrap.invoke.surround=Press {0} to surround the selected code fragment with some template code.
|
||||
surround.and.unwrap.choose.surround.item=Choose {0} item.
|
||||
surround.and.unwrap.invoke.unwrap=Let''s return to the initial file with the unwrapping action by {0}.
|
||||
surround.and.unwrap.choose.unwrap.item=Choose {0} item.
|
||||
surround.and.unwrap.choose.unwrap.item=Choose the {0} item.
|
||||
surround.and.unwrap.help.surround.code.fragments=Surround code fragments
|
||||
surround.and.unwrap.help.unwrapping.and.removing.statements=Unwrapping and removing statements
|
||||
|
||||
@@ -90,15 +90,15 @@ code.completion.module.description=Let the IDE complete your code. Try basic, sm
|
||||
|
||||
basic.completion.lesson.name=Basic completion
|
||||
basic.completion.start.typing=By default, <ide/> proposes completion for your code instantly. \
|
||||
Start typing {0} right where the caret is, and you will see the Lookup Menu with matching suggestions.
|
||||
basic.completion.continue.typing=Continue typing {0} unless it becomes the first item.
|
||||
Start typing {0} right where the caret is, and you will see the completion list with matching suggestions.
|
||||
basic.completion.continue.typing=Continue typing {0} until it becomes the first item.
|
||||
basic.completion.just.press.to.complete=Now just press {0} to complete this statement.
|
||||
basic.completion.activate.explicitly=To activate Basic Completion explicitly, press {0}.
|
||||
basic.completion.activate.explicitly=To activate basic completion explicitly, press {0}.
|
||||
basic.completion.finish.explicit.completion=Select {0} and press {1}.
|
||||
|
||||
completion.with.tab.lesson.name=Completion with tab
|
||||
completion.with.tab.begin.completion=Press {0} to show completion options.
|
||||
completion.with.tab.finish.with.tab=Choose {0}, for example, and press {1}. \
|
||||
completion.with.tab.begin.completion=Press {0} to show the completion suggestions.
|
||||
completion.with.tab.finish.with.tab=For example, choose {0} and press {1}. \
|
||||
This replaces the word at the caret rather than simply inserts it.
|
||||
|
||||
postfix.completion.lesson.name=Postfix completion
|
||||
@@ -111,32 +111,32 @@ refactorings.module.description=Make your code neat with rename, extract, and ot
|
||||
rename.lesson.name=Rename
|
||||
|
||||
refactoring.menu.lesson.name=Refactoring menu
|
||||
refactoring.menu.show.refactoring.list=<ide/> supports a variety of refactorings. Many of them have own shortcuts. \
|
||||
But for rare refactorings you can press {0} and preview a partial list of them.
|
||||
refactoring.menu.show.refactoring.list=<ide/> supports a variety of refactorings. Many of them have their own shortcuts. \
|
||||
But for rare refactorings, you can press {0} and preview a partial list of them.
|
||||
refactoring.menu.introduce.parameter=Suppose we want to replace this expression with a parameter. So we need to choose {0}. \
|
||||
Now simply type <strong>pa</strong> (introduce <strong>pa</strong>rameter) or \
|
||||
<strong>ip</strong> (<strong>i</strong>ntroduce <strong>p</strong>arameter) to reduce the proposed list.
|
||||
refactoring.menu.start.refactoring=Press {0} to start the {1} refactoring. \
|
||||
<strong>Note</strong> that you can learn refactoring shortcuts from the Refactoring menu.
|
||||
refactoring.menu.finish.refactoring=To complete refactoring, you need to choose some name or leave it as default and press {0}.
|
||||
<strong>Note</strong> that you can learn refactoring shortcuts from the refactoring menu.
|
||||
refactoring.menu.finish.refactoring=To complete refactoring, you need to choose some name or leave the default one and press {0}.
|
||||
|
||||
## Code Assistance module
|
||||
code.assistance.module.name=Code assistance
|
||||
code.assistance.module.description=Learn how to format you code, obtain parameter info, and preview quick popups.
|
||||
code.assistance.module.description=Learn how to format your code, obtain parameter info, and preview quick popups.
|
||||
|
||||
code.format.lesson.name=Code format
|
||||
code.format.reformat.selection=IDE can help you correct code formatting with just one action. \
|
||||
to reformat the selected code fragment with {0}.
|
||||
code.format.reformat.selection=<ide/> can help you correct code formatting with just one action. \
|
||||
to reformat the selected code fragment with {0}.
|
||||
code.format.reformat.file=To reformat the whole file when no lines are selected, use {0}.
|
||||
code.format.show.reformat.file.dialog=Use {0} to show reformat settings.
|
||||
code.format.optimize.imports=Here you can configure reformat options. For example, switch {0} on and click {1}.
|
||||
|
||||
parameter.info.lesson.name=Parameter info
|
||||
parameter.info.use.action=Press {0} to see the method signature.
|
||||
parameter.info.use.action=Press {0} to see the method''s signature.
|
||||
parameter.info.add.parameters=Use a width of {0} and a height of {1}.
|
||||
|
||||
quick.popups.lesson.name=Quick popups
|
||||
quick.popups.show.documentation=Press {0} to see documentation for the symbol at the caret.
|
||||
quick.popups.show.documentation=Press {0} to see the documentation for the symbol at the caret.
|
||||
quick.popups.press.escape=Press {0} to close the popup.
|
||||
quick.popups.show.implementation=Press {0} to see the definition of the symbol at the caret.
|
||||
|
||||
@@ -144,78 +144,78 @@ editor.coding.assistance.lesson.name=Editor coding assistance
|
||||
editor.coding.assistance.goto.next.error=Press {0} to go to the next highlighted error in the file.
|
||||
editor.coding.assistance.fix.error=Let''s fix this error. Press {0} and select {1}.
|
||||
editor.coding.assistance.goto.next.warning=Let''s go to the next warning. Press {0}.
|
||||
editor.coding.assistance.show.warning.description=Also, you can show description of the warning or error at the caret. \
|
||||
Press {0} to show a short description and press {0} again to expand it.
|
||||
editor.coding.assistance.show.warning.description=Also, you can see the warning or error description of the item at the caret. \
|
||||
Press {0} to see a short description and press {0} again to expand it.
|
||||
editor.coding.assistance.fix.warning=Let''s fix this warning too. Press {0} and select {1}.
|
||||
editor.coding.assistance.highlight.usages=Another useful tool is usages highlighting. \
|
||||
editor.coding.assistance.highlight.usages=Another useful tool is the usages highlighting. \
|
||||
Press {0} to highlight all usages of the symbol at the caret within the file.
|
||||
|
||||
## Navigation module
|
||||
navigation.module.name=Navigation
|
||||
navigation.module.description=Jump to source, navigate to declaration, implementation, and file structure.
|
||||
navigation.module.description=Jump to source, navigate to declarations, implementations, and a file structure.
|
||||
|
||||
declaration.and.usages.lesson.name=Declaration and usages
|
||||
declaration.and.usages.jump.to.declaration=Press {0} to jump to the declaration of a method.
|
||||
declaration.and.usages.show.usages=Now the caret is at the method declaration. \
|
||||
declaration.and.usages.show.usages=Now the caret is at the method''s declaration. \
|
||||
Use the same shortcut {0} to see all of its usages, then select one of them.
|
||||
declaration.and.usages.find.usages=Press {0} to see a more detailed view of usages. You can invoke {0} on either a declaration or usage.
|
||||
declaration.and.usages.pin.motivation=From the {0} view you can navigate to both usages and declarations. \
|
||||
declaration.and.usages.find.usages=Press {0} to see a more detailed view of usages. You can invoke {0} on either a declaration or a usage.
|
||||
declaration.and.usages.pin.motivation=From the {0} view you can navigate both to usages and declarations. \
|
||||
The next search will override these results in the {0} view. To prevent it, pin the results:
|
||||
declaration.and.usages.right.click.tab=Right click the tab title, {0}.
|
||||
declaration.and.usages.right.click.tab=Right-click the tab title, {0}.
|
||||
declaration.and.usages.select.pin.item=Select {0}.
|
||||
declaration.and.usages.hide.view=When you have finished browsing usages, press {0} to hide the view.
|
||||
declaration.and.usages.open.find.view=Press {0} to open the {1} view again.
|
||||
|
||||
file.structure.lesson.name=File structure
|
||||
file.structure.open.popup=A large source file can be difficult to read and navigate, sometimes you only need to preview it. \
|
||||
file.structure.open.popup=A large source file can be difficult to read and navigate. Sometimes you only need to preview it. \
|
||||
Press {0} to open the file structure.
|
||||
file.structure.request.prefixes=Suppose you want to find some method with {0} and {1} words in its name. \
|
||||
Type {2} (prefixes of the required words) to filter file structure.
|
||||
file.structure.request.prefixes=Suppose you want to find a method with {0} and {1} words in its name. \
|
||||
Type {2} (prefixes of the required words) to filter the file structure.
|
||||
file.structure.navigate=Only one item remains. Now press {0} to jump to the selected item.
|
||||
file.structure.toolwindow=<ide/> can also show you the file structure as a tool window. Open it with {0}.
|
||||
|
||||
recent.files.lesson.name=Recent files and locations
|
||||
recent.files.first.transition=Wondering how the {0} method is implemented? Let''s go to its declaration using {1}.
|
||||
recent.files.dialog.message=We want to simulate a basic workflow: quick navigation between files. \
|
||||
Please don't move the mouse until we stop.
|
||||
Don''t move the mouse until we finish.
|
||||
recent.files.dialog.title=Workflow Simulation
|
||||
recent.files.show.recent.files=We dived deeply into the library files. How can we get back to our file? IDE has a feature that can help us \
|
||||
to show recently opened files. Use {0}.
|
||||
recent.files.show.recent.files=We dived deeply into the library files. How can we get back to our file? <ide/> has a feature that can help us \
|
||||
show recently opened files. Press {0}.
|
||||
recent.files.search.typing=You can search the file by its name. Type {0} (prefixes of the required words).
|
||||
recent.files.search.jump=Only one file remains. Now press {0} to jump to the selected file.
|
||||
recent.files.use.recent.files.again=We are back to our file. But let''s show recent files again using {0}.
|
||||
recent.files.delete=This list contains many source files that we no longer want to visit. Let''s delete {0} files from \
|
||||
our recent files history using {1}.
|
||||
recent.files.close.popup=Now the history of our recent files is more cleaner. Click on the editor to close the popup or use {0}.
|
||||
recent.files.show.recent.locations=Another useful action can show you code in recently visited locations. Use {0}.
|
||||
recent.files.use.recent.files.again=We are back to our file. But let''s view the recent files again by using {0}.
|
||||
recent.files.delete=This list contains many source files that we don''t want to open anymore. Let''s delete {0} files from \
|
||||
our recent files history by using {1}.
|
||||
recent.files.close.popup=Now the history of our recent files is cleaner. Click somewhere outside the popup to close it or use {0}.
|
||||
recent.files.show.recent.locations=Another useful action can show you the code in the recently visited locations. Use {0}.
|
||||
recent.files.locations.search.typing=Here you can search by code fragments that you remember. Type {0}
|
||||
recent.files.locations.search.jump=Now press {0} to jump to the selected code fragment.
|
||||
|
||||
search.everywhere.lesson.name=Search everywhere
|
||||
search.everywhere.invoke.search.everywhere=To open {0} you need to press {1} two times in a row.
|
||||
search.everywhere.type.prefixes=Suppose you are looking for a class with {0} and {1} words in the name. \
|
||||
Type {2} (prefixes of the required words) to the search field.
|
||||
search.everywhere.navigate.to.class=Select {0} by keyboard arrows and press {1} to jump to the definition of this class.
|
||||
search.everywhere.invoke.search.everywhere=To open {0} you need to press {1} twice.
|
||||
search.everywhere.type.prefixes=Suppose you are looking for a class with the {0} and {1} words in the name. \
|
||||
Type {2} (prefixes of the required words) in the search field.
|
||||
search.everywhere.navigate.to.class=Select {0} by using the keyboard arrows and press {1} to jump to the definition of this class.
|
||||
search.everywhere.goto.class=Great! But sometimes it can be inconvenient to see files, classes, and variables in the search tool window. \
|
||||
Use {0} to find only classes and search only in special places.
|
||||
search.everywhere.type.class.name=Suppose you need some library class responsible for buffered reading from input stream. \
|
||||
search.everywhere.type.class.name=Suppose you need some library class responsible for buffered reading from an input stream. \
|
||||
Type {0} (prefixes of the required words). But do not navigate to it yet!
|
||||
search.everywhere.use.all.places=Now you see a class inside this demo project. However, we need to find it''s implementation in libraries. \
|
||||
Let''s switch {0} filter to {1} and you will see the content of available libraries.
|
||||
search.everywhere.use.all.places=Now you see a class inside this demo project. However, we need to find its implementation in libraries. \
|
||||
Let''s switch the {0} filter to {1}, and you will see the content of available libraries.
|
||||
search.everywhere.quick.documentation=Press {0} to preview available documentation.
|
||||
search.everywhere.finish=<strong>Done!</strong> In the same way you can use {0} to look for a method or global variable and use {1} \
|
||||
search.everywhere.finish=<strong>Done!</strong> In the same way, you can use {0} to look for a method or global variable and use {1} \
|
||||
to look for a file.
|
||||
search.everywhere.navigation.promotion=You will find other navigation actions and workflow use cases in the {0} module.
|
||||
|
||||
extract.method.lesson.name=Extract method
|
||||
extract.method.invoke.action=Press {0} to extract the selected code block into a method.
|
||||
extract.method.start.refactoring=Click {0} to start refactoring.
|
||||
extract.method.confirm.several.replaces=Cocktail Sort has two swap places. The first fragment has just been extracted. \
|
||||
extract.method.confirm.several.replaces=Cocktail sort has two swap places. The first fragment has just been extracted. \
|
||||
Click {0} to extract both of them.
|
||||
extract.method.second.fragment=Now you can confirm or reject the replacement of the second fragment.
|
||||
|
||||
extract.variable.lesson.name=Extract variable
|
||||
extract.variable.start.refactoring=Press {0} to extract a local variable from the selected expression {1}.
|
||||
extract.variable.start.refactoring=Press {0} to extract a local variable from the {1} expression.
|
||||
extract.variable.replace.all=This code block contains 3 occurrences of the selected expression. \
|
||||
Choose the second item on the list to replace all of them.
|
||||
extract.variable.choose.name=Choose a name for the new variable or leave it as it is. Press {0} to complete the refactoring.
|
||||
@@ -226,45 +226,45 @@ run.debug.module.description=Run your code and fix errors with the IDE visual de
|
||||
|
||||
run.configuration.lesson.name=Run configuration
|
||||
run.configuration.hide.toolwindow=<ide/> automatically opened the {0} tool window. \
|
||||
Tip: at the top of the {0} tool window you can see the full run command. Now let''s hide the tool window with {1}.
|
||||
run.configuration.temporary.to.permanent=For each new run <ide/> create temporary run configuration. \
|
||||
Tip: at the top of the {0} tool window, you can see the full run command. Now let''s hide the tool window with {1}.
|
||||
run.configuration.temporary.to.permanent=For each new run, <ide/> creates a temporary run configuration. \
|
||||
Temporary configurations are automatically deleted if the default limit of five is reached. \
|
||||
Let''s convert the temporary configuration into a permanent one. Open the drop-down menu with run configurations.
|
||||
run.configuration.select.save.configuration=Select {0}.
|
||||
run.configuration.edit.configuration=Suppose you want to change a configuration or create another one manually. \
|
||||
Then you need to open the drop-down menu again and click {0}. Alternatively you can use {1} action.
|
||||
Then you need to open the drop-down menu again and click {0}. Alternatively, you can use the {1} action.
|
||||
run.configuration.settings.description=This is a place for managing run/debug configurations. \
|
||||
You can set here program parameters, JVM arguments, environment variables, and so on.
|
||||
run.configuration.tip.about.save.configuration.into.file=Tip: Sometimes you may want to save a configuration to its own file. \
|
||||
Such configurations will be easy to share between colleagues (usually by the version control system). \
|
||||
Here you can set program parameters, JVM arguments, environment variables, and so on.
|
||||
run.configuration.tip.about.save.configuration.into.file=Tip: Sometimes you might want to save a configuration to its own file. \
|
||||
Such configurations will be easy to share between colleagues (usually, by using a version control system). \
|
||||
Now close the settings dialog to finish this lesson.
|
||||
|
||||
debug.workflow.lesson.name=Debug workflow
|
||||
debug.workflow.incorrect.breakpoints=Breakpoints are set incorrectly for this lesson.
|
||||
debug.workflow.run.program=Before debugging let''s run the program and see what is going wrong {0}.
|
||||
debug.workflow.toggle.breakpoint=So, there is a problem. Let''s start investigation with placing breakpoint. \
|
||||
To toggle a breakpoint you should click left editor gutter or just press {0}.
|
||||
debug.workflow.start.debug=To start debug selected run configuration, click {0} or press {1}.
|
||||
debug.workflow.need.restart.lesson=Debug session has been stopped. Need to restart lesson.
|
||||
debug.workflow.return.to.editor=Many trace actions will focus debug toolwindow. Let''s return to the editor with {0}.
|
||||
debug.workflow.run.program=Before debugging, let''s run the program and see what is going wrong {0}.
|
||||
debug.workflow.toggle.breakpoint=So, there is a problem. Let''s start investigation by placing a breakpoint. \
|
||||
To set a breakpoint, you click the editor gutter or just press {0}.
|
||||
debug.workflow.start.debug=To start debugging the selected run configuration, click {0} or press {1}.
|
||||
debug.workflow.need.restart.lesson=The debug session has been stopped. Restart the lesson.
|
||||
debug.workflow.return.to.editor=Many trace actions shift focus to the debug tool window. Let''s return to the editor with {0}.
|
||||
debug.workflow.use.watches=<ide/> has several ways to show variable values. For this step, we selected the call. Let''s add it to {0}. \
|
||||
You can copy the expression into the clipboard, click {1} button on the debug panel and paste the copied text. \
|
||||
You can copy the expression to the clipboard, click the {1} button on the debug tool window, and paste the copied text. \
|
||||
Alternatively, you can just use action {2} {3}.
|
||||
debug.workflow.consider.to.add.a.shortcut=(consider to assign a shortcut for it later)
|
||||
debug.workflow.step.into=Lets step into. You can use action {0} or the button {1} at the debug panel.
|
||||
debug.workflow.choose.method.to.step.in=In most cases you will want to skip argument calculating so Smart Step Into feature suggest by \
|
||||
default the wrapping method. However, here we need to choose the second one: {0}. \
|
||||
You can choose it by keyboard {1} and press {2}, or you can click the call.
|
||||
debug.workflow.consider.to.add.a.shortcut=(consider assigning a shortcut for it later)
|
||||
debug.workflow.step.into=Let''s step into. You can use the {0} action or the {1} option on the debug panel.
|
||||
debug.workflow.choose.method.to.step.in=In most cases, you might want to skip argument calculating, so the Smart Step Into feature suggests \
|
||||
the wrapping method by default. However, here we need to choose the second one: {0}. \
|
||||
You can choose it with the keyboard {1} and press {2}, or you can click the call.
|
||||
debug.workflow.quick.evaluate=Let''s see what we are going to pass to {0}. Invoke Quick Evaluate Expression {1} for the selected argument.
|
||||
debug.workflow.fix.error=Oh, we made a mistake in the array index! Let''s fix it right now. Close popup ({0}) and change 0 to 1.
|
||||
debug.workflow.step.over=Let''s check that the call of {0} will not throw an exception now. Use Step Over action {1} or click the button {2}.
|
||||
debug.workflow.mute.breakpoints=Ups, the same breakpoint again. Now we don''t need to stop at this breakpoint. \
|
||||
So, let''s mute breakpoints by clicking the button {0} or with the action {1}.
|
||||
debug.workflow.fix.error=Oh, we made a mistake in the array index! Let''s fix it right now. Close the ({0}) popup and change 0 to 1.
|
||||
debug.workflow.step.over=Let''s check if the call of {0} will not throw an exception now. Use the Step Over action {1} or click the {2} option.
|
||||
debug.workflow.mute.breakpoints=Oops, the same breakpoint again. Now we don''t need to stop at this breakpoint. \
|
||||
So, let''s mute breakpoints by clicking the {0} option or with the {1} action.
|
||||
debug.workflow.run.to.cursor=Let''s check the result of {0}. We''ve moved the editor cursor to the {1} statement. \
|
||||
Press {2} or click {3}. Alternatively, click the line number. Note that {4} works even if breakpoints are muted.
|
||||
debug.workflow.evaluate.expression=It seems the {0} is not an average value we want to find. We forgot to divide by length. \
|
||||
Seems we need to return {1}. Let''s check the guess. Press {2} or click button {3}.
|
||||
debug.workflow.evaluate.expression=It seems the {0} value is not an average value we want to find. We forgot to divide it by length. \
|
||||
It seems we need to return {1}. Let''s check the guess. Press {2} or click the {3} option.
|
||||
debug.workflow.type.result=Type {0} into the {1} field, completion works.
|
||||
debug.workflow.evaluate.it=Press {0} or click {1}.
|
||||
debug.workflow.stop.debug=It will be a correct answer! Lets close the dialog and stop debugging by {0} or button {1}.
|
||||
debug.workflow.resume=Seems there are no exceptions by now. Let''s continue execution with {0} or click the button {1}.
|
||||
debug.workflow.stop.debug=It is a correct answer! Let''s close the dialog and stop debugging with {0} or the {1} button.
|
||||
debug.workflow.resume=It seems there are no exceptions by now. Let''s continue execution with {0} or by clicking the {1} button.
|
||||
|
||||
@@ -1,61 +1,61 @@
|
||||
python.f.string.completion.lesson.name=F-string completion
|
||||
python.f.string.completion.type.prefix=<ide/> supports automatic f-string conversion. Just start to type {0}.
|
||||
python.f.string.completion.type.prefix=<ide/> supports automatic f-string conversion. Just start typing {0}.
|
||||
python.f.string.completion.invoke.manually=You can invoke completion manually with {0}.
|
||||
python.f.string.completion.complete.it=Complete the statement with {0}. Just press {1} to apply the first item.
|
||||
python.f.string.completion.result.message=You may see that a simple Python string was replaced by f-string after the completion.
|
||||
|
||||
python.postfix.completion.select.item=Select {0} item from completion list.
|
||||
python.postfix.completion.select.item=Select {0} item from the completion list.
|
||||
|
||||
python.smart.completion.lesson.name=Smart completion
|
||||
python.smart.completion.try.basic.completion=Try to use Basic Completion by pressing {0}.
|
||||
python.smart.completion.use.smart.completion=Unfortunately <ide/> has no direct information about {0} type. \
|
||||
But sometimes it can guess completion by the context! Use {1} to invoke Smart Completion.
|
||||
python.smart.completion.finish.completion=Now just choose {0} item to finish this lesson.
|
||||
python.smart.completion.try.basic.completion=Try using Basic Completion by pressing {0}.
|
||||
python.smart.completion.use.smart.completion=Unfortunately, <ide/> has no direct information on the {0} type. \
|
||||
But sometimes, it can suggest completion by the context! Use {1} to invoke Smart Completion.
|
||||
python.smart.completion.finish.completion=Now just choose the {0} item to finish this lesson.
|
||||
|
||||
python.tab.completion.lesson.name=Tab completion
|
||||
python.tab.completion.start.completion=Suppose you want to replace {0} with {1}. Invoke completion by pressing {2}.
|
||||
python.tab.completion.select.item=Select item {0} by keyboard arrows or just start typing it.
|
||||
python.tab.completion.use.tab.completion=If you press {0} you will insert {1} before {2}. Instead press {3} to replace {2} with {1}.
|
||||
python.tab.completion.start.completion=Suppose that you want to replace {0} with {1}. Invoke completion by pressing {2}.
|
||||
python.tab.completion.select.item=Select the {0} item using the keyboard arrows or just start typing it.
|
||||
python.tab.completion.use.tab.completion=If you press {0}, you will insert {1} before {2}. Instead, press {3} to replace {2} with {1}.
|
||||
|
||||
python.in.place.refactoring.lesson.name=In-place refactoring
|
||||
python.in.place.refactoring.start.type.new.name=Let''s consider an alternative approach to performing refactorings. \
|
||||
Suppose we want to rename local variable {0} to {1}. Just start typing the new name.
|
||||
Suppose that we want to rename the local variable {0} to {1}. Just start typing the new name.
|
||||
python.in.place.refactoring.invoke.intentions=<ide/> is guessing that you are going to rename the variable. \
|
||||
You can notice it by the icon {0} in the left editor gutter. Invoke intentions by {1} when you finish typing the new name.
|
||||
You can notice it by the {0} icon in the gutter. Invoke intentions by {1} when you finish typing the new name.
|
||||
python.in.place.refactoring.finish.rename=Press {0} to finish rename.
|
||||
python.in.place.refactoring.add.parameter=Let''s add an argument to this method. We place the editor caret just after the first parameter. \
|
||||
Now type comma and parameter''s name: {0}.
|
||||
python.in.place.refactoring.invoke.intention.for.parameter=<ide/> is guessing that you are going to change the method signature. \
|
||||
You can notice it by the same icon {0} at the left editor gutter. Invoke intentions by {1} when you finish typing the new parameter.
|
||||
Now type a comma and parameter''s name: {0}.
|
||||
python.in.place.refactoring.invoke.intention.for.parameter=<ide/> expects that you are going to change the method''s signature. \
|
||||
You can notice it by seeing the same icon {0} in the gutter. When you finish typing the new parameter\u2019s name, invoke intentions by pressing {1}.
|
||||
python.in.place.refactoring.update.callers=Press {0} to update the callers.
|
||||
python.in.place.refactoring.signature.preview=<ide/> is showing you the short signature preview. Press {0} to continue.
|
||||
python.in.place.refactoring.set.default.value=Now you need to type the value which will be inserted as an argument into each call. \
|
||||
python.in.place.refactoring.set.default.value=Now you need to type the value that will be inserted as an argument into each call. \
|
||||
You can choose {0} for this sample. Then press {1} to continue.
|
||||
python.in.place.refactoring.remark.about.application.scope=Note: In-place refactoring may be applied only in the \
|
||||
definition point whiles direct invocation of rename or change-signature refactorings may be called from both definition and usage.
|
||||
|
||||
python.quick.fix.refactoring.lesson.name=Quick fix refactoring
|
||||
python.quick.fix.refactoring.type.new.argument=Several refactorings can be performed as quick fixes. \
|
||||
python.quick.fix.refactoring.lesson.name=Quick-fix refactoring
|
||||
python.quick.fix.refactoring.type.new.argument=Several refactorings can be performed as quick-fixes. \
|
||||
Suppose we want to add a parameter to the method {0} and pass the variable {1} to it. Let''s type {2} after the first argument.
|
||||
python.quick.fix.refactoring.wait.completion.showed=Wait a little bit for the completion list...
|
||||
python.quick.fix.refactoring.close.completion.list=For now, we don''t want to apply any completion. Close the list ({0}).
|
||||
python.quick.fix.refactoring.invoke.intentions=As you may notice, <ide/> is showing you a warning here. Let''s invoke intentions by {0}.
|
||||
python.quick.fix.refactoring.choose.change.signature=Choose {0} quick fix.
|
||||
python.quick.fix.refactoring.invoke.intentions=As you might have noticed, <ide/> is showing you a warning here. Let''s invoke intentions by pressing {0}.
|
||||
python.quick.fix.refactoring.choose.change.signature=Choose the {0} quick fix.
|
||||
python.quick.fix.refactoring.select.new.parameter=Let''s set the default value for the new parameter. Click the new parameter line. \
|
||||
Alternatively, you can set focus to the parameter without a mouse by {0} and then {1}.
|
||||
python.quick.fix.refactoring.set.default.value=You may navigate through the fields (and the checkbox) by using {0}. \
|
||||
With the checkbox, you can let <ide/> inline the default value to the other callers or set it as the default value for the new parameter. \
|
||||
The Signature Preview will help you understand the difference. Now set the default value as 0.
|
||||
Alternatively, you can switch focus to the parameter by pressing {0} and then {1}.
|
||||
python.quick.fix.refactoring.set.default.value=You may navigate through the fields and the checkbox by using {0}. \
|
||||
With the checkbox selected, <ide/> either inlines the default value to the other callers or sets it as the default value for the new parameter. \
|
||||
The Signature Preview will help you understand the difference. Now set the default value to 0.
|
||||
python.quick.fix.refactoring.finish.refactoring=Press {0} (or click {1}) to finish the refactoring.
|
||||
|
||||
python.rename.press.rename=Press {0} to rename field {1} (e.g., to {2}).
|
||||
python.rename.expand.dynamic.references=In simple cases {0} will just rename without confirmation. \
|
||||
But in this sample, <ide/> detects two calls of {0} method for objects with unknown types. Expand {1} item.
|
||||
python.rename.exclude.item=It seems {0} should be excluded from rename. Select it and press {1}.
|
||||
python.rename.finish.refactoring=Now just finish the rename with the {0} button.
|
||||
python.rename.press.rename=Press {0} and rename the {1} field(e.g., to {2}).
|
||||
python.rename.expand.dynamic.references=In simple cases, {0} will just perform the rename refactoring without confirmation. \
|
||||
But in this sample, <ide/> detects two calls of the {0} method for objects with unknown types. Expand the {1} item.
|
||||
python.rename.exclude.item=It seems that {0} should be excluded from the rename refactoring. Select it and press {1}.
|
||||
python.rename.finish.refactoring=Finish the rename refactoring with the {0} button.
|
||||
|
||||
python.editor.coding.assistance.fix.error=Let''s fix this error. Press {0} and select {1} or {2} <strong>\u2192 math</strong>
|
||||
|
||||
python.run.configuration.lets.run=Let''s run our simple example with {0}.
|
||||
|
||||
python.debug.workflow.rerun=Let''s rerun our program. Just click again at {0} or use {1}.
|
||||
python.debug.workflow.rerun=Let''s rerun our program. Just click {0} again or use {1}.
|
||||
|
||||
Reference in New Issue
Block a user