Re: CinePaint Film Gimp plans

And I'm still working on the Gtk color corrector.

This sort of sounds like three projects for one goal.  At some
point, if you ever want a finished product, you will have to
pick one winner and cut your losses on the rest.

I started playing with Cinepaint because I needed something
I could use on Linux now.  It's the great open source tradition,
if you don't like it - start writing some code.  At some
point though, we all have other jobs to do and we
can't spend too much time assembling the tools.

I think that is a good argument for following the path of least
resistance.  Right now I think that path is along the existing
Gtk 1 branch of Cinepaint. The tool that exists today is
nearly completed and there is no other high bit depth equivalent
on Linux.  There is also a large user community out there that
needs something today.  If you can get it to the point where
the only complaints are about the GUI, then you are probably
done (and you will never remove those, no matter what GUI
you pick).

Based on my own experience, and humble opinion, Glasgow is
probably at least one year from any sort of usability, and
that assumes that at least one person can devote a significant
amount of time to it in the interval.  Even if an initial
release is pending, we all know how long it takes for a
project to achieve stability.  I would actually delay the
release as long as possible, the expectations out there
are too high.

Cinepaint, in whatever form, needs to show some progress.
There have been too many fits and starts.  There
may be valid reasons for various events in the
history of the project, but to the outside world
it's all about appearances.


For some reason I can't quite figure out, software for
still and moving image manipulation on Linux is in a
very bad state (Blender excepted).  Cinepaint is
about the only hope for still image manipulation.
Otherwise we either continue to wait, or we come up
with the money for Photoshop seats.

Regards,
Brad Hare




Kai-Uwe Behrmann wrote:
> Hello all,
> 
> here some current thoughts for the legacy flawor of CinePaint.
> 
> Frist of all the Gtk branch seemed not to bring that many interesst to the 
> project, that we found developers to continue heavily on Glasgow. Beside 
> CinePaint being the base for some colour management related fun this 
> target seemed not been meet. My idea therefore is to slow down my pure 
> Gtk effort.
> 
> What I have now is some Gtk2 code for better i18n support in CinePaint.
> The parallel gtk1 builds are slightly broken in CVS therefore.
> Gtk2-CinePaint builds but is missing some important features due to the 
> heavy changes to the Gtk object system, which Gimp and CinePaint 
> are based on.
> As well the menu system is expectedly broken as important functionality 
> are not available in the Gtk2 API. The API used by CinePaint is deprecated 
> in Gtk2.
> So I have here locally a UTF-8 capable Gtk2 version without real 
> functionality.
> If someone wants to continune this effort, let me know to make 
> the code more soon available.
> 
> As we allready started with writing new plug-ins in FLTK, I'd like to 
> continue such things, which are good bricks for Glasgow.
> An example could be the colour selector and the file browser. The later is 
> much better designed in FLTK and would give legacy CinePaint a very nice 
> preview. Just look at the collect plug-in.
> The prise of mixing Gtk and FLTK, is a less uniform GUI. But thats seems 
> fine, at least to me, as it reflects clearly the direction for CinePaint.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV