Difference between revisions of "Basics : Webinars"

From CDOT Wiki
Jump to: navigation, search
Line 1: Line 1:
 
{{Ecl_r|Basics|Webinars}}
 
{{Ecl_r|Basics|Webinars}}
 
{{Ecl_r_entry |c=0
 
{{Ecl_r_entry |c=0
|url=  http://zenit.senecac.on.ca/~jordan.anastasiade/Eclipse/basics/Beginner/Beginner-DexterTutorial.html
+
|url=  http://www.youtube.com/watch?v=4YfAo9ZoEGQ
 
|title= OSGi for Eclipse Developersn - Talk by Chris Aniszczyk, Eclipse Source - Sept 2009
 
|title= OSGi for Eclipse Developersn - Talk by Chris Aniszczyk, Eclipse Source - Sept 2009
 
|descr= *  Eclipse developer, you should be aware that the Eclipse runtime (Equinox) since version 3.0 has been built on top OSGi and you have been
 
|descr= *  Eclipse developer, you should be aware that the Eclipse runtime (Equinox) since version 3.0 has been built on top OSGi and you have been
Line 8: Line 8:
 
ask me to restart every time I install something?    * What's up with OSGi services, how do they compare to extensions widely used in Eclipse?
 
ask me to restart every time I install something?    * What's up with OSGi services, how do they compare to extensions widely used in Eclipse?
 
)
 
)
 +
}}
 +
{{Ecl_r_entry |c=0
 +
|url=  http://www.youtube.com/watch?v=f6RlqdiwGrM
 +
|title= Distributed OSGi in the Eclipse Runtime Project
 +
 +
- Talk by Scott Lewis, EclipseSource - Sept 2009
 +
|descr= *  As part of the OSGi 4.2 specification, there is a new spec (RFC119) intended to standardize the distribution and network discovery of OSGi
 +
services. The ECF project (http://www.eclipse.org/ecf)  has implemented the latest available draft and this is included in the
 +
Galileo release.  *    Scott will present his open source, open protocol, open  provider approach to implementing this spec, show example applications
 +
and discuss how others may extend and/or replace the implementation.  *  He'll also touch on some basic issues of distributed services, such as
 +
network transparency and 'leaky' abstractions like synchronous remote
 +
procedure call (RPC).
 
}}
 
}}

Revision as of 12:27, 24 January 2011

Parameters:

  • c: Background color of the table row; value 0 or 1; if the previous registration was 0, please type 1.
  • url: Resource URL
  • title: Resource title including author; year;
  • descr: The description of the resource's contributions (why should we read it?)

For example, to register a new resource you have to type:

 {{Ecl_r_entry |c=0
 |url=   http://zenit.senecac.on.ca/~jordan.anastasiade/Eclipse/basics/Beginner/Beginner-DexterTutorial.html
 |title= Eclipse and Java for Total Beginners - Max Dexter - 2006
 |descr= * Create Java project in Eclipse * Create Java package * Introduce classes and objects, naming conventions * Write a simple Java class (Person)
 }}
 
  • Eclipse developer, you should be aware that the Eclipse runtime (Equinox) since version 3.0 has been built on top OSGi and you have been

writing OSGi bundles. The goal of this talk is to introduce the Eclipse developer to "OSGi-isms" and to answer some of these questions: * What's the difference between an Eclipse plug-in and an OSGi bundle? * Is there more than Require-Bundle? Why do all the OSGi guys scream about Import-Package? * If OSGi is truly dynamic, why does Eclipse ask me to restart every time I install something? * What's up with OSGi services, how do they compare to extensions widely used in Eclipse? )

[http://www.youtube.com/watch?v=f6RlqdiwGrM Distributed OSGi in the Eclipse Runtime Project

- Talk by Scott Lewis, EclipseSource - Sept 2009]

  • As part of the OSGi 4.2 specification, there is a new spec (RFC119) intended to standardize the distribution and network discovery of OSGi

services. The ECF project (http://www.eclipse.org/ecf) has implemented the latest available draft and this is included in the Galileo release. * Scott will present his open source, open protocol, open provider approach to implementing this spec, show example applications and discuss how others may extend and/or replace the implementation. * He'll also touch on some basic issues of distributed services, such as network transparency and 'leaky' abstractions like synchronous remote procedure call (RPC).