I just tried wrapping some new functions and they seem to work. I
think if wx28 isn't too different from wx26 I could do a diff of the
two include directories and implement wxc wrapper functions to get
wx28 support in wxd.
ulink works fine though. It's great that I have to rely on third-party
linkers like that. -_-
Anders, if I want to edit the wxc bindings to add wx28+ support do I
have to wrap new functions in #ifdef sections to preserve wx26
support? Or should I just disregard wx26 alltogether and leave that as
a
How do I build wx28 in release mode? I've tried BUILD=release but that
didn't help.
The issue I'm having is that Optlink can't link due to a >64k global
symbols error.
Gour wrote:
I haven't build wxD yet, but just curious...you say that the sample
depends on wxc\display.cpp, but I thought that wxc stuff belonged to
wx.NET port, while the wxD site says: "Newer wxD version (0.10) has been
updated to wxWidgets 2.6.4 and linkable with wxWidgets 2.8.4 as well,
and i
On Mon, 28 Nov 2011 02:11:24 +0100
Andrej Mitrovic wrote:
> It has a dependency on the Display class, and it seems wxd is compiled
> with this class but you can't use it because it depends on
> wxc\display.cpp, which has a whole section idfef'd out (via #if
> wxUSE_DISPLAY). So naturally there's
FWIW I've got the StyledText sample fixed for D2 (it wasn't compiling
for D1 either).
It has a dependency on the Display class, and it seems wxd is compiled
with this class but you can't use it because it depends on
wxc\display.cpp, which has a whole section idfef'd out (via #if
wxUSE_DISPLAY). So
Ah right, sizers. I forgot to set a sizer for the tab. Now it works:
http://codepad.org/Kc5TxXjU
Thanks!
On Sat, Nov 26, 2011 at 11:27 PM, Andrej Mitrovic <
andrej.mitrov...@gmail.com> wrote:
> I've managed to get StyledTextCtrl compiled and working. I had to add
> a few missing .obj/.cpp file entries in the DMC makefile for the
> StyledTextCtrl contrib tree (just a couple of lexer files), but there
I've managed to get StyledTextCtrl compiled and working. I had to add
a few missing .obj/.cpp file entries in the DMC makefile for the
StyledTextCtrl contrib tree (just a couple of lexer files), but there
was also a cyclic import problem in wxd between wx.StyledTextCtrl's
and wx.TaskBarIcon's modul
Gour wrote:
So don't generate code, use XRC resources instead ?
wxD can use XRC files?
It would be great, then we can use some of the builders like
DialogBlocks/wxForms...
See the "Xrc" demo in Samples, for some example code.
http://docs.wxwidgets.org/stable/wx_xrcoverview.html
--anders
On Fri, 25 Nov 2011 11:24:02 +0100
Anders F Björklund wrote:
> Drop D1, drop Tango, and make DMD the default compiler syntax
> (possibly using gdmd or ldmd behind the covers, where desired)
+1
> It would just generate a Makefile anyway ? But if it could
> generate the IDE projects, then maybe i
On Fri, 25 Nov 2011 08:51:19 +0100
Andrej Mitrovic wrote:
> On 11/25/11, Gour wrote:
> > Huh, does it fall in the category of 'language bindings' ? :-)
>
> Or maybe I didn't get the joke? Hehe
;)
Sincerely,
Gour
--
As the embodied soul continuously passes, in this body,
from boyhood to y
On Fri, 25 Nov 2011 11:07:45 +0100
Anders F Björklund wrote:
> So don't generate code, use XRC resources instead ?
wxD can use XRC files?
It would be great, then we can use some of the builders like
DialogBlocks/wxForms...
Sincerely,
Gour
--
One who restrains his senses, keeping them under
Gour wrote:
And pick one "make" (GNU).
That's not fully clear to me.
Instead of doing separate GNUmakefile and Makefile, and synching those ?
There was even a build.brf and dsss.conf, while those were in fashion...
Trying to support two languages, two libraries, two+ compilers,
two+ buildt
On 11/25/11, Anders F Björklund wrote:
> Andrej Mitrovic wrote:
>> Well the cool thing is I can use wxGlide to generate C++ code, and
>> convert that to D. I tried it just now and it seems to work, but
>> converting everything by hand is a bit of a chore.
>
> So don't generate code, use XRC resour
Andrej Mitrovic wrote:
Well the cool thing is I can use wxGlide to generate C++ code, and
convert that to D. I tried it just now and it seems to work, but
converting everything by hand is a bit of a chore.
So don't generate code, use XRC resources instead ?
However even though D is C++ inspir
Walter Bright wrote:
Now that DMD has broken the ABI on x86_64,
??
... compared with GDC, that was.
Think we discussed this earlier, it's about the
passing of structs as parameters compared with C++.
The code is passing a D "string" to the C++ side,
and then interpreting this C argument as
On 11/25/11, Gour wrote:
> Huh, does it fall in the category of 'language bindings' ? :-)
It's a GUI builder with code generation: http://wxglade.sourceforge.net/
Or maybe I didn't get the joke? Hehe
On Fri, 25 Nov 2011 05:35:52 +0100
Andrej Mitrovic wrote:
> Well the cool thing is I can use wxGlide to generate C++ code, and
> convert that to D. I tried it just now and it seems to work, but
> converting everything by hand is a bit of a chore.
Huh, does it fall in the category of 'language bi
Anders F Björklund Wrote:
> Sam Hu wrote:
> >>> May I ask which version of wxWidget,2.8.12 or 2.9.? ?Thanks.
> >>
> >> For windows, it's:
> >> http://prdownloads.sourceforge.net/wxwindows/wxWidgets-2.6.4.zip
> >>
> >> Find this string: "1. wxWidgets" here: http://wxd.sourceforge.net/
> >> and fol
On Thu, Nov 24, 2011 at 9:52 PM, Andrej Mitrovic wrote:
> I'm just a little confused about that wxWindows license. So basically,
> if I release my sources then they have to be GPL, but if I don't then
> I can distribute only the binaries freely? IOW, I can't license my
> sources with Boost or sim
I'm just a little confused about that wxWindows license. So basically,
if I release my sources then they have to be GPL, but if I don't then
I can distribute only the binaries freely? IOW, I can't license my
sources with Boost or similar if I use wxd?
Well the cool thing is I can use wxGlide to generate C++ code, and
convert that to D. I tried it just now and it seems to work, but
converting everything by hand is a bit of a chore.
The biggest problem by far are the enums, since wxWidgets enums don't
have a "tag" while the wxd enums do. This mig
On 11/24/2011 4:15 AM, Anders F Björklund wrote:
Now that DMD has broken the ABI on x86_64,
??
On Thu, 24 Nov 2011 13:55:23 +0100
Anders F Björklund wrote:
> http://xkcd.com/224/
LOL.
> Sounds like a good idea, though you probably want to use SWIG 2.0
> for the improved D support - while wxPython uses SWIG 1.3 afaict ?
I do not know about wxPython, but, yes, SWIG 2.0 which has support f
Gour wrote:
What do you think about providing wxWidgets 3.0 API using SWIG?
http://xkcd.com/224/
I've asked for opinion Robin who is doing wxpython and has plenty of
experience with both wx& SWIG...waiting for his reply.
Sounds like a good idea, though you probably want to use SWIG 2.0
for
On Thu, 24 Nov 2011 13:15:49 +0100
Anders F Björklund wrote:
> One might also drop the D and Tango support, and go D2 only ?
+1
and do wx-3.0 only.
Sincerely,
Gour
--
Those who are on this path are resolute in purpose,
and their aim is one. O beloved child of the Kurus,
the intelligence
Andrej Mitrovic wrote:
I'm guessing what needs to be done is to update the wxc wrapper, and
recreate the D wrapper based on the C# port.
There were two main tracks to generating the wrappers, one was
using a patched SWIG and the other was a custom Perl script...
http://wxnet.cvs.sourceforge.ne
On Thu, 24 Nov 2011 12:01:46 +0100
Anders F Björklund wrote:
> Maybe one would want to regenerate the D API for wxWidgets 3.0,
> but should work fine without - similar to "WXWIN_COMPATIBILITY_*"
I'm reading SWIG docs and there is says: "...SWIG is quite capable in
supporting most of C++. Some of
Sam Hu wrote:
May I ask which version of wxWidget,2.8.12 or 2.9.? ?Thanks.
For windows, it's:
http://prdownloads.sourceforge.net/wxwindows/wxWidgets-2.6.4.zip
Find this string: "1. wxWidgets" here: http://wxd.sourceforge.net/
and follow the instructions for step 1 (DM), or if you're on Linux
On Wed, 23 Nov 2011 11:14:46 -0700
Brad Anderson wrote:
> 2.9 is very close to what 3.0 will be (it is the development version
> for the 3.0 release). All the major changes are done. It'd be fine
> to work against 2.9 in anticipation of 3.0 support.
+1
Btw, on wxwidgets list I've heard about
On Wed, Nov 23, 2011 at 10:19 AM, Andrej Mitrovic <
andrej.mitrov...@gmail.com> wrote:
> You'll have to ask Anders that.
>
> I'm guessing what needs to be done is to update the wxc wrapper, and
> recreate the D wrapper based on the C# port.
>
> I've heard something about wx3.0 being in plans, if i
You'll have to ask Anders that.
I'm guessing what needs to be done is to update the wxc wrapper, and
recreate the D wrapper based on the C# port.
I've heard something about wx3.0 being in plans, if it's a significant
change from the 2.x series then maybe it would be a good idea to wait
for that r
Andrej Mitrovic Wrote:
> On 11/23/11, Sam Hu wrote:
> > May I ask which version of wxWidget,2.8.12 or 2.9.? ?Thanks.
>
> For windows, it's:
> http://prdownloads.sourceforge.net/wxwindows/wxWidgets-2.6.4.zip
>
> Find this string: "1. wxWidgets" here: http://wxd.sourceforge.net/
> and follow the
On 11/23/11, Sam Hu wrote:
> May I ask which version of wxWidget,2.8.12 or 2.9.? ?Thanks.
For windows, it's:
http://prdownloads.sourceforge.net/wxwindows/wxWidgets-2.6.4.zip
Find this string: "1. wxWidgets" here: http://wxd.sourceforge.net/
and follow the instructions for step 1 (DM), or if you
Andrej Mitrovic Wrote:
> It compiles fine on DMD 2.056, but you need to compile wxWidgets via
> DMD make first. It's described on wxd's website.
>
> On 11/22/11, dolive wrote:
> > Anders F Björklund Wrote:
> >
> >> On 2011-11-10 18.27, Andrej Mitrovic wrote:
> >> > Btw, it would be great if you
It compiles fine on DMD 2.056, but you need to compile wxWidgets via
DMD make first. It's described on wxd's website.
On 11/22/11, dolive wrote:
> Anders F Björklund Wrote:
>
>> On 2011-11-10 18.27, Andrej Mitrovic wrote:
>> > Btw, it would be great if you could move the repo to Github when you
>
Anders F Björklund Wrote:
> On 2011-11-10 18.27, Andrej Mitrovic wrote:
> > Btw, it would be great if you could move the repo to Github when you
> > have the free time to do it. The samples need a few updates to work
> > with D2, and I'd like to make a pull for that. I don't really know my
> > way
On Mon, 21 Nov 2011 23:13:21 +0100
Anders F Björklund wrote:
> Missed a button, it's now at https://github.com/afb/wxd
Thanks a lot. Hopefully it will get some followers since we hope D
community is not like in Haskell: there are hundreds of Monad tutorials,
plenty of libraries on Hackage, but h
Gour wrote:
All three. Mostly wxD, but also the others - not using.
I'll leave it up as-is, but won't be adding D2 features.
Sorry to found out (when we're reconsidering D) that you go/went away.
:-(
Not sure if I was ever "on" D2, but left all the D1 stuff up.
Including the GDC binaries, wxW
On 2011-11-10 18.27, Andrej Mitrovic wrote:
Btw, it would be great if you could move the repo to Github when you
have the free time to do it. The samples need a few updates to work
with D2, and I'd like to make a pull for that. I don't really know my
way around sforge. :)
Missed a button, it's
On Fri, 26 Aug 2011 19:30:57 +0200
Anders F Björklund wrote:
Hello Anders,
> All three. Mostly wxD, but also the others - not using.
> I'll leave it up as-is, but won't be adding D2 features.
Sorry to found out (when we're reconsidering D) that you go/went away.
:-(
It looks that gtkD is in t
Btw, it would be great if you could move the repo to Github when you
have the free time to do it. The samples need a few updates to work
with D2, and I'd like to make a pull for that. I don't really know my
way around sforge. :)
FWIW the samples compile fine with the latest changesets, using dmd
make. Thanks for your work, Anders!
Well that kinda works now, thanks.
I've tried building the Controls sample. I've had to make some
modifications due to missing toString symbols and missing default
switches. After that I've unfortunately hit this:
http://www.digitalmars.com/ctg/optlink.html
C:\wxMSW-2.8.12\lib\dmc_lib\wxexpatd.li
Andrej Mitrovic wrote:
When I try to build via DMC's make I get:
D:\dev\projects\wxd>make
cd wxc
make
Error on line 181: can't read makefile '/build/msw/config.dmc'
I don't see a build folder anywhere. Are these build instructions
outdated on http://wxd.sourceforge.net/#installation ?
If you
When I try to build via DMC's make I get:
D:\dev\projects\wxd>make
cd wxc
make
Error on line 181: can't read makefile '/build/msw/config.dmc'
I don't see a build folder anywhere. Are these build instructions
outdated on http://wxd.sourceforge.net/#installation ?
s/tarball/zip file
The zipped source has the duplicate newlines, but that probably
doesn't show up based on what editor you use. But anyway, the git
version works fine.
On 8/26/11, Anders F Björklund wrote:
> The code uses CRLF, must be some kind of bug with your
> git setup - looks "OK" from here (with the ^M that is).
Sorry I've downloaded the tarball, not the git repo. The git repo
doesn't have these problems, thanks.
I can see the problem now. The code uses CR followed by CRLF on every
line. This was probably some kind of unix -> windows EOL conversion
bug. Either CRLF or CR's should be killed (personally I'm ok with unix
endlines).
The code uses CRLF, must be some kind of bug with your
git setup - looks "OK
Andrej Mitrovic wrote:
Do you mean you're stepping down as the maintainer of wxd, or just the
GDC/CodeBlocks stuff?
All three. Mostly wxD, but also the others - not using.
I'll leave it up as-is, but won't be adding D2 features.
--anders
Andrej Mitrovic wrote:
I can see the problem now. The code uses CR followed by CRLF on every
line. This was probably some kind of unix -> windows EOL conversion
bug. Either CRLF or CR's should be killed (personally I'm ok with unix
endlines).
The code uses CRLF, must be some kind of bug with y
I can see the problem now. The code uses CR followed by CRLF on every
line. This was probably some kind of unix -> windows EOL conversion
bug. Either CRLF or CR's should be killed (personally I'm ok with unix
endlines).
*correction: It's not just the samples, it's the library code too. I
don't understand, why the blank lines?
Do you mean you're stepping down as the maintainer of wxd, or just the
GDC/CodeBlocks stuff?
wxWidgets look very interesting to me, lots of documentation available
from what I can tell. Plus it seems it's easy to grab a device context
out of a wxWidget frame, so I could use Cairo with that (e.g.
h
Marco Leise wrote:
Would have ? Well, you can still use the existing stuff* for D(1).
It was mostly that focus has shifted to D2, since four years ago...
I updated most of it for better 64-bit support last year, and there
was a new Code::Blocks 10.05 but that was about it for development.
When
Am 26.08.2011, 13:47 Uhr, schrieb Anders F Björklund :
Marco Leise wrote:
That are some good projects you were working on. We've got the
precompiled DMD, Eclipse DDT and GtkD, but I would have tried wxWidgets
in Code::Blocks with D. And while building GDC from source is possible,
the Windows f
Marco Leise wrote:
I am also stepping down as a maintainer, including the pre-built GDC
distribution (gdcwin/gdcgnu/gdcmac) and the Code::Blocks support for D.
Hopefully the new wxD project will have better luck of accomplishing a
open-source cross-platform GUI and IDE for the D programming lang
Am 26.08.2011, 10:10 Uhr, schrieb Anders F Björklund :
I am also stepping down as a maintainer, including the pre-built GDC
distribution (gdcwin/gdcgnu/gdcmac) and the Code::Blocks support for D.
Hopefully the new wxD project will have better luck of accomplishing a
open-source cross-platform G
As part of a necessary rewrite to better support wxWidgets 3.0 and D2,
the wxD development is moving from SourceForge (cvs) to GitHub (git).
As an interim step the existing source repository has been converted,
the details at: http://sourceforge.net/scm/?type=git&group_id=133831
Besides updating
60 matches
Mail list logo
