Re: [CinePaint] CinePaint Plan for 2010
Glen <[email protected]> Fri, 01 Jan 2010 18:51:01 -0800
| Newsgroups | gmane.comp.video.cinepaint.user |
|---|---|
| Message-ID | <1262400661.20283.5.camel@honcho> |
Robin, Thanks for the note, and hoping you had a happy new year's day and a good year to follow. I'll see if I cannot do some more code clean up work. I've been happily using cinepaint 0.25.0 (without oyranos) and just recently downloaded the current cvs and compiled on Ubuntu 9.04 (my current Linux version). Sorry I cannot do more - just too much workload with everything else. Yours, Glen Journeay On Fri, 2010-01-01 at 12:22 -0800, Robin Rowe wrote: > Wishing everyone a happy New Year! Although I haven't been active on the > list lately, I've been working on CinePaint behind the scenes. Here's a > plan for 2010. > > CinePaint 2010 > > 1. Revamp website. Software changes to make it easier for me to post > news more frequently. Probably Drupal with Postgres. > > 2. Revamp CVS. Although there are good arguments for other systems such > as Subversion, the pros don't outweigh the cons of making developers > (especially me) learn a new system. I plan to divide the code into > smaller modules to make it easier to handle. > > 3. Ravamp build. Build CinePaint using C++ without autotools. The GNU > autotools autoconf-automake-configure-make system has always been a > thorn in CinePaint's side because it makes one QA cycle to do a full > rebuild take hours. > > 4. Linux, Mac and Windows releases. We've been stuck getting out a > release for reasons of build management and QA. The Mac and Linux > releases have been held back by build issues. That's being resolved. The > Windows version was derailed by issues related to how we use GTK. There > are a couple ways to resolve that, and it will require me doing some > work. I'm keen to get the Windows version because I work fastest when > debugging in Visual C++. > > 5. Revamp architecture. Make brushes into plugins. Load plugins as DLLs > on all platforms, not spawn processes. Use ASCII strings instead of > variargs in Wire Protocol. Start using more C++ in code, but no STL > please. Make Java a supported scripting language. Release img_img > command line tool. > > 6. Revamp QA. Create a strong QA system with unit tests and more > thorough user testing. > > Anyone who wishes to volunteer to add something useful to the CinePaint > project is, of course, welcome. > > Robin ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev