Re: [Gimp-developer] GsoC - 2011 - Porting GIMP plugins to GEGL operations
On Tue, Mar 22, 2011 at 10:07 PM, Robert Sasu sasu.rob...@gmail.com wrote: I've read the e-mails about this project from the mailing list and I found actually what I have to do. I also looked at the source code and the differences between gimp and gegl implementation. If it is possible I would like a short list of plugins to look at, which are needed to be implemented ? We sort of expect you to come with your own plan :) So make a list of things you find interesting and show it off at IRC. And again: how important do you find this project compared to others for this years GSoC? Importance really hasn't been assigned to tasks. There are couple of projects that if right people pick them up, would probably get preference in slot selection, however you would most likely compete against established contributors on them, so odds of getting a slot would be low. Kevin, cloning was kicked, because welding pixel manipulation code on old paint core is not a good idea, new pixel manipulation should go in gegl and we simply dont have the infrastructure to use that in paint core yet. -- --Alexia ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GsoC - 2011 - Porting GIMP plugins to GEGL operations
Alexandre Prokoudine wrote: The agreement was not to introduce new tools based on old core, and GEGL based tool here means underlying GEGL painting infrastructure which is simply not ready yet. Ok. The wiki page says it is for this years GSoC. On my machine the Recommended and For a later GSoC headings get lost when you are scrolling down the page as they are appear in a thin regular type face compared to the nice bold fonts used to show project ideas. The ideas for a future GSoC should be moved to a separate page. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GsoC - 2011 - Porting GIMP plugins to GEGL operations
Hi, On Wed, Mar 23, 2011 at 8:32 AM, Alexia Death alexiade...@gmail.com wrote: Kevin, cloning was kicked, because welding pixel manipulation code on old paint core is not a good idea, new pixel manipulation should go in gegl and we simply dont have the infrastructure to use that in paint core yet. The name cloning is misleading - this tool has nothing to do with regular paint tools. if it reminds anything by interaction, it's the cage tool - you select a shape, move it around (hopefully with a live preview of what will happen if you drop it there) and then release when satisfied. Please see the demo video if you want to see what I mean - it's on the article page. I'm restoring this idea to the wiki's recommended list. ~LightningIsMyName ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] GSoC application - Adaptive Image Cloning
Hello, My name is Barak Itkin (sometimes known on the web as LightningIsMyName), I'm a third year student for computer science at the Tel-Aviv University (Israel), and I'm a regular visitor of the GIMP irc and mailing lists. I'd like to apply for a GIMP GSoC for the Adaptive Image Cloning (aka Seamless Cloning). Past expirience: - Made several contributions to GIMP already, mainly on the plugin side (script-fu scripts, and wrote the new PDF plugin), but also made several to the core (support for multi-colored text in 2.7 was partially written by me) - Contributed several GEGL operations for existing GIMP plugins - More than two years of practical expirience in C - Good background in image processing and computer graphics - In terms of large code, my biggest projects was a ray tracer (4k lines) Thanks, Barak Itkin ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
