GNOME Bugzilla – Bug 101435
Outdated links in web-browser.scm
Last modified: 2009-08-15 18:40:50 UTC
The script plug-ins/webbrowser/web-browser.scm contains the bookmarks that are displayed in <Toolbox>/Xtns/Web Browser/. Some of these links should be updated: - The GIMP News page does not exist anymore and redirects to the gimp.org home page, so it can be removed - There is no link to the GIMP User Group (GUG, a.k.a. GimpForce), which is a very useful resource for GIMP users because it contains a more up-to-date set of tutorials and FAQs. Attached below is a first patch that corrects these two problems. In addition, several links are still working but provide outdated information. I suggest to remove them: - The GIMP User FAQ and GIMP Developer FAQ: some of these FAQs are covered by the GUG FAQs, and most of the others are outdated anyway (refering to GIMP version 0.99.x or to the "recently released 1.0.0"). In some cases, the answers are incorrect for the current versions of the GIMP and could confuse some users. - The GIMP Tutorials page has not been updated since 1999. Some of the links in that page are broken, and the most interesting tutorials have been rewritten in the GUG Tutorials section. The second patch attached below removes these working but obsolete links.
Created attachment 13062 [details] [review] First patch: add GUG, remove GIMP News
Created attachment 13063 [details] [review] Second patch: remove old FAQs and old tutorials page
Applied to the stable branch: 2002-12-17 Sven Neumann <sven@gimp.org> * plug-ins/webbrowser/webbrowser.scm: applied a patch from Raphael Quinet that removes outdated links and adds one for the GUG (#101435). For the HEAD branch, I'd prefer to remove the plug-in completely. Links can be provided in the help files and on www.gimp.org and the functionality to direct a running browser to a help page (needed by the help system) is better provided by helper applications like gnome-moz-remote.
I've mentioned my ideas about the webbrowser plug-in in bug #51632 and will close this report now.
The fix is part of the stable release 1.2.4. Closing this bug.