Re: [Gimp-developer] donations for GIMP 2.8
Hi everyone, You may know me as the student who coded the cage tool during this summer. I'd like to add something about these bounty. For me, the key point for the health of the community dev of Gimp is the current difficulty to be used to the codebase. I myself had a hard time to understand how things works in the code, and how to do things. The main cause of these difficulty is the lack of technical documentation. We sometimes need to read hundred lines of code just to know what an objet actually do. The code architecture is obscur for most of the dev, and if we loose the key dev, we will have hard time. If i haven't the pressure of the GSOC program, I probably abandoned. I once asked why we don't have these documentation. The answer i had is that writing documentation is boring, that's like that in free software, you just have to deal with. That's a vicious circle. The less we have docs, the less we have dev. And so, and so ... My idea is to use this money to reverse the trend. Lets give bounty for these docs. Here is some example of documentation I think is needed: - How to write a cool GObject for Gimp - How to write a cool Gegl op - A summary of what do core object if it's not already documented Just have a look on what Blender's dev do to present their work, and compare Blender and Gimp activity. http://code.blender.org/index.php/2011/01/a-look-at-point-cache/ I hope this message will go somewhere ... -- Michael Muré ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] combo boxes in osx
Hi I've just got gimp to compile from git on OSX, I've just noticed that the combo boxes popup is displaying behind the dialogue panel so they are hidden. Thats every combo box. It can be seen if docked in the toolbox then squeezed to the edge. When you hit the combo box the options popup is visible at the side behind the toolbox dialogue. Does anyone else have this problem on OSX or is it just my ruff compile setup? Thanks Sean ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] donations for GIMP 2.8
On Mon, Jan 10, 2011 at 5:05 PM, Michael Muré batolet...@gmail.com wrote: You may know me as the student who coded the cage tool during this summer. I'd like to add something about these bounty. For me, the key point for the health of the community dev of Gimp is the current difficulty to be used to the codebase. I myself had a hard time to understand how things works in the code, and how to do things. The main cause of these difficulty is the lack of technical documentation. We sometimes need to read hundred lines of code just to know what an objet actually do. The code architecture is obscur for most of the dev, and if we loose the key dev, we will have hard time. If i haven't the pressure of the GSOC program, I probably abandoned. I once asked why we don't have these documentation. The answer i had is that writing documentation is boring, that's like that in free software, you just have to deal with. That's a vicious circle. The less we have docs, the less we have dev. And so, and so ... snip My idea is to use this money to reverse the trend. Lets give bounty for these docs. Here is some example of documentation I think is needed: snip Code documentation is also one of the tasks that are not permitted for instance in the Google summer of code, perhaps we could come up with a set of bounties, or find someone motivated and fund them on a task by task basis or even part time for documenting? For a while, almost all the time I spent on GEGL (to the detriment of progress wrt features and performance) was spent on cleaning it up, and documenting it, website - references and more; this in case I decided to completely drop the ball or get consumed by other things, what I added was far from enough; and being the actual originator of much of the things in GEGL I am almost a bit cursed by knowledge and thus not the person best suited for it. Getting more documentation sure will be one of the best ways of making it easier to involve more people (and I am sorry for any bits of almost existing docs that aren't fully integrated yet.) /pippin -- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] donations for GIMP 2.8
On Monday, January 10, 2011 19:17:51 Øyvind Kolås wrote: Code documentation is also one of the tasks that are not permitted for instance in the Google summer of code, perhaps we could come up with a set of bounties, or find someone motivated and fund them on a task by task basis or even part time for documenting? I think this is a frightfully good idea too. One of those tasks could be writing the GIMP code Codex. Coding standards and best practices and so on. It could give us much easyer to merge forks for example. Its extremely annoying having to rewrite most of a great feature to make it fit for merge And yes, I do remember my starting days trying to make sense of the GIMP on the inside. Best, Alexia ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] donations for GIMP 2.8
On Mon, Jan 10, 2011 at 5:39 PM, Alexia Death alexiade...@gmail.com wrote: On Monday, January 10, 2011 19:17:51 Øyvind Kolås wrote: Code documentation is also one of the tasks that are not permitted for instance in the Google summer of code, perhaps we could come up with a set of bounties, or find someone motivated and fund them on a task by task basis or even part time for documenting? I think this is a frightfully good idea too. One of those tasks could be writing the GIMP code Codex. Coding standards and best practices and so on. It could give us much easyer to merge forks for example. Its extremely annoying having to rewrite most of a great feature to make it fit for merge And yes, I do remember my starting days trying to make sense of the GIMP on the inside. Note that many of the documents/the start of the documentation described or desired do already exist but might not be appropriately pointed to, and it has already been created and contributed to without monetary reward. Lets hope use of rewards wouldnt scare off people from contributing such work for free. /pippin ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] translate menu mod
On Sat, 2011-01-08 at 12:02 +0700, Ek kian wrote: i usually modify menu directly from image-menu.xml, but that made menu is broken on other language than English. what is the right steps to do menu modification so the menu still can be translateable to other language? The right step is to get your changes upstream. What exactly are you changing and why? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] combo boxes in osx
On Mon, 2011-01-10 at 17:14 +, s...@startide.org wrote: Hi I've just got gimp to compile from git on OSX, I've just noticed that the combo boxes popup is displaying behind the dialogue panel so they are hidden. Thats every combo box. Are you running GTK+ on X11 or did you compile GTK+ with the Quartz backend? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] donations for GIMP 2.8
2011/1/10 Øyvind Kolås pip...@gimp.org Lets hope use of rewards wouldnt scare off people from contributing such work for free. It could be a one-time operation, with clearly defined goal and bounty. Just the time we need to have these needed documentation. -- Michael Muré ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] donations for GIMP 2.8
On Mon, 2011-01-10 at 19:39 +0200, Alexia Death wrote: On Monday, January 10, 2011 19:17:51 Øyvind Kolås wrote: Code documentation is also one of the tasks that are not permitted for instance in the Google summer of code, perhaps we could come up with a set of bounties, or find someone motivated and fund them on a task by task basis or even part time for documenting? I think this is a frightfully good idea too. One of those tasks could be writing the GIMP code Codex. Coding standards and best practices and so on. It could give us much easyer to merge forks for example. Its extremely annoying having to rewrite most of a great feature to make it fit for merge And yes, I do remember my starting days trying to make sense of the GIMP on the inside. But who could write (and review) such docs? That would be the core developers and we really need the core developers to work on GIMP 2.8. Focusing on developer documentation is not going to make GIMP 2.8 happen earlier. On the contrary, it is likely to delay it further. Please try to come up with suggestions that focus on the 2.8 release. Thanks. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] translate menu mod
i only create new Photo menu where consist of many photography related functions, to speed up our workflow on editing photo rather than jumping around on the menu. can you be more specific about the steps? do i need to call command update-po? Thanks, ek kian On Tue, Jan 11, 2011 at 3:44 AM, Sven Neumann s...@gimp.org wrote: On Sat, 2011-01-08 at 12:02 +0700, Ek kian wrote: i usually modify menu directly from image-menu.xml, but that made menu is broken on other language than English. what is the right steps to do menu modification so the menu still can be translateable to other language? The right step is to get your changes upstream. What exactly are you changing and why? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] combo boxes in osx
i also experience this on OSX 10.6.2, i use GIMP 2.6.8 compiled with GTK-OSX (http://gtk-osx.sourceforge.net/). but for GIMP from http://gimp.lisanet.de, it working ok and i think it using X11. i prefer using GIMP with GTK-OSX because it using Global Menu and using OSX Native UI.Regards, Regards, ek kian ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
