Re: [Gimp-print-devel] development release?

[S. M. <sm...@rn...>]

Robert L Krawitz wrote:
> 
> I have to admit that there's stuff even in the low levels that I'd
> like to use C++ for, but it's probably going to cause more problems
> than it will solve.  However, if there's one place that it really
> makes sense, it's in the GUI, which after all is not going to be
> directly portable to anything beyond the Gimp and where inheritance is
> known to be very useful.  So my take would be to lean against it, but
> if it's going to make your life radically easier and won't force the
> lower level stuff to use C++, I'd say give it a whirl.
> 
> (Besides, we might actually learn a little something about how to
> design printing interfaces in general that might just come in handy
> down the road.)
> 
Perhaps I should have stressed more that I was only talking about the
GUI.  To me GUIs are inherently object oriented, and it made sense to
use C++ there.  Calling other languages from C++ is trivial, but the
reverse is probably not the case.  What I wasn't sure of is what
restrictions Gimp imposed.  I haven't completely figured out how
plug-ins interface with Gimp, but since there is a main I assumed it was
a standalone executable, and so this approach might work.  So as long as
I can keep from bleeding into the driver code (which I guess is one of
the main goals anyway), and keep the Makefile from breaking, I'll see
what I can do with it.

Steve
-- 
-----------------------------------------
Just because I have a short attention span
doesn't mean I
------------------------------------------