Eclipse Mylin有何用处? [英] How is Eclipse Mylin useful?

问题描述

在Eclipse Preferences -> Java -> Editor -> Content Assist -> Advanced设置中，我看到以下内容:

In my Eclipse Preferences -> Java -> Editor -> Content Assist -> Advanced settings, I see the following:

• Java非类型提案
• Java提案
• Java提案(以任务为中心)
• Java类型提案
• JPA提案(对我而言始终是空的)
• PDE API工具建议(在Content-Assist Cycling设置中选中时会跳过)
• SWT模板提案(始终为空)
• 模板提案(始终为空)
• 单词建议(在内容辅助循环"设置中选中时会跳过)

• Java Non-Type Proposals
• Java Proposals
• Java Proposals (Task-focused)
• Java Type Proposals
• JPA Proposals (is always empty for me)
• PDE API Tools Proposals (gets skipped when checked in the Content-Assist Cycling settings)
• SWT Template Proposals (always empty)
• Template Proposals (always empty)
• Word Proposals (gets skipped when checked in the Content-Assist Cycling settings)

我尝试分别搜索"Java非类型提案"和"Java提案(针对任务)"，但没有发现任何描述它们的内容.

I tried googling (separately) for "Java Non-Type Proposals" and "Java Proposals (Task-Focused)", but didn't find anything describing them.

与/Java ((Non-)?Type)? Proposals/匹配的条目对我来说很有意义，而其他条目则没有.

The entries matching /Java ((Non-)?Type)? Proposals/ make sense to me, but the others don't.

那么，其他人做什么呢?

So, what do the others do?

• 我从未见过PDE，SWT，模板或Word提案的结果.它们什么时候有用?
• 我也从未真正开始使用Mylyn，我想它就是提供"Java提案(以任务为中心)"的工具.如果我没有使用Mylyn理解的错误跟踪器，那将给我带来什么好处?

推荐答案

我也从未真正开始使用Mylyn，我想这就是 提供"Java提案 (以任务为中心)".那会买什么 我，如果我不使用错误跟踪器 Mylyn明白的吗?

I've also never really started using Mylyn, which I imagine is what provides "Java Proposals (Task-focused)". What would that buy me, if I'm not using a bug-tracker that Mylyn understands?

即使没有集成的bug跟踪程序(在Mylyn看来，任务存储库")，使用Mylyn所能做的就是在本地"存储库中创建任务，并使用它们来维护不同开发环境任务.

What you can do with Mylyn, even without an integrated bug tracker (in the Mylyn parlance, a "task repository"), is create tasks in your "local" repository, and use them to maintain the context of your different development tasks.

Mylyn中的上下文支持非常独特，尽管您在为新任务首次激活它时会感到不安，因为Mylyn所做的是像Package Explorer这样的过滤窗口内容，这样只有您访问过的那些工件才可见在激活任务的同时，现在，由于您是第一次激活任务，因此没有任何访问，并且Package Explorer是空白的！

The context support in Mylyn is quite unique, although disconcerting when you first activate it for a new task, because what Mylyn does is filter the contents of windows like the Package Explorer so that only those artifacts are visible which you've visited while the task was activated, and now, since you have just activated a task for the first time, nothing has been visited, and the Package Explorer is blank!

假设任务描述类似于在您的.code.AbstractMappingParameter中查找NPE的原因"，您可能想做的是使用Ctrl-shift-T(打开类型...)并导航到那个班级. (为自己节省一些输入，并在打开任务"对话框中使用驼峰式案例支持:只需键入"AMP".)您的Package Explorer现在显示该类及其上方的层次结构(其中的文件，包和项目) .如果已将编辑器配置为自动折叠代码，则该编辑器将显示折叠的每个注释和方法，以便您可以看到平时更多的类.

What you'd probably want to do, assuming your task description was something like "Find the cause of the NPE in your.code.AbstractMappingParameter", is use Ctrl-shift-T (Open Type...) and navigate to that class. (Save yourself some typing and use the camel case support in the Open Task dialog: just type "AMP".) Your Package Explorer now shows that class, and the hierarchy above it (the file it's in, the package, and the project). The editor, if you've configured it to fold code automatically, will display each comment and method folded, so you can see more of the class that you usually might.

访问更多类似的文件，然后开始建立上下文，Mylyn会自动将其与任务一起保存.现在，您随后的打开类型..."搜索将首先显示上下文类别，并且您提到的内容辅助提议也将起作用.注意:除非您认为文件与任务无关，否则不要关闭文件.当关闭编辑器时，类/文件/等.已从上下文中删除，并且不再出现在Package Explorer中.一般的开发任务最多需要十几个文件，少量文件和编辑器窗口，以便在您处理它时保持打开状态.

Visit a couple more files like that, and you start to build up your context, which Mylyn automatically saves along with the task. Your subsequent "Open Type..." searches now present in-context classes first, and the content-assist proposals you mentioned work also. NOTE: don't close files unless you think they're not relevant to the task. When you close an editor, the class/file/etc. is deleted from the context, and no longer appears in your Package Explorer. The average development task doesn't take more than a dozen or so files, a small-enough number of files and editor windows to keep open while you're working on it.

如果您现在(在本地或在存储库中)创建了另一个任务，然后将其激活，那么您将再次从已清除的Package Explorer开始，并在工作时建立上下文.

If you now created another task (locally, or in a repository), and then activated it, you would again start with a cleared Package Explorer, and would build up context as you worked.

然后，如果您重新激活第一个任务，您会看到一件有趣的事情:您打开的窗口将关闭，包浏览器将被清除，然后是您上次处理该浏览器时的内容.任务将会出现，并且您当时打开的所有窗口现在都将再次打开！您将重新开始工作.非常方便.

Then, if you reactivated the first task, you'd see an interesting thing: the windows you have open will close, and the package explorer will clear, and then the contents of the explorer from the last time you worked on that task will appear, and all the windows you had opened at that time will now be opened again! You're back to work on it. It's very handy.

有一个简短的摘要，您可以在没有集成存储库的情况下使用Mylyn进行操作.如果您想了解更多信息，可以访问 http://www.eclipse.org/mylyn/并阅读其中的内容.

There's a brief summary of what you can do with Mylyn without an integrated repository. If you're curious to hear more, you might go to http://www.eclipse.org/mylyn/ and read what's there.

这篇关于Eclipse Mylin有何用处?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！