[Gimp-developer] Re: Preview widget name
While we are at it. The two characters "Fu" to represent "A uniform interface that allows setting parameters for the execution of a sequence of gimp functions where each type of parameter has a fixed GUI mapping" is much weirder, imho. And that is exposed to the user, which Prevue would not be... Regards, Dov On Wed, Apr 02, 2003 at 05:48:44PM -0600, Brian Mullin wrote: > I do see those sorts of spellings from time to time, yes. The same thing > with "prevu". > > But, to answer your question... Yes, "GimpPrevue" does look kind of > weird. It does to me, at any rate. :) > > Brian Mullin > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ernst Lippe > Sent: Wednesday, April 02, 2003 5:24 PM > To: Gimp-developer > Subject: Preview widget name > > > My Webster's lists prevue as a synonym for preview (to me this appears > to be the original French root of the word). > > Does GimpPrevue sound very weird for native English speakers? > > greetings, > > Ernst Lippe > ___ > Gimp-developer mailing list [EMAIL PROTECTED] > http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer > > ___ > Gimp-developer mailing list > [EMAIL PROTECTED] > http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer -- ___ ___ / o \ o \ Dov Grobgeld ( o o ) o | The Weizmann Institute of Science, Israel \ o /o o / "Where the tree of wisdom carries oranges" | | | | _| |_ _| |_ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Tool API [LONG!]
Here is a list of all the symbols currently used by the current tools, courtesy of nm tools/*.o paint/*.o | cut -b 10- | grep ^T | cut -b 3- | sort | uniq stdlib, glib, gdk, pango, and gtk calls have been eliminated from this list. The big things that stand out are accessing the global "the_gimp", and calling tile and tile manager functions. "the_gimp" should not be accessed directly, and tile_manager is probably too ugly for tool developers with weak stomachs. Rockwalrus active_color add_alpha_region apply_mask_to_region blend_region brightness_contrast_lut_setup brush_scale_mask brush_scale_pixmap color_balance color_balance_create_lookup_tables color_balance_init color_balance_range_reset color_pixels color_region combine_mask_and_region convolve_region copy_region curves_calculate_curve curves_channel_reset curves_init curves_lut_func find_mask_boundary floating_sel_anchor floating_sel_relax floating_sel_rigor gdisplays_check_valid gimp_base_config_get_type gimp_bezier_stroke_extend gimp_bezier_stroke_get_type gimp_bezier_stroke_new gimp_brush_get_spacing gimp_brush_get_type gimp_brush_select_brush gimp_brush_want_null_motion gimp_bucket_fill_mode_get_type gimp_channel_add_segment gimp_channel_invalidate_bounds gimp_channel_new_mask gimp_channel_ops_get_type gimp_channel_value gimp_color_area_get_type gimp_color_area_new gimp_color_area_set_color gimp_color_panel_get_type gimp_color_panel_set_context gimp_config_connect gimp_config_copy_properties gimp_config_deserialize gimp_config_disconnect gimp_config_duplicate gimp_config_reset gimp_config_serialize gimp_container_add gimp_container_add_handler gimp_container_get_child_by_name gimp_container_remove_handler gimp_container_thaw gimp_context_copy_properties gimp_context_define_properties gimp_context_get_brush gimp_context_get_display gimp_context_get_gradient gimp_context_get_opacity gimp_context_get_paint_mode gimp_context_get_pattern gimp_context_get_tool gimp_context_get_type gimp_context_new gimp_context_set_background gimp_context_set_display gimp_context_set_foreground gimp_context_set_parent gimp_context_set_tool gimp_context_tool_changed gimp_crop_type_get_type gimp_cursor_new gimp_devices_get_current gimp_dialog_create_action_area gimp_dialog_factory_dialog_raise gimp_dialog_get_type gimp_directory gimp_display_config_get_type gimp_display_coords_in_active_drawable gimp_display_flush gimp_display_flush_now gimp_display_get_type gimp_display_shell_draw_guide gimp_display_shell_get_type gimp_display_shell_scale_by_values gimp_display_shell_selection_visibility gimp_display_shell_set_cursor gimp_display_shell_set_override_cursor gimp_display_shell_transform_xy gimp_display_shell_transform_xy_f gimp_display_shell_unset_override_cursor gimp_display_shell_untransform_xy gimp_dock_get_type gimp_double_adjustment_update gimp_drawable_blend gimp_drawable_bucket_fill gimp_drawable_bytes gimp_drawable_calculate_histogram gimp_drawable_data gimp_drawable_get_color_at gimp_drawable_get_type gimp_drawable_has_alpha gimp_drawable_height gimp_drawable_is_indexed gimp_drawable_is_rgb gimp_drawable_mask_bounds gimp_drawable_offsets gimp_drawable_push_undo gimp_drawable_transform_cut gimp_drawable_transform_matrix_perspective gimp_drawable_transform_matrix_rotate_center gimp_drawable_transform_matrix_scale gimp_drawable_transform_matrix_shear gimp_drawable_transform_paste gimp_drawable_transform_tiles_affine gimp_drawable_transform_tiles_flip gimp_drawable_type gimp_drawable_width gimp_enum_option_menu_new gimp_enum_radio_frame_new gimp_get_current_context gimp_get_mod_name_alt gimp_get_mod_name_control gimp_get_type gimp_get_user_context gimp_gradient_get_color_at gimp_gradient_type_get_type gimp_gui_config_get_type gimp_help_connect gimp_help_set_help_data gimp_histogram_box_get_type gimp_histogram_box_new gimp_histogram_calculate gimp_histogram_channel_get_type gimp_histogram_free gimp_histogram_get_count gimp_histogram_get_mean gimp_histogram_get_median gimp_histogram_get_std_dev gimp_histogram_nchannels gimp_histogram_new gimp_histogram_view_get_channel gimp_histogram_view_get_type gimp_histogram_view_new gimp_histogram_view_set_channel gimp_histogram_view_set_histogram gimp_histogram_view_set_range gimp_hls_to_rgb_int gimp_image_active_drawable gimp_image_add_guide gimp_image_add_hguide gimp_image_add_layer gimp_image_add_vectors gimp_image_add_vguide gimp_image_apply_image gimp_image_contiguous_region_by_seed gimp_image_crop gimp_image_crop_auto_shrink gimp_image_delete_guide gimp_image_find_guide gimp_image_floating_sel gimp_image_flush gimp_image_get_active_layer gimp_image_get_background gimp_image_get_color gimp_image_get_foreground gimp_image_get_type gimp_image_map_abort gimp_image_map_apply gimp_image_map_clear gimp_image_map_commit gimp_image_map_get_color_at gimp_image_map_new gimp_image_mask_boundary gimp_image_mask_bounds gimp_image_mask_clear gimp_image_mask_float gimp_image_mask_is_empty gimp_image_mask_select_by_color gimp_image_mas
Re: [Gimp-developer] Plug-in preview API proposal
On Thu, 3 Apr 2003, Ernst Lippe wrote: > On the contrary, there appear to be lots of acceptable > names. > I am suprised that nobody has suggested YetAnotherGimpPreview :) How about GimpPluginView? GimpSample? GimpTheWidgetFormerlyKnownAsPreview? GimpFancyPreview? GimpMcPreview? GimpExample? GimpView? Actually, GimpThumbnail is more reasonable for the core widget's name than it is for the plugin widget's name. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Preview widget name
On Wed, 02 Apr 2003 16:05:52 -0800 Jeshua Lacock <[EMAIL PROTECTED]> wrote: > > On Wednesday, April 2, 2003, at 03:41 PM, Kevin Myers wrote: > > > Personally I don't think that it sounds too bad at all, especially > > considering the lack of other decent alternatives suggested so far... > > Hello Kevin, > > I think the average American will think it was translated funky and > assume it is the work of an amateur. Of course, this is just my humble > opinion. But it is the work of an amateur, up till now nobody has offered me any payment for it. What's worse I now realize that it is possible that some literate americans (yes, they do exist) might assume that it was written by some Frenchman, which might be dangerous in the present circumstances. greetings, Ernst ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Plug-in preview API proposal
On Thu, 03 Apr 2003 02:15:42 +0200 "David Necas (Yeti)" <[EMAIL PROTECTED]> wrote: > On Thu, Apr 03, 2003 at 01:15:31AM +0200, Ernst Lippe wrote: > > P.S. I just modified my preview so that the re-entrancy problem has > > been eliminated. > > Excuse me, but which reentrancy problem has been eliminated? > Does it mean the render function no longer needs to be > reentrant? Yes, just added some book-keeping to preview, and it seems to work. > > Regards, > > Yeti > > > P.S.: Regarding the name, when I've seen the last > suggestions, GimpWWAAN (Widget Without Any Acceptable Name) > seem to be the most accurate... :-) On the contrary, there appear to be lots of acceptable names. I am suprised that nobody has suggested YetAnotherGimpPreview :) greetings, Ernst ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Plug-in preview API proposal
On Thu, Apr 03, 2003 at 01:15:31AM +0200, Ernst Lippe wrote: > P.S. I just modified my preview so that the re-entrancy problem has > been eliminated. Excuse me, but which reentrancy problem has been eliminated? Does it mean the render function no longer needs to be reentrant? Regards, Yeti P.S.: Regarding the name, when I've seen the last suggestions, GimpWWAAN (Widget Without Any Acceptable Name) seem to be the most accurate... :-) ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Preview widget name
On Wednesday, April 2, 2003, at 03:41 PM, Kevin Myers wrote: Personally I don't think that it sounds too bad at all, especially considering the lack of other decent alternatives suggested so far... Hello Kevin, I think the average American will think it was translated funky and assume it is the work of an amateur. Of course, this is just my humble opinion. Whatever the name, it will be welcomed functionality. How about: GimpPredo GimpThumb GimpPeek GimpProView GimpSneak (Just what popped into my head based on the description) Cheers, Jeshua Lacock __ Programmer/OwnerPhone: 760.935.4736 http://OpenOSX.com Fax:760.935.4845 -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
RE: [Gimp-developer] Preview widget name
I do see those sorts of spellings from time to time, yes. The same thing with "prevu". But, to answer your question... Yes, "GimpPrevue" does look kind of weird. It does to me, at any rate. :) Brian Mullin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ernst Lippe Sent: Wednesday, April 02, 2003 5:24 PM To: Gimp-developer Subject: [Gimp-developer] Preview widget name My Webster's lists prevue as a synonym for preview (to me this appears to be the original French root of the word). Does GimpPrevue sound very weird for native English speakers? greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Preview widget name
Personally I don't think that it sounds too bad at all, especially considering the lack of other decent alternatives suggested so far... Kevin M. Round Rock, Texas - Original Message - From: "Jeshua Lacock" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 02, 2003 5:39 PM Subject: Re: [Gimp-developer] Preview widget name > > On Wednesday, April 2, 2003, at 03:24 PM, Ernst Lippe wrote: > > > My Webster's lists prevue as a synonym for preview (to me this appears > > to be the original French root of the word). > > > > Does GimpPrevue sound very weird for native English speakers? > > Yes - it sounds quite Euro. : ) > > Kind of like Shoppe or Colour... > > > Jeshua Lacock __ > Programmer/OwnerPhone: 760.935.4736 > http://OpenOSX.com Fax:760.935.4845 > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ > > ___ > Gimp-developer mailing list > [EMAIL PROTECTED] > http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer > ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Preview widget name
On Wednesday, April 2, 2003, at 03:24 PM, Ernst Lippe wrote: My Webster's lists prevue as a synonym for preview (to me this appears to be the original French root of the word). Does GimpPrevue sound very weird for native English speakers? Yes - it sounds quite Euro. : ) Kind of like Shoppe or Colour... Jeshua Lacock __ Programmer/OwnerPhone: 760.935.4736 http://OpenOSX.com Fax:760.935.4845 -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Preview widget name
My Webster's lists prevue as a synonym for preview (to me this appears to be the original French root of the word). Does GimpPrevue sound very weird for native English speakers? greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 1.2.4 Final?
Greetings, If there is anything we can do to help with these issues, please just let me know and I will get my guy on it. On Thursday, March 20, 2003, at 08:28 AM, Sven Neumann wrote: Hi, Raphaël Quinet <[EMAIL PROTECTED]> writes: Well, yes this is a ridiculous bug. However, the license problems are now publicly known. And there is a Debian bug report related to that. So I assume that any distribution that is aware of these issues and cares about being able to distribute packages legally would consider this bug to be a blocker. Otherwise, they would be liable in the (unlikely) case that some copyright holder complains about the licenses. Not very likely, maybe, but some distributors are probably taking these legal issues seriously. Well, we already took care about a couple of affected files. Let's look at the remaining files: plug-ins/common/edge.c This file has about 500 lines from which at least 400 are completely GIMP specific. The algorithm used boils down to a few lines and could probably be "discovered" by any high-school student who made his/her maths homework from time to time. I'd like to cite RMS here: "You don't need to worry about copyrights or licenses for just a few lines of code." plug-ins/common/gif.c This one is difficult since its a mix of some older code for which the license is not perfectly clear and lots of new code that has been added while this file lived in the GIMP source tree under a GPL license. Definitely a difficult choice with rather unpleasant consequences since other projects have long adapted this code under GPL and LGPL licenses. plug-ins/common/mail.c This plug-in contains a few lines that perform base64 encoding. The authors of this code should feel honored for being mentioned since anyone could take the base64 spec and rewrite this from scratch. plug-ins/common/nlfilt.c The algorithms here are not really trivial and it would make sense to try to contact the author. If he doesn't agree to relicense his code, we could just drop the plug-in. plug-ins/common/tiff.c I don't see where this plug-in uses any non-GIMP-specific code that is worth being mentioned. The TIFF file format is handled by libtiff and I doubt there's anything in this plug-in that can not be determined from reading the libtiff docs. plug-ins/webbrowser/webbrowser.c The algorithm used here is rather trivial and can be redone using the docs provided by Netscape. The original authors should feel honored for being mentioned. We want to get rid of this plug-in for GIMP-1.4 anyway. plug-ins/script-fu/interp_slib.c I'd rather not have to rewrite this one. But then we have always very clearly stated the source of the SIOD interpreter that runs Script-Fu. Just go and try 'gimp-1.3 -i -b -'. You will see the following lines: Welcome to SIOD, Scheme In One Defun, Version 3.2x 12-MAR-96 (C) Copyright 1988-1994 Paradigm Associates Inc. Help: (help) IMO this is exactly what the SIOD license asks for. I don't see any problems. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Plug-in preview API proposal
Even though I fully agree that the only serious problem in my API proposal is the name of the widget, I'd really like to get more input from more people about my API proposal. Especially, I would like to hear remarks from other plug-in developers, because they are after all the intended audience for this widget. (I somehow have the feeling that Sven is not really an average plug-in developer:). So for all average (and especially the below-average) plug-in developers: * Do you miss any features? * Is the documentation sufficient? * Would you use it? Of course I would also like some inputs about the discussion about using iterators in the rendering function. greetings, Ernst P.S. I just modified my preview so that the re-entrancy problem has been eliminated. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Plug-in preview API proposal
On Wed, 02 Apr 2003 15:30:04 +0200 [EMAIL PROTECTED] wrote: > > Sven Neumann <[EMAIL PROTECTED]> wrote: > > >anyway. Now if only we could come up with a good name for the core > >widget ... > > May I suggest "GimpMiniview"? Yes, you may :) But it sounds like something tiny. Actually when you zoom in and use a large preview it can be much bigger than the original image. greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Plug-in preview API proposal
>From [EMAIL PROTECTED] on 2 Apr 2003: > May I suggest "GimpMiniview"? GimpMiniMe would be shorter, and probably more in the gimp tradition. A filter just as diabolical but at 1/8th the size! Michael ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Plug-in preview API proposal
Sven Neumann <[EMAIL PROTECTED]> wrote: >anyway. Now if only we could come up with a good name for the core >widget ... May I suggest "GimpMiniview"? -- Pedro Gimeno ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Keybindings
On 02 Apr 2003 12:40:37 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote: > Owen <[EMAIL PROTECTED]> writes: > > I've updated keybindings.txt,tex and pdf to match the cvs as at 31 Mar > > there's one more thing you might want to change. Your version states > that keybindings can be dynamically reassigned. This is not any longer > possible by default. You need to explicitely turn this feature on in > the preferences dialog (labelled as "Dynamic Keyboard Shortcuts"). > > The idea behind this change is that this prevents users from > accidentally reassigning shortcuts. The user should be advised that in > order to change the keybindings, she should enable Dynamic Keyboard > Shortcuts in the prefs, do the changes and redisable the feature > afterwards. ObBugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=106991 While you are updating the text, please fix the spelling mistake at the end of the second paragraph: "it's binding" should be "its binding". Suggestion for re-writing that paragraph: The GIMP allows menu keybindings to be dynamically re-assigned. So if you don't like these, they are easy enough to change. To do this, you should first activate the "Dynamic Keyboard Shortcuts" in the preferences dialog. Then you can just highlight the menu item of your choice, and press the desired new key combination. If that combination is already assigned, the old command will lose its binding. And please use a fixed-width font while editing the text file. This will ensure that all shortcuts are correctly aligned. You can check this by viewing the text file in a web browser, for example. It looks like the paragraphs in the text file were wrapped at line 65 (instead of the default 70 or 72). If you are using Emacs for editing the text file, you can use M-: followed by (setq fill-column 65) to wrap the text to the same column as in the original file. -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Keybindings
Hi, Owen <[EMAIL PROTECTED]> writes: > I've updated keybindings.txt,tex and pdf to match the cvs as at 31 Mar there's one more thing you might want to change. Your version states that keybindings can be dynamically reassigned. This is not any longer possible by default. You need to explicitely turn this feature on in the preferences dialog (labelled as "Dynamic Keyboard Shortcuts"). The idea behind this change is that this prevents users from accidentally reassigning shortcuts. The user should be advised that in order to change the keybindings, she should enable Dynamic Keyboard Shortcuts in the prefs, do the changes and redisable the feature afterwards. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Keybindings
Hi, Owen <[EMAIL PROTECTED]> writes: > I've updated keybindings.txt,tex and pdf to match the cvs as at 31 Mar > > http://www.webone.com.au/~oc/gimp/keybindings.pdf > http://www.webone.com.au/~oc/gimp/keybindings.tex > http://www.webone.com.au/~oc/gimp/keybindings.txt The PDF looks rather nice and I think we should include it with the tarball. Is there a reason the .txt version is so horribly aligned if viewed with a fixed-width font? Would you mind if I fix it before I commit to CVS? Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
