This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
blog:mylyn_makes_code_presentations_clearer [2009/11/27 18:29] djo Changed title |
blog:mylyn_makes_code_presentations_clearer [2014/10/17 22:08] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Mylyn Makes Code Easier to Present, Easier to Follow ====== | ||
+ | |||
+ | |||
+ | Last week I gave a presentation on refactoring regular Java code toward a Scala DSL to the Chicago Area Scala Enthusiasts (CASE). Along the way, I discovered a really cool way to use the Eclipse Mylyn tool to solve a perennial presenter's problem: how to smoothly switch between various code examples during the presentation. | ||
+ | |||
+ | As one of the few Eclipse people who normally works on Linux (currently Ubuntu), I am used to the cool Compiz feature of rendering my desktops on a 3d cube that visibly rotates (in 3d) to switch between different desktops. When presenting this is handy because I like to put the slides on one face of the cube and Eclipse (with a workspace containing my code examples) on another face of the cube. Then I can simply rotate the cube to smoothly switch between Eclipse code examples and my presentation slides. | ||
+ | |||
+ | But once I'm in Eclipse, I normally have several code examples that I would like to use to illustrate the points I am making. | ||
+ | |||
+ | It turns out that the Mylyn tool provides a really handy way to switch between code examples. It even automatically highlights the important parts of the code in the Package Explorer in the process. | ||
+ | |||
+ | So before I present, I create a new Mylyn context for each example I want to show. I then record into the context the Mylyn landmarks I want to make sure I cover in the presentation. These landmarks wind up boldfaced inside the Package Explorer. | ||
+ | |||
+ | {{:blog:blogs:mylyn1.png|}} | ||
+ | |||
+ | Then during the presentation, I can simply switch between contexts using the Mylyn Task List. When I do this, Mylyn automatically opens and closes the right editors, and highlights the correct parts of the code in the Package Explorer for showing the next code example. | ||
+ | |||
+ | {{:blog:blogs:mylyn2.png|}} | ||
+ | |||
+ | The result is that I can keep track of where I am more easily in the code examples (since the important parts are automatically highlighted), and--for the same reason--it's also easier for the audience to follow what I am trying to communicate. | ||
+ | |||
+ | ~~LINKBACK~~ | ||
+ | ~~DISCUSSION~~ | ||