| internal API use vs. code clone [message #1765536] |
Mon, 12 June 2017 05:09  |
Eclipse User |
|
|
|
In Eclipse ACTF project, we need to access Windows native applications
- to get accessibility information
- to control existing Text-to-Speech engines
- to embed applications (IE/OpenOffice.org) as Eclipse Editor/view for accessibility evaluation
- etc.
To achieve this, we had used many components from swt.internal. We removed many of these dependencies by using our own actf.util.win32.comclutch package. However, some dependencies are still remaining.
We might be able to remove these dependencies by replicating swt.internal components into our internal package, but it will be a code clone.
To avoid it, we would like to continue to use these internal APIs. Would you please let us know if there are any concerns about it? Or, would you please let us know if there are any other good approach for it?
Thank you in advance for your support.
[internal classes that currently used in ACTF]
- org.eclipse.swt.internal.Callback
- org.eclipse.swt.internal.win32.OS
- org.eclipse.swt.internal.win32.MSG
- org.eclipse.swt.internal.win32.TCHAR
- org.eclipse.swt.internal.ole.win32.COM
- org.eclipse.swt.internal.ole.win32.COMObject
- org.eclipse.swt.internal.ole.win32.GUID
- org.eclipse.swt.internal.ole.win32.IDispatch
- org.eclipse.swt.internal.ole.win32.IUnknown
|
|
|
|
Powered by
FUDForum. Page generated in 0.06682 seconds
Home