Re: DWT2 Windows building error

2009-03-21 Thread yidabu
On Sun, 22 Mar 2009 03:32:36 +0100
Frank Benoit  wrote:

> yidabu schrieb:
> > Rake building error:
> > 
> > dwt2>Rake base --trace
> > (in .../dwt2)
> > ** Invoke base (first_time)
> > ** Execute base
> > Building base/src
> > dmd @...dwt2\rsp
> > dwt2\base\src\java\lang\wrappers.d(15): Error: identifier 'equals_t
> > ' is not defined
> > dwt2\base\src\java\lang\wrappers.d(15): Error: equals_t is used as
> > a type
> ...
> 
> > Ruby Windows 1.91, Rake 0.83
> > 
> > Tango 0.99.7, Revision:4052, last changed date:2008-10-30
> > DMD 1.037
> 
> for dwt2 i use the tango 0.99.8 ( see svn tags/releases/0.99.8), there
> the type equals_t is defined in object.di. For dmd i use 1.041.

how to building lib file on Windows? 
Run Rake, obj fiels generated, Should I to run "lib a.obj b.obj " to 
generated dwt2.lib?

-- 
yidabu 
http://www.dsource.org/projects/dwin

D 语言-中文(D Chinese):
http://www.d-programming-language-china.org/
http://bbs.d-programming-language-china.org/
http://dwin.d-programming-language-china.org/
http://scite4d.d-programming-language-china.org/




Re: DWT2 Windows building error

2009-03-21 Thread Frank Benoit
yidabu schrieb:
> Rake building error:
> 
> dwt2>Rake base --trace
> (in .../dwt2)
> ** Invoke base (first_time)
> ** Execute base
> Building base/src
> dmd @...dwt2\rsp
> dwt2\base\src\java\lang\wrappers.d(15): Error: identifier 'equals_t
> ' is not defined
> dwt2\base\src\java\lang\wrappers.d(15): Error: equals_t is used as
> a type
...

> Ruby Windows 1.91, Rake 0.83
> 
> Tango 0.99.7, Revision:4052, last changed date:2008-10-30
> DMD 1.037

for dwt2 i use the tango 0.99.8 ( see svn tags/releases/0.99.8), there
the type equals_t is defined in object.di. For dmd i use 1.041.


Re: The new DWT2

2009-03-21 Thread Frank Benoit
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.



DWT2 Windows building error

2009-03-21 Thread yidabu
On Sat, 21 Mar 2009 09:57:32 +0100
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;
> 
> 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.


Rake building error:

...dwt2>Rake base --trace
(in .../dwt2)
** Invoke base (first_time)
** Execute base
Building base/src
dmd @...dwt2\rsp
...dwt2\base\src\java\lang\wrappers.d(15): Error: identifier 'equals_t
' is not defined
...dwt2\base\src\java\lang\wrappers.d(15): Error: equals_t is used as
a type
...dwt2\base\src\java\lang\wrappers.d(15): function java.lang.wrappers
.ArrayWrapperT!(byte).ArrayWrapperT.opEquals of type void(Object o) overrides bu
t is not covariant with object.Object.opEquals of type int(Object o)
...dwt2\base\src\java\lang\wrappers.d(15): function java.lang.wrappers
.ArrayWrapperT!(byte).ArrayWrapperT.opEquals does not override any function
...dwt2\base\src\java\lang\wrappers.d(69): template instance java.lang
.wrappers.ArrayWrapperT!(byte) error instantiating
rake aborted!
compile error
.../dwt2/rakefile:83:in `block (2 levels) in buildTree'
...Ruby/lib/ruby/1.9.1/rake.rb:981:in `call'
...Ruby/lib/ruby/1.9.1/rake.rb:981:in `sh'
...Ruby/lib/ruby/1.9.1/rake.rb:1065:in `sh'
.../dwt2/rakefile:75:in `block in buildTree'
.../dwt2/rakefile:69:in `chdir'
.../dwt2/rakefile:69:in `buildTree'
.../dwt2/rakefile:116:in `block in '
...Ruby/lib/ruby/1.9.1/rake.rb:613:in `call'
...Ruby/lib/ruby/1.9.1/rake.rb:613:in `block in execute'
...Ruby/lib/ruby/1.9.1/rake.rb:608:in `each'
...Ruby/lib/ruby/1.9.1/rake.rb:608:in `execute'
...Ruby/lib/ruby/1.9.1/rake.rb:574:in `block in invoke_with_call_chain
'
...Ruby/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize'
...Ruby/lib/ruby/1.9.1/rake.rb:567:in `invoke_with_call_chain'
...Ruby/lib/ruby/1.9.1/rake.rb:560:in `invoke'
...Ruby/lib/ruby/1.9.1/rake.rb:2012:in `invoke_task'
...Ruby/lib/ruby/1.9.1/rake.rb:1990:in `block (2 levels) in top_level'

...Ruby/lib/ruby/1.9.1/rake.rb:1990:in `each'
...Ruby/lib/ruby/1.9.1/rake.rb:1990:in `block in top_level'
...Ruby/lib/ruby/1.9.1/rake.rb:2029:in `standard_exception_handling'
...Ruby/lib/ruby/1.9.1/rake.rb:1984:in `top_level'
...Ruby/lib/ruby/1.9.1/rake.rb:1963:in `block in run'
...Ruby/lib/ruby/1.9.1/rake.rb:2029:in `standard_exception_handling'
...Ruby/lib/ruby/1.9.1/rake.rb:1960:in `run'
...Ruby/bin/rake.bat:39:in `'





\src\dwt2>Rake swt
(in /src/dwt2)
Building org.eclipse.swt.win32.win32.x86/src
src\dwt2\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\C
ompatibility.d(15): module File cannot read file 'java\io\File.d'
rake aborted!
compile error
/dwt2/rakefile:83:in `block (2 levels) in buildTree'
(See full trace by running task with --trace)





my environment:

Ruby Windows 1.91, Rake 0.83

Tango 0.99.7, Revision:4052, last changed date:2008-10-30
DMD 1.037







-- 
yidabu 
http://www.dsource.org/projects/dwin

D 语言-中文(D Chinese):
http://www.d-programming-language-china.org/
http://bbs.d-programming-language-china.org/
http://dwin.d-programming-language-china.org/
http://scite4d.d-programming-language-china.org/




Re: The new DWT2

2009-03-21 Thread Christopher Wright

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

2009-03-21 Thread torhu

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.


Re: The new DWT2

2009-03-21 Thread Piotrek

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

2009-03-21 Thread Christopher Wright

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

2009-03-21 Thread Frank Benoit
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"


DWT2 D2+Phobos help needed

2009-03-21 Thread Frank Benoit

If you want to contribute, please note:
http://www.dsource.org/projects/dwt/wiki/Contribution

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.

To build with D1+Tango, the dmd.conf/sc.ini must be setup correctly
(version=Tango,Posix, include paths, libs)
You can build all with a simple call to 'rake'. The available target can
be shown with 'rake -T'.

The repository contains the following trees:
Java stuff and helper:
see "base"
SWT:
org.eclipse.swt.win32.win32.x86
org.eclipse.swt.gtk.linux.x86
Additional stuff:
org.eclipse.*

What I already did and still doing is, i try to make the code compilable
for Phobos. I do this by deactivating the tango code by 'version' and
put in 'implMissing()' calls for the missing Phobos implementation. If
needed i also add dummy code (like the 'return 0;' to make it compile.

public int lastIndexOf(String str, char ch, int formIndex){
version(Tango){
int res = tango.text.Util.locatePrior( str, ch, formIndex );
if( res is str.length ) res = -1;
return res;
} else { // Phobos
implMissing( __FILE__, __LINE__ );
return 0;
}
}

Now the code compiles, but it does not work. If a call to implMissing is
entered, the application will be terminated.

That is where I need help. Please help me to replace the "implMissing"
with the correct implementation. Highest priority has the 'base' tree
and within this tree, the places where a tango implementation exists,
but none for Phobos. Places where also is no Tango implementation can be
ignored.

Code changes can be committed locally (hg ci) and packed into bundle
files (hg bundle). Then the bundle file can be sent to me by email
(keinfarb...@googlemail.com). After reviewing i will add the change to
the global repository and do merges if necessary.

Please reply in this thread or start a new one, if you want to start
working with a file(s), so nobody else is starting the same work. On the
other hand, please do also tell, if you will pause/stop working on this,
so someone else can take over.

For questions and general conversation, please also try to find me in
IRC (freenode, #dwt, keinfarbton).





Re: The new DWT2

2009-03-21 Thread Saaa
I'll be trying it out for dmd 2.. how far along is it at the moment? 




The new DWT2

2009-03-21 Thread Frank Benoit
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.