Hi Eric, Mads, and all,
On Apr 12, 2009, at 10:38 AM, Eric Y. Kow wrote:
> On Sun, Apr 12, 2009 at 19:23:01 +0200, Mads Lindstrøm wrote:
>> * Convince the wxWidgets team to maintain the script. I guess this
>> involves not just talking to the wxWidges team, but also show that
>> other
>> people
On Sun, Apr 12, 2009 at 19:23:01 +0200, Mads Lindstrøm wrote:
> * Convince the wxWidgets team to maintain the script. I guess this
> involves not just talking to the wxWidges team, but also show that other
> people will find the c-wrapper useful.
This would be a big win and I think we may be able
Hi
I made another version of the c_wrapper.py program. I have attached the
program, a new smaller diff to doxymlparser.py and output from running
the program. The output can compile now:
> python c_wrapper.py out/xml/classwx_button.xm
> g++ `wx-config --libs` `wx-config --cxxflags` -c wrapped_wxB
Hi
Kevin Ollivier wrote:
> Hi Eric,
>
> On Apr 9, 2009, at 11:18 AM, Eric Kow wrote:
>
> > On Thu, Apr 09, 2009 at 18:57:29 +0100, Eric Kow wrote:
> >> This is where Kevin Ollivier of wxWidgets pointed out something
> >> interesting: in the current wxWidgets trunk, it should be possible to
> >>
Hi
Eric Y. Kow wrote:
> On Sat, Apr 11, 2009 at 01:57:30 +0200, Mads Lindstrøm wrote:
> > Besides the overly verbose syntax, I did not feel like XSLT were a good
> > match for the task.
>
> I realise you weren't talking about the syntax, but in case it plays a
> role in this, there is always PXSL
gt;
> email message attachment
> > Forwarded Message
> > From: Kevin Ollivier
> > To: Eric Y.Kow
> > Subject: Re: [wxhaskell-users] autogenerating wxc from
> > wxWidgets?Doxygen output?
> > Date: Fri, 10 Apr 2009 15:46:38 -0700
> >
> >
On Sat, Apr 11, 2009 at 01:57:30 +0200, Mads Lindstrøm wrote:
> Besides the overly verbose syntax, I did not feel like XSLT were a good
> match for the task.
I realise you weren't talking about the syntax, but in case it plays a
role in this, there is always PXSL, which has significantly dampened
Hi
Eric Kow wrote:
> This is where Kevin Ollivier of wxWidgets pointed out something
> interesting: in the current wxWidgets trunk, it should be possible to
> automatically generate the C bindings from the Doxygen XML output. In
> fact, he has already done something similar for Python, metadata
: Re: [wxhaskell-users] autogenerating wxc from wxWidgets
Doxygen output?
Hi
Eric Kow wrote:
On Thu, Apr 09, 2009 at 18:57:29 +0100, Eric Kow wrote:
This is where Kevin Ollivier of wxWidgets pointed out something
interesting: in the current wxWidgets trunk, it should be possible
to
automa
Hi
Eric Kow wrote:
> On Thu, Apr 09, 2009 at 18:57:29 +0100, Eric Kow wrote:
> > This is where Kevin Ollivier of wxWidgets pointed out something
> > interesting: in the current wxWidgets trunk, it should be possible to
> > automatically generate the C bindings from the Doxygen XML output. In
> >
Hi
Eric Kow wrote:
> I'm vaguely aware that our copy of wxc has some information which helps
> us keep track of the wxWidgets class hierarchy. Presumably the same
> information could be autogenerated as well? This sort of thing has been
> suggested before (people have mentioned SWIG).
>
It see
Hi Eric,
On Apr 9, 2009, at 11:18 AM, Eric Kow wrote:
> On Thu, Apr 09, 2009 at 18:57:29 +0100, Eric Kow wrote:
>> This is where Kevin Ollivier of wxWidgets pointed out something
>> interesting: in the current wxWidgets trunk, it should be possible to
>> automatically generate the C bindings from
Hi everybody,
I've recently been thinking about ways we would make the wxhaskell
installation process less painful.
My desire is for the "cabal install" part of the process to be
completely painless. Right now, the wxcore process is slow, complicated
and doesn't work for the user package databas
13 matches
Mail list logo
