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?
>
>
Y
>
> 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?
Saaa schrieb:
> dmd 2.026
> phobos
> newest ruby one-click :)
>
> What am I doing wrong ?
>
> C:\_D\Compiler\dwt2>rake
> (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\in
sleek schrieb:
> Will the old dwt-win/linux/samples/addons be modified to work with the new
> Tango release?
>
yes
Will the old dwt-win/linux/samples/addons be modified to work with the new
Tango release?
"Frank Benoit" wrote in message
news:gq2a5l$2ob...@digitalmars.com...
> Now there is the new hg repository for DWT2.
>
> DWT2 is like dwt-win/linux/addons, but the folders are organized in the
> original d
dmd 2.026
phobos
newest ruby one-click :)
What am I doing wrong ?
C:\_D\Compiler\dwt2>rake
(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):
Err
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 =>
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
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 origin
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.ecl
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
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
I'll be trying it out for dmd 2.. how far along is it at the moment?
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.
14 matches
Mail list logo
