Home » Eclipse Projects » Technology Project and PMC » Technology Project Declaration: Desktop Integration Project
| Technology Project Declaration: Desktop Integration Project [message #66686] |
Sat, 19 February 2005 11:51  |
Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------080205060904010501020503
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
As per the Eclipse Development Process
< http://www.eclipse.org/org/documents/Eclipse%20Development%2 0Process%202003_11_09%20FINAL.pdf>,
we are notifying the Eclipse Membership-at-Large of the intent to
propose the Desktop Integration Project as a Technology sub-project. A
brief description of the project is below. A draft project proposal is
at http://www.eclipse.org/proposals/eclipse-dip/index.htm
<http://www.eclipse.org/proposals/eclipse-dip/index.html>l
<http://www.eclipse.org/proposals/eclipse-dip/index.html>
------------------------------------------------------------ ------------
*Data Integration Project*
Much of the technical success of the Eclipse Platform can be attributed
to its practical integration and use of platform specific services and
technologies. The most notable of these is the Standard Window Toolkit
(SWT), which uses platform specific user interface technologies where
possible to delivery a high quality, native, user interface experience.
Other platform-specific Eclipse features include: a partial OLE/COM
bridge, the SWT_AWT bridge for co-hosting Swing / AWT and SWT
user-interfaces within one another, the embedded Eclipse Internet
Explorer Web Browser, and recent SWT mechanisms for interacting with the
Windows System Tray and creating custom shaped windows.
Eclipse demonstrates the tremendous value available to Java developers
when local services and technologies are integrated into a Java
framework or application in an intelligent and user-centered manner. The
number of platform-specific integration requirements is expected to
increase as a result of the growing popularity of the RCP and its
positive influence in a renewed effort to deliver native Java desktop
applications.
Unlike many of the Eclipse proposals, whose technical and implementation
scope is limited to pure Java technologies, this project concentrates on
enhancing Eclipse through the use of non-Java technologies and services.
Specifically, this project seeks out opportunities to integrate
high-quality native services and technologies that will significantly
benefit the Eclipse developer community.
We foresee this project serving as an incubator for technologies and
techniques used by the Eclipse Platform team, supplemental technologies,
frameworks, RCP application developers that need tighter integration,
and for native application developers that seek to leverage Eclipse
technologies within their products.
We look forward to input and discussion from the Eclipse community.
--
*Bjorn Freeman-Benson*
Technical Director, Open Source Process and Infrastructure
Eclipse Foundation <http://www.eclipse.org/>
voice: 971-327-7323
fax: 971-327-7320
email: bjorn.freeman-benson@eclipse.org
<mailto:bjorn.freeman-benson@eclipse.org>
<http://www.eclipsecon.org/>
--------------080205060904010501020503
Content-Type: multipart/related;
boundary="------------000201010000090602020802"
--------------000201010000090602020802
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<small><font face="Arial">As per the <a
href=" http://www.eclipse.org/org/documents/Eclipse%20Development%2 0Process%202003_11_09%20FINAL.pdf">Eclipse
Development Process</a>, we are notifying the Eclipse
Membership-at-Large of the intent to propose the Desktop Integration
Project as a Technology sub-project. A brief description of the project
is below. A
draft project proposal is at <a
href="http://www.eclipse.org/proposals/eclipse-dip/index.html">http://www.eclipse.org/proposals/eclipse-dip/index.htm</a><a
href="http://www.eclipse.org/proposals/eclipse-dip/index.html">l</a><br>
</font></small>
<hr size="2" width="100%"><br>
<small><font face="Arial"><b>Data Integration Project</b><br>
Much of the technical success of the Eclipse Platform can be attributed
to its practical integration and use of platform specific services and
technologies. The most notable of these is the Standard Window Toolkit
(SWT), which uses platform specific user interface technologies where
possible to delivery a high quality, native, user interface experience.
Other platform-specific Eclipse features include: a partial OLE/COM
bridge, the SWT_AWT bridge for co-hosting Swing / AWT and SWT
user-interfaces within one another, the embedded Eclipse Internet
Explorer Web Browser, and recent SWT mechanisms for interacting with
the Windows System Tray and creating custom shaped windows.<br>
<br>
Eclipse demonstrates the tremendous value available to Java developers
when local services and technologies are integrated into a Java
framework or application in an intelligent and user-centered manner.
The number of platform-specific integration requirements is expected to
increase as a result of the growing popularity of the RCP and its
positive influence in a renewed effort to deliver native Java desktop
applications.<br>
<br>
Unlike many of the Eclipse proposals, whose technical and
implementation scope is limited to pure Java technologies, this project
concentrates on enhancing Eclipse through the use of non-Java
technologies and services. Specifically, this project seeks out
opportunities to integrate high-quality native services and
technologies that will significantly benefit the Eclipse developer
community.<br>
<br>
We foresee this project serving as an incubator for technologies and
techniques used by the Eclipse Platform team, supplemental
technologies, frameworks, RCP application developers that need tighter
integration, and for native application developers that seek to
leverage Eclipse technologies within their products.<br>
<br>
</font></small><small><font face="Arial">We look forward to input and
discussion from the Eclipse community.</font></small><br>
<small><font face="Arial"></font></small>
<div class="moz-signature">-- <br>
<meta http-equiv="Content-Language" content="en-us">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; ">
<title>Bjorn Freeman</title>
<table style="border-collapse: collapse;" id="AutoNumber1" border="0"
bordercolor="#111111" cellspacing="0">
<tbody>
<tr>
<td colspan="2"><font face="Tahoma" size="2"><b>Bjorn
Freeman-Benson</b><br>
Technical Director, Open Source Process and Infrastructure<br>
<a href="http://www.eclipse.org/">Eclipse Foundation</a></font></td>
</tr>
<tr>
<td align="right"><font face="Tahoma" size="2">voice: </font></td>
<td><font face="Tahoma" size="2">971-327-7323</font></td>
</tr>
<tr>
<td align="right"><font face="Tahoma" size="2">fax: </font></td>
<td><font face="Tahoma" size="2">971-327-7320</font></td>
</tr>
<tr>
<td align="right"><font face="Tahoma" size="2">email: </font></td>
<td><font face="Tahoma" size="2"> <a
href="mailto:bjorn.freeman-benson@eclipse.org">bjorn.freeman-benson@eclipse.org</a></font></td>
</tr>
<tr>
<td colspan="2"> <a href="http://www.eclipsecon.org/"><img
src="cid:part1.00050400.08060609@eclipse.org" border="0" height="19"
width="117"></a></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>
--------------000201010000090602020802
Content-Type: image/gif;
name="117x19.gif"
Content-Transfer-Encoding: base64
Content-ID: <part1.00050400.08060609@eclipse.org>
Content-Disposition: inline;
filename="117x19.gif"
R0lGODlhdQATAJEAAP///66TvicjV/4BAiH5BAUUAAMALAAAAAB1ABMAAAKx lI+py+0Po5y0
2ouz3rz7D4biSJbm6QWqELCoBiBxpq5H3Ro2m7t8j6gFd78bzjPj2JY5ZrPX 9AVvOqo0agEk
BdpZUnvoysAGMk/B1AmJE6wPqmY7vOXE9lvn2vPy9PlYAVd1hSbRRSeTmPfF SNb3pBYXODUo
SAmxpaeYp5mJaBR5Jroj5wBEiGqJaSbG2RhmxmUGGAdl20YrZASka5L5Aozy G0xcbHyMnKy8
zNzsTFEAADs=
--------------000201010000090602020802--
--------------080205060904010501020503--
|
|
| | |
| Re: Technology Project Declaration: Desktop Integration Project [message #66772 is a reply to message #66686] |
Mon, 21 February 2005 13:35  |
| Eclipse User |
|
|
|
The URL for the project proposal in Bjorn's announcement should be updated
to:
http://www.eclipse.org/proposals/eclipse-desk/index.html
"Bjorn Freeman-Benson" <bjorn.freeman-benson@eclipse.org> wrote in message
news:42176E87.6080509@eclipse.org...
> As per the Eclipse Development Process
> < http://www.eclipse.org/org/documents/Eclipse%20Development%2 0Process%202003_11_09%20FINAL.pdf>,
> we are notifying the Eclipse Membership-at-Large of the intent to
> propose the Desktop Integration Project as a Technology sub-project. A
> brief description of the project is below. A draft project proposal is
> at http://www.eclipse.org/proposals/eclipse-dip/index.htm
> <http://www.eclipse.org/proposals/eclipse-dip/index.html>l
> <http://www.eclipse.org/proposals/eclipse-dip/index.html>
> ------------------------------------------------------------ ------------
>
> *Data Integration Project*
> Much of the technical success of the Eclipse Platform can be attributed
> to its practical integration and use of platform specific services and
> technologies. The most notable of these is the Standard Window Toolkit
> (SWT), which uses platform specific user interface technologies where
> possible to delivery a high quality, native, user interface experience.
> Other platform-specific Eclipse features include: a partial OLE/COM
> bridge, the SWT_AWT bridge for co-hosting Swing / AWT and SWT
> user-interfaces within one another, the embedded Eclipse Internet
> Explorer Web Browser, and recent SWT mechanisms for interacting with the
> Windows System Tray and creating custom shaped windows.
>
> Eclipse demonstrates the tremendous value available to Java developers
> when local services and technologies are integrated into a Java
> framework or application in an intelligent and user-centered manner. The
> number of platform-specific integration requirements is expected to
> increase as a result of the growing popularity of the RCP and its
> positive influence in a renewed effort to deliver native Java desktop
> applications.
>
> Unlike many of the Eclipse proposals, whose technical and implementation
> scope is limited to pure Java technologies, this project concentrates on
> enhancing Eclipse through the use of non-Java technologies and services.
> Specifically, this project seeks out opportunities to integrate
> high-quality native services and technologies that will significantly
> benefit the Eclipse developer community.
>
> We foresee this project serving as an incubator for technologies and
> techniques used by the Eclipse Platform team, supplemental technologies,
> frameworks, RCP application developers that need tighter integration,
> and for native application developers that seek to leverage Eclipse
> technologies within their products.
>
> We look forward to input and discussion from the Eclipse community.
> --
> *Bjorn Freeman-Benson*
> Technical Director, Open Source Process and Infrastructure
> Eclipse Foundation <http://www.eclipse.org/>
> voice: 971-327-7323
> fax: 971-327-7320
> email: bjorn.freeman-benson@eclipse.org
> <mailto:bjorn.freeman-benson@eclipse.org>
> <http://www.eclipsecon.org/>
>
>
------------------------------------------------------------ --------------------
> Bjorn FreemanAs per the Eclipse Development Process, we are notifying the
> Eclipse Membership-at-Large of the intent to propose the Desktop
> Integration Project as a Technology sub-project. A brief description of
> the project is below. A draft project proposal is at
> http://www.eclipse.org/proposals/eclipse-dip/index.html
>
> ------------------------------------------------------------ --------------------
>
> Data Integration Project
> Much of the technical success of the Eclipse Platform can be attributed to
> its practical integration and use of platform specific services and
> technologies. The most notable of these is the Standard Window Toolkit
> (SWT), which uses platform specific user interface technologies where
> possible to delivery a high quality, native, user interface experience.
> Other platform-specific Eclipse features include: a partial OLE/COM
> bridge, the SWT_AWT bridge for co-hosting Swing / AWT and SWT
> user-interfaces within one another, the embedded Eclipse Internet Explorer
> Web Browser, and recent SWT mechanisms for interacting with the Windows
> System Tray and creating custom shaped windows.
>
> Eclipse demonstrates the tremendous value available to Java developers
> when local services and technologies are integrated into a Java framework
> or application in an intelligent and user-centered manner. The number of
> platform-specific integration requirements is expected to increase as a
> result of the growing popularity of the RCP and its positive influence in
> a renewed effort to deliver native Java desktop applications.
>
> Unlike many of the Eclipse proposals, whose technical and implementation
> scope is limited to pure Java technologies, this project concentrates on
> enhancing Eclipse through the use of non-Java technologies and services.
> Specifically, this project seeks out opportunities to integrate
> high-quality native services and technologies that will significantly
> benefit the Eclipse developer community.
>
> We foresee this project serving as an incubator for technologies and
> techniques used by the Eclipse Platform team, supplemental technologies,
> frameworks, RCP application developers that need tighter integration, and
> for native application developers that seek to leverage Eclipse
> technologies within their products.
>
> We look forward to input and discussion from the Eclipse community.
>
> --
> Bjorn Freeman-Benson
> Technical Director, Open Source Process and Infrastructure
> Eclipse Foundation
> voice: 971-327-7323
> fax: 971-327-7320
> email: bjorn.freeman-benson@eclipse.org
>
>
|
|
| | | | | | |
| Re: Technology Project Declaration: Desktop Integration Project [message #598406 is a reply to message #66686] |
Mon, 21 February 2005 13:35 |
| Eclipse User |
|
|
|
The URL for the project proposal in Bjorn's announcement should be updated
to:
http://www.eclipse.org/proposals/eclipse-desk/index.html
"Bjorn Freeman-Benson" <bjorn.freeman-benson@eclipse.org> wrote in message
news:42176E87.6080509@eclipse.org...
> As per the Eclipse Development Process
> < http://www.eclipse.org/org/documents/Eclipse%20Development%2 0Process%202003_11_09%20FINAL.pdf>,
> we are notifying the Eclipse Membership-at-Large of the intent to
> propose the Desktop Integration Project as a Technology sub-project. A
> brief description of the project is below. A draft project proposal is
> at http://www.eclipse.org/proposals/eclipse-dip/index.htm
> <http://www.eclipse.org/proposals/eclipse-dip/index.html>l
> <http://www.eclipse.org/proposals/eclipse-dip/index.html>
> ------------------------------------------------------------ ------------
>
> *Data Integration Project*
> Much of the technical success of the Eclipse Platform can be attributed
> to its practical integration and use of platform specific services and
> technologies. The most notable of these is the Standard Window Toolkit
> (SWT), which uses platform specific user interface technologies where
> possible to delivery a high quality, native, user interface experience.
> Other platform-specific Eclipse features include: a partial OLE/COM
> bridge, the SWT_AWT bridge for co-hosting Swing / AWT and SWT
> user-interfaces within one another, the embedded Eclipse Internet
> Explorer Web Browser, and recent SWT mechanisms for interacting with the
> Windows System Tray and creating custom shaped windows.
>
> Eclipse demonstrates the tremendous value available to Java developers
> when local services and technologies are integrated into a Java
> framework or application in an intelligent and user-centered manner. The
> number of platform-specific integration requirements is expected to
> increase as a result of the growing popularity of the RCP and its
> positive influence in a renewed effort to deliver native Java desktop
> applications.
>
> Unlike many of the Eclipse proposals, whose technical and implementation
> scope is limited to pure Java technologies, this project concentrates on
> enhancing Eclipse through the use of non-Java technologies and services.
> Specifically, this project seeks out opportunities to integrate
> high-quality native services and technologies that will significantly
> benefit the Eclipse developer community.
>
> We foresee this project serving as an incubator for technologies and
> techniques used by the Eclipse Platform team, supplemental technologies,
> frameworks, RCP application developers that need tighter integration,
> and for native application developers that seek to leverage Eclipse
> technologies within their products.
>
> We look forward to input and discussion from the Eclipse community.
> --
> *Bjorn Freeman-Benson*
> Technical Director, Open Source Process and Infrastructure
> Eclipse Foundation <http://www.eclipse.org/>
> voice: 971-327-7323
> fax: 971-327-7320
> email: bjorn.freeman-benson@eclipse.org
> <mailto:bjorn.freeman-benson@eclipse.org>
> <http://www.eclipsecon.org/>
>
>
------------------------------------------------------------ --------------------
> Bjorn FreemanAs per the Eclipse Development Process, we are notifying the
> Eclipse Membership-at-Large of the intent to propose the Desktop
> Integration Project as a Technology sub-project. A brief description of
> the project is below. A draft project proposal is at
> http://www.eclipse.org/proposals/eclipse-dip/index.html
>
> ------------------------------------------------------------ --------------------
>
> Data Integration Project
> Much of the technical success of the Eclipse Platform can be attributed to
> its practical integration and use of platform specific services and
> technologies. The most notable of these is the Standard Window Toolkit
> (SWT), which uses platform specific user interface technologies where
> possible to delivery a high quality, native, user interface experience.
> Other platform-specific Eclipse features include: a partial OLE/COM
> bridge, the SWT_AWT bridge for co-hosting Swing / AWT and SWT
> user-interfaces within one another, the embedded Eclipse Internet Explorer
> Web Browser, and recent SWT mechanisms for interacting with the Windows
> System Tray and creating custom shaped windows.
>
> Eclipse demonstrates the tremendous value available to Java developers
> when local services and technologies are integrated into a Java framework
> or application in an intelligent and user-centered manner. The number of
> platform-specific integration requirements is expected to increase as a
> result of the growing popularity of the RCP and its positive influence in
> a renewed effort to deliver native Java desktop applications.
>
> Unlike many of the Eclipse proposals, whose technical and implementation
> scope is limited to pure Java technologies, this project concentrates on
> enhancing Eclipse through the use of non-Java technologies and services.
> Specifically, this project seeks out opportunities to integrate
> high-quality native services and technologies that will significantly
> benefit the Eclipse developer community.
>
> We foresee this project serving as an incubator for technologies and
> techniques used by the Eclipse Platform team, supplemental technologies,
> frameworks, RCP application developers that need tighter integration, and
> for native application developers that seek to leverage Eclipse
> technologies within their products.
>
> We look forward to input and discussion from the Eclipse community.
>
> --
> Bjorn Freeman-Benson
> Technical Director, Open Source Process and Infrastructure
> Eclipse Foundation
> voice: 971-327-7323
> fax: 971-327-7320
> email: bjorn.freeman-benson@eclipse.org
>
>
|
|
|
| Re: Recycle Bin support for RCP applications [message #598414 is a reply to message #66746] |
Tue, 22 February 2005 02:50 |
| Eclipse User |
|
|
|
Ryan Lowe schrieb:
> I'd like to be able to send a Java File to the Recycle Bin (Windows) or
> Trash Can (Mac OS X, Linux) from an RCP application. This is not
> supported by Java nor Eclipse right now. Could this be the type of
> functionality your project could offer?
Indeed, that's another good problem to solve for the project.
Cu, Gunnar
|
|
|
| Re: Recycle Bin support for RCP applications [message #598440 is a reply to message #66746] |
Tue, 22 February 2005 04:26 |
| Eclipse User |
|
|
|
Ryan,
Thanks for this suggestion. Yes, this an example of functionality that
falls under the scope of this project. We will be compiling a list of
candidate desktop technologies and mechanisms for discussion in the very
near future.
Wayne
"Ryan Lowe" <newsgroups@ryanlowe.ca> wrote in message
news:cvd4v3$th7$1@www.eclipse.org...
> I'd like to be able to send a Java File to the Recycle Bin (Windows) or
> Trash Can (Mac OS X, Linux) from an RCP application. This is not
> supported by Java nor Eclipse right now. Could this be the type of
> functionality your project could offer?
>
> Ryan Lowe
> newsgroups@ryanlowe.ca
|
|
|
| Sending mails with attachments [message #598448 is a reply to message #66686] |
Tue, 22 February 2005 05:41 |
| Eclipse User |
|
|
|
Originally posted by: joerg.von.frantzius.artnology.nospam.com
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
While this seems the time to express some more wishes ;)<br>
<br>
The only reason for us to go for <a href="https://jdic.dev.java.net/">JDIC</a>
recently was the possibility to send mails using the user's standard
mail client <i>including attachments</i>. So that would be a nice
feature as well...<br>
</body>
</html>
|
|
| |
Goto Forum:
Current Time: Wed May 07 17:01:29 EDT 2025
Powered by FUDForum. Page generated in 0.06396 seconds |
Home