Re: [Gimp-developer] Tentative 2.2 feature list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 7, 2004, at 1:14 am, Tim Mooney wrote: As I recall, the SIOD that's part of gimp is not a stock version of SIOD, as there were various bugs detected and fixed in SIOD in the 0.99.x and 1.2.x gimp releases. There *may* be fixes in the gimp's custom SIOD that never got back into the mainline SIOD. That means that using a newer SIOD *might* cause some regressions. Do we know which version exactly? If so, it might make sense to either use a revision control system or fine grained diffs between that and the current version to bring The GIMP up-to-date instead of simply importing the new version and papering over the problems... - -- Servus, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iQEVAwUBQCQynDBkNMiD99JrAQL+wwf/Y7MPmsYqgXQpzROjxV59jj94StiumMZ8 DaMxsi5p9N7RDIrnEIleVz3MB3HPjWUSGDmFigi7w3Usyci4EzRbNwAtLJbGgNZp f2ulIZbMcAkr8pYHh/V4FU1RNmpW2gd61oiYM7xmHLOxFFas4tVzOuUmv1bvKE/8 89S6siYy8LuLe+FId0gitUM1Wy0qH4MrL8gV/CXRTK4pg6zgAJxTSICFiSvJx2KV vyKdmSp+0vptBniqY25hVv/s0HD+2S1qaJC0ok9RLkv6VvG/aF61ZHFf//WS0b28 3iHXZy/gVnkFins48qsIkLmHrpM8UHQWtK/ewUaJxGicUOvr9adYQQ== =g4it -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
On Fri, 2004-02-06 at 19:34, Daniel Egger wrote: On Feb 7, 2004, at 1:14 am, Tim Mooney wrote: As I recall, the SIOD that's part of gimp is not a stock version of SIOD, as there were various bugs detected and fixed in SIOD in the 0.99.x and 1.2.x gimp releases. There *may* be fixes in the gimp's custom SIOD that never got back into the mainline SIOD. That means that using a newer SIOD *might* cause some regressions. Do we know which version exactly? The current SIOD used in the GIMP is Release 3.2X MAR-96. The latest copy of SIOD I found was a tarball named siod-3.2.tar.gz and it says Release 3.2 12-JUN-96. I plan to compare the two versions to see what the differences are rather than just drop this other version in to place. I will also check the CVS log files to check for any bugs that may have been fixed in GIMP's current SIOD that may not have been passed back to the SIOD developers. -- Cheers! Kevin. (http://www.interlog.com/~kcozens/) Owner of Elecraft K2 #2172|What are we going to do today, Borg? E-mail:kcozens at interlog dot com|Same thing we always do, Pinkutus: Packet:[EMAIL PROTECTED]| Try to assimilate the world! #include disclaimer/favourite | -Pinkutus the Borg ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
Kevin Cozens wrote: On Thu, 2004-02-05 at 17:12, David Neary wrote: 9) A decent image browser/thumbnail viewer + cover-sheet support This sounds a bit like the old GUASH (which I have started to port to GTK+ 2.x/GIMP 2.0) but I'm not sure what you mean by cover-sheet support. http://bugzilla.gnome.org/show_bug.cgi?id=132532 Photographers make these a lot to have a nuber of photos in an array on paper. Perhaps this should/could be done at the gimp-print level, but it should integrate nicely into the thumbnail viewer... By the way, Sven has also been talking about doing a thumbnail viewer based on libgimpthumb. I don't know what stage it's at though. In any case, updating GUASH to 2.0 should be a fairly quick job, good luck - perhaps some code clean-up would be nice too? :) Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
Hi, David Neary [EMAIL PROTECTED] writes: That said, here's what I think is a reasonable target feature set for 2.2: 1) Migration to GTK+ 2.4, including - File selector upgrade (allows things like bookmarks) - remove all GtkOptionMenus - use GtkActions for shortcuts Agreed. 2) Cut Paste across other applications including at least - image/pnm (raw, uncompressed data) - image/png (compressed data, slower copies) - image/svg+xml (sodipodi, OO Draw and InkScape would be cool) Some of this is already there (SVG drops are supported) and I think it's reasonable to attempt to finish this for 2.2. 3) Edit patterns in-place 4) Save as GIMP Pattern saves direct to ~/.gimp-1.3/patterns (same for Save as GIMP brush) This would be nice but I don't think it's a blocker for 2.2. If someone wants to give it a try, fine. Not sure if it should be on the list though. 5) Preview widget to replace GimpOldPreview That's a rather large change. If we get someone interested and a proposal for an implementation is posted early enough, then it should probably go in. 6) User-defined presets for most plug-ins Can you explain this further? Actually I don't like the idea of doing it the way we've done it for PNG now. I'd rather attempt to develop a new PDB that can be used alternatively. That redesigned PDB would then bring default values, user-defined presets and lots of other nice things to all plug-ins using it. Did anyone check how far libpdb has come? Would be nice if we could base our efforts on it. 7) Move from SIOD to guile for script-fu Guile or another interpreter or fix the current implementation. All nice but we keep asking for this for years now and I don't see it happen until summer. Let's say, it would be nice to have but it shouldn't block 2.2. On the list of maybe stuff, there's: 9) A decent image browser/thumbnail viewer + cover-sheet support This can be developed outside GIMP. There's no need to put it on our TODO list. 10) Macro recorder, if anyone has ideas on how it can be done with the current PDB/undo system I don't think it can be done with the current system but it should be considered for a PDB redesign which could be part of 2.2 (see above). I also doubt that it makes sense to tackle layer groups and layer effects in 2.2. The timeframe is way too short for these. On the policy side, here's how I would like things to be handled in 2.1.x: - Every feature added to CVS has a bug # associated with it How is that more useful than annoying? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
Hi, Dave Neary [EMAIL PROTECTED] writes: As a matter of interest, why do we not simply take the old GtkPreview code an rename it GimpPreview, put it in libgimpwidgets and use that? Just wondering. Because the old GtkPreview code is not what we would like to see as a GIMP preview widget? It shares a few characters in the name but that's about where the similarity ends. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
Hi, Dave Neary [EMAIL PROTECTED] writes: The idea I had (knowing that this is a big change) is to export the serialisation stuff to libgimp, have plug-ins which want presets extend GimpPlugIn which will implement the serializable interface. The plug-ins should then move from a structure of options (as they currently have) to GObject properties for options they want serialised. Then we could re-use the widgets that are in place in the core in the plug-ins. I won't be able to do this myself, but it would be a very nice feature for someone to take on, if that plan sounded reasonable. If we did this (and I think it's way too much of a change for 2.2), then it should be done right. Doing it right means coming up with an API (probably similar to GimpConfig in the core) that also fits the needs of the redesigned PDB since we will want to reuse that API for it as well. Agreed. But someone could claim this now, and make it the thing they do for 2.2 - given the work that mitch did recently in further separating out siod from script-fu, this should be a fairly small job. What Mitch did there was to prepare the SIOD implementation for an update to the latest released version which is at least two years newer that what we are using now. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
Hi, Sven Neumann wrote: Dave Neary [EMAIL PROTECTED] writes: As a matter of interest, why do we not simply take the old GtkPreview code an rename it GimpPreview, put it in libgimpwidgets and use that? Just wondering. Because the old GtkPreview code is not what we would like to see as a GIMP preview widget? It shares a few characters in the name but that's about where the similarity ends. Ah - I recalled you saying on several occasions that you didn't understand why GtkPreview had been deprecated, that you thought it was a very good widget. I must have misunderstood. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
At 06:18 AM 02/06/2004, Sven wrote: 7) Move from SIOD to guile for script-fu Guile or another interpreter or fix the current implementation. All nice but we keep asking for this for years now and I don't see it happen until summer. Let's say, it would be nice to have but it shouldn't block 2.2. I have started to look at Guile to see how easy/difficult it would be to use it as an eventual replacement for Script-Fu. In the short-term, while looking at the source for Script-Fu/SIOD in the GIMP, I think that some a series of minor patches can help to improve the reporting of error messages. I need to run some additional tests by breaking some scripts and testing error reports. 10) Macro recorder, if anyone has ideas on how it can be done with the current PDB/undo system I don't think it can be done with the current system but it should be considered for a PDB redesign which could be part of 2.2 (see above). While researching Guile as a replacement for Script-Fu, I ran across an article relating to the PDB system. Someone (I forget who) stated they thought that instead of developing the PDB system, the GIMP should have used a system based on CORBA(?). One of the reasons cited for it not being done back then was the lack of open source versions or sufficiently mature implementations IIRC. I don't know much about CORBA other than hearing about it in relation to Windows stuff. Would the features of something based on a CORBA-like system be any better than the existing PDB system? I know this would be a lot of work so any change here would be for a GIMP version 2.2. Also, IIRC, wasn't some of the work being done in the 2.x series meant to clean things up in ways that would make it easier to do the Macro recorder at some point in the future? Cheers! Kevin. (http://www.interlog.com/~kcozens/) Owner of Elecraft K2 #2172|What are we going to do today, Borg? E-mail:kcozens at interlog dot com|Same thing we always do, Pinkutus: Packet:[EMAIL PROTECTED]| Try to assimilate the world! #include disclaimer/favourite | -Pinkutus the Borg ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
At 07:06 AM 02/06/2004, Sven wrote: What Mitch did there was to prepare the SIOD implementation for an update to the latest released version which is at least two years newer that what we are using now. The most recent copy of SIOD I could find was from 1998, IIRC. So, if the current SIOD part of Script-Fu is indeed from 2 years earlier, would it make sense in the short term to update the copy of SIOD currently used in the GIMP until a replacement for the whole Script-Fu system is available? Cheers! Kevin. (http://www.interlog.com/~kcozens/) Owner of Elecraft K2 #2172|What are we going to do today, Borg? E-mail:kcozens at interlog dot com|Same thing we always do, Pinkutus: Packet:[EMAIL PROTECTED]| Try to assimilate the world! #include disclaimer/favourite | -Pinkutus the Borg ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 6, 2004, at 7:25 pm, Kevin Cozens wrote: While researching Guile as a replacement for Script-Fu, Guile is a nasty beast. Gnucash is one of the hardest to compile and keep working applications just because of their use of guile. I'm not really sure you want that amount of fun... - -- Servus, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iQEVAwUBQCP36DBkNMiD99JrAQL+5ggAiym8DW502bSXPPILWmrL9dhQ4YYhEOhO ybp0iSHI8CRUMae+r2D9RYiSQ7iHiHsccYq49FjUMoFO65TwpuFayGAY8X5aeIZm 46C2wfx7+o3KDdkDq69Ws6uEfjtiosNxWSJqKQ0B6MCy8ZaUG9+WrXrIfwQUYtbh +w5wblGnPeO7Xi0xHcYP4o/gNwXb/8zBGO60ZlgxjKnFWhDR3gXKVUnMpa/K8oYn /MTQE1vHXWY3pcsmEbl1JcmzFYerUhniAX2V2+3AMT8B0rAemlTqcoXkzd8I1f6N VBmUH34dvmvPf/X8k2YxHxUarTiMUy3ENtkWT5GYpIkkIICi8QObmQ== =1vwE -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
Hi, Kevin Cozens [EMAIL PROTECTED] writes: At 07:06 AM 02/06/2004, Sven wrote: What Mitch did there was to prepare the SIOD implementation for an update to the latest released version which is at least two years newer that what we are using now. The most recent copy of SIOD I could find was from 1998, IIRC. So, if the current SIOD part of Script-Fu is indeed from 2 years earlier, would it make sense in the short term to update the copy of SIOD currently used in the GIMP until a replacement for the whole Script-Fu system is available? Yes, I think it would be worthwhile to update SIOD to that version. This would probably help to make you more familiar with the current implementation and it could be done in the short timeframe we've setup for GIMP-2.2. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
In regard to: Re: [Gimp-developer] Tentative 2.2 feature list, Sven Neumann...: The most recent copy of SIOD I could find was from 1998, IIRC. So, if the current SIOD part of Script-Fu is indeed from 2 years earlier, would it make sense in the short term to update the copy of SIOD currently used in the GIMP until a replacement for the whole Script-Fu system is available? Yes, I think it would be worthwhile to update SIOD to that version. This would probably help to make you more familiar with the current implementation and it could be done in the short timeframe we've setup for GIMP-2.2. As I recall, the SIOD that's part of gimp is not a stock version of SIOD, as there were various bugs detected and fixed in SIOD in the 0.99.x and 1.2.x gimp releases. There *may* be fixes in the gimp's custom SIOD that never got back into the mainline SIOD. That means that using a newer SIOD *might* cause some regressions. I'm not trying to dissuade anyone from making the change, I'm just trying to give whoever does it a heads up that they may want to see if they can detect if there are any fixes that should be forward-ported into the new SIOD gimp swallows. Tim -- Tim Mooney [EMAIL PROTECTED] Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tentative 2.2 feature list
On Thu, 2004-02-05 at 17:12, David Neary wrote: 9) A decent image browser/thumbnail viewer + cover-sheet support This sounds a bit like the old GUASH (which I have started to port to GTK+ 2.x/GIMP 2.0) but I'm not sure what you mean by cover-sheet support. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
