Re: The new DWT2
Saaa schrieb: Meanwhile the org.eclipse.swt.win32.win32.x86 tree builds for D2. But will not be usable until the missing impls are done. What does it mean for an implMissing to not be encapsulated within a version check? Didn't the tango version need those implementations? Yes, also did add those in the beginning of dwt. So if there is no tango implementation, that means, that function was never called before. So it can stay not implemented.
Re: The new DWT2
Saaa schrieb: dmd 2.026 phobos newest ruby one-click :) What am I doing wrong ? C:\_D\Compiler\dwt2rake (in C:/_D/Compiler/dwt2) Cleaning Building dwt-base Building org.eclipse.swt.win32.win32.x86 C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\COMTYPES.d(19): Error: org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) conflicts with org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\OBJIDL.d(125): Error: org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) conflicts with org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\OBJIDL.d(382): Error: org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) conflicts with org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\OBJIDL.d(785): Error: org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) conflicts with org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\ifs.d(65): Error: org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) conflicts with org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\events\SelectionListener.d(19): module Traits cannot read file 'tango\core\Traits.d' rake aborted! compile error C:/_D/Compiler/dwt2/rakefile:138:in `buildTree' Meanwhile the org.eclipse.swt.win32.win32.x86 tree builds for D2. But will not be usable until the missing impls are done.
Re: The new DWT2
dmd 2.026 phobos newest ruby one-click :) What am I doing wrong ? C:\_D\Compiler\dwt2rake (in C:/_D/Compiler/dwt2) Cleaning Building dwt-base Building org.eclipse.swt.win32.win32.x86 C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\COMTYPES.d(19): Error: org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) conflicts with org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\OBJIDL.d(125): Error: org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) conflicts with org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\OBJIDL.d(382): Error: org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) conflicts with org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\OBJIDL.d(785): Error: org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) conflicts with org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\ifs.d(65): Error: org.eclipse.swt.internal.win32.WINTYPES.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\win32\WINTYPES.d(190) conflicts with org.eclipse.swt.internal.ole.win32.extras.IID at C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\ole\win32\extras.d(54) C:\_D\Compiler\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\events\SelectionListener.d(19): module Traits cannot read file 'tango\core\Traits.d' rake aborted! compile error C:/_D/Compiler/dwt2/rakefile:138:in `buildTree'
The new DWT2
Now there is the new hg repository for DWT2. DWT2 is like dwt-win/linux/addons, but the folders are organized in the original directory structure of the Eclipse sources. This also means the packages are again like the original. DWT.CENTER = SWT.CENTER import dwt.widgets.Button; = import org.eclipse.swt.widgets.Button; This makes future porting of more files and versions much more easier. I started to make dwt2 compilable also for D2+Phobos. Support for D1+Tango will certainly stay. The repositories dwt-win/linux/addons/samples will stay and i will support them with bug fixes for a while. But I plan to do my future work in DWT2. Get it with Mercurial (hg) Version Control software: First get: hg clone http://hg.dsource.org/projects/dwt2 To get later changes from the server hg pull -u To build you need Rake, that is the Ruby make tool and is part of a standard Ruby installation. Also DMD needs to be in the path environment variable.
Re: The new DWT2
I'll be trying it out for dmd 2.. how far along is it at the moment?
Re: The new DWT2
Saaa schrieb: I'll be trying it out for dmd 2.. how far along is it at the moment? At the moment the refactoring is complete for D1+Tango. The 'base' tree compiles also for D2+Tango and i am working on the swt tree. But compile means really just compile. There is implementation work needed for Phobos. Please see also my posting: DWT2 D2+Phobos help needed
Re: The new DWT2
Frank Benoit wrote: Now there is the new hg repository for DWT2. DWT2 is like dwt-win/linux/addons, but the folders are organized in the original directory structure of the Eclipse sources. This also means the packages are again like the original. DWT.CENTER = SWT.CENTER import dwt.widgets.Button; = import org.eclipse.swt.widgets.Button; Wow, that's like twelve extra characters. I did want to try this out, but I already have gtkd, and that lets me just import gtk.Button. It shouldn't be too hard to write a script that would generate files of the type: module dwt.Button; public import org.eclipse.swt.widgets.Button;
Re: The new DWT2
Christopher Wright pisze: Wow, that's like twelve extra characters. I did want to try this out, but I already have gtkd, and that lets me just import gtk.Button. It shouldn't be too hard to write a script that would generate files of the type: module dwt.Button; public import org.eclipse.swt.widgets.Button; But SWT re-brand seems to be the better choice after all. I use Descent so I even don't type 1 character. Cheers
Re: The new DWT2
torhu wrote: On 21.03.2009 14:08, Christopher Wright wrote: Frank Benoit wrote: Now there is the new hg repository for DWT2. DWT2 is like dwt-win/linux/addons, but the folders are organized in the original directory structure of the Eclipse sources. This also means the packages are again like the original. DWT.CENTER = SWT.CENTER import dwt.widgets.Button; = import org.eclipse.swt.widgets.Button; Wow, that's like twelve extra characters. I did want to try this out, but I already have gtkd, and that lets me just import gtk.Button. It's a bit annoying, but seems like the right thing to do. I'll probably just type it once for each file, then use my editor's 'duplicate line' feature for the rest. That's what I've been doing already anyway. It's well motivated from a development standpoint. I don't see what it contributes, otherwise.
Re: The new DWT2
Christopher Wright schrieb: It's well motivated from a development standpoint. I don't see what it contributes, otherwise. there are existing naming conflicts of packages. org.eclipse.swt = dwt that was the start. Well then, rename all other swt to dwt also. So we have SWT = DWT SWTError = DWTError SWTException = DWTException SWTEventObject = DWTEventObject SWTEventListener = DWTEventListener then there are the packages from jface. Oh the first problem. org.eclipse.jface where to map those. Ok, have all the future packages from org.eclipse in dwtx, dwtx to be an abbreviation for org.eclipse org.eclipse.jface = dwtx.jface ... Oh, oh, now there is org.eclipse.osgi and org.osgi, now it gets a bit ugly. You see, where this is going to? All those renaming produce work in comparing versions and updates. A porting project like this needs lots of comparing and merging. It produces work for me, the developer. And I think my time is the most valuable resource the dwt project has. And really, I see not what those renaming contribute. Instead, when the original namings are used, examples and snippets can be used without or less change, that is a contribute for the user.
