Bug 135775 - Embed .NET controls into SWT container
Summary: Embed .NET controls into SWT container
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-09 22:01 EDT by Ivan Mising name CLA
Modified: 2019-09-24 13:59 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Mising name CLA 2006-04-09 22:01:53 EDT 
Nice if SWT able to embed .NET controls into SWT container as easy as OLE/ActiveX

Thanks
Comment 1 Steve Northover CLA 2006-04-10 14:08:33 EDT 
This is a major work item that could only be address as a plan item.
Comment 2 Henzler Peter CLA 2010-02-26 10:50:07 EST 
As .NET controls begin to replace ActiveX controls it is time to consider support for embedding .NET controls in eclipse SWT.
Comment 3 Henzler Peter CLA 2010-06-10 04:25:52 EDT 
ActiveX is dieing. All new currently components are .NET controls and the existing ActiveX controls will not be supported any more.

What must I do that this issue will be included in the development plans?
Comment 4 Felipe Heidrich CLA 2010-06-10 10:39:05 EDT 
(In reply to comment #3)
> What must I do that this issue will be included in the development plans?

I don't have a straigh answer. Sorry.
What you can do is get more people on board (blog/tweet/etc). The more people interested in the feature better are the chances to get it in the plan.

Better describe how many cool thing you wold be able to do with this new feature.

Offer to help with design, implementation, documentation, test, maintenance.

Write a prototype.
Comment 5 Lars Vogel CLA 2019-09-24 13:59:05 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.