That's why we need a Gimp PRO, Inkscape PRO, Scribus PRO - someone, a Firm / Govern / Foundation / Linux Distro / Billionaire ...or a mixture of them must hire core developers of all 3 projects - put them into a big WEB / DTP Core Linux project and manage development and releases. This will bring us - a single, unified 2D HQ rendering / printing core. Same advanced vector tools and similar vector manipulation methods on all 3 applications ( which need to work as a unit ) . Same live effects for vectors and rasters >> imagine how easy you can move Objects, Layers, Groups between applications just using drag-and-drop. Finally, the same HQ quality for print, the same PDF export engine. As separate projects - on Open Source World - this process can take long time from now. Manny years. So, for all 3 teams we need -> 1. to accept Ideea ( to work on the same core for something PRO and new ); 2. to find or to found a crazy legal creature that can fund all development, 3. a good market policy -> Joe, if U make free plugins with our toolkit - U don't need to pay for tools - for commercial plugins U have to pay for toolkit / libraries, etc. 4. At this step - If all OK - we all are OK >> that mean : Free and PRO versions, free and paid plug-ins / add-ons, free source, a nice toolkit with the best libs for developers, time (paid time) for developers - a continuous, sane, development / future for Open Source Suite, a good way to turn to Linux a bunch of programmers, a good way to prepare the future -> giving best tools and practices for IT Universities, ...finally helping Linux to grow faster, helping world to be free. A bit strange maybe all that I'm saying here but... so quick ( movement on this direction ), so good. From 2008 MS will leave XP. All new computers will sell Vista. Before the big moment a lot of users / enterprises will search around for solutions. THAT will be for Linux The Day. If Linux will loose momentum, ...hmm, the progress will be damaged. but ..keeping a happy note ( as always ) for the final > let the GEGL be with us ;) Sorin. P.S. Sorry Engel for my response - U ask for something and I told you crazy things. well - go on and don't give up with this crazy - because sooner or later will be real. and you won't miss the dance. 2007/4/15, gg@xxxxxxxxxxx <gg@xxxxxxxxxxx>: > On Sat, 14 Apr 2007 19:19:06 +0200, Hal V. Engel <hvengel@xxxxxxxxxxx> > wrote: > > > On Saturday 14 April 2007 08:04, Chris Puttick wrote: > >> Hi > >> > >> Forgive me if I have missed this information, but can someone give an > >> estimate for the release of 2.4? We are trying to move to open source > >> throughout the organisation, but the graphics team are solidly stuck to > >> Adobe Photoshop and Gimp 2.4 seems the most likely candidate to replace > >> it. > >> Unless the list thinks that 2.4 would not be a candidate to replace > >> Photoshop? > >> > >> Thanks for your help. > >> > >> Regards > >> > >> Chris > > > > Release dates don't really exist for Gimp. I asked this same question last > September and got the same polite silence. > > Due to the nature of Gimp development the new release happens when the > work is done, rather than setting a target date and trying to get it out > of the door on time. Development cycles tend to be rather long in general > so you should probably follow Hal's comments and determine what you need > and what can or can't be done with Gimp. > > One key thing to bear in mind when doing this is that Gimp does not aim to > be a free clone of Photoshop. Some things are done differently and while > the basic tasks are often similar the feature sets are different and > things are often done differently. There are some things you can do with > PS that you can't do with Gimp and vice versa. > > As he said you really need one of your graphics team to determine any > important tasks that you cant manage to do with gimp and ask. It may > simply be that you have not discovered how to do the task or it may add > impetus to finish a feature in development. > > HTH. > gg > > > > Chris, > > > > There is not nearly enough information in your post to answer that > > question. > > It depends entirely on the requirements of your graphics team. For > > example, > > if they work only with 8 bit/channel images then gimp 2.4 might be a good > > candidate to replace Photoshop. But if they work with 16 bit/channel > > images > > then it is not. But there are lots of other things that need to be > > considered and your note does not have any information on any if these > > variables. > > > > I would think that the best thing to do would be to find someone on your > > graphics team who is open minded enough to not get hung up on the > > differences > > in the UI who will actually evaluate the available functionality and > > give an > > assessment of what things your shop requires and how close current GIMP > > development is to meeting your needs. However it might be difficult to > > find > > someone who will be able to look past the UI differences. If at that > > point > > you find that there are features that your graphics team uses and NEEDS > > that > > are missing from GIMP 2.3.x (and presumably 2.4 since the feature set is > > close to being frozen) then you could follow up with the GIMP developers > > to > > make sure those things end up in the next version. You might even > > consider > > having your organization sponsor (IE. fund) some of that work to ensure > > that > > the next release meets your needs. > > > > Also keep in mind that there are other open source tools for doing > > graphics > > work that might also complement GIMP and provide functionality that your > > graphics team needs. In other words it might not be GIMP that ends up > > replacing Photoshop but GIMP plus some other tools and you need to > > consider > > your whole graphics work flow to be able to answer the question of how > > you > > will go about replacing Photoshop with open source software. > > > > Also on a side note I see on your web site that there is at least one > > stitched > > mosaic of photos. If you are not already using open source tools for > > this > > work might I suggest you try Hugin, enblend and autopano-SIFT. In fact > > this > > suite of tools would have done a significantly better job then what I > > saw on > > your web site for the image next to "HERITAGE" on your Services page. > > > > Hal > > > >> > >> Chris Puttick > >> CIO > >> Oxford Archaeology: Exploring the Human Journey > >> Direct: +44 (0)1865 263 818 > >> Switchboard: +44 (0)1865 263 800 > >> Mobile: +44 (0)7914 402 907 > >> http://thehumanjourney.net > >> > >> > >> This message has been scanned for viruses by BlackSpider MailControl - > >> www.blackspider.com _______________________________________________ > >> Gimp-developer mailing list > >> Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx > >> https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer > > _______________________________________________ > > Gimp-developer mailing list > > Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx > > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer > > > > > _______________________________________________ > Gimp-developer mailing list > Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer > -- Nemes Ioan Sorin _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
