Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
On Mon, Jan 10, 2000 at 01:56:01PM +0100, Sven Neumann wrote: > > * Error Console (well, here it is, but where are my errors?) > > I don't see your problem. I do get my errors in the error-console. All > that's missing IMO is a way to set the error_console as the default > error_handler in the preferences. That should be easy and is definitely worth > the effort. Well, I think you hit the nail right on the head, I have seen this nice Error Console dialog, and never found out how to get my errors reported there. From your description it sounds like that's just some plumbing. > > * Display Filters > > Are being worked on actively in the last time and the latest CVS version has > a working Gamma filter. Aha! Can someone talk about the intended use of the Gamma filter in Gimp? How does this interact with the (mostly unused) gamma-correction setting in the user's .gimp-1.1/gimprc file? I would like to be able (optionally) to reflect PNG image gAMA settings in the initial view of an image, and to save more accurate values for gAMA when images are entering/ leaving the digital domain. Right now, most users will just get 1 / 2.2 = 0.45 by default, but then almost all apps ignore/abuse the gAMA chunk anyway... Nick.
Re: [gimp-devel] Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Garry R. Osgood ([EMAIL PROTECTED]) wrote: > If there were one feature of Simon's path tool that I would like to have > automagically appear in the Integrated path selection tool, it is the ability > to manipulate the curve by "pulling" on it directly. it is a very pleasant > way to adjust curves. It's effect needs to be adjusted near control points; > bezier basis functions associated with the first and fourth control points > grow expotentially to unity, so manipulating Simon's path near control ^ infinity? > points can be a tad exasperating. Yeah. The basic idea is, that when you drag on the curve near an endpoint you dont want to change the curve at the other endpoint. So I have to move the handle from the near endpoint more drastically to achieve the "curve-dragging" effect. Maybe I should limit the ratio at some point... Anyway: It is not too hard to get the control-point back: Simply drag the curve near the anchor towards the anchor. The controlpoint will appear as quick as he went away earlier :-) Bye, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/
Re: [gimp-devel] Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Simon Budig wrote: > Sven Neumann ([EMAIL PROTECTED]) wrote: > > > How about some comments for feature triage? There are some features in > > > Gimp 1.1.x which are buggy or unusable, yet stay the same for weeks > > Ill try to do something on the tool in the next time, but as always I > cannot promise anything. The first thing would be the API cleanup, the > second thing would be to prepare the conversion to a selection, but bound to > some strange events, since we need the Integration for the right way to > do it. If there were one feature of Simon's path tool that I would like to have automagically appear in the Integrated path selection tool, it is the ability to manipulate the curve by "pulling" on it directly. it is a very pleasant way to adjust curves. It's effect needs to be adjusted near control points; bezier basis functions associated with the first and fourth control points grow expotentially to unity, so manipulating Simon's path near control points can be a tad exasperating. Be good, be well Garry
Re: [ANNOUNCE] GimpMill - A Sawmill Theme Tool
On Mon, Jan 10, 2000 at 09:09:51AM -0800, Carl B. Constantine wrote: > On 1/10/2000 8:55, Ian McKellar at [EMAIL PROTECTED] wrote: > > > GimpMill is a GIMP plugin written in Python using James Henstrige's > > really cool Python GIMP bindings. It allows the construction of Sawmill > > themes within The GIMP - extending the GIMP interface to allow theme > > creation like the GAP extends it to allow animation creation. > > very cool! I've been meaning to take a hard look at Sawmill and compare it > with E and such like. I have theme ideas and this will help greatly. Sawmill is vastly superior. For a start its missing all of E's extra features :) > > Also, slightly off topic, but there is also another sawmill theme creation > tool in the works by John Harper. There's a link to it on the > sawmill.themes.org site. > Yes, its apparently part of 0.21 which I haven't had a chance to look at yet. I thought I would write mine before I got to see his, so my ideas weren't clouded by reality. I strongly feel that theme production tools which are integrated into GIMP are the right way to go. Ian -- Ian McKellar | Email: yakk(a)yakk.net | Web: http://www.yakk.net/ Fax: +61 (8) 9265 0821 / +0 (775) 205 0307 | Home: +61 (8) 9389 9152 If God didn't want us to eat animals, he wouldn't have made them out of meat.
Re: [ANNOUNCE] GimpMill - A Sawmill Theme Tool
On 1/10/2000 8:55, Ian McKellar at [EMAIL PROTECTED] wrote: > GimpMill is a GIMP plugin written in Python using James Henstrige's > really cool Python GIMP bindings. It allows the construction of Sawmill > themes within The GIMP - extending the GIMP interface to allow theme > creation like the GAP extends it to allow animation creation. very cool! I've been meaning to take a hard look at Sawmill and compare it with E and such like. I have theme ideas and this will help greatly. Thank you very much. Also, slightly off topic, but there is also another sawmill theme creation tool in the works by John Harper. There's a link to it on the sawmill.themes.org site. -- __ _ Carl B. Constantine / / (_)__ __ __ [EMAIL PROTECTED] / /__/ / _ \/ // /\ \/ / (2.2.12)http://www.pobox.com/~macman //_/_//_/\_ _/ /_/\_\ Stormix 0.99b4 PGP key available on request VLUG - Victoria Linux Users GroupICQ: 26351441
[ANNOUNCE] GimpMill - A Sawmill Theme Tool
_ __ __ _ _ _ / ___(_)_ __ ___ _ __ | \/ (_) | | | | _| | '_ ` _ \| '_ \| |\/| | | | | | |_| | | | | | | | |_) | | | | | | | \|_|_| |_| |_| .__/|_| |_|_|_|_| |_| 0.1 A Sawmill theme tool for The GIMP. GimpMill is a GIMP plugin written in Python using James Henstrige's really cool Python GIMP bindings. It allows the construction of Sawmill themes within The GIMP - extending the GIMP interface to allow theme creation like the GAP extends it to allow animation creation. To run GimpMill you'll need GIMP 1.1 installed (I'm using 1.1.14, but I don't know what other versions will work) and pygimp (Debian package gimp-python, or look at http://www.daa.com.au/~james/pygimp/). Just copy the gimpmill.py file to ~/.gimp-1.1/plug-ins and start The GIMP. GimpMill's design revolves around the design of Sawmill and its themes, so to understand how to use GimpMill you'll need to have a understanding of Sawmill themes. Sawmill themes are based around "frame parts" - images or text that are stuck to the outside of windows. To use GimpMill, first create a mockup "screenshot" of how you would like one window to look. Next turn the "application window" bit of your image (i.e the bit in between your window borders) into its own layer - the size of the window - by selecting the area and using /Select/Float and then /New. Name this layer "WINDOW". For each of the frame parts create a separate layer in the way described above, but call each of these "PART: name" where name will be used in the image name. To set frame part attributes append "name = value" pairs to the frame part's layer's name (e.g. "PART: closebutton class=close-button"). Finally to specify the difference between the default frame decoration and the focussed, mouseover, etc decoration you can optionally create layers called NORMAL, FOCUSED, HIGHLIGHTED and CLICKED. These are merged with frame part layers before they're saved. Often a black layer with 50% opacity in "Multiply" mode will be what you're after, but if nececarry you can provide complete replacement images. Finally "/Filters/Misc/Make Sawmill Theme" will build your theme and put it in your ~/.sawmill/themes directory - ready for you to use and test. Take a look at the BoldLineY.xcf for the nitty gritty implementation details. PROBLEMS: o GIMP 1.1.14 seems to have a bug converting floating selections into layers by pressing /New. If often gets the size wrong and generally internally confused. o Only one frame type is supported. It is used for default, transient, shaped and shaped-transient windows. I would like to support differnt frame types, but I can't think of an elegant way of doing it. I would certainly welcome suggestions. o Its probably hard to produce really complex themes fully using this tool. It is however a good way to produce the required images and an initial theme.jl file. I'm planning to support tiled images when I can think of a nice way of specifying them (again, ideas are more than welcome). NOTE: BoldLineY is based off the BoldLineY screenshot I got off http://www.kaleidoscope.net/. It was designed by Hideaki Kamada. Some more of his themes (or schemes as Kaleidoscope calls them) for the Mac are available at: http://www.kaleidoscope.net/cgi-bin/schemes.cgi?author=hideakikamada Enjoy, and don't forget to submit your themes to sawmill.themes.org. Updates will be posted at http://www.yakk.net/projects.gimpmill.html. Files are stored at ftp://ftp.ucc.gu.uwa.edu.au/members/yakk/gimpmill/. Ian McKellar <[EMAIL PROTECTED]> Tue Jan 11 2000 -- Ian McKellar | Email: yakk(a)yakk.net | Web: http://www.yakk.net/ Fax: +61 (8) 9265 0821 / +0 (775) 205 0307 | Home: +61 (8) 9389 9152 If God didn't want us to eat animals, he wouldn't have made them out of meat.
sparkle
In the sparkle plugin the data is written directly into tiles. Is there something that speaks against it?
email / cvs
Please change my email in the GIMP cvs from [EMAIL PROTECTED] to [EMAIL PROTECTED] Thanks Martin
gflare bugs
Please mail me all gflare bugs [EMAIL PROTECTED]
Re: [gimp-devel] Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Sven Neumann ([EMAIL PROTECTED]) wrote: > > How about some comments for feature triage? There are some features in > > Gimp 1.1.x which are buggy or unusable, yet stay the same for weeks > > at a time. Without paid staff to do this work, we must throw away [*] > > stuff that's not going to make it. On my short list... [...] > > * Paths > > Simon ? Umm - Yes. I´m terribly sorry, but at the moment my Dis-organizer works a little bit too well. A short summary of the state of the tool: Good News: * Manipulating the path works, maybe needs some minor cleanups. * Converting to a selection probably is easy, since there is code from Andy to convert an array of floats to an selection. * The code seems fairly stable - I dont get crashes at the moment. Bad News: * The API for new path types is not sane at the moment. At some points are Ints instead of floats, some functions do have too much parameters and so on. * The integration with the paths Tab in the L&C Dialog/the PDB Path API/ The XCF-Format is probably horrible - at least for me. Im not sure if this is on the TODO for 1.2, since there are lots of points, where we can break something. My point of view: If the Integration of the Paths tool could not be done before 1.2 we should not include the tool. Its use is too limited in the current state. It should be fairly easy to remove the files shortly before the 1.2 release if necessary. Ill try to do something on the tool in the next time, but as always I cannot promise anything. The first thing would be the API cleanup, the second thing would be to prepare the conversion to a selection, but bound to some strange events, since we need the Integration for the right way to do it. Hope this clears some things. Ill respond to questions... :-) Bye, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Hi, > It's the start of a new year, and my mind turns to Spring cleaning already > > How about some comments for feature triage? There are some features in > Gimp 1.1.x which are buggy or unusable, yet stay the same for weeks > at a time. Without paid staff to do this work, we must throw away [*] > stuff that's not going to make it. On my short list... > > * Resizable toolbar Yosh? I hope we can get the wrapboxes to work. They are considered to be part of GTK+-1.4, so it should be possible to fix this. As a workaround I'd suggest making the layout (horizontal, vertical) a preferences option and disable the interactive resizing. > * Natural airbrush Olof ? > * Error Console (well, here it is, but where are my errors?) I don't see your problem. I do get my errors in the error-console. All that's missing IMO is a way to set the error_console as the default error_handler in the preferences. That should be easy and is definitely worth the effort. > * Display Filters Are being worked on actively in the last time and the latest CVS version has a working Gamma filter. > * Paths Simon ? I think we can wait a little longer with the decision about the removal of the two new tools, Path and Xinput Airbrush, since they don't interact with any other part of the GIMP and can very easily be removed if necessary. Otherwise I'm all for pushing The GIMP into 1.2 as soon as possible. Salut, Sven
Re: [gimpwin-users] PNG blank display bug
Hi, > > I have changed the core so that it does not accept zero resolutions. > > > > Additionally I have changed all plug-ins that try to set the resolution > > to check the value and simply don't set it at all if it is invalid. Gimp > > will then use the default set up by the user. > > Perl, IIRC teaches us that "There's always more than one way to do it", > while it seems that Gimp teaches us that "There's always more than one > place to change it." > > If we do not accept arbitrary values for xresolution & yresolution we > need to check for this in image_set_resolution_invoker as well. This > is the approach I've taken in current CVS. > > Alternatively we could change image_set_resolution_invoker() and > similar functions to be thin wrappers around core functionality -- > I do not have time to do that, but perhaps someone else does? > Oops, I thought (but should have checked) that image_set_resolution_invoker was calling the gimp_image_set_resolution() in app/gimpimage.c. And probably it should since the core function keeps the undo_stack in sync by calling undo_push_resolution (gimage). On the other hand if called from the PDB, we probably don't want to gdisplays_shrink_wrap (gimage)... Salut, Sven
Triage! (was Re: [gimpwin-users] PNG blank display bug)
On Mon, Jan 10, 2000 at 10:29:29AM +0100, Sven Neumann wrote: > Oops, I thought (but should have checked) that image_set_resolution_invoker > was calling the gimp_image_set_resolution() in app/gimpimage.c. And probably > it should since the core function keeps the undo_stack in sync by calling > undo_push_resolution (gimage). On the other hand if called from the PDB, we > probably don't want to gdisplays_shrink_wrap (gimage)... Um, yes, that's pretty much the sequence of thoughts that went through my mind. However, doing a good job of removing such redundancy will take a lot of time, and provide no noticeable improvements (save the possibility of stumbling on a bug fix) for our poor users. -- It's the start of a new year, and my mind turns to Spring cleaning already How about some comments for feature triage? There are some features in Gimp 1.1.x which are buggy or unusable, yet stay the same for weeks at a time. Without paid staff to do this work, we must throw away [*] stuff that's not going to make it. On my short list... * Resizable toolbar * Natural airbrush * Error Console (well, here it is, but where are my errors?) * Display Filters * Paths More? Comments from people who started these features? This is your excuse to tell us the long tale of how the perfect 100% bug free version of Fill-in-your-feature was tragically lost to a Volcano during your desperate struggle to save an innocent baby... Nick. [*] Well, put it to one side until 1.3.x, but even then, if no-one will write code for it, how will the feature get finished?
