samj has posted a new build on hew website. It is 64/32bit.

http://samjcreations.blogspot.it/2016/0 ... p-293.html

Thanks for the heads up bilbo9955! Testing it now.

Great job.
Samj just does not add icons brushes MyPaint (this is easily remedied - downloaded MyPaint and make up for the * .png)
Icon layout is probably better than the gimp-symmetry.

Edit: Samj completed.
Thanks.

After some use of the 64bit version, everything runs well. The only thing I would like to see is inclusion of all the extra filters, like in her previous builds. Maybe this is becoming problematic in this version.

For the lazy - pack icon brush MyPaint in the annex.

To remove(error in the original Mypaint)
history 1-5.myb;
redbrush.myb
s008.myb;
watercolor.myb

Edit: Samj completed.
Thanks.

Where do you install these new images?

Hi Rod - in the folder containing the files *.myb

You mean you can show the brush dynamic as a brush icon? Pretty darn cool.

Hi Lyle - it's just the principle MyPaint - x.png (icon) and x.myb (brush) must be in hand.

And one more note - the lack of some icons in the menu.
This is easily fixed - you can download and add to the appropriate directories plus gtkrc.

PS.Samj - if it had read it, add it in the next version.
I cordially greet my first teacher compilation
I'm missing you on this forum, but please can you come back

With this build there are what looks like different applications...one being called just 'GIMP'. Do the others refer to a language etc. I have just opened the one just called GIMP and it looks ok for English. What are the others? I also had a 2.9.1 EN portable which was mostly English. Just answered my own question....they are for different languages.

Can I delete the ones not needed And if so which...I don't want to delete anything that may affect the one I'm using?

The panorama projection is cool.

I copied all of my scripts over to the scripts folder in 2.9.3. Found they are not working properly....throwing a lot of errors. Do they just need a change in the wording to allow them to be used in 2.9? (By the way there was no 'script-fu' tag at the top until I put something in the scripts folder.) I did not make another folder for scripts. The one I put them in is already in the folders in preferences. So path is there already.
I assume it will be the same with plugins, they will not work correctly straight away?

Thank you. I've been yearning to test this version.

Cheers.

Most logo and alpha to logo scripts will not work correctly.I believe most are the plug-in PDB calls.
Should be "(gimp-drawable-plug-in-name-here)" NOT "(gimp-plug-in-name-here)" and the number of parameters are also changed. You shouldn't add scripts or plug-ins to this build. Unless the plug-ins were compiled with the GIMP-2.9 src gimptool. Most python will not work either as those PDB calls have also been deprecated.

Thanks Rod. I can always move them out again.
Was hoping there might be a quick fix. means I don't have extras like layer effects etc. I haven't tried plugins but won't now as you said.

Also you won't find Map Object in the filters menu. BUT you can go to Help>Search and find it there.

New (28-03-2016) development version Gimp 2.9.3 Portable 32-bit and 64-bit Windows.
http://samjcreations.blogspot.it/2016/03/version-de-developpement-gimp-293.html
Merci Samj.

thanks Samj (and thanks MareroQ) !
Inside it is said that the first launch is very slow; I did it and it took just 15 seconds (not bad at all!).
I will do some experiment with it, thanks again.

There are Gimp scripts still being written that use deprecated calls, you just do not see them

Not tried with Samj Gimp 2.9 (I use linux) You can try running Gimp 2.9 with the compatibility switch on

--pdb-compat-mode=mode
PDB compatibility mode (off|on|warn).

If the script/plug-in is going to work then that should stifle the deprecated function messages.

Otherwise there are differences that cause problems. No Lancos3 sharpening any more, so a script that calls that will fail. I have converted one or two scripts but hard going for me.

Maybe a repository of corrected scripts could be set up.

And if anybody does this, please indicate which version (GIT commit) of 2.9.3 it's been shown to work using, given that "2.9.3" is NOT a fixed version and is continually changing.

Kevin