Re: [Gimp-developer] 2.4 and how to continue from here
resending... Sven wrote, On Fri, 2007-11-09 at 12:36 -0300, Joao S. O. Bueno wrote: One other smallf eature I will want to add is the ability to add free- angled guides. I have this almost complete on my codebase, just .XCF saving for it is missing. I should commit that early on 2.6 cycle. I would like to get some feedback from the UI team and from some artists on this. And of course the patch would have to be reviewed before it is committed. I am not yet convinced that this is an important feature and I also have the impression that it's just added ad-hoc without seeing the big picture. It certainly has the potential to cause a lot of problems. yeah. Kamila came up with the plan for rotating guides and I could see then how it could have an impact on for instance web design by breaking the normal hor/vert grid. and after a few minutes I could come up with a decent on-screen UI. but the real question is the priority of this yet-another-feature. something like geometry tools integration has a much higher priority than this. --ps founder + principal interaction architect man + machine interface works http://mmiworks.net/blog : on interaction architecture ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
A Sunday 11 November 2007 20:48:27, peter sikking escreveu: but the real question is the priority of this yet-another-feature. something like geometry tools integration has a much higher priority than this. There eason I proposed this at this stage is that I have this feature complete minus UI and XCF saving in my GIMP tree. It has been like that for over an year when I was told it was too late to make it into gimp 2.4. js -- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
A Monday 29 October 2007 16:24:11, Sven Neumann escreveu: I suggest that we keep brainstorming for the 2.6 roadmap for another week and then collect the ideas. It would be nice if we could end with a list of well-defined tasks. When that list is collected, I would like to discuss which of these tasks should be put on the roadmap for 2.6. Hi Sevn and others, I have been obn the process of moving myself to another city over the last few weeks (almost complet now, just waiting for my mobile nad main machinne to get here). ] As soons as that happens I should consolidate my work hours and spare a few of then for GIMP. The feature I'd like to work on is a brush stroke pannel to be able to set up stroking with curves for relating pressure, speed, angle, etc with opacity, size, jitter, color, etc... One other smallf eature I will want to add is the ability to add free- angled guides. I have this almost complete on my codebase, just .XCF saving for it is missing. I should commit that early on 2.6 cycle. Regards, js -- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
Sven Neumann wrote: At that point trunk will be open for development. But since we are aiming for a short development cycle, we need to absolutely keep the tree in a good shape. I don't want to see any commits that haven't been discussed and approved beforehand. This doesn't mean line-by-line code review. But I would like you guys to present your plans here beforehand and not learn about them from reading the commit logs. So if are planning any particular features for 2.6, now is the time to present them here so that they can be put on the roadmap. This includes stuff that has been planned for quite a while, like for example finishing the metadata framework/editor (Raphael!), but also the port to GEGL (Mitch!). I'd like to get a couple paint tool related patches in. 323921 GIMPNEW enh add support for color jitter in the paint tools 163050 GIMPNEW enh paint tools should support smudging as they paint. Patches exist, though they haven't been tested against 2.4/2.5, I think they should apply pretty easily however. If theres interest, I can update them. Adrian ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
At that point trunk will be open for development. But since we are aiming for a short development cycle, we need to absolutely keep the tree in a good shape. I don't want to see any commits that haven't been discussed and approved beforehand. This doesn't mean line-by-line code review. But I would like you guys to present your plans here beforehand and not learn about them from reading the commit logs. So if are planning any particular features for 2.6, now is the time to present them here so that they can be put on the roadmap. This includes stuff that has been planned for quite a while, like for example finishing the metadata framework/editor (Raphael!), but also the port to GEGL (Mitch!). I will continue working on GimpRectangleTool and I aim for more or less complete Selection + crop tool specification [1] conformance in 2.6. - Martin Nordholts [1] http://gui.gimp.org/index.php/Selection_%2B_crop_tool_specification ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
So if are planning any particular features for 2.6, now is the time to present them here so that they can be put on the roadmap. I plan to make iwarp into a tool. --tml ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
Hi, On Tue, 2007-10-30 at 00:50 -0200, Filipe Soares Dilly wrote: Ok, thats my feature request: I think you misunderstood me. This thread is not about sending your feature requests. It is about telling us what you would like to work on for the next time in GIMP. We already have more than enough feature requests. Please don't post more here but instead let the developers discuss what's important to address and what they would like to work on. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
Hi, so as I've already written a few weeks ago in my mail about the new features for the text-tool in the PDB, I'd like to contribute especially in that part. As far as I understood the discussion about the roadmap, the PDB will get a little rework for the 2.6 release (named parameters, etc.). So as I'm absolutely new to gimp-development, I'd like to know where is a good starting point to get all informations/things. I'm a bit confused about all information sources: mailing lists, web-pages, wikis, bugzilla, and the source-code itself of course, etc. As Sven told me in a mail-reply, I should bring up the topic about the new text-tool PDB thing... So I have done it now ;) best regards Marcus ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
Marcus Heese wrote: so as I've already written a few weeks ago in my mail about the new features for the text-tool in the PDB, I'd like to contribute especially in that part. As far as I understood the discussion about the roadmap, the PDB will get a little rework for the 2.6 release (named parameters, etc.). It is nice of you to offer to work on improving the text tool portion of GIMP. This is one of those items that has needed work for sometime. It would be worth looking at the text tool related items in Bugzilla. The main (tracking) bug about text tool fixes and enhancement is bug #136740. I saw, but haven't tried, the patch you sent to the mailing list. I see you are allowing extra text options to be set but it isn't easy to see what you are proposing. A new text tool API is one of the outstanding bug reports. It would be helpful to see a summary of the API changes you feel should be made in a form some along the lines of the PDB browser (ie. function name, arguments required, and values returned). I have done a little bit of work on the text operation of GEGL and I know there can be a lot of parameters to set/get. Will you handle only some parameters now and others later? How would the extra parameters be handled later? Setting/getting all text parameters in one call may not be the best option. This may depend on the whether the PDB supported the use of named parameters when a new text tool API is being implemented. Just some things to think about while you plan out a new text tool API. Hopefully, the next version of the text tool and its API will get it right the first time. :-) Looking forward to the improvements you come up with. -- Cheers! Kevin. http://www.ve3syb.ca/ |What are we going to do today, Borg? Owner of Elecraft K2 #2172 |Same thing we always do, Pinkutus: | Try to assimilate the world! #include disclaimer/favourite | -Pinkutus the Borg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] 2.4 and how to continue from here
Moin, currently we are still fixing bugs in the 2.4.0 release but it seems that we caught the major problems now and want to prepare a 2.4.1 release soon. When that is done, we will immidiately create a gimp-2-4 branch to continue bug-fixing there. At that point trunk will be open for development. But since we are aiming for a short development cycle, we need to absolutely keep the tree in a good shape. I don't want to see any commits that haven't been discussed and approved beforehand. This doesn't mean line-by-line code review. But I would like you guys to present your plans here beforehand and not learn about them from reading the commit logs. So if are planning any particular features for 2.6, now is the time to present them here so that they can be put on the roadmap. This includes stuff that has been planned for quite a while, like for example finishing the metadata framework/editor (Raphael!), but also the port to GEGL (Mitch!). I suggest that we keep brainstorming for the 2.6 roadmap for another week and then collect the ideas. It would be nice if we could end with a list of well-defined tasks. When that list is collected, I would like to discuss which of these tasks should be put on the roadmap for 2.6. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
On 10/29/07, Sven Neumann wrote: So if are planning any particular features for 2.6, now is the time to present them here so that they can be put on the roadmap. This includes stuff that has been planned for quite a while, like for example finishing the metadata framework/editor (Raphael!), but also the port to GEGL (Mitch!). What are the plans for vector layers from GSoC 2006? Alexandre ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 and how to continue from here
First of all I'm a Digital illustrator and 3d artist. GIMP in the actual state is great. My job can be done in 2.4 easily (thanks for the Jitter, scalable brushes and better zoom!). And I know that GEGL will be in the future of GIMP and the interface already have great proposals (and designers). So I decide to not propose these kind of features... Ok, thats my feature request: GIMP have a ease and very flexible way to create animated brushes, with features like Random and Angular (to create brushes that rotates as you move in different angles). The thing is: If we have some of these features in the Tools Options for brushes will be more fast and ease to use the brushes that are not animated. Some examples: - The Random feature could be simple rotating (in its own axis) the original brush in a random way. Just a simple check box for activate it, maybe a intensity control how much is random. - The Angular could also be activated using a Check Box. The angle of the brush changing as you drawn in different directions, dynamically rotating the brush. His frequency controlled by the Space option in the Brush Dialog. - Other features that are avaible only creating animated Brushes could be in to. But these to are just great. Other proposal for brushes are a option to control the Softness and Sharpness of Brushes. Today you need to create another brush just to change his softness (or hardness). Maybe a good alternative is to have in the Tools Options a Slider if two ways to go: If you move the slider to the Left the brush will be Sharpened... to the Right will be Blurred. Here is a very ugly mockup: http://fc03.deviantart.com/fs21/f/2007/302/f/a/very_ugly_mockup_by_Filsd.png Thats it and thanks for the hard work. -- Filipe Soares Dilly dilly.carbonmade.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
