You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Eric K. <eri...@gm...> - 2009-04-13 11:25:06
|
Dear wxc users, So a few years ago, Surendra Singhi suggested that we automate the generation of the C wrappers for wxWidgets. Now with wxWidgets 2.8 out for some time and the wxWidgets team is busy working towards 3.0, I would like to suggest that we revisit this discussion. Let's not update this wrapper to work with wxWidgets 3.0. Instead, how about starting over from something that's completely automatically generated? In fact, we've just had some discussion on this on the wxHaskell mailing list, in which we attempt to generate these bindings from the Doxygen XML output (thanks to Kevin Ollivier from the wxWidgets team for the idea): * https://sourceforge.net/mailarchive/message.php?msg_name=20090409175728.GA15805%40brighton.ac.uk * https://sourceforge.net/mailarchive/message.php?msg_name=8AD3AF71-4A6A-4984-8925-3C42F7F9B0E2%40theolliviers.com Having this kind of automatically generated code could save us a lot of work and help us to keep our bindings up to date. If we play our cards right, we may be able to get this script into the official wxWidgets tree (!), which could considerably simplify matters. So are there any wxOcaml and wxEiffel or other wxC users around? If so, could you comment on whether this technique could work well for you, or what you would need from a WXC binding? In particular, wxHaskell seems to make use of extra type information for our marshalling layer: http://code.haskell.org/wxhaskell/wxc/include/wxc_types.h How about you? And how can we move forward? Thanks! Eric PS. Below is a small extract of the automatically-generated code: > /* Constructor */ > wxButton wxButton_wxButton (); > /* Constructor */ > wxButton wxButton_wxButton (wxWindow * _parent, wxWindowID _id, > wxString & _label, wxPoint & _pos, > wxSize & _size, long _style, > wxValidator & _validator, wxString & _name); > void wxButton_Destruct (wxButton * _obj); > bool wxButton_Create (wxButton _obj, wxWindow * _parent, wxWindowID _id, > wxString & _label, wxPoint & _pos, wxSize & _size, > long _style, wxValidator & _validator, > wxString & _name); > wxString wxButton_GetLabel (wxButton _obj); > wxWindow *wxButton_SetDefault (wxButton _obj); > void wxButton_SetLabel (wxButton _obj, wxString & _label); > wxSize wxButton_GetDefaultSize (wxButton _obj); -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric Y. K. <eri...@gm...> - 2008-02-23 09:35:48
|
Hi wxc developers, Attached is a patch to enable Unicode support in wxc. Unfortunately, some parasite changes might also have snuck in there, so you might want to keep an eye out. Also, I've had to do some ugly stuff (see other.patch) to make it compile :-/ One thing which should be easy to fix is that wxc does not recognise Intel Macs as being Macs (it sets the DLL_EXTS) incorrectly. Cheers, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric Y. K. <eri...@gm...> - 2006-08-13 14:57:27
|
On Sun, Aug 13, 2006 at 09:37:07 -0400, Surendra Singhi wrote: > >Presumably, the _wrap code does all the interpreter-wrapping magic, > >but that's in C++, which is not what I'm looking for. >=20 > Even the current wxC is in C++, the important thing is that the > function which it exports follow C semantics. Of course! I feel positively silly for not realising this :-)=20 Smooshing C++ down to C means writing C++ code that acts like C on the outside, and hides away all that object oriented machinery on the inside. I got scared off when I saw classes and templates in the _wrap code; but if I had scrolled down, I would have found the exported functions... =20 > I am not much familiar with the Python module of SWIG, but I think > Python like Ruby, TCL etc. requires the foreign-function > interface(FFI) code to be written in C, whereas Lisp requires that to > be in Lisp, I am not much familiar with Haskell, but think it is the > same. The AllegroCL and CFFI (the one on which I am currently working) > module just generate bare bone C wrapper code for the C++ file. I think the Haskell FFI wants Haskell code, i.e. in the Haskell stuff, you write something like foreign import ccall "string.h strlen" cstrlen :: Ptr CChar -> IO CSize And that gives you a nice Haskell function cstrlen with type Ptr CChar -> IO CSize > I am attaching proof of concept sample interface file and the generated c= ode.=20 Thanks! > >Also, say we went for the third scenario, generating Y code directly (Y > >=3D=3D your favourite language) I get the impression that the swig inter= face > >files, the .i stuff, is target-language specific. Is this the case? > Yes, they are. Ok, well, in either case, (I'm not sure if I can speak for the rest of the wxhaskell crowd), but I think our goals would be short term) get a new release of wxC/wxhaskell using the old=20 hand-written code, targeting wxWidgets 2.6.3 long term) generate wxC automatically using SWIG adapt our wxFoo wrappers to use the SWIG generated code rather than the hand-written stuff Of course, languages like O'Caml might feel better off having the O'Caml-specific bits instead of a generic wxC, but those of us for whom a direct SWIG-wrapper interface is tricky would probably be happy with this. Some day later, I'm going to try using the -cffi target to generate bare bones C. I'm still a little bit worried because our Haskell-FFI generator relies on C macros to provide certain annotations... So for example, a wxC header like this: void wxButton_SetDefault( TSelf(wxButton) _obj ); gets boiled down by the C preprocessor into boring old void wxButton_SetDefault( wxButton* _obj ); That might seem kinda pointless -- why not just write wxButton* directly -- but we need to do this, because our code generator does funky Haskell things with that TSelf annotation. Saying that we're going from C directly to Haskell is a bit of a fib. We use annotations like TSelf to sneak some of that C++ stuff in as well. But maybe that's not a big deal. It seems like we could still use SWIG to generate the bulk of the code (i.e. the C++ smooshing stuff), and either continue writing the header files by hand, or be really clever and generate them automatically as well. Definitely a long term goal though, not an immediate priority. > >Would it be feasible/useful to share bits of swig template across many > >languages? > > > Depends, you can share stuff with languages which are similar. Is OCaml s= imilar to Haskell?=20 I'm not the best person to ask. Hopefully somebody who knows more about programming languages will pick up on this thread! They're both functional languages, though O'Caml is strict, where Haskell is not; and O'Caml has object-oriented bits and we do not. Our basic types are probably different, i.e. a Haskell Int probably isn't the same as an O'Caml one, nor a C one for that matter. I'm also not sure what the SWIG wrapper generates for O'Caml; if it uses neat stuff like Functors, there might be a lot of extra work adapting that to Haskell (typeclasses?) Cheers, --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: <EFu...@ne...> - 2006-08-13 13:37:20
|
Hello, "Eric Y. Kow" <eri...@gm...> wrote: >On Thu, Aug 10, 2006 at 04:26:17 -0400, Surendra Singhi wrote: >> >Are you saying that SWIG can give us this? >> >(use SWIG to generate wxC) >> > wxWidgets --> wxC (via SWIG) --> Y wrapper --> Y code >> > >> Definitely possible right now. > >[snip] > >> So, generate wxC automatically, and then generate Haskell wrapper >> automatically. Tryin swig on a c++ header file will give you a better >> idea of what kind of wrappers it produces. > >Could you please show us how to do this? A documentation link would >be great! I've looked through the manual, but maybe not in the right >places. > >I've been sort of dabbling with SWIG (starting with the wxPython code), >and I can generate Python code, or whatever target language. C does not >seem to be available as a target language. I notice that when I have a >file foo.cpp (and maybe a foo.i), running swig on it will give me >something like foo.py and foo_wrap.cxx. Presumably, the _wrap code does >all the interpreter-wrapping magic, but that's in C++, which is not what >I'm looking for. > >How would I generate something like wxC? Is this sort of thing - >smooshing C++ down to C - a common idiom among SWIG users, or do we have >to do something clever? Even the current wxC is in C++, the important thing is that the function which it exports follow C semantics. I am not much familiar with the Python module of SWIG, but I think Python like Ruby, TCL etc. requires the foreign-function interface(FFI) code to be written in C, whereas Lisp requires that to be in Lisp, I am not much familiar with Haskell, but think it is the same. The AllegroCL and CFFI (the one on which I am currently working) module just generate bare bone C wrapper code for the C++ file. I am attaching proof of concept sample interface file and the generated code. > >Also, say we went for the third scenario, generating Y code directly (Y >== your favourite language) I get the impression that the swig interface >files, the .i stuff, is target-language specific. Is this the case? Yes, they are. >Would it be feasible/useful to share bits of swig template across many >languages? > Depends, you can share stuff with languages which are similar. Is OCaml similar to Haskell? Cheers, -- Surendra Singhi http://ssinghi.kreeti.com/, http://www.kreeti.com __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp |
From: Eric Y. K. <eri...@gm...> - 2006-08-12 16:44:45
|
Hi again, On Thu, Aug 10, 2006 at 04:26:17 -0400, Surendra Singhi wrote: > >Are you saying that SWIG can give us this? > >(use SWIG to generate wxC) > > wxWidgets --> wxC (via SWIG) --> Y wrapper --> Y code > > > Definitely possible right now.=20 [snip] > So, generate wxC automatically, and then generate Haskell wrapper > automatically. Tryin swig on a c++ header file will give you a better > idea of what kind of wrappers it produces. Could you please show us how to do this? A documentation link would be great! I've looked through the manual, but maybe not in the right places. I've been sort of dabbling with SWIG (starting with the wxPython code), and I can generate Python code, or whatever target language. C does not seem to be available as a target language. I notice that when I have a file foo.cpp (and maybe a foo.i), running swig on it will give me something like foo.py and foo_wrap.cxx. Presumably, the _wrap code does all the interpreter-wrapping magic, but that's in C++, which is not what I'm looking for. How would I generate something like wxC? Is this sort of thing - smooshing C++ down to C - a common idiom among SWIG users, or do we have to do something clever? Also, say we went for the third scenario, generating Y code directly (Y =3D=3D your favourite language) I get the impression that the swig interface files, the .i stuff, is target-language specific. Is this the case? Would it be feasible/useful to share bits of swig template across many languages? Thanks, --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: <EFu...@ne...> - 2006-08-10 08:26:30
|
Hi, "Eric Y. Kow" <eri...@gm...> wrote: >On Wed, Aug 09, 2006 at 05:09:05 -0400, Surendra Singhi wrote: >> So, why not use a tool like SWIG*, to autogenerate C wrappers? >> wxPython, wxRuby, etc. they use SWIG to auto-generate the foreign >> library code. > >What do you mean by autogenerate C wrappers? Autogenerate C code, or >autogenerate the Your-Favourite-Language-Here (henceforth Y) code to >wrap around the wxWidgets C++ code? > At least autogenerate C code. Even generating Y code to wrap around is possible. >The current situation is this: > wxWidgets --> wxC (by hand) --> Y wrapper --> Y code >where Foo is your favourite language > Can be improved. >Are you saying that SWIG can give us this? >(use SWIG to generate wxC) > wxWidgets --> wxC (via SWIG) --> Y wrapper --> Y code > Definitely possible right now. >Or something even further like this? >(use SWIG to obsolete wxC) > wxWidgets --> Y wrapper of C++ (via SWIG) --> Y code > Ruby, Python, Java etc. do that. Will be hard to do that for a new language requires lot of SWIG understanding (because of C++ overloading and other complications), but doing for C would be easy. >I ask because the wxhaskell paper (2004) seems to think it'll be a lot >of work to have a Haskell binding to swig. Also, our Haskell wrapper >around the wxC stuff is generated automatically, so for us, once we have >wxC + annotations, we're happy. So, generate wxC automatically, and then generate Haskell wrapper automatically. Tryin swig on a c++ header file will give you a better idea of what kind of wrappers it produces. Few things which may require changing are, overloaded function names SWIG renames, say function func, as func1, func2, etc. Overloaded operators as Classname__add_, Classname__subtract_, etc. These names can be changed, certain functions can be ignored, by annotating SWIG interface files. Cheers, -- Surendra Singhi http://ssinghi.kreeti.com/, http://www.kreeti.com __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp |
From: Eric Y. K. <eri...@gm...> - 2006-08-09 22:38:37
|
On Wed, Aug 09, 2006 at 05:09:05 -0400, Surendra Singhi wrote: > So, why not use a tool like SWIG*, to autogenerate C wrappers? > wxPython, wxRuby, etc. they use SWIG to auto-generate the foreign > library code. What do you mean by autogenerate C wrappers? Autogenerate C code, or autogenerate the Your-Favourite-Language-Here (henceforth Y) code to wrap around the wxWidgets C++ code? The current situation is this: wxWidgets --> wxC (by hand) --> Y wrapper --> Y code=20 where Foo is your favourite language Are you saying that SWIG can give us this? (use SWIG to generate wxC) wxWidgets --> wxC (via SWIG) --> Y wrapper --> Y code=20 Or something even further like this? (use SWIG to obsolete wxC) wxWidgets --> Y wrapper of C++ (via SWIG) --> Y code I ask because the wxhaskell paper (2004) seems to think it'll be a lot of work to have a Haskell binding to swig. Also, our Haskell wrapper around the wxC stuff is generated automatically, so for us, once we have wxC + annotations, we're happy. The last proposition seems like it would be best in the long term, but in the short term, it seems like it would involve changing more stuff. As you can tell, I don't really know much about SWIG. Just glanced through the online doc... seems handy. --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: <EFu...@ne...> - 2006-08-09 09:09:21
|
Hi, I maintain wxCL project, and we currently use wxC. But, I feel that since wxWidgets is a moving target, keeping up with it will always be an issue. So, why not use a tool like SWIG*, to autogenerate C wrappers? wxPython, wxRuby, etc. they use SWIG to auto-generate the foreign library code. *I also maintain the CFFI module of SWIG, so can help a bit in this direction. Regards, -- Surendra Singhi http://ssinghi.kreeti.com/, http://www.kreeti.com __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp |
From: Eric Y. K. <eri...@gm...> - 2006-08-09 06:59:39
|
On Wed, Aug 09, 2006 at 15:50:11 +1000, James Dumay wrote: > Should wxc be focusing on the 2.7.x branch (yes, I know the API is unstab= le) > or the 2.6.x series? I personally intend to work against the 2.7.x series > for wx.NET. I personally would feel more comfortable targeting something stable. --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: James D. <jam...@gm...> - 2006-08-09 05:50:17
|
Should wxc be focusing on the 2.7.x branch (yes, I know the API is unstable) or the 2.6.x series? I personally intend to work against the 2.7.x series for wx.NET. James ---------- Forwarded message ---------- From: Vadim Zeitlin <va...@wx...> Date: Aug 7, 2006 8:46 AM Subject: [wx-announce] ANN: wxWidgets 2.7.0 released To: wx-...@li... Announcing wxWidgets 2.7.0: a cross-platform GUI toolkit ---------------------------------------------------------------- August 5th, 2006 -- the wxWidgets team is pleased to announce a new release of the mature cross-platform C++ application framework. The following platforms are supported: - Windows 95/98/ME, Windows NT, Windows 2000, Windows XP - Windows 64 on Itanium and x86-64 architectures - Windows CE, including Pocket PC 2003 and Smartphone 2003 - Unix (Linux, *BSD, Solaris, AIX, HP-UX, IRIX, Tru64) and VMS with GTK+ - Unix with X11 (beta) - Unix with Motif/Lesstif - Mac OS X using Carbon - Mac OS X using Cocoa (beta) - OS/2 (beta) - MGL for Linux and DOS - Palm OS (alpha) To get wxWidgets, please go to the Download page at: http://www.wxwidgets.org/ This is the first version in the new 2.7 development series. Please notice that this series is called "development" and not "stable" solely because ABI or API compatibility is not assured between different 2.7.x series versions. Rest assured however that these potentially incompatible changes are made in order to evolve the toolkit to the next ABI stable release series (2.8.x) and that normally efforts are made to preserve compilation compatibility, so often moving to a new development release just requires a full recompile of the application using wxWidgets. There are currently no known issues with the stability of the programs using this version. There have been many changes since the 2.6 series, please see the change log file included in the distribution for more details. The most significant additions to the GUI part of the libraries were: - AUI (advanced user interface) library providing dockable windows and much more - richtext library implementing wxRichTextCtrl - New wxComboCtrl and wxOwnerDrawnComboBox controls - New wxTreebook book-like control - New wxColour/Dir/File/Font/PickerCtrls - wxHyperlinkCtrl control *** About wxWidgets wxWidgets is a comprehensive open-source, multi-platform C++ GUI framework, that can be used to build commercial and free software. First released in 1992 under the name wxWindows, it's increasingly used by organisations and individuals all over the world due to its winning combination of sophistication, wide platform coverage, ease of use, unrestrictive licence and vibrant user community. For most ports, wxWidgets adopts the native look and feel of each platform since it uses the native widget sets. There is also a generic widget set, used for example by the wxX11 port - no other widget set is required, giving the potential for embedded use. An extraordinary range of classes is provided - but don't be put off by this because most people find wxWidgets easier to learn and use than MFC and other frameworks. As well as comprehensive support for the usual widgets, advanced features include: HTML viewing/printing, wxImage class providing handlers for reading and writing many image types, resizeable panels and dialogs on all platforms, document/view, OpenGL support, HTML-based and context-sensitive help, wizards, drag and drop, a grid class, ODBC support, threads, sockets, container classes, a styled text control, and much more. A 2,000-page reference manual is provided in HTML, MS HTML Help, WinHelp, wxWidgets Help and PDF formats, and there are over eighty samples and demos. If you're an MFC user, you'll find many wxWidgets concepts reassuringly familiar, while often clearer and more consistent. If you're not, you should still find it intuitive from the start. wxWidgets bindings for many other languages are available, including Python, Perl, Basic, Lua, JavaScript and Eiffel. If you're considering wxWidgets, do check out some of these links: http://www.wxwidgets.org/about/feedback.htm ; Comments from users http://www.wxwidgets.org/about/screensh.htm ; Screenshots http://www.wxwidgets.org/about/users.htm ; Some of our users Have fun! The wxWidgets team --------------------------------------------------------------------- To unsubscribe, e-mail: wx-...@li... For additional commands, e-mail: wx-...@li... |
From: James D. <jam...@gm...> - 2006-08-08 23:56:41
|
SGV5IGlmIHlvdSBndXlzIGFyZSBnb2luZyB0byBtYWtlIHd4QyByb2NrIEkgZG9udCB0aGluayBp dCBtYXR0ZXJzIHRvbyBtdWNoCndoYXQgcmV2aXNpb24gY29udHJvbCBzeXN0ZW0gaXMgdXNlZCA6 KQoKWWVhaCBkYXJjcyByb2NrcyA6KQoKV2hlbiBhcmUgeW91IHN0YXJ0aW5nIHRoZSByZWZhY3Rv cj8KCkphbWVzCgpPbiA4LzcvMDYsIEVyaWMgWS4gS293IDxlcmljLmtvd0BnbWFpbC5jb20+IHdy b3RlOgo+Cj4gSGkgd3hDIGRldmVsb3BlcnMgKGFuZCB3eCogcmVmYWN0b3JlcnMpLAo+Cj4gQXMg SSBtZW50aW9uZWQgcmVjZW50bHksIHRoZSB3eGhhc2tlbGwgcHJvamVjdCBpcyBzbG93bHkgYmVp bmcgcmV2aXZlZC4KPiBPbmUgb2YgdGhlIGZpcnN0IHRoaW5ncyB3ZSBwbGFuIHRvIGRvIGlzIHN3 aXRjaCBvdmVyIGZyb20gQ1ZTIHRvIGRhcmNzLgo+IFdlIGFsc28gd2FudCB0byBmYWN0b3Igb3Vy IHd4QyBzdHVmZiBhbmQgbWFrZSBzb21lIGltcHJvdmVtZW50cyB0byBpdC4KPiBJIHRoaW5rIHRo aXMgcHJvY2VzcyB3b3VsZCBiZSBlYXNpZXIgaWYgd3hDIHN3aXRjaGVkIHRvIGRhcmNzIGFzIHdl bGwsCj4gc28gSSB3b3VsZCBsaWtlIHRvIGFzazogYW55IG9iamVjdGlvbnMgdG8gdGhlIHN3aXRj aD8KPgo+IEJlbG93IEkgd2lsbCBnaXZlIGEgdHdvIHNlY29uZCBvdmVydmlldyBvZiBkYXJjcyBh bmQgd2h5IGl0IG1hdHRlcnMKPiB0byB3eEMgYW5kIHRoZW4gZWxhYm9yYXRlIG9uIGVhY2ggb2Yg bXkgcG9pbnRzLgo+Cj4gd2h5IGRhcmNzIGlzIHJlbGV2YW50IHRvIHd4Qwo+IC0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0KPiBEYXJjcyBpcyBhIGNvbXBsZXRlbHkgZGVjZW50cmFsaXNlZCB2 ZXJzaW9uIGNvbnRyb2wgc3lzdGVtLCB3aGljaCBtZWFucwo+IHRoYXQgaXQgc2hvdWxkCj4KPiAx LiBNYWtlcyB3eEMgbW9yZSByZXNpc3RhbnQgdG8gYml0cm90IGFuZCBwcm9qZWN0IGRlYXRoIHdo ZW4gaXRzCj4gICAgbWFpbnRhaW5lcnMgZG8gaGF2ZSBub3QgaGF2ZSB0aW1lIHRvIHdvcmsgb24g aXQuCj4KPiAyLiBNYWtlIGl0IG11Y2ggZWFzaWVyIGZvciBvdXRzaWRlcnMgdG8gc3VibWl0IG1v ZGlmaWNhdGlvbnMuCj4KPiBob3cgZGFyY3MgaGVscHMgdG8gcHJldmVudCBiaXRyb3QKPiAtLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBJZiB0aGUgbWFpbiBwZW9wbGUgd29ya2lu ZyBvbiB0aGUgcHJvamVjdCBzdG9wLCBhbnlib2R5IHRoZQo+IG91dHNpZGUgY291bGQgc2ltcGx5 ICdnZXQnIGFuIGFsdGVybmF0aXZlIGNvcHkgb2YgdGhlIHJlcG9zaXRvcnksCj4gcGlja2luZyB1 cCB3aGVyZSB3ZSBsZWZ0IG9mZi4gIE1vcmVvdmVyLCBpZiB0aGUgbWFpbiBkZXZlbG9wZXJzIGZp bmQKPiB0aW1lIHRvIHN0YXJ0IG1haW50YWluaW5nIHRoZSBwcm9qZWN0IGFnYWluLCB0aGV5IGNh biBjaG9vc2UgdG8gJ3B1bGwnCj4gdGhlIHJlY2VudCBwYXRjaGVzIGluIGZyb20gdGhlIGFsdGVy bmF0aXZlIHJlcG9zaXRvcnksIHRodXMgaGVhbGluZyB0aGUKPiBmb3JrLgo+Cj4gVGhpcyBzb3J0 IG9mIHRoaW5nIHdvdWxkIGhhdmUgaGVscGVkIHVzIGEgbG90IHdoZW4gd3hoYXNrZWxsCj4gKHVu ZGVyc3RhbmRhYmx5KSBzdGFnbmF0ZWQuICBGb3IgZXhhbXBsZSwgSSB3YWl0ZWQgYSB5ZWFyIGZv ciBteSBVbmljb2RlCj4gcGF0Y2hlcyB0byBiZSBhY2NlcHRlZCwgYW5kIGR1cmluZyB0aGF0IHll YXIsIHBhdGNoZXMgd2VyZSBiZWluZyBwdXQgb24KPiB0b3Agb2YgbXkgcGF0Y2hlcy4gIEhhdmlu ZyBhIHRlbXBvcmFyeSBmb3JrIHRoYXQgd2Uga25ldyB3b3VsZCBoZWFsCj4gZWFzaWx5IHdvdWxk IGhhdmUgYmVlbiBhIGdyZWF0IGhlbHAuCj4KPiBJbnRlcmVzdGluZ2x5LCB3eEMgY2FuIGJlIHNl ZW4gYXMgZm9yayBvZiB3eGhhc2tlbGwuICBJdCBtaWdodCBiZQo+IHBvc3NpYmxlIHRvIHRoaW5n cyBpbiBhIHdheSB0aGF0IGludGVncmF0aW5nIG15IFVuaWNvZGUgcGF0Y2ggaW50bwo+IHd4aGFz a2VsbCBpcyBhIHRyaXZpYWwgY29uc2VxdWVuY2Ugb2YgaW50ZXJncmF0aW5nIGl0IGludG8gd3hD Lgo+Cj4gaG93IGRhcmNzIHNpbXBsaWZpZXMgb3V0c2lkZXIgY29udHJpYnV0aW9ucwo+IC0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBPbmUgd2F5IGl0IHNpbXBs aWZpZXMgdGhpbmcgaXMgYnkgYWxsb3dpbmcgZm9yIHRyaXZpYWwgZm9ya2luZyBhbmQKPiBtZXJn aW5nIGFzIEkgbWVudGlvbmVkIGFib3ZlLiAgQSBtb3JlIGNvbmNyZXRlIHdheSBpcyB0aGF0IGl0 IGFsbG93cwo+IHBlb3BsZSB0byBtYWtlIG9mZmxpbmUgbW9kaWZpY2F0aW9ucyB0byB0aGVpciBy ZXBvc2l0b3J5LCBjb21taXQKPiB0aGVtIGxvY2FsbHksIGFuZCBldmVudHVhbGx5ICdkYXJjcyBz ZW5kJy4KPgo+IFRoaXMgYXV0b21hdGljYWxseSBzZW5kcyB0aGUgcGF0Y2ggYnkgZW1haWwgdG8g dGhlIGRldmVsb3BlcnMsIHdobwo+IGNhbiB0aGVuIGNob29zZSB0byBhY2NlcHQgdGhlIHBhdGNo IGJ5ICdkYXJjcyBhcHBseSdpbmcgaXQgdG8gdGhlCj4gb2ZmaWNpYWwgcmVwb3NpdG9yeS4KPgo+ IE5vdGUgdGhhdCBsb3dlcmluZyB0aGUgYmFycmllciBvZiBlbnRyeSBpcyBlc3BlY2lhbGx5IHVz ZWZ1bCBmb3IKPiB3eEMgaW4gcGFydGljdWxhciBiZWNhdXNlIHdlJ3JlIGFpbWluZyB0byBiZSBh IGNvbW1vbiBjb2RlIGJhc2UKPiBmb3IgbWFueSBkaWZmZXJlbnQgd3gqIHByb2plY3RzLCBlYWNo IHdpdGggdGhlaXIgb3duIHNwZWNpYWwKPiByZXF1aXJlbWVudHMuCj4KPiBGaW5hbGx5LCBhIGJp dCBvZiBkaXNjbG9zdXJlIDogSSBoYXZlIHJlY2VudGx5IGJlY29tZSBpbnZvbHZlZCBpbiBkYXJj cwo+IGRldmVsb3BtZW50LCBzbyBJJ20gbm90IGNvbXBsZXRlbHkgZGlzaW50ZXJlc3RlZCBpbiB0 aGlzIGRpc2N1c3Npb24uCj4gVGhlbiBhZ2FpbiwgbXkgaW52b2x2ZW1lbnQgaW4gZGFyY3MgaXMg YSBnb29kIGV4YW1wbGUgb2Ygc2ltcGxpZnlpbmcKPiBvdXRzaWRlciBjb250cmlidXRpb25zLiAg QmVjb21pbmcgYSBkYXJjcyBoYWNrZXIgd2FzIHZlcnkgZWFzeSBmb3IgbWUKPiBiZWNhdXNlIEkg Y291bGQgc2ltcGx5IGZvcmsgb2ZmIGEgbG9jYWwgY29weSBvZiB0aGUgZGFyY3MgcmVwb3NpdG9y eSwKPiBzZW5kIG15IGNoYW5nZXMgaW4sIGFuZCBrZWVwIG9uIGhhY2tpbmcgd2hpbHN0IHdhaXRp bmcgZm9yIHRoZSBkYXJjcwo+IG1haW50YWluZXJzIHRvIHJldmlldyBteSBwYXRjaC4gIElmIGl0 IHdlcmVuJ3QgZm9yIGRhcmNzIHNlbmQsIEkgd291bGQKPiBwcm9iYWJseSBoYXZlIGdvdHRlbiBz aWNrIG9mZiB0aGUgd2hvbGUgcm91dGluZSwgZ2VuZXJhdGluZyB0aGUgcGF0Y2ggYnkKPiBoYW5k LCB3cml0aW5nIGEgbWFpbCBmb3IgaXQsIGFuZCBtb3JlIGFubm95aW5nbHksIGtlZXBpbmcgbXkg c2VudAo+IHBhdGNoZXMgc2VwZXJhdGUgZnJvbSBteSB3b3JrIGluIHByb2dyZXNzLiAgSXQncyBz aW1pbGFyIHRvIHRoZQo+IHdpa2lwZWRpYSBlZmZlY3QgLS0gZGFyY3MgbG93ZXJzIHRoZSBiYXJy aWVyIG9mIGVudHJ5IHRvIG91dHNpZGVycywKPiB3aGljaCBlbmNvdXJhZ2VzIHRoZW0gdG8gY29u dHJpYnV0ZSBhbmQgZXZlbnR1YWxseSBiZWNvbWUgbWVtYmVycyBvZiB0aGUKPiBjb21tdW5pdHku ICBXYW50IHRvIGZpeCBhIHR5cG8/ICBZb3UganVzdCBkbyBpdC4KPgo+IHNvIGJhY2sgdG8gdGhl IHF1ZXN0aW9uCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBTbyBpZiB3ZSBvbiB0aGUgd3ho YXNrZWxsIHNpZGUgZGlkIGFsbCB0aGUgd29yaywgd291bGQgeW91IGJlIHdpbGxpbmcKPiB0byBt YWtlIHRoZSBzd2l0Y2g/Cj4KPiBXZSBjYW4gZXZlbiBrZWVwIENWUyAodXNpbmcgdGhlIHdvbmRl cmZ1bCBUYWlsb3Igc2NyaXB0KSwgc28gdGhlIHJlYWwKPiBxdWVzdGlvbiBpcywgaWYgd2UgaGFk IGEgZGFyY3MgbWlycm9yIG9mIHRoZSB3eEMgcmVwb3NpdG9yeSwgY291bGQgd2UKPiBtYWtlIGl0 IHRoZSAib2ZmaWNpYWwiIHJlcG9zaXRvcnkgZm9yIHd4Qz8KPgo+IFRoYW5rcywKPgo+IC0tCj4g RXJpYyBLb3cgICAgICAgICAgICAgICAgICAgICBodHRwOi8vd3d3LmxvcmlhLmZyL35rb3cKPiBQ R1AgS2V5IElEOiAwOEFDMDRGOSAgICAgICAgIE1lcmNpIGRlIGNvcnJpZ2VyIG1vbiBmcmFuw6dh aXMuCj4KPgo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBUYWtlIFN1cnZleXMuIEVhcm4gQ2FzaC4gSW5m bHVlbmNlIHRoZSBGdXR1cmUgb2YgSVQKPiBKb2luIFNvdXJjZUZvcmdlLm5ldCdzIFRlY2hzYXkg cGFuZWwgYW5kIHlvdSdsbCBnZXQgdGhlIGNoYW5jZSB0byBzaGFyZQo+IHlvdXIKPiBvcGluaW9u cyBvbiBJVCAmIGJ1c2luZXNzIHRvcGljcyB0aHJvdWdoIGJyaWVmIHN1cnZleXMgLS0gYW5kIGVh cm4gY2FzaAo+IGh0dHA6Ly93d3cudGVjaHNheS5jb20vZGVmYXVsdC5waHA/cGFnZT1qb2luLnBo cCZwPXNvdXJjZWZvcmdlJkNJRD1ERVZERVYKPgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fCj4gV3hjLWRldmVsIG1haWxpbmcgbGlzdAo+IFd4Yy1kZXZl bEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9s aXN0cy9saXN0aW5mby93eGMtZGV2ZWwKPgo+Cj4KPgo= |
From: Eric Y. K. <eri...@gm...> - 2006-08-07 09:47:44
|
Hi wxC developers (and wx* refactorers), As I mentioned recently, the wxhaskell project is slowly being revived. One of the first things we plan to do is switch over from CVS to darcs. We also want to factor our wxC stuff and make some improvements to it. I think this process would be easier if wxC switched to darcs as well, so I would like to ask: any objections to the switch? Below I will give a two second overview of darcs and why it matters to wxC and then elaborate on each of my points. why darcs is relevant to wxC ---------------------------- Darcs is a completely decentralised version control system, which means that it should 1. Makes wxC more resistant to bitrot and project death when its maintainers do have not have time to work on it. 2. Make it much easier for outsiders to submit modifications. how darcs helps to prevent bitrot --------------------------------- If the main people working on the project stop, anybody the outside could simply 'get' an alternative copy of the repository, picking up where we left off. Moreover, if the main developers find time to start maintaining the project again, they can choose to 'pull' the recent patches in from the alternative repository, thus healing the fork. This sort of thing would have helped us a lot when wxhaskell (understandably) stagnated. For example, I waited a year for my Unicode patches to be accepted, and during that year, patches were being put on top of my patches. Having a temporary fork that we knew would heal easily would have been a great help. Interestingly, wxC can be seen as fork of wxhaskell. It might be possible to things in a way that integrating my Unicode patch into wxhaskell is a trivial consequence of intergrating it into wxC. how darcs simplifies outsider contributions ------------------------------------------- One way it simplifies thing is by allowing for trivial forking and merging as I mentioned above. A more concrete way is that it allows people to make offline modifications to their repository, commit them locally, and eventually 'darcs send'. This automatically sends the patch by email to the developers, who can then choose to accept the patch by 'darcs apply'ing it to the official repository. Note that lowering the barrier of entry is especially useful for wxC in particular because we're aiming to be a common code base for many different wx* projects, each with their own special requirements. Finally, a bit of disclosure : I have recently become involved in darcs development, so I'm not completely disinterested in this discussion. Then again, my involvement in darcs is a good example of simplifying outsider contributions. Becoming a darcs hacker was very easy for me because I could simply fork off a local copy of the darcs repository, send my changes in, and keep on hacking whilst waiting for the darcs maintainers to review my patch. If it weren't for darcs send, I would probably have gotten sick off the whole routine, generating the patch by hand, writing a mail for it, and more annoyingly, keeping my sent patches seperate from my work in progress. It's similar to the wikipedia effect -- darcs lowers the barrier of entry to outsiders, which encourages them to contribute and eventually become members of the community. Want to fix a typo? You just do it. so back to the question ----------------------- So if we on the wxhaskell side did all the work, would you be willing to make the switch? We can even keep CVS (using the wonderful Tailor script), so the real question is, if we had a darcs mirror of the wxC repository, could we make it the "official" repository for wxC? Thanks, --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: James D. <jam...@gm...> - 2006-08-04 13:25:05
|
SGV5IHRoaXMgaXMgY29vbCAtIEltIHN0YXJ0aW5nIHdvcmsgb24gYSBzYW5lIHJlZmFjdG9yIG9m IHd4Lk5FVCAtIGEgY29tbW9uCnd4YyB3b3VsZCBiZSBleGNlbGxlbnQuCgpKYW1lcwoKT24gOC80 LzA2LCBFcmljIEtvdyA8ZXJpYy5rb3dAZ21haWwuY29tPiB3cm90ZToKPgo+IE91cHMhIG1lYW50 IHRvIHNlbnQgdGhhdCB0byB0aGUgbGlzdC4KPgo+IC0tLS0tLS0tLS0gRm9yd2FyZGVkIG1lc3Nh Z2UgLS0tLS0tLS0tLQo+IEZyb206IEVyaWMgS293IDxlcmljLmtvd0BnbWFpbC5jb20+Cj4gRGF0 ZTogQXVnIDQsIDIwMDYgMzoxOCBQTQo+IFN1YmplY3Q6IFJlOiBbd3hDLWRldmVsXSBXaGVyZSB0 byBmaW5kIHRoZSBzb3VyY2UKPiBUbzogcHBzZkBvbmxpbmUuZGUKPgo+Cj4gPiBjdXJyZW50bHkg dGhlcmXCtHMgbm90IG11Y2ggYWN0aXZpdHkgaW4gdGhpcyBwcm9qZWN0IGR1ZSB0byBsYWNrIG9m Cj4gPiByZXNvdXJjZXMuCj4KPiBKdXN0IGEgc2hvcnQgd29yZCB0byByZXBvcnQgdGhhdCB3eGhh c2tlbGwgaXMgc2xvd2x5IHdha2luZyBiYWNrIHVwLgo+IE9uZSBvZiB0aGUgaGFza2VsbC1jYWZl IHVzZXJzIHRvb2sgdGhlIGluaXRpYXRpdmUgdG8gcmV2aXZlIHRoZQo+IHByb2plY3QsIGFuZCBh IHNtYWxsIGhhbmRmdWwgb2YgdXMgYXJlIHdvcmtpbmcgdG93YXJkcyBhIG5ldyByZWxlYXNlLgo+ Cj4gT25lIG9mIG91ciBtaWQtdGVybSBob3BlcyBpcyB0byBmYWN0b3Igb3VyIHd4YyBvdXQgYW5k IGp1c3QgdXNlIHRoZQo+IHd4Yy5zb3VyY2Vmb3JnZS5uZXQgdmVyc2lvbiAoaS5lLiBhdXRvLWdl bmVyYXRlIG91ciBIYXNrZWxsIGJhc2UgdmlhCj4gaGVhZGVycyBmcm9tIGEgInN0YW5kYXJkIiB3 eGMpCj4KPiBBbm90aGVyIG9uZSBvZiBtb3JlIHNob3J0LXRlcm0gaG9wZXMgaXMgdG8gaW50ZWdy YXRlIG15IFVuaWNvZGUgcGF0Y2gKPiBpbnRvIHd4aGFza2VsbC4gIE5vdywgdGhpcyBwYXRjaCBp cyBsYXJnZWx5IGEgd3hjIG9uZSwgYW5kIEkgaW50ZW5kIHRvCj4gc2VwYXJhdGUgdGhhdCBwYXJ0 IG91dCBhbmQgbWVyZ2UgaXQgaW50byB3eEMuCj4KPiBTbywgdGhpbmdzIG1heSBiZSBkb3JtYW50 LCBidXQgdGhlcmUgYXJlIGxpdHRsZSBiaXRzIG9mIGFjdGl2aXR5IGdvaW5nCj4gb24gaW4gdGhl IGNvcm5lcnMuCj4KPiAtLQo+IEVyaWMgS293ICAgICAgICAgICAgICAgICAgICAgaHR0cDovL3d3 dy5sb3JpYS5mci9+a293Cj4gUEdQIEtleSBJRDogMDhBQzA0RjkgICAgICAgICBNZXJjaSBkZSBj b3JyaWdlciBtb24gZnJhbsOnYWlzLgo+Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+IFRha2UgU3VydmV5 cy4gRWFybiBDYXNoLiBJbmZsdWVuY2UgdGhlIEZ1dHVyZSBvZiBJVAo+IEpvaW4gU291cmNlRm9y Z2UubmV0J3MgVGVjaHNheSBwYW5lbCBhbmQgeW91J2xsIGdldCB0aGUgY2hhbmNlIHRvIHNoYXJl Cj4geW91cgo+IG9waW5pb25zIG9uIElUICYgYnVzaW5lc3MgdG9waWNzIHRocm91Z2ggYnJpZWYg c3VydmV5cyAtLSBhbmQgZWFybiBjYXNoCj4gaHR0cDovL3d3dy50ZWNoc2F5LmNvbS9kZWZhdWx0 LnBocD9wYWdlPWpvaW4ucGhwJnA9c291cmNlZm9yZ2UmQ0lEPURFVkRFVgo+IF9fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gV3hjLWRldmVsIG1haWxpbmcg bGlzdAo+IFd4Yy1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKPiBodHRwczovL2xpc3RzLnNv dXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby93eGMtZGV2ZWwKPgo= |
From: Eric K. <eri...@gm...> - 2006-08-04 13:19:41
|
Oups! meant to sent that to the list. ---------- Forwarded message ---------- From: Eric Kow <eri...@gm...> Date: Aug 4, 2006 3:18 PM Subject: Re: [wxC-devel] Where to find the source To: pp...@on... > currently there=B4s not much activity in this project due to lack of > resources. Just a short word to report that wxhaskell is slowly waking back up. One of the haskell-cafe users took the initiative to revive the project, and a small handful of us are working towards a new release. One of our mid-term hopes is to factor our wxc out and just use the wxc.sourceforge.net version (i.e. auto-generate our Haskell base via headers from a "standard" wxc) Another one of more short-term hopes is to integrate my Unicode patch into wxhaskell. Now, this patch is largely a wxc one, and I intend to separate that part out and merge it into wxC. So, things may be dormant, but there are little bits of activity going on in the corners. --=20 Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon fran=E7ais. |
From: Pascal P. <ppsf@Online.de> - 2006-08-04 12:44:51
|
Hello Lee, currently there=B4s not much activity in this project due to lack of resources. The code actually lags somewhat behind the current release of wxWidgets. Also some efforts need to be done to join the different code bases of existing bindings. The current code is based on the elj and wxHaskell projects but the aim is to provide something suitable for all the wx-non-C++ bindings (e.g. wx.Net and wxCL). This has not been done yet and so there are no stable packages to download. You need to get the code from the cvs. The code is the original one from elj cotaining patches from wxHaskell. Mattia Barbon has written some make file stuff. All this has to be revised and adapted to the latest wxWidgets release and to be made suitable for other projects. E.g. it would be helpful to be able to generate interfacing code in the target language automatically (say e.g. with XSLT or with SWIG). Since there=B4s a lot to do you are welcome to join the work. To get and view the current code you can follow the instructions on http://sourceforge.net/cvs/?group_id=3D110473 Regards Pascal > > Hi list, > > I=B4m looking to use wxC to enable wxWidgets support for a C based api > I=B4m building, so would love to help you guys develop this. Is there > anywhere I can download it as the link on SourceForge complains about > lack of packages. > > Regards, > Lee > > > |
From: Lee McColl-S. <lee...@ly...> - 2006-08-04 07:36:50
|
Hi list, =20 I'm looking to use wxC to enable wxWidgets support for a C based api I'm building, so would love to help you guys develop this. Is there anywhere I can download it as the link on SourceForge complains about lack of packages. =20 Regards, Lee =20 =20 |
From: James W. D. <i3...@kr...> - 2006-03-28 08:32:51
|
Pascal, Sorry about my delay too! Had a large commercial project that needed tending to... You know... money :) More than willing to test wxc than to develop much on it as my expertise is more CLR/.NET oriented than writing native code. I think the wx-c in wx.NET was derived from the wxPascal project but don't quote me on it (it was rather a long time ago, when I wasn't part of the project). The current wx-c API is comparable with the 2.6.x wxWidgets library. Im keen on moving this code out of wx.NET so we can concentrate on our core function and willing to take the time todo it. Cheers, James Dumay On 3/12/2006, "Pascal Poncin" <ppsf@Online.de> wrote: >Hello James, > >Sorry for the delay. Thank you for your interest and your offer to >help. I think that some testing on your side will be quite helpful. I >do not think that in the end wxc lib needs much programming but >rather maintenance and updating. The first (and quite big) task will >be to get the lib into a state usable by the majority of interested >projects. I'll have a look into your version of wxc during the next >time and see what it is. BTW, did you derive this from one of the >existing wxc versions or did you set up something new? > >Regards >Pascal > >>On 28 Feb 2006 at 10:09, James William Dumay wrote: >> >> Pascal, >> Rocking :). Im not much of a C hacker at all, but I will gladly help out >> wher e ever possible. You may want to checkout our "wx-c" library - it >> may be slightly more up to date than wxc. I signed up to the mailing >> list too. >> >> Where to from here? >> >> ~James Dumay >> >> On 2/27/2006, "Pascal Poncin" wrote: >> >> >Hello James, >> > >> >the wxC project has been evolving from the elj and wxHaskell >> >projects. The elj project had a binding of wx to the Eiffel language. >> >It is inactive by now since the major developers left. One of the >> >main problems was that the SmartEiffel compiler was repeatedly >> >changed in an incompatible (to other compilers and to itself) manner. >> >So maintaining the project was somewhat painstaking. However I had >> >the idea that the most valuable parts could still be saved. Since the >> >wxHaskell people took over the c part of the code to create a Haskell >> >library (and the wxOcaml project then over the code of the wxHaskell >> >project) there were (at least) two versions of the stuff. I've tried >> >to merge these versions into one usable for both projects (and >> >hopefully other ones as well). This was the rationale for the wxC >> >project. >> >But in wxHaskell wasn't happening much the last time and the Eiffel >> >part of the elj project had to be redone in vital parts since the >> >SmartEiffel compiler had completely departed from the standardization >> >discussions for the Eiffel. This made it extremely difficult to keep >> >the code up to date. As my spare time (wxC is some free time project) >> >is quite short at the moment, there wasn't much activity. >> >However, right now, there seems to be some interest in having a c >> >binding of wxWidgets. And as there is now a new free Eiffel compiler >> >(the original Eiffel libs have always been my main interest), there's >> >a somewhat higher motivation to keep this going at a higher pace >> >(though this may still be a slow one, I fear). >> >My vision is to provide a core c library to access wxWidgets in order >> >to prevent the need that each project needs to re-implemnt it >> >themselves. Maybe I can recruit some developers from the interested >> >parties to get this going. >> >So I invite you to join the mailing list (see on the project page, >> >not much traffic yet), in order take part in the future evolution of >> >the project. There's help needed. >> > >> >Regards >> > Pascal >> > >> >>On 27 Feb 2006 at 10:15, James William Dumay wrote: >> >> >> >> Hey there, >> >> I recently became maintainer for wx.NET and I was thinking about ditchi= ng >> >> our internal "wx-c" for the wxc project that you maintain on >> >> sourceforge. Whats happening with this project? it appears it hasnt bee= n >> >> updated in the last 12 months. >> >> >> >> Any info would be great. >> >> >> >> >> >> >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> James W. Dumay >> >> Sydney, NSW, Australia. >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > >> > > > > > >------------------------------------------------------- >This SF.Net email is sponsored by xPML, a groundbreaking scripting language >that extends applications into web and mobile media. Attend the live webcast >and join the prime developer group breaking into this new coding territory! >http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D12= 1642 >_______________________________________________ >Wxc-devel mailing list >Wxc...@li... >https://lists.sourceforge.net/lists/listinfo/wxc-devel |
From: Pascal P. <ppsf@Online.de> - 2006-03-12 14:56:46
|
Hello James, Sorry for the delay. Thank you for your interest and your offer to help. I think that some testing on your side will be quite helpful. I do not think that in the end wxc lib needs much programming but rather maintenance and updating. The first (and quite big) task will be to get the lib into a state usable by the majority of interested projects. I'll have a look into your version of wxc during the next time and see what it is. BTW, did you derive this from one of the existing wxc versions or did you set up something new? Regards Pascal >On 28 Feb 2006 at 10:09, James William Dumay wrote: > > Pascal, > Rocking :). Im not much of a C hacker at all, but I will gladly help out > wher e ever possible. You may want to checkout our "wx-c" library - it > may be slightly more up to date than wxc. I signed up to the mailing > list too. > > Where to from here? > > ~James Dumay > > On 2/27/2006, "Pascal Poncin" wrote: > > >Hello James, > > > >the wxC project has been evolving from the elj and wxHaskell > >projects. The elj project had a binding of wx to the Eiffel language. > >It is inactive by now since the major developers left. One of the > >main problems was that the SmartEiffel compiler was repeatedly > >changed in an incompatible (to other compilers and to itself) manner. > >So maintaining the project was somewhat painstaking. However I had > >the idea that the most valuable parts could still be saved. Since the > >wxHaskell people took over the c part of the code to create a Haskell > >library (and the wxOcaml project then over the code of the wxHaskell > >project) there were (at least) two versions of the stuff. I've tried > >to merge these versions into one usable for both projects (and > >hopefully other ones as well). This was the rationale for the wxC > >project. > >But in wxHaskell wasn't happening much the last time and the Eiffel > >part of the elj project had to be redone in vital parts since the > >SmartEiffel compiler had completely departed from the standardization > >discussions for the Eiffel. This made it extremely difficult to keep > >the code up to date. As my spare time (wxC is some free time project) > >is quite short at the moment, there wasn't much activity. > >However, right now, there seems to be some interest in having a c > >binding of wxWidgets. And as there is now a new free Eiffel compiler > >(the original Eiffel libs have always been my main interest), there's > >a somewhat higher motivation to keep this going at a higher pace > >(though this may still be a slow one, I fear). > >My vision is to provide a core c library to access wxWidgets in order > >to prevent the need that each project needs to re-implemnt it > >themselves. Maybe I can recruit some developers from the interested > >parties to get this going. > >So I invite you to join the mailing list (see on the project page, > >not much traffic yet), in order take part in the future evolution of > >the project. There's help needed. > > > >Regards > > Pascal > > > >>On 27 Feb 2006 at 10:15, James William Dumay wrote: > >> > >> Hey there, > >> I recently became maintainer for wx.NET and I was thinking about ditching > >> our internal "wx-c" for the wxc project that you maintain on > >> sourceforge. Whats happening with this project? it appears it hasnt been > >> updated in the last 12 months. > >> > >> Any info would be great. > >> > >> > >> > >> =================================== > >> James W. Dumay > >> Sydney, NSW, Australia. > >> =================================== > > > > |
From: <efu...@ne...> - 2006-01-25 05:21:20
|
Hello Pascal, Yes, we are able to compile it on both linux and windows using wxWidgets 2.6.2. There were no requirements as such, but for convenience we just added some new functions from wxWidgets 2.6.2, we also removed some old functions (which were there only for versions older than 2.4). Then we split up some of the files into multiple files, depending upon functionality. Also, I modified the wxC wrapper functions such as getTitle, from taking a buffer and then filling it with string, to return pointer to wxString objects. Then in the lisp side using the wxString length and c_Str() functions I copy the c-string into lisp. I am sure this can be done in Haskell also, but don't know about Ocaml. Right now I intend to remove the function definitions from class declarations, so that there is no mix of C and C++ code. Even I am in favor of having a modern converged version of wxC. Thanks and Cheers. -- Surendra Singhi http://ssinghi.kreeti.com/ -----Original Message----- From: Pascal Poncin <Pascal.Poncin@T-Online.de> To: wxc...@li... Sent: Wed, 25 Jan 2006 00:08:30 +0100 Subject: [wxC-devel] Some remarks Hello Surendra, thanks for your latest reports on the mailing list. Did you have some more success lately in compiling with wx 2.6.x? If I can I'll make some tries during the next time with the stuff from the wxC cvs and or the other versions (the wxHaskell cvs is possibly a little outdated, I think?). BTW, as I'm new to wxCL so perhaps you can give me a hint what changes you needed to add (roughly) to the wxHaskell version of wxC to make it work with CL? This would be helpful to create some converging version of wxC. Thanks & Regards Pascal ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Wxc-devel mailing list Wxc...@li... https://lists.sourceforge.net/lists/listinfo/wxc-devel ___________________________________________________ Try the New Netscape Mail Today! Virtually Spam-Free | More Storage | Import Your Contact List http://mail.netscape.com |
From: Pascal P. <Pascal.Poncin@T-Online.de> - 2006-01-24 23:05:44
|
Hello Surendra, thanks for your latest reports on the mailing list. Did you have some more success lately in compiling with wx 2.6.x? If I can I'll make some tries during the next time with the stuff from the wxC cvs and or the other versions (the wxHaskell cvs is possibly a little outdated, I think?). BTW, as I'm new to wxCL so perhaps you can give me a hint what changes you needed to add (roughly) to the wxHaskell version of wxC to make it work with CL? This would be helpful to create some converging version of wxC. Thanks & Regards Pascal |
From: <EFu...@ne...> - 2005-12-19 23:53:05
|
__________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp |
From: <EFu...@ne...> - 2005-12-18 22:52:41
|
-- Surendra Singhi http://www.public.asu.edu/~sksinghi/index.html __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp |
From: <EFu...@ne...> - 2005-09-19 20:12:52
|
Hello all, Thanks for endeavoring to work on wxC. I am the developer of the wxCL project and we use wxC (currently right from the wxHaskell repository and then we have made some changes). I have few feature requests for wxC, I think even wxOcaml project will benefit from these. [1] Please try to provide pre-built dlls for Windows, linux and Mac OS X. I can help in this regard for Windows and Mac OS X. [2] Provide interfaces to new classes/functions added in wxWidgets 2.6.1, for example wxSound, wxMediaCtrl, etc. [3] APIs deprecated in wxWidgets should also be deprecated in wxC [4] Provide Unicode support. [5] Improve some of the existing APIs, i.e, use char* instead of void*, this will help in automatic generation of wrapper codes. I will try to help as much as I can in achieving the above goals. Thanks, once again. -- Surendra Singhi http://www.public.asu.edu/~sksinghi/index.html __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp |