Menu
▾
▴
wxhaskell-devel — wxhaskell developers
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
(53) |
Mar
(145) |
Apr
(22) |
May
(7) |
Jun
(14) |
Jul
(14) |
Aug
(9) |
Sep
(10) |
Oct
(48) |
Nov
(59) |
Dec
(45) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(36) |
Feb
(5) |
Mar
(33) |
Apr
(28) |
May
(5) |
Jun
(6) |
Jul
(1) |
Aug
(7) |
Sep
(11) |
Oct
(3) |
Nov
(31) |
Dec
|
| 2010 |
Jan
(8) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(9) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(1) |
May
(2) |
Jun
(12) |
Jul
(36) |
Aug
(7) |
Sep
(40) |
Oct
(6) |
Nov
(40) |
Dec
(8) |
| 2012 |
Jan
(54) |
Feb
(8) |
Mar
(1) |
Apr
(16) |
May
(2) |
Jun
(12) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(7) |
| 2013 |
Jan
(8) |
Feb
|
Mar
(13) |
Apr
(2) |
May
(13) |
Jun
(44) |
Jul
|
Aug
(13) |
Sep
(12) |
Oct
(11) |
Nov
(7) |
Dec
(6) |
| 2014 |
Jan
(3) |
Feb
(4) |
Mar
(9) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(2) |
Jun
(3) |
Jul
|
Aug
(2) |
Sep
(5) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Kido T. <she...@co...> - 2009-04-12 05:46:05
|
Sun Apr 12 01:40:01 EDT 2009 shelarcy <she...@gm...>
* Add Setup.lhs to wxcore directory.
Ignore-this: d7fd9f80bbab6d6ce52b45b4ac2a7f43
A ./wxcore/Setup.lhs
View patch online:
http://code.haskell.org/wxhaskell/_darcs/patches/20090412054001-c1071-c8ffbd069123a6268c95b1f31afe93182067cc4a.gz
|
|
From: Kido T. <she...@co...> - 2009-04-12 05:46:05
|
Sun Apr 12 01:38:04 EDT 2009 shelarcy <she...@gm...>
* Bump version number to 0.11.1.3.
Ignore-this: d87a5e52d5a887da66f909c762f5d8
M ./configure -1 +1
M ./wx/wx.cabal -1 +1
M ./wxc/wxc-2.8.dsp -4 +4
M ./wxcore/wxcore.cabal -1 +1
M ./wxdirect/wxdirect.cabal -1 +1
View patch online:
http://code.haskell.org/wxhaskell/_darcs/patches/20090412053804-c1071-fb896bebb56995d901d0c6a894d43be8adca6ad0.gz
|
|
From: shelarcy <she...@gm...> - 2009-04-12 05:18:19
|
I pushed these changes now, thanks. On Sat, 11 Apr 2009 01:25:25 +0900, shelarcy <she...@gm...> wrote: >> Is this the right approach? >> >> Wed Apr 8 11:38:47 BST 2009 Eric Kow <E....@br...> >> * Move wxcore.cabal to wxcore and use Simple build method. >> The assumption here is that the automatically generated files have already >> been built. >> >> Fri Apr 10 15:50:29 BST 2009 Eric Kow <E....@br...> >> * Split wxcore-only into wxcore-gen and wxcore-libs. >> >> Fri Apr 10 15:50:48 BST 2009 Eric Kow <E....@br...> >> * Do not build wxcore in the default target (let that be a separate cabal step). > > Yes. We can make binary distribution now. > > But you forgot to add wxcore-install. This means that we must build > wxcore twice when we want to build binary distribution. So, I added > more 1 patch for adding wxcore-install target. -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
|
From: Kido T. <she...@co...> - 2009-04-12 05:13:03
|
Fri Apr 10 10:50:48 EDT 2009 Eric Kow <E....@br...>
* Do not build wxcore in the default target (let that be a separate cabal step).
Ignore-this: 5e11f493186f151caf3765f4cdfaafdf
M ./makefile -3 +8
View patch online:
http://code.haskell.org/wxhaskell/_darcs/patches/20090410145048-2067a-c6492be4a0752703fd0a6dbf1f06d1df8348864d.gz
|
|
From: Kido T. <she...@co...> - 2009-04-12 05:13:03
|
Fri Apr 10 10:50:29 EDT 2009 Eric Kow <E....@br...>
* Split wxcore-only into wxcore-gen and wxcore-libs.
Ignore-this: 2e8d9eba2b15f875b11cce3acae90340
M ./makefile -1 +3
View patch online:
http://code.haskell.org/wxhaskell/_darcs/patches/20090410145029-2067a-d427826c967179f32d3d6aa6594442df503c4824.gz
|
|
From: Kido T. <she...@co...> - 2009-04-12 05:13:02
|
Wed Apr 8 06:38:47 EDT 2009 Eric Kow <E....@br...>
* Move wxcore.cabal to wxcore and use Simple build method.
Ignore-this: d28ead6f7493fdde373167faa0fb5725
The assumption here is that the automatically generated files have already
been built.
./wxcore.cabal -> ./wxcore/wxcore.cabal
A ./wxcore/license.txt
M ./wxcore/wxcore.cabal -3 +2
View patch online:
http://code.haskell.org/wxhaskell/_darcs/patches/20090408103847-2067a-bcd19e7ab0ee587b9d9543f02939505672aa28a6.gz
|
|
From: Kido T. <she...@co...> - 2009-04-12 05:13:01
|
Fri Apr 10 12:16:41 EDT 2009 shelarcy <she...@gm...>
* Add wxcore-install for building binary distribution more easily.
Ignore-this: 84b4c94d6d2694f18001dbf2ac1a1def
M ./makefile +2
View patch online:
http://code.haskell.org/wxhaskell/_darcs/patches/20090410161641-c1071-6b838ac372ef3b6a87436cb2fe70b8d8d6f1ec2d.gz
|
|
From: shelarcy <she...@gm...> - 2009-04-10 16:25:45
|
On Sat, 11 Apr 2009 00:38:41 +0900, Eric Kow <eri...@gm...> wrote: > Is this the right approach? > > Wed Apr 8 11:38:47 BST 2009 Eric Kow <E....@br...> > * Move wxcore.cabal to wxcore and use Simple build method. > The assumption here is that the automatically generated files have already > been built. > > Fri Apr 10 15:50:29 BST 2009 Eric Kow <E....@br...> > * Split wxcore-only into wxcore-gen and wxcore-libs. > > Fri Apr 10 15:50:48 BST 2009 Eric Kow <E....@br...> > * Do not build wxcore in the default target (let that be a separate cabal step). Yes. We can make binary distribution now. But you forgot to add wxcore-install. This means that we must build wxcore twice when we want to build binary distribution. So, I added more 1 patch for adding wxcore-install target. Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
|
From: Eric K. <eri...@gm...> - 2009-04-10 15:38:47
|
Is this the right approach? Wed Apr 8 11:38:47 BST 2009 Eric Kow <E....@br...> * Move wxcore.cabal to wxcore and use Simple build method. The assumption here is that the automatically generated files have already been built. Fri Apr 10 15:50:29 BST 2009 Eric Kow <E....@br...> * Split wxcore-only into wxcore-gen and wxcore-libs. Fri Apr 10 15:50:48 BST 2009 Eric Kow <E....@br...> * Do not build wxcore in the default target (let that be a separate cabal step). |
|
From: shelarcy <she...@gm...> - 2009-04-10 10:05:33
|
On Thu, 09 Apr 2009 17:38:59 +0900, Eric Y. Kow <eri...@gm...> wrote: > One thing we could consider doing is shipping a .pc file for wxc > http://en.wikipedia.org/wiki/Pkg-config > > Cabal has support for it, so we could get the wxcore cabal file to > require the wxc with the pkgconfig-depends flag Unfortunately pkg-config doesn't solve our problem. If Windows user installs pkg-config, pkg-config solves problem. But Windows doesn't not install pkg-config in defaut. GHC doesn't include pkg-config. And GTK+ project's pkg-cofig binary requires to install glib dll. Windows user must install unix shell or GTK+ when Windows user want to use pkg-config. This is not friendly for Windows user. On Fri, 10 Apr 2009 17:41:22 +0900, <E....@br...> wrote: > Here are three new patches which makes wxcore require wxc. > Does this move us closer to doing the right thing? > > I'm still not sure what we need to do to account for bindist, though? > > (snip) > > New patches > ----------- > Thu Apr 9 18:34:23 BST 2009 Eric Kow <E....@br...> > * Generate a pkg-config file for our wxc. > > Thu Apr 9 20:05:25 BST 2009 Eric Kow <E....@br...> > * Install libwxc.pc file in pkgconfig dir. > > Thu Apr 9 20:09:09 BST 2009 Eric Kow <E....@br...> > * Express dependency on wxc in wxcore.cabal via pkgconfig. So, new patches are not solution for our problem. We still need to supply bindist. Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
|
From: shelarcy <she...@gm...> - 2009-04-10 09:40:18
|
On Thu, 09 Apr 2009 17:38:59 +0900, Eric Y. Kow <eri...@gm...> wrote: >> > - install wxWidgets (configure, etc) >> > - install wxc (configure, etc) >> > - cabal install wx >> >> I agree this change is useful. But that is not good for all Windows users. >> I think we must modify your patch to support binary distribution. > > Do you have a clear picture what needs to be done? I don't really. I think we need not remove wxcore-install-files, (WXCORE-LIB) and other make targets. We just modify all and install targets, and add wxcore-gen and wxcore-install targets. For example: all: wxcore-gen install: wxc-install-files wxcore: wxcore-gen $(WXCORE-LIBS) wxcore-gen: wxd wxc wxcore-dirs $(WXCORE-GEN-HS) wxcore-install wxcore-install-files wxcore-register Then we can build bindist by following command. ./configure make make install (Windows doesn't require this command.) make wxcore make wxcore-install make wx make bindist We use above solution for removing wx package from make process before. We can use it for current problem, too. Alternative solution is that "make bindist" copies wxcore/dist and wx/dist file to make binary distribution. I don't know this is easy or not. Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
|
From: <E....@br...> - 2009-04-09 19:11:41
|
Here are three new patches which makes wxcore require wxc. Does this move us closer to doing the right thing? I'm still not sure what we need to do to account for bindist, though? Previously sent --------------- Wed Apr 8 11:38:47 BST 2009 Eric Kow <E....@br...> * Move wxcore.cabal to wxcore and use Simple build method. The assumption here is that the automatically generated files have already been built. Wed Apr 8 11:40:33 BST 2009 Eric Kow <E....@br...> * Do not build wxcore objects (let cabal do that). Wed Apr 8 11:41:20 BST 2009 Eric Kow <E....@br...> * Remove targets for building wxcore. New patches ----------- Thu Apr 9 18:34:23 BST 2009 Eric Kow <E....@br...> * Generate a pkg-config file for our wxc. Thu Apr 9 20:05:25 BST 2009 Eric Kow <E....@br...> * Install libwxc.pc file in pkgconfig dir. Thu Apr 9 20:09:09 BST 2009 Eric Kow <E....@br...> * Express dependency on wxc in wxcore.cabal via pkgconfig. |
|
From: Eric Y. K. <eri...@gm...> - 2009-04-09 08:39:07
|
On Thu, Apr 09, 2009 at 14:01:27 +0900, shelarcy wrote: > > * Remove targets for building wxcore. > > Why this changes doesn't care about "make bindist"? It's not deliberate. It shouldn't be too difficult to revise make bindist to also include the new purely cabalised wxcore. > Windows user doesn't have unix shell (e.g. msys or cygwin) in default. > And current Cabal doesn't care about installing C library binary > before building Haskell project. So, breaking binary distribution > causes serious problem. One thing we could consider doing is shipping a .pc file for wxc http://en.wikipedia.org/wiki/Pkg-config Cabal has support for it, so we could get the wxcore cabal file to require the wxc with the pkgconfig-depends flag > > - install wxWidgets (configure, etc) > > - install wxc (configure, etc) > > - cabal install wx > > I agree this change is useful. But that is not good for all Windows users. > I think we must modify your patch to support binary distribution. Do you have a clear picture what needs to be done? I don't really. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
|
From: shelarcy <she...@gm...> - 2009-04-09 05:13:53
|
On Thu, 09 Apr 2009 03:12:49 +0900, Eric Kow <eri...@gm...> wrote: > On Wed, Apr 08, 2009 at 19:28:06 +0200, Mads Lindstrøm wrote: >> I link to Huber's langauge-c >> http://hackage.haskell.org/cgi-bin/hackage-scripts/package/language-c >> for those who want to check it out. >> >> Anyway, can we do with a C parser? Won't we need a C++ parser? > > I guess that depends if those header files in wxWidgets happen to be C > parseable. wxWidget header files also use C++ features (e.g. class and template). So, we need a C++ parser. Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
|
From: shelarcy <she...@gm...> - 2009-04-09 05:01:43
|
Hi, On Wed, 08 Apr 2009 20:52:58 +0900, <E....@br...> wrote: > Wed Apr 8 11:41:20 BST 2009 Eric Kow <E....@br...> > * Remove targets for building wxcore. Why this changes doesn't care about "make bindist"? Windows user doesn't have unix shell (e.g. msys or cygwin) in default. And current Cabal doesn't care about installing C library binary before building Haskell project. So, breaking binary distribution causes serious problem. You can see this problem following thread. http://www.haskell.org/pipermail/hopengl/2009-March/000795.html http://www.haskell.org/pipermail/libraries/2009-April/011493.html > So what this patch bundle aims to do is to move us in the direction of only > using the configure and make stuff to build wxc, install wxc and generate the > wxcore Haskell files with wxdirect. > > I don't know yet if this is the right way to about things. All I noticed is > that wxcore really does build with the Simple method once you have generated > the hs files. I guess the idea would be that we would have to generate the > files and then release them on hackage. I also don't know if the generated > .hs files are platform-independent. If they are not, would it be difficult > to make them so? > > Anyway, if this works as expected then we can tell people: > > - install wxWidgets (configure, etc) > - install wxc (configure, etc) > - cabal install wx I agree this change is useful. But that is not good for all Windows users. I think we must modify your patch to support binary distribution. Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
|
From: <E....@br...> - 2009-04-08 18:17:47
|
Wed Apr 8 19:15:43 BST 2009 Eric Kow <E....@br...> * Remove seemingly unused external definitions in wxEiffel headers. |
|
From: Eric K. <eri...@gm...> - 2009-04-08 18:12:54
|
On Wed, Apr 08, 2009 at 19:28:06 +0200, Mads Lindstrøm wrote: > I link to Huber's langauge-c > http://hackage.haskell.org/cgi-bin/hackage-scripts/package/language-c > for those who want to check it out. > > Anyway, can we do with a C parser? Won't we need a C++ parser? I guess that depends if those header files in wxWidgets happen to be C parseable. Anyway, it's not that great a priority. I was just looking at various ways we could chip away at the wxhaskell build method and make cabal installing wxhaskell smoother. This doesn't play too great a role in it. But getting rid of this Eiffel stuff does make wxHaskell a little less random looking, which could be handy if we want to explain to outsiders what's going on later. I wish we could convince wxWidgets HQ to take care of wxc. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
|
From: Mads L. <mad...@ya...> - 2009-04-08 17:28:16
|
On Wed, 2009-04-08 at 13:59 +0100, Eric Kow wrote: > Whoops, maybe it's not a good idea to apply this... > > I was trying to get rid of external definitions like this > > - wxEVT_COMMAND_BUTTON_CLICKED : INTEGER is > > - external "C use %"ewxw_glue.h%"" > > - alias "expEVT_COMMAND_BUTTON_CLICKED" > > - end > > But not constants like these > > > - wxTR_EDIT_LABELS: INTEGER is 512 > > - wxTR_ROW_LINES: INTEGER is 1024 > > - wxTR_HIDE_ROOT: INTEGER is 2048 > > - wxTR_HAS_VARIABLE_ROW_HEIGHT: INTEGER is 128 > > Sorry for the noise. > > But since I'm writing another message to the list, how about using > Benedikt Huber's language-c module to parse the wxWidgets includes > files rather this handwritten Eiffel layer of constants? > I link to Huber's langauge-c http://hackage.haskell.org/cgi-bin/hackage-scripts/package/language-c for those who want to check it out. Anyway, can we do with a C parser? Won't we need a C++ parser? /Mads > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ wxhaskell-devel mailing list wxh...@li... https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel |
|
From: Eric K. <eri...@gm...> - 2009-04-08 12:59:36
|
Whoops, maybe it's not a good idea to apply this... I was trying to get rid of external definitions like this > - wxEVT_COMMAND_BUTTON_CLICKED : INTEGER is > - external "C use %"ewxw_glue.h%"" > - alias "expEVT_COMMAND_BUTTON_CLICKED" > - end But not constants like these > - wxTR_EDIT_LABELS: INTEGER is 512 > - wxTR_ROW_LINES: INTEGER is 1024 > - wxTR_HIDE_ROOT: INTEGER is 2048 > - wxTR_HAS_VARIABLE_ROW_HEIGHT: INTEGER is 128 Sorry for the noise. But since I'm writing another message to the list, how about using Benedikt Huber's language-c module to parse the wxWidgets includes files rather this handwritten Eiffel layer of constants? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
|
From: <E....@br...> - 2009-04-08 12:31:19
|
This would be a first step in simplifying the auto-generation of the wxcore stuff. One thing I'm wondering though is do we really have to define these in Eiffel? If we could rewrite them in C, it would make things feel a little less exotic. Better yet, some of these constants appear to be defined in /usr/include/wx-2.8 anyway. Could we teach wxdirect to parse those files (for example, teach it what enumerations are) directly so that we avoid duplicating information and having to modify our constants lists by hand? Wed Apr 8 13:16:09 BST 2009 Eric Kow <E....@br...> * Remove seemingly unused wxEiffel definitions. These are ignored by wxdirect anyway. |
|
From: <E....@br...> - 2009-04-08 10:45:47
|
Hi everyone, This bundle is mostly for discussion. The idea is that "cabal install wxcore" should really "just work". For Cabalised projects that use wxHaskell, the difficulty of installing wxcore is a big stumbling block. So what this patch bundle aims to do is to move us in the direction of only using the configure and make stuff to build wxc, install wxc and generate the wxcore Haskell files with wxdirect. I don't know yet if this is the right way to about things. All I noticed is that wxcore really does build with the Simple method once you have generated the hs files. I guess the idea would be that we would have to generate the files and then release them on hackage. I also don't know if the generated .hs files are platform-independent. If they are not, would it be difficult to make them so? Anyway, if this works as expected then we can tell people: - install wxWidgets (configure, etc) - install wxc (configure, etc) - cabal install wx Thanks! Wed Apr 8 11:38:47 BST 2009 Eric Kow <E....@br...> * Move wxcore.cabal to wxcore and use Simple build method. The assumption here is that the automatically generated files have already been built. Wed Apr 8 11:40:33 BST 2009 Eric Kow <E....@br...> * Do not build wxcore objects (let cabal do that). Wed Apr 8 11:41:20 BST 2009 Eric Kow <E....@br...> * Remove targets for building wxcore. |
|
From: shelarcy <she...@gm...> - 2009-04-04 00:29:21
|
Pushed. 2009/4/3 shelarcy <she...@gm...>: > Fri Apr 3 23:09:05 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2009 shelarcy <shelarc= > y...@gm...> > * Fix building profile version library with GHC 6.10.2. -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
|
From: Kido T. <she...@co...> - 2009-04-04 00:17:08
|
Fri Apr 3 10:09:05 EDT 2009 shelarcy <she...@gm...>
* Fix building profile version library with GHC 6.10.2.
Ignore-this: 84f415959b79d8d821bad8cb579117bc
M ./makefile -1 +1
View patch online:
http://code.haskell.org/wxhaskell/_darcs/patches/20090403140905-c1071-eedf4c867d4941ba8de4945e552bc9f2ab64e5e2.gz
|
|
From: shelarcy <she...@gm...> - 2009-04-03 14:13:15
|
DarcsURL: C:/home/shelarcy/wxhaskell MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_" --=_ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Fri Apr 3 23:09:05 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2009 shelarcy <shelarc= y...@gm...> * Fix building profile version library with GHC 6.10.2. --=_ Content-Type: text/x-darcs-patch; name="fix-building-profile-version-library-with-ghc-6_10_2_.dpatch" Content-Transfer-Encoding: quoted-printable Content-Description: A darcs patch for your repository! New patches: [Fix building profile version library with GHC 6.10.2. shelarcy <she...@gm...>**20090403140905 Ignore-this: 84f415959b79d8d821bad8cb579117bc ] hunk ./makefile 683 $(WXCORE-CORE-A-PROF-OBJS) $(WXCORE-CORE-B-PROF-OBJS) $(WXCORE-CORE-C-PROF= -OBJS) $(WXCORE-PROF-OBJS): $(WXCORE-IMPORTSDIR)/%.p_o: $(WXCORE-SRCDIR)/%.= hs @$(call compile-prof-hs,$@,$<,$(WXCORE-HCFLAGS) $(HC-PROF-FLAGS) -Iwxc/in= clude,$(WXCORE-IMPORTSDIR),$(WXCORE-HSDIRS) ) $(WXCORE-STUB-PROF-OBJS): $(WXCORE-IMPORTSDIR)/%_stub.p_o: $(WXCORE-SRCDIR= )/%.hs - $(HC) -c $(basename $@).c + $(HC) -c $(basename $@).c -osuf p_o = # automatically include all dependency information. -include $(WXCORE-DEPS) Context: [Use Foreign.Concurrent.newForeignPtr instead of Foreign.ForeignPtr.newFore= ignPtr. shelarcy <she...@gm...>**20090321065748 Ignore-this: a7a92ba715f83d252d3b89158b34ba59 ] = [Move reimp.exe to wxc/util. shelarcy <she...@gm...>**20090316033739 Ignore-this: 5d26d2c189796b8a4e91c6418643cd4f ] = [Add util directory to wxc. shelarcy <she...@gm...>**20090313065547 Ignore-this: b133e073586824e1d9f4e6c57779a06c util contains a few files. These are come from Subversion repository at http://snmsts.dreamhosters.com/wxc for to sync two repositories. ] = [Add socket.cpp and sckaddr.cpp to wxc. shelarcy <she...@gm...>**20090313064952 Ignore-this: a15673b832efc7dc3b7d99544e572b96 MERGED: add socket/sckaddr ------------------------------------------------------------------------ r25 | snmsts | 2009-01-17 10:33:37 +0900 (Sat, 17 Jan 2009) | 1 line from Subversion repository at http://snmsts.dreamhosters.com/wxc ] = [Use filepath package instead of defining same functionality (dirSep and pa= thSep are deprecated now). shelarcy <she...@gm...>**20090312181517 Ignore-this: d39415c33e3c0f4a4326b4e29a9fe3a1 ] = [Change Color type function to be more flexible. shelarcy <she...@gm...>**20090312171934 Ignore-this: 5e778e86a6123c8f77ef92cebbac5ca8 ] = [Fix typo in previous Refactor to return wxPoint/wxSize/wxRect class direct= ly patch. shelarcy <she...@gm...>**20090312171345 Ignore-this: 9788064c548976d584252389fb26191d ] = [Refactor to return wxPoint/wxSize/wxRect class directly in wxc. shelarcy <she...@gm...>**20090310053838 Ignore-this: e414ff89344e856a3f61a0e6f318c427 We accept to return wxPoint, wxSize and wxRect class directly in wxc, now. = We always used passing int* pointer arguments to return Point, Size and Re= ct type, previously. But this convention is complex. We sometimes mistook to return wxPoint, wxSize and wxRect. Its mistake causes problems. = So, we accept to return wxPoint, wxSize and wxRect now. And we refactor so= me old code to return these types, to show we can return these types now. ] = [Bump version number to 0.11.1.2. shelarcy <she...@gm...>**20090305140242 Ignore-this: f13691126a6cf23247b66e55488065dd ] = [Fix: previous Refactor to use C++ bool directly patch causes build error o= n Linux. shelarcy <she...@gm...>**20090305125306 Ignore-this: 7059932f64f20392ceee48d255d31045 ] = [Fix: wxHaskell documents refer to old sourceforge's web page. shelarcy <she...@gm...>**20090301075411 Ignore-this: e2228b995afcf476bcd3e02195519ba8 ] = [Add to generate Readme.txt file for source distribution. shelarcy <she...@gm...>**20090301075126 Ignore-this: fc749fdadbd9e49b38682acbab85e6c ] = [Refactor to use C++ bool directoly, instead of casting to int type and con= verting to bool type. shelarcy <she...@gm...>**20090228023601 = We cast int type where wxWidgets' method returns bool type, and we convert int to bool where wxWidgets method's argument is bool. = But some new wxc code uses bool type directly. This causes problems. = So, we changed to use bool type directly everwhere in wxc code. We hope this change avoid to occur problem and fixes a few bugs. ] = [Change version number from 0.11.1 to 0.11.1.0. shelarcy <she...@gm...>**20090227150124 Ignore-this: c6772c8eac4bd552702e469b76a3101a ] = [Fix: managed.cpp causes problem on Linux (Debian and Ubuntu) platform. shelarcy <she...@gm...>**20090115080604 = MERGED: manage to run managed.cpp on ubuntu r21 | snmsts | 2009-01-10 05:49:49 +0900 (Sat, 10 1 2009) from Subversion repository at http://snmsts.dreamhosters.com/wxc = This change probably fixes #1924535. See http://snmsts.dreamhosters.com/diary/index.cgi?routine=3Done&name=3D20= 09-01-08-1756 (Note: This page isn't English page. This page is written in Japanese.) = ] = [Add int / C++ bool conversion function in wxc. shelarcy <she...@gm...>**20090113135754 Ignore-this: 83a08a3687437074e79f8c8da12c1626 ] = [Remove unused eljtreectrl.cpp. shelarcy <she...@gm...>**20090113104755 Ignore-this: a64b576e93152ebe3474c368fcfc03e9 ] = [Refactor to use wxString instead of calling WString (wxChar) directly. shelarcy <she...@gm...>**20090113094641 = This change will be easy to add encoding mode. wxWidget 2.9 and 3.0 will support to build UTF-8 mode. If we use wxChar directly, we must change many part to support this build mode. = http://www.wxwidgets.org/develop/roadmap.htm = And we think we get some advantages from this change. utf8-string package only support UTF-8, so we want to use full unicode support we must write UTF-8 <-> UTF-16 <-> UTF-32 conversion layer, or we must support new UTF-8 build mode. = (C++0x and C1x will support new string charactor set types, char16_t and char32_t. Haskell and wxWidgets will support these types if compiler (e.g. gcc, VC) support theirs. If we use abstract layer to use string, we can extend wxHaskell support soonly when compiler and library change.) = ] = [Use wxString_Length function instead of getting wxString twice. shelarcy <she...@gm...>**20090108142643 Ignore-this: 2160aa7a6c9e4b5ed07ea0f17be20332 ] = [Fix typos in previous color's alpha channel support. shelarcy <she...@gm...>**20090107021037 Ignore-this: 710e1ec9472142465ed050c97e49892d ] = [Add experimental alpha channel support to Color type. shelarcy <she...@gm...>**20090106182310 Ignore-this: 6c35ed5d80bed81134a6110cd9cfb60a ] = [Add Word support. shelarcy <she...@gm...>**20090106171139 Ignore-this: 81376472899f15f9724f724b656c251d ] = [Change Color's primitive type from CChar to Word8. shelarcy <she...@gm...>**20090106151818 Ignore-this: a63da969a83ee42f141db3797b824fc8 ] = [Add Word8 and Word32 support. shelarcy <she...@gm...>**20090106141358 Ignore-this: 704189efa0ea7576c4752df6d9a39faf ] = [Bump version number to 0.11.1 shelarcy <she...@gm...>**20090106132911 Ignore-this: d945970996e6812d312a0592c2ff2b6e ] = [Remove unused wxWidgets 2.4 and 2.6's Visual Studio project files. shelarcy <she...@gm...>**20090105012854 Ignore-this: 20cc431e49694e048d1d676170200ed6 ] = [TAG 0.11.0 shelarcy <she...@gm...>**20090102223052] = Patch bundle hash: b0437436a940d4d754a68ff0cae9fce10abf828e --=_-- . |
|
From: shelarcy <she...@gm...> - 2009-03-22 01:09:18
|
Pushed. 2009/3/22 shelarcy <she...@gm...>: > Sat Mar 21 15:57:48 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2009 shelarcy <shelarc= > y...@gm...> > * Use Foreign.Concurrent.newForeignPtr instead of Foreign.ForeignPtr.newF= > oreignPtr. -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
15 messages has been excluded from this view by a project administrator.
