On Tue, 2010-01-19 at 15:56 +0100, Murray Cumming wrote:
On Tue, 2010-01-19 at 14:16 +0100, Krzesimir Nowak wrote:
And so I did, but it a still work in progress though, some more detailed
informations should be added.
http://live.gnome.org/gtkmm/mmproc
Looks good. Some thoughts:
1.
On Sun, 2010-01-10 at 12:06 +0100, Murray Cumming wrote:
On Sat, 2010-01-09 at 21:04 +0100, Krzesimir Nowak wrote:
On Thu, 2010-01-07 at 09:39 +0100, Murray Cumming wrote:
Anyone should feel free to play with ideas in a git branch, even on
gitorious or github if they don't have
On Tue, 2010-01-19 at 14:16 +0100, Krzesimir Nowak wrote:
And so I did, but it a still work in progress though, some more detailed
informations should be added.
http://live.gnome.org/gtkmm/mmproc
Looks good. Some thoughts:
1. I'd use call it gmmproc3. That's simpler.
2.
* Rework defs and
On Sat, 2010-01-09 at 21:04 +0100, Krzesimir Nowak wrote:
On Thu, 2010-01-07 at 09:39 +0100, Murray Cumming wrote:
gmmproc's use of perl and m4 (and how those parts are interdependent)
makes it very hard to add new features or to fix problems.
How much extensibility is needed? I mean -
On Thu, 2010-01-07 at 09:43 +0100, Murray Cumming wrote:
We hope to use the new .gir files, which should actually be correct and
widely shared:
http://live.gnome.org/GObjectIntrospection
However, I hope any gmmproc rewrite does the .defs/.gir switch as a
separate task.
.gir files would
On Thu, 2010-01-07 at 09:39 +0100, Murray Cumming wrote:
gmmproc's use of perl and m4 (and how those parts are interdependent)
makes it very hard to add new features or to fix problems.
How much extensibility is needed? I mean - should it be easy just to add
new feature to gmmproc itself or
On Wed, 2010-01-06 at 19:00 +0100, Krzesimir Nowak wrote:
Some people (Daniel, Murray, probably others, citations needed) said
that it would be good to rewrite gmmproc (in python). I'd rather won't
agree - gmmproc for sure is not perfect, but it could be refactored.
Rewrites tend to throw away
On Wed, 2010-01-06 at 19:00 +0100, Krzesimir Nowak wrote:
- I was wondering if current defs file format is all that great. Why
not
use XML for example? True, it can get quite lengthy, but there are
lots
of software parsing this stuff and format is rather quite reliable -
unpaired parentheses
2010/1/7 Murray Cumming murr...@murrayc.com:
gmmproc's use of perl and m4 (and how those parts are interdependent)
makes it very hard to add new features or to fix problems.
Agree 100%. I tried to add a feature to _WRAP_VFUNC that would make
wrapping GIO stream vfuncs easier (related to this
