Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse Day Krakow 2012/Talks"
m (→Redefining Modularity with Object Teams) |
|||
| Line 1: | Line 1: | ||
== Orion Workshop == | == Orion Workshop == | ||
| − | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Szymon_Brandys Szymon Brandys] | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Szymon_Brandys Szymon Brandys] |
[http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Ma.C5.82gorzata_Janczarska Małgorzata Janczarska] | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Ma.C5.82gorzata_Janczarska Małgorzata Janczarska] | ||
| − | [http://eclipse.org/orion/ Orion] is an open tool integration platform for writing browser-based development tools. In this tutorial you will learn how to use the Orion platform and extend it by integrating other web pages and services into the Orion development workflow. Close integration is achieved through writing Orion plugins to extend the platform with additional capabilities. We will walk through the process from a simple first plugin, up to a plugin that extends Orion in a variety of way: adding links to other pages, new language tools, and even a brief foray into connecting Orion with remote file systems. | + | [http://eclipse.org/orion/ Orion] is an open tool integration platform for writing browser-based development tools. In this tutorial you will learn how to use the Orion platform and extend it by integrating other web pages and services into the Orion development workflow. Close integration is achieved through writing Orion plugins to extend the platform with additional capabilities. We will walk through the process from a simple first plugin, up to a plugin that extends Orion in a variety of way: adding links to other pages, new language tools, and even a brief foray into connecting Orion with remote file systems. |
| − | == Redefining Modularity with Object Teams == | + | == Redefining Modularity with Object Teams == |
| − | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Stephan_Herrmann Stephan Herrmann] | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Stephan_Herrmann Stephan Herrmann] |
| − | Modularity is our key concept for mastering complexity, but what kind of modularity do we need to address the challenges of tomorrow? Can a programming language provide the necessary means? Can Java? | + | Modularity is our key concept for mastering complexity, but what kind of modularity do we need to address the challenges of tomorrow? Can a programming language provide the necessary means? Can Java? |
| − | The [http://www.eclipse.org/objectteams Object Teams] approach demonstrates how far a truly object-oriented programming language can go, how classes and objects can indeed be the building blocks for uncompromisingly modular software designs. Rather than introducing new kinds of modules the approach adds new ways how classes and objects can be connected into a system: | + | The [http://www.eclipse.org/objectteams Object Teams] approach demonstrates how far a truly object-oriented programming language can go, how classes and objects can indeed be the building blocks for uncompromisingly modular software designs. Rather than introducing new kinds of modules the approach adds new ways how classes and objects can be connected into a system: Existing relationships like nesting and inheritance are enhanced and only one new relationship is introduced: role playing. |
| − | Existing relationships like nesting and inheritance are enhanced and only one new relationship is introduced: role playing. | + | |
| − | With these conceptual tools every requirement, every reusable asset can be cast into a module. Every variation of an existing system can be described by an additional module. Object Teams supports modularity in all circumstances: extreme modularity. | + | With these conceptual tools every requirement, every reusable asset can be cast into a module. Every variation of an existing system can be described by an additional module. Object Teams supports modularity in all circumstances: extreme modularity. |
| − | For more than 5 years [http://wiki.eclipse.org/OTJ OT/J] has been successfully used in plug-in development, including, e.g., a prototype for JDT's new [http://wiki.eclipse.org/JDT_Core/Null_Analysis annotation-based null analysis] as a separately deployable module. | + | For more than 5 years [http://wiki.eclipse.org/OTJ OT/J] has been successfully used in plug-in development, including, e.g., a prototype for JDT's new [http://wiki.eclipse.org/JDT_Core/Null_Analysis annotation-based null analysis] as a separately deployable module. |
| − | Extracted from such applications this presentation will show the most useful patterns, patterns that don't trade one solution for a bag of new problems but holistically improve software quality. | + | Extracted from such applications this presentation will show the most useful patterns, patterns that don't trade one solution for a bag of new problems but holistically improve software quality. |
| − | In this presentation the audience will see little syntax of OT/J, that's not where big things happen, but the goal is to change the way developers think about modularity. | + | In this presentation the audience will see little syntax of OT/J, that's not where big things happen, but the goal is to change the way developers think about modularity. |
| − | == No more excuse for your NPE: JDT 3.8 understands null-annotations == | + | == No more excuse for your NPE: JDT 3.8 understands null-annotations == |
| − | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Stephan_Herrmann Stephan Herrmann] | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Stephan_Herrmann Stephan Herrmann] |
| − | NullPointerExceptions are among the most common and most embarrassing symptoms of failures in Java programs. Starting with the Juno release, JDT has entered the next stage of fighting NPE as-you-type: annotating your code with null specifications. This talk will show you how to get the most from this new feature, and I will outline what's currently cooking. | + | NullPointerExceptions are among the most common and most embarrassing symptoms of failures in Java programs. Starting with the Juno release, JDT has entered the next stage of fighting NPE as-you-type: annotating your code with null specifications. This talk will show you how to get the most from this new feature, and I will outline what's currently cooking. |
== Tworzenie aplikacji typu Rich Clients za pomocą Eclipse 4 RCP == | == Tworzenie aplikacji typu Rich Clients za pomocą Eclipse 4 RCP == | ||
| Line 34: | Line 33: | ||
[http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Kamil_Pi.C4.99tak Kamil Piętak] | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Kamil_Pi.C4.99tak Kamil Piętak] | ||
| − | Language: Polish | + | Language: Polish |
The recently released Eclipse 4 RCP delivers brand new features that significantly improve building rich client applications. Application model, dependency injection, built-in services are the more important elements that allow to easily create brand new applications (not only IDEs). | The recently released Eclipse 4 RCP delivers brand new features that significantly improve building rich client applications. Application model, dependency injection, built-in services are the more important elements that allow to easily create brand new applications (not only IDEs). | ||
| − | In the talk I will shortly present the most important features of Eclipse 4 RCP in contrast of the ones that exist in the 3.x branch.<br> | + | In the talk I will shortly present the most important features of Eclipse 4 RCP in contrast of the ones that exist in the 3.x branch.<br> |
| − | == Eclipse Command Language == | + | == Eclipse Command Language == |
| − | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Bartosz_Czerwi.C5.84ski Bartosz Czerwiński] | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Bartosz_Czerwi.C5.84ski Bartosz Czerwiński] |
| − | == Eclipse of idleness and focus on current task == | + | == Eclipse of idleness and focus on current task == |
| − | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Dariusz_.C5.81uksza Dariusz Łuksza] | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Dariusz_.C5.81uksza Dariusz Łuksza] |
| − | == Dekonstrukcja architektury w czasach kryzysu == | + | == Dekonstrukcja architektury w czasach kryzysu == |
| − | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Jaros.C5.82aw_Pa.C5.82ka Jarosław Pałka] | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Jaros.C5.82aw_Pa.C5.82ka Jarosław Pałka] |
| − | Language: Polish | + | Language: Polish |
| − | Napięte terminy, budżety na ścisłej diecie, eksplodujące metryki | + | Napięte terminy, budżety na ścisłej diecie, eksplodujące metryki KLOC,CC,RFC, mgławice technologii, paradygmatów oraz manifestów. Rozproszone zespoły, "nonsensownie" wielkie i złożone systemy. Czy w dobie globalnego kryzysu finansowego, jesteśmy też świadkami (a być może też sprawcami) kryzysu w naszej branży? Kryzysu, który ma o wiele dalej wybiegające konsekwencje. |
| − | KLOC,CC,RFC, mgławice technologii, paradygmatów oraz manifestów. | + | |
| − | Rozproszone zespoły, "nonsensownie" wielkie i złożone systemy. | + | |
| − | Czy w dobie globalnego kryzysu finansowego, jesteśmy też świadkami (a | + | |
| − | być może też sprawcami) kryzysu w naszej branży? Kryzysu, który ma o | + | |
| − | wiele dalej wybiegające konsekwencje. | + | |
| − | Podczas prezentacji spróbujemy zrozumieć czym jest kryzys architektury | + | Podczas prezentacji spróbujemy zrozumieć czym jest kryzys architektury systemów IT, jakie są jego źródła i konsekwencje. Spróbujemy też wyjrzeć poza nasz "ogródek", i poszukać rozwiązań korzystając z "myślenia systemowego" i "teorii systemów złożonych". Przyglądniemy się archetypom systemów, zrozumiemy czym charakteryzują się "złożone systemy" i jakie rozwiązania proponują prezentowane podejścia. Czy zamiast analizować kolejne linijki kodu, próbując zrozumieć intencje autora, możemy usprawnić nasz system, niekoniecznie paraliżując nasz system nerwowy. Czy znajomość własności hierarchii systemów, źródeł tzw. "emerging behaviours" pozwoli nam uniknąć problemów w przyszłości. Czy może zamiast poznawać kolejne języki programowania, paradygmaty które z czasem przeminą lub okażą się niekompletne nie powinniśmy zainwestować naszego czasu w zgłębienie natury rzeczy? Natury "systemów" i ich "złożoności. |
| − | systemów IT, jakie są jego źródła i konsekwencje. Spróbujemy też | + | |
| − | wyjrzeć poza nasz "ogródek", | + | == Tycho - using maven to build OSGi plugins == |
| − | i poszukać rozwiązań korzystając z "myślenia systemowego" i "teorii | + | |
| − | systemów złożonych". Przyglądniemy się archetypom systemów, zrozumiemy | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Krzysztof_Daniel Krzysztof Daniel] |
| − | czym charakteryzują się | + | |
| − | "złożone systemy" i jakie rozwiązania proponują prezentowane | + | == XText - creating your own code generation tools == |
| − | podejścia. Czy zamiast analizować kolejne linijki kodu, próbując | + | |
| − | zrozumieć intencje autora, możemy usprawnić | + | [http://wiki.eclipse.org/Eclipse_Day_Krakow_2012/Speakers#Krzysztof_Daniel Krzysztof Daniel] |
| − | nasz system, | + | |
| − | niekoniecznie paraliżując nasz system nerwowy. Czy znajomość własności | + | |
| − | hierarchii systemów, źródeł tzw. "emerging behaviours" pozwoli nam | + | |
| − | uniknąć problemów w przyszłości. | + | |
| − | Czy może zamiast poznawać kolejne języki programowania, paradygmaty | + | |
| − | które z czasem przeminą lub okażą się niekompletne nie powinniśmy | + | |
| − | zainwestować naszego czasu | + | |
| − | w zgłębienie natury rzeczy? Natury "systemów" i ich "złożoności. | + | |
Revision as of 09:22, 13 August 2012
Contents
- 1 Orion Workshop
- 2 Redefining Modularity with Object Teams
- 3 No more excuse for your NPE: JDT 3.8 understands null-annotations
- 4 Tworzenie aplikacji typu Rich Clients za pomocą Eclipse 4 RCP
- 5 Eclipse Command Language
- 6 Eclipse of idleness and focus on current task
- 7 Dekonstrukcja architektury w czasach kryzysu
- 8 Tycho - using maven to build OSGi plugins
- 9 XText - creating your own code generation tools
Orion Workshop
Orion is an open tool integration platform for writing browser-based development tools. In this tutorial you will learn how to use the Orion platform and extend it by integrating other web pages and services into the Orion development workflow. Close integration is achieved through writing Orion plugins to extend the platform with additional capabilities. We will walk through the process from a simple first plugin, up to a plugin that extends Orion in a variety of way: adding links to other pages, new language tools, and even a brief foray into connecting Orion with remote file systems.
Redefining Modularity with Object Teams
Modularity is our key concept for mastering complexity, but what kind of modularity do we need to address the challenges of tomorrow? Can a programming language provide the necessary means? Can Java?
The Object Teams approach demonstrates how far a truly object-oriented programming language can go, how classes and objects can indeed be the building blocks for uncompromisingly modular software designs. Rather than introducing new kinds of modules the approach adds new ways how classes and objects can be connected into a system: Existing relationships like nesting and inheritance are enhanced and only one new relationship is introduced: role playing.
With these conceptual tools every requirement, every reusable asset can be cast into a module. Every variation of an existing system can be described by an additional module. Object Teams supports modularity in all circumstances: extreme modularity.
For more than 5 years OT/J has been successfully used in plug-in development, including, e.g., a prototype for JDT's new annotation-based null analysis as a separately deployable module.
Extracted from such applications this presentation will show the most useful patterns, patterns that don't trade one solution for a bag of new problems but holistically improve software quality.
In this presentation the audience will see little syntax of OT/J, that's not where big things happen, but the goal is to change the way developers think about modularity.
No more excuse for your NPE: JDT 3.8 understands null-annotations
NullPointerExceptions are among the most common and most embarrassing symptoms of failures in Java programs. Starting with the Juno release, JDT has entered the next stage of fighting NPE as-you-type: annotating your code with null specifications. This talk will show you how to get the most from this new feature, and I will outline what's currently cooking.
Tworzenie aplikacji typu Rich Clients za pomocą Eclipse 4 RCP
Language: Polish
The recently released Eclipse 4 RCP delivers brand new features that significantly improve building rich client applications. Application model, dependency injection, built-in services are the more important elements that allow to easily create brand new applications (not only IDEs).
In the talk I will shortly present the most important features of Eclipse 4 RCP in contrast of the ones that exist in the 3.x branch.
Eclipse Command Language
Eclipse of idleness and focus on current task
Dekonstrukcja architektury w czasach kryzysu
Language: Polish
Napięte terminy, budżety na ścisłej diecie, eksplodujące metryki KLOC,CC,RFC, mgławice technologii, paradygmatów oraz manifestów. Rozproszone zespoły, "nonsensownie" wielkie i złożone systemy. Czy w dobie globalnego kryzysu finansowego, jesteśmy też świadkami (a być może też sprawcami) kryzysu w naszej branży? Kryzysu, który ma o wiele dalej wybiegające konsekwencje.
Podczas prezentacji spróbujemy zrozumieć czym jest kryzys architektury systemów IT, jakie są jego źródła i konsekwencje. Spróbujemy też wyjrzeć poza nasz "ogródek", i poszukać rozwiązań korzystając z "myślenia systemowego" i "teorii systemów złożonych". Przyglądniemy się archetypom systemów, zrozumiemy czym charakteryzują się "złożone systemy" i jakie rozwiązania proponują prezentowane podejścia. Czy zamiast analizować kolejne linijki kodu, próbując zrozumieć intencje autora, możemy usprawnić nasz system, niekoniecznie paraliżując nasz system nerwowy. Czy znajomość własności hierarchii systemów, źródeł tzw. "emerging behaviours" pozwoli nam uniknąć problemów w przyszłości. Czy może zamiast poznawać kolejne języki programowania, paradygmaty które z czasem przeminą lub okażą się niekompletne nie powinniśmy zainwestować naszego czasu w zgłębienie natury rzeczy? Natury "systemów" i ich "złożoności.