Re: [Gimp-developer] Problem starting gimp 2.0.0
In regard to: Re: [Gimp-developer] Problem starting gimp 2.0.0, Owen said...: >On Tue, 6 Apr 2004 20:58:54 +0200 >Frank Wittemeier <[EMAIL PROTECTED]> wrote: > >> ** (gimp:9612): WARNING **: Cannot open font file for font Verdana 10 >> Speicherzugriffsfehler > > >I would suggest that this means; > >a. the font has not installed correctly >b. the file format is faulty > >Unless you *desperately* need verdana 10, ignore the message. >Alternatively, you may try reinstalling that font. I believe ``Speicherzugriffsfehler'' is "bus error" or "segfault" or something similar, auf Deutsch, so it's going to be a little hard to ignore until the problem font is removed. 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] plug-in observations/questions
On Apr 06 Sven Neumann ([EMAIL PROTECTED]) wrote: > > The example in the gimp-plugin-template is correct, works and it shows > how to install html files distributed with the plug-in. I don't > understand why you messed the template up so badly when all you had to > do was replacing "template" with the name of your plug-in and > providing a unique URL to identify the help domain registered by your > plug-in. > OK. Sorry about that. I think what happened was that early on I got my call to gimp_plugin_help_register out of sync with what was in the gimp-help.xml file. That, combined with ignorance, superstition, and hubris led me down the wrong path. Thanks for straightening me out! Steve -- Steve Lipa [EMAIL PROTECTED] gpg fingerprint = 8B68 77D7 9E09 9991 C97E 25FF 6A12 D2B9 EC7D 66C1 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Bugzilla clean-up 2
Hi Raphael, Raphaël Quinet wrote: > There is another thing that could be cleaned up in Bugzilla: moving > all 1.3.x bugs that are in RESOLVED state to the CLOSED state and > adding a comment saying that the fix is part of the official release > 2.0.0 (or 2.0.1 soon). Personally I don't see the need. I've personally looked at the milestones to see when bugs were fixed (and the comments), and I have never really seen a benefit to having both resolved and closed - in fact, in my company's installation of bugzilla we reduced the lifecycle of bugs to 4 states - New, Assigned, Resolved and Reopened, which suits our usage patterns fine. You mention a benefit to users, but I don't think personally that users (in general) use bugzilla to an extent where this is a large factor. Nor do people in general have a deep knowledge of the nuances of "resolved" and "closed". I think that the overhead of going through the bugs and changing them to CLOSED probably outweighs the benefit of it. But if you feel otherwise, I don't mind (although slogging through 300 bugzilla mails is going to be a pain). Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Problem starting gimp 2.0.0
On Tue, 6 Apr 2004 20:58:54 +0200 Frank Wittemeier <[EMAIL PROTECTED]> wrote: > ** (gimp:9612): WARNING **: Cannot open font file for font Verdana 10 > Speicherzugriffsfehler I would suggest that this means; a. the font has not installed correctly b. the file format is faulty Unless you *desperately* need verdana 10, ignore the message. Alternatively, you may try reinstalling that font. Owen -- - __0 http://www.pcug.org.au/~rcook/rr.html for rides _ \<,_ (_)./(_) http://weather.smh.com.au/weather/canberra.html --- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Bugzilla clean-up 2
There is another thing that could be cleaned up in Bugzilla: moving all 1.3.x bugs that are in RESOLVED state to the CLOSED state and adding a comment saying that the fix is part of the official release 2.0.0 (or 2.0.1 soon). This helps the users who are searching for bugs by telling them in which stable release some bug was fixed. I got some positive feedback about that in the past, so it looks like these comments are useful. This can also help us by reminding us of which bugs are only fixed in CVS or in developer's releases (RESOLVED) and which ones are fixed in stable releases (CLOSED). I have done that in the past for the 1.2.x releases and I can do it again for 2.0.x. Unfortunately, this will generate a lot of notifications because of the additional comments that should be added. So before starting with that, I would like to be sure that nobody objects. Any comments? -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] plug-in observations/questions
Hi,
Steve Lipa <[EMAIL PROTECTED]> writes:
> I have found by trial and error that if I don't have this xmlns:etc
> line pointing to the directory that the documentation is in, the help
> system simply does not work for me. The approach I am using is the
> only one that I have been able to get to work.
>
> I think most plug-ins will be like mine, in that they will have
> built-in documentation, so it might make sense for the
> gimp-plugin-template to have an example of how to do it right.
> Failing that, I was hoping to do my plug-in right so people could
> use it as an example. The other plug-ins I've looked at so far
> simply have not been any help.
The example in the gimp-plugin-template is correct, works and it shows
how to install html files distributed with the plug-in. I don't
understand why you messed the template up so badly when all you had to
do was replacing "template" with the name of your plug-in and
providing a unique URL to identify the help domain registered by your
plug-in.
I will paste the gimp-help.xml from the gimp-plugin-template below and
explain once more what's going on:
The raw version:
http://developer.gimp.org/plug-in-template/help";>
A commented version:
The classic XML header, just keep it.
http://developer.gimp.org/plug-in-template/help";>
The toplevel element of each gimp-help.xml file is .
Here we define a namespace for the identifiers that we are going to
register with the GIMP's help system. The namespace has the prefix
"template", you should change this to the name of your plug-in,
let's call it "foobar". The URI is _not_ pointing to any files on
the world wide web. It's sole purpose is to provide a unique
identifier. An identifier that is guaranteed not to be used by any
other GIMP plug-in that registers help pages. The idea is that you
use an address on your web-server, on your area of the web. You
don't need to put any pages there, just make sure that it's a unique
URI.
Here we install a mapping from an ID to a HTML file. You will notice
that id is defined in the "template" namespace defined above. So you
will need to use "foobar:id" here instead. The identifier
"plug-in-template" is mapped to the file "index.html". This filename
is relative to the position of gimp-help.xml that we are reading
right now.
There could be more lines like the above if you want to install more
help IDs.
This closes the top-level element again.
An example
==
So, assuming your plug-in is named "foobar", your gimp-help.xml would
look like this:
http://eos.ncsu.edu/plug-in-foobar/help";>
I do hope this explanation clears things up. If you have further
questions, please ask them.
> In the good old days, users could install plug-ins in
> ~/.gimp-x.x/plug-ins. Up until very recently, gimp-plugin-template
> (effectively) put plug-ins in ${prefix}/lib/gimp/2.0/plug-ins. The
> latest CVS version doesn't. But if you say $(GIMP_LIBDIR) will put
> them in the right place then that's good enough for me!
The gimp-plugin-template Makefile installs the plug-in system-wide.
That's better then doing it for each user individually. But I will
look into adding a "user-install" make target that puts the plug-in
into the user's gimp directory. We need to make a 2.0.0 release of
gimp-plugin-template anyway. There are a few minor changes in CVS that
need to be released.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Problem starting gimp 2.0.0
Hello, I have a problem with gimp 2.0.0. I have compiled the software listed on www.gimp.org/unix/ and then gimp-2.0.0, all with no problems. When I try to start gimp I get the followind error: ** (gimp:9612): WARNING **: Cannot open font file for font Verdana 10 Speicherzugriffsfehler I had this problem with the pre-Release of gimp (pre 2-4) and asked about the problem on this list, but with no solution. Any help? Frank BTW: the same problem with gimp --no-fonts -- Frank Wittemeier Krugweg 1 32 602 Vlotho ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp usability tests
On Tue, Apr 06, 2004 at 11:41:42AM +0200, Dave Neary wrote: > If I understood correctly, the objective of this exercise is to see if > people find the tool options, understand the icons, and understand what the > changing cursor means. Yes - thats the main objective of the tests :) Greetings -- Roman Joost www: http://www.romanofski.de email: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Gimp-developer] plug-in observations/questions
On Apr 06 Sven Neumann ([EMAIL PROTECTED]) wrote:
> Hi,
>
> Steve Lipa <[EMAIL PROTECTED]> writes:
>
> > First, the gimp-plugin-template is set up to
> > use a static gimp-help.xml file that always points
> > to a web address:
> >
> >
> > http://developer.gimp.org/plug-in-template/help";>
> >
> >
>
> This is a misunderstanding. The URL given there is just a unique
> identifier of the XML namespace declaration for "template:". There
> doesn't need to be any page pointed to by this URL. Please read up on
> XML namespaces if you want to understand this better or just ask again
> here.
>
> I have posted detailed explanations of the help system earlier on this
> list. Perhaps we should pull these out of the archives and put them
> online on developer.gimp.org.
>
Sven:
Trust me, I have tried to figure this out by reading through the old
archives but I haven't been able to find anything that applies. This
problem is exacerbated by the fact that the gimp-devel search engine
gives me nothing by error messages about not being able to find a
.htaccess file or some such, so it is hard to search effectively.
I have found by trial and error that if I don't have this xmlns:etc
line pointing to the directory that the documentation is in, the help
system simply does not work for me. The approach I am using is the
only one that I have been able to get to work.
I think most plug-ins will be like mine, in that they will have
built-in documentation, so it might make sense for the
gimp-plugin-template to have an example of how to do it right.
Failing that, I was hoping to do my plug-in right so people could
use it as an example. The other plug-ins I've looked at so far
simply have not been any help.
> The latter won't work if GIMP is not installed in the same prefix and
> I don't understand your problem with the first approach. You cannot
> simply install GIMP plug-ins somewhere, they need to go into the GIMP
> plug-in dir which is determined from the gimp-2.0.pc file. What is
> probably missing here is the addition of $(DESTDIR). I will consider
> to add that.
>
>
> Sven
In the good old days, users could install plug-ins in ~/.gimp-x.x/plug-ins.
Up until very recently, gimp-plugin-template (effectively) put plug-ins in
${prefix}/lib/gimp/2.0/plug-ins. The latest CVS version doesn't. But if
you say $(GIMP_LIBDIR) will put them in the right place then that's good
enough for me!
--
Steve Lipa
[EMAIL PROTECTED]
gpg fingerprint = 8B68 77D7 9E09 9991 C97E 25FF 6A12 D2B9 EC7D 66C1
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] plug-in observations/questions
Hi, Steve Lipa <[EMAIL PROTECTED]> writes: > First, the gimp-plugin-template is set up to > use a static gimp-help.xml file that always points > to a web address: > > > http://developer.gimp.org/plug-in-template/help";> > > This is a misunderstanding. The URL given there is just a unique identifier of the XML namespace declaration for "template:". There doesn't need to be any page pointed to by this URL. Please read up on XML namespaces if you want to understand this better or just ask again here. I have posted detailed explanations of the help system earlier on this list. Perhaps we should pull these out of the archives and put them online on developer.gimp.org. > Recent changes in gimp-plugin-template have changed > some things. First, in the file Makefile.am in > the src directory, the idea of a PLUGIN_DIR seems to > have gone away and the gimp-plugin-template puts the > binary in: > > bindir = $(GIMP_LIBDIR)/plug-ins > > This destination seems (at least in my case) to > be controlled by the contents of my gimp-2.0.pc > file and the prefix in that file overrides any > --prefix specification that I use when installing > the plug-in. It seems to me that for general > plug-in users who might not be allowed to write > to the system gimplibdir the following makes > more sense, and it works for me: > > bindir = $(prefix)/lib/gimp/2.0/plug-ins > > Can anyone let me know which of these is better > and why? The latter won't work if GIMP is not installed in the same prefix and I don't understand your problem with the first approach. You cannot simply install GIMP plug-ins somewhere, they need to go into the GIMP plug-in dir which is determined from the gimp-2.0.pc file. What is probably missing here is the addition of $(DESTDIR). I will consider to add that. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp usability tests
Hi Simon (and Brix), Simon Budig wrote: Roman Joost ([EMAIL PROTECTED]) wrote: 1. Create a rectangular selection and subtract the edge of the created selection. c) Does the user know, that the starting point of the subtract selection has to be placed outside of the current selection and not inside the selection itself. c) is not necessary. When pressing CTRL you can happily subtract stuff starting inside the current selection (otherwise it would be impossible to create holes in the selection) I know we're correcting the usability expectations with these comments, but somehow they have already highlighted some usability concerns - if the people doing the usability tests, in consultation with someone pretty familiar with the GIMP, isn't aware of these things, it might indicate that this is non-obvious (for example, the separation of the default grid and the grid in the current image is one which is not obvious, similarly, selection handling with modifier keys is not obvious). If I understood correctly, the objective of this exercise is to see if people find the tool options, understand the icons, and understand what the changing cursor means. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp usability tests
Roman Joost ([EMAIL PROTECTED]) wrote:
> Well, i think first a bit to the background of upcoming Usability Tests.
> I met Ellen Reitmayr at the GIMP 2.0 Release Party in Berlin and she is
> involved in some Usability studies for the KDE Project (with the whole
> company relevantive AG). After some discussions about the KDE Usability
> tests, we agreed, that some Usability tests for the GIMP would be nice
> for having feedback to the developers from some usability experts.
Great.
> 1. Create a rectangular selection and subtract the edge of the created
> selection.
> a) Were the necessary modes found?
> b) Does the user select the modi in the right sequence to achieve the
> goal. ('Replace a current selection', then use 'Subtract from the
> current selection')
> c) Does the user know, that the starting point of the subtract selection
> has to be placed outside of the current selection and not inside the
> selection itself.
c) is not necessary. When pressing CTRL you can happily subtract stuff
starting inside the current selection (otherwise it would be impossible
to create holes in the selection)
Bye,
Simon
--
[EMAIL PROTECTED] http://www.home.unix-ag.org/simon/
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp usability tests
Hi Roman,
Roman Joost wrote:
Well, i think first a bit to the background of upcoming Usability Tests.
I met Ellen Reitmayr at the GIMP 2.0 Release Party in Berlin and she is
involved in some Usability studies for the KDE Project (with the whole
company relevantive AG). After some discussions about the KDE Usability
tests, we agreed, that some Usability tests for the GIMP would be nice
for having feedback to the developers from some usability experts.
This is excellent news, and an excellent initiative.
I've added [EMAIL PROTECTED] to the CC list for their feedback too, and left
the entire mail intact.
Thanks for doing this, Roman, and I'm looking forward to seeing the results.
Cheers,
Dave.
I met Ellen again and we put some tasks for people who are new to
the GIMP and poeple who consider to change from photoshp to the GIMP.
Ellen wrote the draft that you'll find below. It's considered as a
basis for comments and suggestions to improve the usability of the GIMP
interface. It should not test the functionality itself and issues
already known as bugs. The test should be as effective as possible with
the 4 users and the mostly common tasks.
The first test consists of 4 persons and deals only the 'all-day-use'
with the Gimp (what is the handling of the application like, how good
can one achieve a task etc.). Later, we want to conduct a more extensive
test that will also consider the users' understanding of the common
concepts, such as layers, paths etc. - and how the new user could be
helped to learn these basic concepts (that would be nice to know for the
gimp-help-2 module to get the manual as effective as possible for
helping the user).
The GIMP is the SuSE package of the GIMP 2.0 with the german language
enabled.
Tasks for the first test (all-day-usage; all of the are common tasks for
all people, except the one where the indicated group is mentioned):
1. Create a rectangular selection and subtract the edge of the created
selection.
a) Were the necessary modes found?
b) Does the user select the modi in the right sequence to achieve the
goal. ('Replace a current selection', then use 'Subtract from the
current selection')
c) Does the user know, that the starting point of the subtract selection
has to be placed outside of the current selection and not inside the
selection itself.
2. Create a selection with fixed width and height and a fixed aspect
ratio.
a) Does the user find the right input field.
b) Does the user understand 'Fixed Aspect Ratio' or the german label:
'festes Seitenverhaeltnis'.
3. Selection by color, fill an area with a pattern and cancel the
selection.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user know how to fill the area with the patterns?
c) How to cancel a currently activated selection?
4. Measure how long a distance between some image objects is.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user find the value directly?
c) Where does the user look for the value? At the statusbar or at the
info window?
5. Clone an image object with the clone tool.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user understand how to indicate the starting point for the
clone tool?
c) Does the user choose the right brush from the brush browser?
6. Transform image objects.
The photoshop user should create a layer and shear it with a value for
XX pixels.
The new user should only shear the whole image.
a) Does the user find the right tool in the toolbox or in the menu?
b) Is the user able to use the grid for shearing?
7. Use the color picker to get the color info with sample merged
enabled.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user know why the color which is shown in the image window
is not the same which the color picker gets from the layer?
c) Does he know how to find the checkbox to enable the 'Sample Merged'
function?
8. Using the undo history.
a) Does the user find the journal directly?
b) Does the user understand, how to undo single steps?
9. Add an image grid and change the distance of the grid points.
a) Does the user find the image grid function?
b) Does the user find the image grid preferences in the preferences
dialog?
c) Does the user find the correct option for changing grid preferences?
10. This task is only for photoshop professionals. They should use the
path tool to create a cloud and stroke it with some patterns.
a) Does the user find the path tool?
b) Does he know how to use the path tool?
c) Does he know how to stroke the created path with a pattern?
11. Try to dock some tabs into the docks.
a) Does the user understand that only tabs can be moved betweend docks
and not the docks itself.
b) Does the user find the active area, where he can drop the tab to the
dock.
Thats all of them. In hope it would be useful,
Greetings
--
Dave Neary
[EMAIL PROTECTED]
___
Gimp-developer
Re: [Gimp-developer] Gimp usability tests
Hi, On Tue, 2004-04-06 at 10:25, Roman Joost wrote: [snip good initiative] > 9. Add an image grid and change the distance of the grid points. > a) Does the user find the image grid function? > b) Does the user find the image grid preferences in the preferences > dialog? > c) Does the user find the correct option for changing grid preferences? Finding the Default Image Grid preferences in the Preferences dialog is not needed for changing the distance of grid points in an image. This can be achieved using the Configure Image Grid dialog found in /Image/Configure Grid... The Default Image Grid preferences is only used to create a default grid for new images and for images that doesn't have a grid (non-XCF files). Sincerely, Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Gimp usability tests
Well, i think first a bit to the background of upcoming Usability Tests.
I met Ellen Reitmayr at the GIMP 2.0 Release Party in Berlin and she is
involved in some Usability studies for the KDE Project (with the whole
company relevantive AG). After some discussions about the KDE Usability
tests, we agreed, that some Usability tests for the GIMP would be nice
for having feedback to the developers from some usability experts.
I met Ellen again and we put some tasks for people who are new to
the GIMP and poeple who consider to change from photoshp to the GIMP.
Ellen wrote the draft that you'll find below. It's considered as a
basis for comments and suggestions to improve the usability of the GIMP
interface. It should not test the functionality itself and issues
already known as bugs. The test should be as effective as possible with
the 4 users and the mostly common tasks.
The first test consists of 4 persons and deals only the 'all-day-use'
with the Gimp (what is the handling of the application like, how good
can one achieve a task etc.). Later, we want to conduct a more extensive
test that will also consider the users' understanding of the common
concepts, such as layers, paths etc. - and how the new user could be
helped to learn these basic concepts (that would be nice to know for the
gimp-help-2 module to get the manual as effective as possible for
helping the user).
The GIMP is the SuSE package of the GIMP 2.0 with the german language
enabled.
Tasks for the first test (all-day-usage; all of the are common tasks for
all people, except the one where the indicated group is mentioned):
1. Create a rectangular selection and subtract the edge of the created
selection.
a) Were the necessary modes found?
b) Does the user select the modi in the right sequence to achieve the
goal. ('Replace a current selection', then use 'Subtract from the
current selection')
c) Does the user know, that the starting point of the subtract selection
has to be placed outside of the current selection and not inside the
selection itself.
2. Create a selection with fixed width and height and a fixed aspect
ratio.
a) Does the user find the right input field.
b) Does the user understand 'Fixed Aspect Ratio' or the german label:
'festes Seitenverhaeltnis'.
3. Selection by color, fill an area with a pattern and cancel the
selection.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user know how to fill the area with the patterns?
c) How to cancel a currently activated selection?
4. Measure how long a distance between some image objects is.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user find the value directly?
c) Where does the user look for the value? At the statusbar or at the
info window?
5. Clone an image object with the clone tool.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user understand how to indicate the starting point for the
clone tool?
c) Does the user choose the right brush from the brush browser?
6. Transform image objects.
The photoshop user should create a layer and shear it with a value for
XX pixels.
The new user should only shear the whole image.
a) Does the user find the right tool in the toolbox or in the menu?
b) Is the user able to use the grid for shearing?
7. Use the color picker to get the color info with sample merged
enabled.
a) Does the user find the right tool in the toolbox or in the menu?
b) Does the user know why the color which is shown in the image window
is not the same which the color picker gets from the layer?
c) Does he know how to find the checkbox to enable the 'Sample Merged'
function?
8. Using the undo history.
a) Does the user find the journal directly?
b) Does the user understand, how to undo single steps?
9. Add an image grid and change the distance of the grid points.
a) Does the user find the image grid function?
b) Does the user find the image grid preferences in the preferences
dialog?
c) Does the user find the correct option for changing grid preferences?
10. This task is only for photoshop professionals. They should use the
path tool to create a cloud and stroke it with some patterns.
a) Does the user find the path tool?
b) Does he know how to use the path tool?
c) Does he know how to stroke the created path with a pattern?
11. Try to dock some tabs into the docks.
a) Does the user understand that only tabs can be moved betweend docks
and not the docks itself.
b) Does the user find the active area, where he can drop the tab to the
dock.
Thats all of them. In hope it would be useful,
Greetings
--
Roman Joost
www: http://www.romanofski.de
email: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
