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"
(→Tworzenie aplikacji typu Rich Clients za pomocą Eclipse 4 RCP) |
|||
Line 16: | Line 16: | ||
== Eclipse of idleness and focus on current task == | == Eclipse of idleness and focus on current task == | ||
+ | |||
+ | == Dekonstrukcja architektury w czasach kryzysu == |
Revision as of 07:27, 13 August 2012
Contents
- 1 Orion Workshop
- 2 Redefining Modularity with Object Teams (English)
- 3 No more excuse for your NPE: JDT 3.8 understands null-annotations (English)
- 4 Tworzenie aplikacji typu Rich Clients za pomocą Eclipse 4 RCP
- 5 Eclipse Command Language (English)
- 6 Eclipse of idleness and focus on current task
- 7 Dekonstrukcja architektury w czasach kryzysu
Orion Workshop
Redefining Modularity with Object Teams (English)
No more excuse for your NPE: JDT 3.8 understands null-annotations (English)
Tworzenie aplikacji typu Rich Clients za pomocą Eclipse 4 RCP
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.