Standard [35 minutes]
The e4 styling engine is the de facto way to dress up your RCP app! Join me for an in depth tour of the styling engine's main features - APIs to tooling to examples; everything you need to get you up and styling. We will start by taking a look at how the IDE makes use of the styling engine and how you can use the provided tools to customize your IDE and create new looks.
The Internet of Things and Machine to Machine are growing areas, and security and privacy are prime issues. In this session we will examine the security challenges around using M2M devices with protocols such as MQTT & CoAP. In particular we will look at encryption, federated identity and authorization models. On the topic of encryption, we’ll examine securing MQTT with TLS, challenges with Arduino, and using hardware encryption for microcontrollers. A key privacy requirement for user-centric IoT use cases will be giving users control over how their things collect and share data.
Supporting a large user base implies catering to a lot of different needs.
In Ericsson's case this means building over 20 different eclipse distributions and creating a corporate wide p2 repository to make it easy for our users to get all the plugins they need.
This talk focus on how we automatically create this p2 repository aggregating over 30 external repos, describe the wide variety of technologies being used (b3 aggregator, artifactory, jenkins, tycho, p2 tools, etc.) and talks about the challenges encountered.
You knew you wanted them, *we* knew you wanted them...finally we can do them !
There are a number of features that despite having been clearly identified as desirable (years ago) have never appeared and had essentially been given up for dead. The reason these features never made it to a release is that they were pretty well impossible to do using the 3.x architecture. We've now taken another look and find that using e4 they're actually not that hard.
In this talk we will explain how Polarsys technologies dramatically changes the way architects can work on complex systems.
By using the Polarsys and Eclipse Modeling stacks (Sirius, GenDoc, Acceleo, xText, OCL, ...) industry solutions can be created which fully fit the needs of architects (design, analysis, verification, simulation, etc.) in many domains (Transportation, Space, Insurance, Telecom, etc).
Well, things have changed and in this presentation, you will see how the workflow used to deliver web applications has evolved over the past few years!
Imagine your boss tells you to set up the cloud-infrastructure for a public trial system in three days. It should consist of isolated software labs where the trial users are able to execute their uploaded web applications. When a user joins the trial, a sandbox for his personal use should be created on-the-fly. In this sandbox he can access, manage, and monitor his latest application whenever he wants.
You think this is impossible? We thought the same :-).
This past year I was asked to evaluate the accessibility of my team's product. At the time, I was not entirely clear what that really meant. I knew there were people out there that used different input/output devices, could not perceive certain colours, had difficulty seeing small print-- and encompassed a variety of other concerns, but I really didn't know how that related to our product, or if our implementation helped or hindered these users (roughly 16% of the population).
After a fair bit of investigation, it is a lot clearer how the things we do in our design and code relates to these accessibility concerns for our users.
The use of OSGi technology has evolved over the past decade from being used to manage devices (service gateways etc.), to providing an extensible framework for desktop applications (Eclipse RCP), to being used by a majority of JEE servers for implementing extensible and modular servers, and as a programming model for developing server-side applications as well as applications deployed to the cloud.