Re: [Gimp-developer] script-fu menu
I am not a GIMP developer, though I have been a spectator on this list for a while now. I suggest that you specify exactly what you are trying, and what exactly you are looking for. A detailed work-flow and a UI mock-up image would best describe what you want. Specify the problem.. not the solution. I HTH . -- Laxminarayan Kamath Ammembal (+91) 9945036093 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] GSOC 2008 - ideas
Hi there! We have some ideas for Google Summer of Code project in the wiki, but all of tehna re dangling since last year. Mos t of tehm look good, but some may have been obsoleted in the current devel cycle, or would involve changes in code that is going away in the cycle. I am posting the full set of ideas bellow and asking for commetns on ideas, new ideas, and overall, people who would be willing to mentor a stundet through some of them. regards, js -- http://wiki.gimp.org/gimp/SummerOfCode2008ideas - [BOTTOM][TOP]GSoC2008 Project Ideas Please note that, although you are welcome to look at what is here, this is a workspace for mentors to write down and modify their ideas, and suggestions here should not be taken as necessarily viable projects until they have been finalized. Also, the fact that something appears here does not necessarily mean that anybody has volunteered to mentor it. Note to people who add stuff here: Please try to add information about a prorpsal's overall complexity and experience that could be helpful. E.G. experience with GTK+, image manipulation algorithms, web application development, ... Filetype registration There is currently no way to register a file type to open with GIMP from within GIMP itself. On some desktop environments and platforms, this makes registering types to open with GIMP awkward. We need a configuration GUI within GIMP, which does show the available types and/or file extensions, and a means (a backend) to register them according to the platform/environment. The latter should probably be modular and extensible, because this is different on each of them. Resource management. Currently resources such as brushes, gradients etc are shown to the user in an unstructured way, only sorted alphabetically. This greatly limits the number of items a user can deal with. People love to make collections of things, so this would greatly enhance the user experience. It has been suggested that this should not be a finite set of categories, bug rather tags. Create an SDI manager widget. Would allow all of GIMP's windows to be contained in a single parent window, as requested hundreds of times by Windows users. (This would be optional, not forced on people who don't want it.) Plug-in stability effort Tests have shown that it is possible to crash plug-ins when feeding them bogus data via the PDB API, for example when calling them from scripts (another interesting approach might be to run file loader plug-ins with [WWW] zzuf). Needed: a test framework to find the bugs, and then time to fix them. Additional file format plug-ins There is a number of file formats that GIMP should support, but doesn't or at least doesn't support fully, for example MNG. The MNG save plug-in needs to be modified to save images in MNG-LC profile. Then a loader can be easily written to work similar to the GIF loader. It also needs support for JPEG chunks. On-canvas text editing Right now, the text tool opens a dialog window where the text has to be put. Nearly every other option of the text toold is in its tool options dialog, so it would be nice to get rid of this dialog as well. Search-based menu browser The amount of menu entries in GIMP - either from plug-ins, scripts or internal functions - is huge. The name of a particular function might be easier to remember than its menu location. Being able to search for the function and applying it to the image without having to go through the menus can help (similar to Emacs' M-x feature). Unified UI for scripting We have three major scripting interfaces, Script-Fu, ?PyGimp and Perl-Fu. All of them allow to create an interface for a script easily, just by registering a function with their respective parameters. However, all widgets look a bit different depending on the binding. Redesign and reimplementation of Save and Export in GIMP. Change the semantics of Save and Save As so that images are always saved in the XCF file format. Only the native GIMP format really saves all the image information and allows to lossless continue editing later. So only saving as XCF should clear the dirty flag of the image. Saving to other formats than XCF is done by exporting the image. The File menu should have an Export menu item (and perhaps also Export As). Unit testing framework GIMP currently doesn't have a test framework that API changes or internal changes could be tested against. This is crucial to avoid regressions, especially with the major rewrite we will seen when GEGL is introduced. Work on GEGL [WWW] GEGL is a graph based image processing framework. It will be introduced into the GIMP trunk after 2.4 has been released. Processing is done by the nodes of the graph, which are implemented as so-called operations or 'ops'. A good introduction to the current state of GEGL is the [WWW]
[Gimp-developer] Pressure emulation using mouse?
Is it possible to add pressure emulation using the second mouse's y axis? -- Laxminarayan Kamath Ammembal (+91) 9945036093 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] script-fu menu
* El 02/03/08 a las 15:25, Laxminarayan Kamath chamullaba: I am not a GIMP developer, though I have been a spectator on this list for a while now. I suggest that you specify exactly what you are trying, and what exactly you are looking for. A detailed work-flow and a UI mock-up image would best describe what you want. Specify the problem.. not the solution. Sorry, I thought I was clear enough (did I specify the solution??) What I want to do is what is pretty standard in these cases: My script-fu has a lot of options, and a check box to use default values of these options. I want these options to become grayed out when the check box is checked. Just that. My other question was if it is possible to add text to a script-fu option window that is not related to an option of the script. But I do not know if these are possible in script-fu, and I didn't find a complete enough reference for script-fu. Thanks again, L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Pressure emulation using mouse?
On Sunday 02 March 2008 14:08:13 Laxminarayan Kamath wrote: Is it possible to add pressure emulation using the second mouse's y axis? practically no, (theoretically maybe, but it would be a pita mixing events from two sources). All pointer movement is driven by events that carry info about the pointers current state. These events are read from the driving device and then given to gimp to do whats needed. However it is possible to substitute a derived dynamic, velocity, for pressure. I have already done most of the groundwork needed for this and events do carry velocity info, drawing tools just don't know at the moment how to use it... ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] script-fu menu
On Sun, Mar 2, 2008 at 4:44 AM, Luis A. Florit [EMAIL PROTECTED] wrote: Sorry, I thought I was clear enough (did I specify the solution??) What I want to do is what is pretty standard in these cases: You were certainly clear enough, but there is no way to do that using script-fu. If you need fine control of the interface, you'll have to use a more powerful language. -- Bill ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp-developer Digest, Vol 66, Issue 3
Sorry, I thought I was clear enough (did I specify the solution??) What I want to do is what is pretty standard in these cases: You were certainly clear enough, I thought I was... but there is no way to do that using script-fu. If you need fine control of the interface, you'll have to use a more powerful language. Ok, this is what I suspected. Someone here told me some time ago to try python-fu, but my script is almost done since long time ago, and I am not sure if python-fu would do it. Of course C would... Thanks Bill! L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GSOC 2008 - ideas
Hi, On Sun, 2008-03-02 at 07:44 -0300, Joao S. O. Bueno wrote: I am posting the full set of ideas bellow and asking for commetns on ideas, new ideas, and overall, people who would be willing to mentor a stundet through some of them. Sorry, the text you posted is so badly formatted that I am not willing to read it. But nevertheless I would like to say that IMO we should try to focus on GEGL and babl tasks for this year's SoC. That should bring us closer to our goal of full GEGL integration in GIMP. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] script-fu menu
On Sunday 02 March 2008, Luis A. Florit wrote: * El 02/03/08 a las 15:25, Laxminarayan Kamath chamullaba: I am not a GIMP developer, though I have been a spectator on this list for a while now. I suggest that you specify exactly what you are trying, and what exactly you are looking for. A detailed work-flow and a UI mock-up image would best describe what you want. Specify the problem.. not the solution. Sorry, I thought I was clear enough (did I specify the solution??) What I want to do is what is pretty standard in these cases: My script-fu has a lot of options, and a check box to use default values of these options. I want these options to become grayed out when the check box is checked. Just that. My other question was if it is possible to add text to a script-fu option window that is not related to an option of the script. But I do not know if these are possible in script-fu, and I didn't find a complete enough reference for script-fu. Thanks again, L. Hi there, At first, I have toḋ say to you it is likely these chanegs are not going to be made. The auto-interface build up in script-fu, perl-fu and python-fu is a convenience, and presented as is. More sofisticated plug-ins should use GTK+ to draw their own interfaces . Unfortunatelly this is no option when you are using Scheme (script-fu). If you do your work in python, however, you have, in the opinos of many people, and in my strong opinion, an easier to work langauge than Scheme, and will gain the flexibility to build your custom interface as you please. (And still, won't miss any flexibilit otherwise avaliable only to plug-ins written in C). Ah, there are also Ruby bindings, should you prefer Ruby than Python. And finally, so that you don't think you are alone in this desire for greater control on the authomatic interfaces, I have thoguth about that as well, and it is possible that something more or less like what you are asking to be implemented for Python plug-ins. Regards, js -- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] script-fu menu
Luis A. Florit wrote: I want to do these on the plugin option window: 1) Gray-out some options according to checkboxes; 2) Add arbitrary text, horizontal lines, boxes, or something like that. You can't do either of the above in Script-Fu. Adding new parameter types to allow adding extra text or horizontal lines is possible but is not currently on the ToDo list. Greying out other items based on selections being made is a feature that is unlikely to be seen in Script-Fu anytime in the near, or distant, future. -- 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
Re: [Gimp-developer] script-fu menu
Luis A. Florit wrote: But I do not know if these are possible in script-fu, and I didn't find a complete enough reference for script-fu. There is some documentation about Script-Fu at http://www.gimp.org/docs/. I have been putting together my own set of documentation for Script-Fu which you can find at: http://www.ve3syb.ca/wiki/doku.php?id=software:sf:start Amongst the things you will find there are a list of the items you can use in the register block. -- 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
Re: [Gimp-developer] Gimp-developer Digest, Vol 66, Issue 3
On Sunday 02 March 2008, Luis A. Florit wrote: Ok, this is what I suspected. Someone here told me some time ago to try python-fu, but my script is almost done since long time ago, and I am not sure if python-fu would do it. Of course C would... Thanks Bill! Python-fu is capable of everything script-fu is, an dmost of what C is, as well. Translating a script-fu to a python-fu is mostly a matter of re-arranging (and dropping) parenthesis :-) js -- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp-developer Digest, Vol 66, Issue 4
Luis A. Florit wrote: But I do not know if these are possible in script-fu, and I didn't find a complete enough reference for script-fu. There is some documentation about Script-Fu at http://www.gimp.org/docs/. I have been putting together my own set of documentation for Script-Fu which you can find at: http://www.ve3syb.ca/wiki/doku.php?id=software:sf:start Amongst the things you will find there are a list of the items you can use in the register block. Thanks a lot Kevin, and all the others that kindly answered my post. Now at least I know that I cannot do what I wanted in script-fu. My next projects will be done directly in C or python-fu. It seems that script-fu is kind of 'stalled'... Cheers, L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
