[Gimp-developer] how to get the code of feather function?

[zhang chi]

I hope to know the feather algorithm for my research,so how to get the
feather funcion code?

thank you!
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] prefix issues

[Sven Neumann]

Hi,

On Tue, 2007-02-27 at 23:44 +0100, Marco Ciampa wrote:

> - are those options generated automatically by normal automake/autoconf
>   nowadays gnu programs or are those a gimp only convention?

These are standard and they are documented in the automake and autoconf
manuals.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Gimp-developer] gimpwin install

[Joao S. O. Bueno Calligaris]

Hi,

I, exceptionally, have a question reguarding the GIMP builds for 
windows:

How  hard would it be to create a .msi installer for gimp + gtk+, 
instead of the current zip files? 

It seems to be quite standard nowadays, and a couple high profile free 
software packages are uisng it.

I think that could be a nice surprise for win users.

regards,

js
-><-
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] prefix issues

[Michael Natterer]

On Tue, 2007-02-27 at 23:44 +0100, Marco Ciampa wrote:
> On Tue, Feb 27, 2007 at 11:16:43PM +0100, Michael Natterer wrote:
> > On Tue, 2007-02-27 at 22:13 +0100, [EMAIL PROTECTED] wrote:
> > 
> > > Thanks for your explaination. This is what I gathered from Alexandre's  
> > > post but I got a msg saying that target did not exist :?
> > 
> > you don't have "make maintainer-clean" because at some point
> > after you said ./autogen.sh, you did ./configure without
> > passing --enable-maintainer-mode. autogen.sh passes that
> > automatically for you.
> > 
> Newbie questions: 
> 
> - are there any other mantainer options to know of?
> - are those options generated automatically by normal automake/autoconf
>   nowadays gnu programs or are those a gimp only convention?
> - documentation links?

less autogen.sh

ciao,
--mitch

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] LGM - goint to, and GIMP presentation

[Jakub Steiner]

On Mon, 2007-02-26 at 23:50 -0300, Joao S. O. Bueno Calligaris wrote:
> GIMP presentation at LGM -
> 
> Hi people -
> 
> LGM guys are asking for a GIMP presentation at the Libre Graphics 
> Meeting. Something to show off GIMP's capabilities, new features in 
> the 2.4 version, and plans for the future.
> 
> The other big projects there will feature such a presentation (more or 
> less like Andyfitsz's presentation last year, sans the bugs)
> 
> """ usage is of utmost importance; we expect many graphics 
> pros who haven't even heard of FLOSS"""
> 
> So, if anyone wants to present such a lecture, please step ahead -
> 
> Just remembering you that Pippin will already present something about 
> the achievements and other dark magic in GEGL.

Hi Joao,
I wouldn't mind showing off the hard work of other people :). Some
photo-related things that come to my mind:

  * Linux input device support - wacom(pressure) + powermate(brush
size). (Removing dust, dodging/burning)
  * Fullscreen photo editing, view customizations, demo of the new
transform tools. 
  * Perspective clone, (healing brush?).
  * If time allows, corrective perspective transform usually appeals
to people.

Color management would perhaps be nice to demo, but I'm not sure if
we'll going to be in demoable state.

cheers

-- 
Jakub Steiner <[EMAIL PROTECTED]>

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Enhancement Proposal: Add a temporary magnifier

[Jakub Steiner]

Hi Gimpers,
allow me to join the brainstorm. As the loupe tool seems to be most
useful for making pixel-perfect selections while retaining a global view
on the image, what if the selection tools provided that functionality?

When creating or resizing selections, the loupe would show up after
holding the mouse button for a certain amount of time, automatically.
Alternatively it could be a checkbox in the tool's preferences. 

I also believe the preview is more useful being rectangular rather than
round.

cheers

-- 
Jakub Steiner <[EMAIL PROTECTED]>

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] prefix issues

[Marco Ciampa]

On Tue, Feb 27, 2007 at 11:16:43PM +0100, Michael Natterer wrote:
> On Tue, 2007-02-27 at 22:13 +0100, [EMAIL PROTECTED] wrote:
> 
> > Thanks for your explaination. This is what I gathered from Alexandre's  
> > post but I got a msg saying that target did not exist :?
> 
> you don't have "make maintainer-clean" because at some point
> after you said ./autogen.sh, you did ./configure without
> passing --enable-maintainer-mode. autogen.sh passes that
> automatically for you.
> 
Newbie questions: 

- are there any other mantainer options to know of?
- are those options generated automatically by normal automake/autoconf
  nowadays gnu programs or are those a gimp only convention?
- documentation links?

TIA

-- 

Marco Ciampa

++
| Linux User  #78271 |
| FSFE fellow   #364 |
++
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] prefix issues

[Michael Natterer]

On Tue, 2007-02-27 at 22:13 +0100, [EMAIL PROTECTED] wrote:

> Thanks for your explaination. This is what I gathered from Alexandre's  
> post but I got a msg saying that target did not exist :?

you don't have "make maintainer-clean" because at some point
after you said ./autogen.sh, you did ./configure without
passing --enable-maintainer-mode. autogen.sh passes that
automatically for you.

ciao,
--mitch

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] prefix issues

[gg]

On Tue, 27 Feb 2007 22:04:54 +0100, Sven Neumann <[EMAIL PROTECTED]> wrote:

> Hi,
>
> On Tue, 2007-02-27 at 12:05 +0100, [EMAIL PROTECTED] wrote:
>
>> I am having a lot of trouble getting a clean install from snv.
>>
>> I specified --prefix=/opt/gimp
>>
>> make[2]: Entering directory `/svn/gimp/libgimpconfig'
>> test -z "/opt/gimp/lib" || mkdir -p -- "/opt/gimp/lib"
>>   /bin/sh ../libtool --mode=install /usr/bin/install -c
>> 'libgimpconfig-2.0.la' '/opt/gimp/lib/libgimpconfig-2.0.la'
>> libtool: install: error: cannot install `libgimpconfig-2.0.la' to a
>> directory not ending in /opt/lib
>> make[2]: *** [install-libLTLIBRARIES] Error 1
>>
>>
>> I did a previous build with --prefix=/opt which was not what I required.
>
> You need to 'make maintainer-clean' after changing the prefix.
>
>
> Sven
>
>
>

Thanks for your explaination. This is what I gathered from Alexandre's  
post but I got a msg saying that target did not exist :?


bash-3.2#make maintainer-clean
make: *** No rule to make target `maintainer-clean'.  Stop.

I have resolved the immediate problem by deleting everything in sight  
including the source and starting over again.

When I can spare the computer next I will try 'make maintainer-clean'  
again, now it is all installed.

I'd prefer to do this cleanly rather than having to resort to shotgun  
deletions.

Thanks again.
gg
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] prefix issues

[Sven Neumann]

Hi,

On Tue, 2007-02-27 at 12:05 +0100, [EMAIL PROTECTED] wrote:

> I am having a lot of trouble getting a clean install from snv.
> 
> I specified --prefix=/opt/gimp
> 
> make[2]: Entering directory `/svn/gimp/libgimpconfig'
> test -z "/opt/gimp/lib" || mkdir -p -- "/opt/gimp/lib"
>   /bin/sh ../libtool --mode=install /usr/bin/install -c   
> 'libgimpconfig-2.0.la' '/opt/gimp/lib/libgimpconfig-2.0.la'
> libtool: install: error: cannot install `libgimpconfig-2.0.la' to a  
> directory not ending in /opt/lib
> make[2]: *** [install-libLTLIBRARIES] Error 1
> 
> 
> I did a previous build with --prefix=/opt which was not what I required.  

You need to 'make maintainer-clean' after changing the prefix.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Enhancement Proposal: Add a temporary magnifier

[peter sikking]

Raphaël wrote:

>> Let's look at the user requirements: for a _moment_
>> you want to see what you are _doing_ at high magnification,
>> while working on a _macroscopic_ scale.
>
> I would like to know why you state that the user requirements
> include showing for a _moment_ what you are doing at high
> magnification.

the first mail in this thread does, also the
"I really _miss_ this feature!" mail by Steve Stavropoulos does.

The macroscopic and momentarily aspects are the core of this problem.

> If the view of the zoomed-in area does not overlap the normal
> work area, some users may be equally interested in seeing at
> all times[...]

> To me, the argument that the zoomed-in area should only be
> displayed for a brief moment is far from obvious.

different use case. I already said that additional tracking views
of the same file at different magnifications will solve that.

back the the problem of this thread.

>> I add here that to be able to be of help, the magnified
>> area needs to have a strong relationship (closeness) to
>> the actual mouse position, but always needs to be out
>> of the way.
>>
>> everything speaks for a key-triggered loupe.
>
> Again, this is far from obvious.  You state that it "always
> needs to be out of the way" but there is no real way to
> ensure that it is _always_ out of the way

this does it:



it is always out of the way where the mouse and the attention is
(centre of the smaller circle).

> The user
> may still be interested in some context around this area in
> order to be able to align things, repeat some pattern, etc.

my solution involves a switch (on/off of the loupe) to do that,
your solution involves a switch (user views out/in of the main
window) to do that.

the problem with your solution is the cost in screen real-estate
minimum 100x100, which force the loupe window to be small, and
not see the surrounding of the point of interest at a generous
magnification. It is also by definition farther away, being non-
overlapping with the man window, which is not what one wants when
performing finicky surgery.

The way for the future for GIMP UI is to display a lot more things
on the fly, just when one needs them, and only the truly universal
things fixed in the inspectors. Can already get used to the term HUD
(heads-up display).

>> during the moment that one is focussed on the detail
>> there is plenty screen space to put a really sizeable
>> loupe window, and it will be automatically close, but
>> also automatically out of the way.
>
> You assume that focusing on the detail means that the user
> lost interest in the context.

during those 1-2 seconds. It is actually physiological.
you angle of view narrows to a few degrees, when concentrating.

> This is not always the case.
> If you do not let the user position the high magnification
> area (as would be possible with an auto-tracking view), then
> the key-triggered loupe would probably have to support a
> combination of modifiers so that the user can tell GIMP: "no,
> don't pop it up somewhere above my mouse pointer, but rather
> somewhere in the lower left corner, or somewhere far to the
> right".

see the linked picture above, close and always out of the way.
very cool.

gg: I am not going to forbid anyone to pop up a loupe while
the mouse is down.

 --ps

 principal user interaction architect
 man + machine interface works

 http://mmiworks.net/blog : on interaction architecture



___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] prefix issues

[Michael Schumacher]

Von: [EMAIL PROTECTED]

> It seems that the make scripts are incompleter somehow and are not  
> cleaning up properly.

There are other clean-targets. For example, maintainer-clean.


HTH,
Michael
-- 
"Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ...
Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Gimp-developer] prefix issues

[gg]

Hi,

I am having a lot of trouble getting a clean install from snv.

I specified --prefix=/opt/gimp

make[2]: Entering directory `/svn/gimp/libgimpconfig'
test -z "/opt/gimp/lib" || mkdir -p -- "/opt/gimp/lib"
  /bin/sh ../libtool --mode=install /usr/bin/install -c   
'libgimpconfig-2.0.la' '/opt/gimp/lib/libgimpconfig-2.0.la'
libtool: install: error: cannot install `libgimpconfig-2.0.la' to a  
directory not ending in /opt/lib
make[2]: *** [install-libLTLIBRARIES] Error 1


I did a previous build with --prefix=/opt which was not what I required.  
It seems that make uninstall; make clean; is not sufficient to clean up  
the installation.

I also went through and manually deleted anything that seemed to relate to  
gimp then reran make install.

It seems that the make scripts are incompleter somehow and are not  
cleaning up properly.

gg
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer