Bugzilla – Full Text Bug Listing
| Summary: | Port SWT to WPF | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | John Arthorne <john.arthorne> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | bogofilter+eclipse.org, bpasero, bradleyjames, cocoakevin, eclipse.felipe, eclipse, ed.burnette, francois, fujara, gunnar, jdunrue, Jim.Adams, jonas1_lu, Konstantin.Scheglov, mark.k.mclaren, mike.milinkovich, mlists, mseele, olibralo, pombredanne, remy.suen, rjlorimer, wmitsuda |
| Version: | 3.3 | Keywords: | plan |
| Target Milestone: | 3.3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
John Arthorne
AFAIK WinFX is bases on and now part of the .NET framework (versions 2.0 and 3.0 respectively). Would it mean mixing .NET and Java in the same process? >Would it mean mixing .NET and Java in the same process?
Yes
changing the name, winfx is no longer in use.
Avalon -> WPF
WinFX -> .Net Framework 3.0
Sounds like it's going to be fun seing two managed heaps, GCs and JITs interact. Actually it can be an opportunity to create an API-level support for interacting with .NET code. Something similar to the OS class? looking forward for this interaction between .NET and Java API When the fun will begin ? Does this mean that SWT based Java applications need .NET Framework 2.0 or 3.0 to run on target machines with Windows XP or Vista? I guess Vista comes with .NET, but how about XP? If my assumption is correct then using SWT would mean an additional dependency to .NET Framework with a download size of 50,3 MB (3.0) or 22,4 MB (2.0). I dont think so. to me, .NET just like another platform means probably we need another set of swt.jar just for .NET and another set are reserved for Win32 (9x, 2k, Me, xp ) I believe that what they will try to do. (In reply to comment #5) > Does this mean that SWT based Java applications need .NET Framework 2.0 or 3.0 > to run on target machines with Windows XP or Vista? > > I guess Vista comes with .NET, but how about XP? If my assumption is correct > then using SWT would mean an additional dependency to .NET Framework with a > download size of 50,3 MB (3.0) or 22,4 MB (2.0). > The existing win32 port works very well on Vista and does not require .Net. The new WPF port will require .Net 3.0. Since the 2 SWT ports are completely separate, users will be able to decide which they want to use. Thanks for your answers. I guess this means that I can use the same win32 port on w2k, xp and vista. yes, you can use the win32 port on all of those OS's I saw that a 32 bit build has been released. Any chance of releasing a 64 bit build for vista. The 32 bit version is still early access, a 64 bit version is not planned at this point. If I were to install both the win32 and wpf pieces will the wpf pieces automatically run if I were on vista or would I have to enable them. I was just wondering because if I use the rcp delta pack to create installers for my products I will be installing early access code on my customers which doesn't seem like a nice thing to be doing. Jim, I'm not sure that I understand your question. win32, and wpf are 2 separate and complete ports. Both of them work on Vista, but not within the same application. Jim, the chosen fragment will depend on the "ws" property. If ws=wpf, it will use the WPF port, if ws=win32, it will use the win32 port. If you have a ws preference, this property can be specified with the -ws command line argument, or via the osgi.ws system property. Currently, if no ws property is supplied then the win32 port will be chosen if you are running any Windows OS (including Vista). This is completed in 3.3, marking as FIXED. Eclipse is available in an early access form on WPF. There is still more work to do on this port, but this bug can be closed. SWT was ported to WPF. |