After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 15084 - Frosty not working as earlier
Frosty not working as earlier
Status: RESOLVED DUPLICATE of bug 132145
Product: GIMP
Classification: Other
Component: Script-Fu
1.x
Other Linux
: Low enhancement
: Future
Assigned To: GIMP Bugs
Daniel Egger
: 51010 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2000-06-23 10:40 UTC by Martin Weber
Modified: 2004-11-04 04:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Reference image (frosty.gif) supplied by Peter Bergt (17.26 KB, image/gif)
2003-01-17 11:53 UTC, Raphaël Quinet
Details

Description Martin Weber 2001-01-28 15:55:10 UTC
Package: gimp
Version: 1.1.23

Name........: Martin Weber
Email.......: martweb@gmx.net
Platform....: SuSE Linux 6.4
GIMP Version: 1.1.23
GTK Version.: 1.2.8
WM/Version..: 


-- Other system notes:

--

-- Problem description:
The scriptfu frosty does not lead to the results as in earlier GIMP 1.1 or 1.0 versions.
--


-- How to repeat:

--


-- Other comments:

--




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-28 10:55 -------
This bug was previously known as bug 15084 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=15084
Originally filed under the gimp product and general component.

The original reporter (martweb@gmx.net) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, egger@suse.de.

Comment 1 Raphaël Quinet 2001-02-19 08:31:20 UTC
*** Bug 51010 has been marked as a duplicate of this bug. ***
Comment 2 Raphaël Quinet 2001-02-19 12:49:22 UTC
I am not sure that the script itself (frosty-logo.scm) is the culprit.
The script generates different results in 1.0.x and 1.1.x or later
because the Sparkle plug-in was modified in some early 1.1.x version.

One solution would be to modify the Frosty script and find a
combination of parameters that can generate more or less the same
results as in 1.0.x.  Another solution would be to modify the Sparkle
plug-ins so that it generates the same output as before.

A link to some images comparing an early 1.1.x version (before the
changes in the Sparkle plug-in) and the 1.2.x version can be found
in bug #51010.

Note: the sparkle plug-in has some bugs related to the usage of
selections, as described in bug #50911.  However, the Frosty script
clears the selection before calling the Sparkle plug-in, so these two
bugs are only indirectly related (if at all).
Comment 3 Raphaël Quinet 2001-04-26 18:11:37 UTC
Re-assigning all Gimp bugs to default component owner (Gimp bugs list)
Comment 4 Daniel Egger 2001-10-24 09:06:46 UTC
We tried to make it more similar by fixing the used plugin
(sorry, forgot the name :)) though I don't believe this is
really a problem.
Comment 5 Henrik Brix Andersen 2003-01-17 10:30:24 UTC
The frosty.scm script included with 1.2.3 produces a resulty not too far from the one mentioned in bug #51010 (refered above).

Maybe we can close this bug report?
Comment 6 Raphaël Quinet 2003-01-17 11:52:31 UTC
The results generated by the Frosty script (and the Sparkle plug-in)
in 1.2.3 and 1.2.4-pre2 are still far from the nice results that could
be obtained earlier, IMHO.

Even after playing with the various parameters, I cannot reproduce the
same results as in versions 1.0.x and 1.1.x.  I will attach the
reference image supplied by Peter Bergt in bug #51010 to this bug
report so that it is not lost if Peter's web site disappears.
Comment 7 Raphaël Quinet 2003-01-17 11:53:52 UTC
Created attachment 13648 [details]
Reference image (frosty.gif) supplied by Peter Bergt
Comment 8 Alan Horkan 2003-07-23 18:39:00 UTC
Changes at the request of Dave Neary on the developer mailing list.  
I am changing many of the bugzilla reports that have not specified a target
milestone to Future milestone.  Hope that is acceptable.  
Comment 9 Manish Singh 2004-11-04 04:59:37 UTC

*** This bug has been marked as a duplicate of 132145 ***