Re: [Gimp-user] Replication Array Layer

2016-12-30 Thread Rick C. Hodgin
It comes back to something taught in the Bible, which I've observed is
correct in life:

http://biblehub.com/kjv/proverbs/29-12.htm
"If a ruler hearken to lies, all his servants are wicked."

Stallman is at the head of GNU and the FSF.  Those who help build up his
products, they are acquiescing to his views on things because you cannot
divide a man in two.  It's like a sermon I heard one time:  "How many drops
of gasoline would it take to ruin a 32 oz. ice cold soft drink?"  Even if
99.99% of the soft drink were pure, that last little bit is what poisons
all of it.

The same is true with people.  And Stallman's views extend to bestiality,
child pornography, and other such things.  He holds these views in his
heart, and they affect all aspects of his life.

GNU was a good idea, but it's run by someone who is not sane.  The idea can
be salvaged as it is more of a general fundamental concept, but it must
sever all ties with GNU and Stallman in so doing.

That's what I'm doing with LibSF, created as an alternative to FSF, and my
Village Freedom Project, created as an alternative to GNU.

Best regards,
Rick C. Hodgin


On Fri, Dec 30, 2016 at 10:08 AM, Simon Budig <si...@budig.de> wrote:

> Rick C. Hodgin (rick.c.hod...@gmail.com) wrote:
> > GIMP is a non-professional name.  I think Image Professional would be
> > better.  Or something that has a positive upbeat tone.
> >
> > I don't expect people to change.  But it would be great.  It would allow
> me
> > to work on the project because it disassociates itself with Stallman.
>
> It is up to you to dislike Stallman. He is a controversial figure and I
> am by no means going to defend him.
>
> However, GNU is a very important contribution to the world of computers,
> and I am not willing to sacrifice it, because stallman allegedly is
> wrong on other stuff.
>
> If you think that "Image Professional" is more prone for success than
> Gimp then by all means, go ahead, fork the code and try to convince
> people to work for your vision. But please do not abuse the
> GIMP-ressources like this mailinglist to fight your personal vendetta
> against GNU/Stallman and the GIMP brand.
>
> Thank you.
> Simon
> --
>   si...@budig.de  http://simon.budig.de/
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


Re: [Gimp-user] Replication Array Layer

2016-12-30 Thread Rick C. Hodgin
My goals are to change things around so they are focused upon positive
things.  I am doing this with LibSF and the tools I'm creating, but in
general I want to encourage other people to do this as well with their
projects.

GIT is a bad name.  It's insulting, hurtful, etc.  It has no place being
the name of such a powerful tool.

GIMP is a non-professional name.  I think Image Professional would be
better.  Or something that has a positive upbeat tone.

I don't expect people to change.  But it would be great.  It would allow me
to work on the project because it disassociates itself with Stallman.

Best regards,
Rick C. Hodgin


On Fri, Dec 30, 2016 at 9:44 AM, Ofnuts <ofn...@gmx.com> wrote:

> On 30/12/16 15:15, Rick C. Hodgin wrote:
>
>> Also, the name "GIMP" is not very professional as it's associated with the
>> slang use of the word.  It's along the same lines as "GIT," named that way
>> on purpose by Linus.
>>
>>
> The irony is that most people whose mother's tongue isn't English learn
> about the other meaning of "gimp" because people
> complain about Gimp's name.
>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


Re: [Gimp-user] Replication Array Layer

2016-12-30 Thread Rick C. Hodgin
Because GNU is associated with Richard Stallman and his unnatural views
(believes pedophilia and necrophilia should be legal among other htings).

Also, the name "GIMP" is not very professional as it's associated with the
slang use of the word.  It's along the same lines as "GIT," named that way
on purpose by Linus.

We just need to break away from GNU and create works which make a clean
break from Stallman and those in the GNU camp, and proceed forward in a
more positive way.

Best regards,
Rick C. Hodgin


On Fri, Dec 30, 2016 at 9:06 AM, Jernej Simončič <
jernej|s...@eternallybored.org> wrote:

> On Fri, 30 Dec 2016 08:46:07 -0500, Rick C. Hodgin wrote:
>
> > If anyone's willing to break away from GIMP and their GNU-based roots,
> and
> > spawn off a fork of GIMP to a new named tool (Impro might be nice "Image
> > Professoinal"), then I'll be more than happy to contribute to that
> product.
>
> Why break away?
>
> --
> < Jernej Simončič ><><><><>< http://eternallybored.org/ >
>
>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Replication Array Layer

2016-12-30 Thread Rick C. Hodgin
If anyone's willing to break away from GIMP and their GNU-based roots, and
spawn off a fork of GIMP to a new named tool (Impro might be nice "Image
Professoinal"), then I'll be more than happy to contribute to that product.

Best regards,
Rick C. Hodgin


On Fri, Dec 30, 2016 at 8:38 AM, Rick C. Hodgin <rick.c.hod...@gmail.com>
wrote:

> I'll have to look at it.  It doesn't quite look like what I have in mind.
>
> I'm thinking there needs to be a new layer type created, which isn't just
> a regular layer, but is a modifier layer.  That modifier layer can receive
> parameters where things from other layers can be linked into it, and then
> acted upon by operations, such as you link a rectangle from layer A, rotate
> it 90 degrees, decrease its scale by 30%, and move it to these X,Y
> coordinates.  And then any time content from that rectangle in layer A
> changes, those changes are reflected in the modifier layer through the
> operations.
>
> In that way, modifier layers perform operations to derive content for
> display on their layer, or possibly to publish the content they modify onto
> another layer.
>
> It basically creates a worker layer that performs operations on content
> without actually baking them into the bits, but rather generating them from
> source bits through operations, and then using the generated portion, but
> in a way that by altering the operation stack, or changing the original
> source bit data, the changes push through to everywhere they are referenced.
>
> A whole set of features could be added to the modifier layer, not the
> least of which is the array modifier I mention.  But every operation we
> have today could be added, and they could be performed in a stack upon that
> original content source from another layer, or from a selected portion from
> another layer.
>
> Best regards,
> Rick C. Hodgin
>
>
> On Fri, Dec 30, 2016 at 4:55 AM, Ofnuts <ofn...@gmx.com> wrote:
>
>> On 30/12/16 02:02, Rick C. Hodgin wrote:
>>
>>> GIMP needs to add a feature which allows an area to be selected and
>>> copied
>>> into a new layer, and then that area is replicated onto other layers (or
>>> multiple times into another single layer), such that when changes are
>>> made
>>> to the originating layer, those changes are reflected everywhere.
>>>
>>> In Blender, this is known as an array modifier:
>>> https://www.youtube.com/watch?v=1mNUHOkKQcY
>>>
>>> GIMP needs a feature like this which can exist in modifier form, or be
>>> "baked" into the image with the modifier being applied.
>>>
>>> Best regards,
>>> Rick C. Hodgin
>>>
>>
>> Maybe what you need is interleave-layers: http://gimp-tools.sourceforge.
>> net/animationtools.shtml
>>
>>
>> ___
>> gimp-user-list mailing list
>> List address:gimp-user-list@gnome.org
>> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
>> List archives:   https://mail.gnome.org/archives/gimp-user-list
>>
>
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


Re: [Gimp-user] Replication Array Layer

2016-12-30 Thread Rick C. Hodgin
I'll have to look at it.  It doesn't quite look like what I have in mind.

I'm thinking there needs to be a new layer type created, which isn't just a
regular layer, but is a modifier layer.  That modifier layer can receive
parameters where things from other layers can be linked into it, and then
acted upon by operations, such as you link a rectangle from layer A, rotate
it 90 degrees, decrease its scale by 30%, and move it to these X,Y
coordinates.  And then any time content from that rectangle in layer A
changes, those changes are reflected in the modifier layer through the
operations.

In that way, modifier layers perform operations to derive content for
display on their layer, or possibly to publish the content they modify onto
another layer.

It basically creates a worker layer that performs operations on content
without actually baking them into the bits, but rather generating them from
source bits through operations, and then using the generated portion, but
in a way that by altering the operation stack, or changing the original
source bit data, the changes push through to everywhere they are referenced.

A whole set of features could be added to the modifier layer, not the least
of which is the array modifier I mention.  But every operation we have
today could be added, and they could be performed in a stack upon that
original content source from another layer, or from a selected portion from
another layer.

Best regards,
Rick C. Hodgin


On Fri, Dec 30, 2016 at 4:55 AM, Ofnuts <ofn...@gmx.com> wrote:

> On 30/12/16 02:02, Rick C. Hodgin wrote:
>
>> GIMP needs to add a feature which allows an area to be selected and copied
>> into a new layer, and then that area is replicated onto other layers (or
>> multiple times into another single layer), such that when changes are made
>> to the originating layer, those changes are reflected everywhere.
>>
>> In Blender, this is known as an array modifier:
>> https://www.youtube.com/watch?v=1mNUHOkKQcY
>>
>> GIMP needs a feature like this which can exist in modifier form, or be
>> "baked" into the image with the modifier being applied.
>>
>> Best regards,
>> Rick C. Hodgin
>>
>
> Maybe what you need is interleave-layers: http://gimp-tools.sourceforge.
> net/animationtools.shtml
>
>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


[Gimp-user] Replication Array Layer

2016-12-29 Thread Rick C. Hodgin
GIMP needs to add a feature which allows an area to be selected and copied
into a new layer, and then that area is replicated onto other layers (or
multiple times into another single layer), such that when changes are made
to the originating layer, those changes are reflected everywhere.

In Blender, this is known as an array modifier:
https://www.youtube.com/watch?v=1mNUHOkKQcY

GIMP needs a feature like this which can exist in modifier form, or be
"baked" into the image with the modifier being applied.

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


[Gimp-user] Multiple clipboards

2016-12-25 Thread Rick C. Hodgin
It would be nice to add a feature like layers with clipboards, so that a
history of recent content copied to the clipboard could be cycled through
and re-used.

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


[Gimp-user] Why does Export To require confirmation on certain files

2016-12-25 Thread Rick C. Hodgin
I'm wondering what the thinking / logic was in requiring confirmation when
exporting to a file that the original source image was loaded from?

I can understand if I loaded a .xcf file, or .bmp file, and then later went
to export it to a .png file, for example, asking for confirmation before
overwrite.  But, if I were to load a .png file, and then went to export it
(and not "Export As..." to a new destination), but to write-out the
original .png that was loaded, why does it ask for confirmation the first
time?  Why not just recognize it as an editing session and save it back out
in the same format?

If I load a .xcf file, and then press Ctrl+S after making changes, it
doesn't ask for confirmation.  Why does the "Export" feature require
confirmation when writing back out to the original file it was loaded
from?  And why after writing out those changes to the original source file,
and going to exit, does it ask me if I want to discard my changes?  I am
not discarding them.  I just haven't saved them in the .xcf format, but I
have saved them in the original format.

It seems to be a conscious effort to make all non-.xcf file formats second
or third class citizens in GIMP, and it came about when the Ctrl+S change
was made to only work with .xcf files, and to push everything else to the
Ctrl+E export area.

What was the thinking / logic there?  It causes a great deal of problems
for users.  It's also confusing because I get the message about unsaved
changes, even after I've exported them out as .png files.  It actually
makes me cancel the close file operation, go out and export again, and then
close file and discard changes.

It's counter-productive and it causes people issues in using GIMP for
non-.xcf file formats.

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


[Gimp-user] Ctrl+Shift+J Fit Image In Window

2016-12-23 Thread Rick C. Hodgin
There should be an option available to set a margin for the Fit Image In
Window auto-size.  It would allow an N-pixel buffer around the image to
make room for mouse actions to start before the edge and drag into the
image.

As it is now, it requires the edges which touch the border to start inside
the image, followed by a second action to drag the side close to the edge
all the way over to the edge.

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


[Gimp-user] Find and Replace

2016-12-17 Thread Rick C. Hodgin
How about a feature where you select something, click Find and it selects
all of the matching areas in the image.  Click Find and Replace and it
selects all of the matching areas where you can then de-select or select
new areas if you want to, each of the size of the initial selection, and it
brings up another GIMP editor window where you can replace the content in
those areas with an edited image which can then be applied to each of the
selected areas, with an option to do each in its own layer so you can apply
different modes on it?

I could've used this feature today.

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


Re: [Gimp-user] GIMP still maintained by GNU

2016-12-13 Thread Rick C. Hodgin
On Tue, Dec 13, 2016 at 5:27 PM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> On Wed, Dec 14, 2016 at 1:13 AM, Rick C. Hodgin wrote:
> > Is GIMP still maintained by GNU?
>
> Was it ever?
>

GIMP = GNU Image Manipulation Program:

http://directory.fsf.org/wiki/GIMP

"This is a GNU package: gimp"


> > Or has it more or less broken away from
> > GNU and just has loose affiliation?
>
> Had it been caged?
>

Once a software product is GPL'd it's always GPL'd, but that doesn't mean
it must still proceed as part of the GNU Project.  It can be a spawned
non-GNU project.  However, GIMP appears to be still a GNU project.


> Alex
>

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


[Gimp-user] GIMP still maintained by GNU

2016-12-13 Thread Rick C. Hodgin
Is GIMP still maintained by GNU?  Or has it more or less broken away from
GNU and just has loose affiliation?

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


Re: [Gimp-user] Change canvas size fill with option

2016-12-13 Thread Rick C. Hodgin
Thank you, Alex.  It was the next logical step, yes? :-)

Best regards,
Rick C. Hodgin


On Tue, Dec 13, 2016 at 12:58 AM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> 12 дек. 2016 г. 23:09 пользователь "Rick C. Hodgin" <
> rick.c.hod...@gmail.com>
> написал:
>
> I'm using GIMP 2.8.18.
>
> I thought a nice feature would be to add "Create a New Image" to resize
> canvas options (and specifically the "Fill with:" options -- background
> color, foreground color, white, transparency).
>
>
> Already done in upcoming 2.9.6.
>
> Alex
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Change canvas size fill with option

2016-12-12 Thread Rick C. Hodgin
(1)  Create a new image of any size (200 x 200 for example).
(2)  Click the "+" by Advanced options, and note the "Fill with:" combo box
/ dropdown.
(3)  Click OK.
(4)  Go to Layer -> Transparency -> Add alpha channel (if you didn't select
it during (2)).
(5)  Go to Image -> Canvas Size.
(6)  Change it to 300 width and 300 height, and click "Center".
(7)  Select "All layers" under "Resize layers:"
(8)  Click "Resize".

Note that there is a transparent border around the 200 x 200 center.  It
would be nice to have the same "Fill with:" option available in (2) under
the "Advanced Options".

Best regards,
Rick C. Hodgin


On Mon, Dec 12, 2016 at 3:31 PM, Michael Schumacher <schum...@gmx.de> wrote:

>
>
> On 12/12/2016 09:08 PM, Rick C. Hodgin wrote:
> > I'm using GIMP 2.8.18.
> >
> > I thought a nice feature would be to add "Create a New Image" to resize
> > canvas options (and specifically the "Fill with:" options -- background
> > color, foreground color, white, transparency).
> >
> > Right now it forces transparency if you're using an alpha channel and you
> > must paint.  And if there are pixels at the edge of the new transparent
> > area which fall within the threshold of the paint bucket, it spills over.
>
> Sorry... but I don't get what you are describing.
>
> Can you make a list of steps you currently have to do to achieve what
> you want, and a list of steps you'd like to do instead?
>
>
> --
> Regards,
> Michael
> GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list


[Gimp-user] Change canvas size fill with option

2016-12-12 Thread Rick C. Hodgin
I'm using GIMP 2.8.18.

I thought a nice feature would be to add "Create a New Image" to resize
canvas options (and specifically the "Fill with:" options -- background
color, foreground color, white, transparency).

Right now it forces transparency if you're using an alpha channel and you
must paint.  And if there are pixels at the edge of the new transparent
area which fall within the threshold of the paint bucket, it spills over.

Best regards,
Rick C. Hodgin
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list