Re: [Sooc-devel] why Sooc?

[Mike R. <mik...@gm...>]

If we port a gtkmm project, we will have to work with GObject to an
extent.  In particular, a C++ project is likely to include derived
widgets.  Those are a major pain with GtkWidget.  But with Sooc, they
can be expressed using a combination of composition and inheritance,
which I did easily enough in OTweeze.  The SGtkWidget wrapper for
GtkWidget was designed in like 5 minutes and it was straightforward
enough to use.  In fact, it's because this is exactly the sort of
challenge Sooc needs to handle gracefully that I think a gtkmm project
would be appropriate.  Also, the gtkmm website maintains a list of
some client projects, which might be a good starting point in choosing
a project.

That said, a completely different project might be still more
appropriate.  I'll be thinking about C++ and Java apps I know of... or
maybe we can just find something on SF somewhere :)

-Mike