Re: [Mtpaint-devel] patch mtpaint - GtkFileChooserDialog

[Mark T. <mar...@go...>]

Sylvain,

You wrote:

> I think that it's an interesting idea. If you want maybe I can help you on
> this way.

You are very welcome to maintain the new GTK+2/3 version if you like,
and start using the newer widgets such as the file chooser, stock
buttons, and replacing deprecated widgets with the new equivalents
(e.g. clists to GtkTreeView).  This work won't start for a month or
two while the next release is prepared and the final plans are put
together, but this time is a good opportunity to study how you might
change things and try some test code.

Once the next release comes in a few weeks time (or March maybe), we
will then start work on the structural changes for version 3.20 which
will have the separate directories for different toolkits.  We will
then gradually go through each source file and split the code into
kernel space or toolkit space.  This won't all happen at once, because
it will be easier to adopt a piecemeal approach whereby each
successive release (i.e. 3.30, 3.40 etc.) contains more
transformations into the new structure.  Once all of this is completed
and the program is truly toolkit agnostic, version 4.00 of mtPaint can
be released.


> Otherwise do you want an updated french translation for 3.10 version ?

That would be great.  Here is a link to the latest development version
with a refreshed set of po files:

http://mtpaint.sourceforge.net/temp/mtpaint-3.14.16.tar.bz2


We are always discussing new ideas for mtPaint, so here are some ideas
we have collected in recent months:

New layer file format, integrated with inifile engine.
Layer compositing to a new layer.
Option to save/load layered images as ZIP files.
Layer grouping.
Undo for layer operations.
Undoable image loads.
Support for save/load of TGA and PCX images, and binary palettes (PAL).
Undo memory shared between layers, backed by disk to preserve the
existing behaviour of persistent per-layer undo stacks.
Skew, (subpixel) shift, perspective transform of images.
Edge detection filters.
Rendering filters - "Supernova", fire effect, neon glow.
Filter Factory engine.
Changing colour A to a colour nearest to it from the current palette.
"Filtered" drawing mode: 3 toggles for HSV colour components - "Hue",
"Saturation", "Value" - and 3 more for RGB components - "Red",
"Green", and  "Blue". If some component's toggle is off, that
component's value remains unchanged when you draw over a pixel; thus,
you could, for example, modify only the hues of pixels, while their
saturation and (relative) brightness remain unchanged - like
repainting yellow and green gradients to be red ones.
"Scratchpad layer" and a drawing mode using its pixels as drawing
colour (and maybe mixing its selection channel with tool_opacity).
Configuration toggles for lines (accessed by right click on line tool)
- square ends and antialiasing.
Optional antialiasing for ellipses and polygons.
Sampling mode for colour-selective mode (select colours around those
sampled from the image).
Gradient save/load, selecting lines from images to use as gradients,
dynamic gradient preview.
Mirroring the hue circle, and option for preserving brigtness through
hue transform, in "Transform colour".
"Transform" drawing mode - storing settings from "Transform colour"
dialog to apply them to pixels you draw over.
Changing patterns from inside program (options to make them into a new
image or layer and to load them back).
Better support for bitmap brushes - maybe best implemented by
exchanging clipboard with internal "RGBA pattern", and using that
pattern for drawing while it is non-empty. Or would it be better to
add several slots for bitmap brushes to pattern window, use exchanging
with clipboard to fill them, but select and deselect them as any other
pattern?
Support for brushes with opacity "channel", and "image hose" brushes.
Regular, configurable brush spacing for non-continuous mode.
Separate tool_opacities for colours A and B.
Support for loading new keybindings from configuration file.
Better quantization algorithm(s).
Make flood_fill_poly() and flood_fill_poly24() to use the new
"quadtree" flood-fill engine, to prevent possible stack overflows when
using lasso tool. And use the possibility to add a "fuzzy mode" to
lasso tool, too.
The "Curves" tool. (Or would it be better to make it "Levels/Curves"?
"Levels" is, after all, just an indirect way to set up the same
translation table that "Curves" allows to set up more directly, so why
not combine both interfaces in one dialog?)
An option to composite layers to a new layer.
Extend the polygon tool to allow moving, adding and removing vertices,
moving the entire contour, converting edges to Akima curves and back
to straight lines, making two curved segments (or a curved and a
straight one) connect at a vertex either smoothly or at an angle.
Maybe also add options for saving/loading these contours (using text
files for the purpose).
"Magnetic lasso"/"Intelligent scissors" like tool, producing a polygon
from object's traced edges.
Scaling and free-rotating the clipboard.
Support for animation "strips" - per-layer sequences of images,
replacing one another with configurable delays when building
animation.
Grid configuration dialog: spacing and colour for "tile grid", minimum
scale for pixel grid, colours for pixel grid - possibly different ones
for opaque areas, transparent areas, and boundaries between them (to
better see which pixels belong to the current layer, and which to the
underlying ones).
"Tiled view" mode - copies of current layer rendered tiled over all
canvas, to make drawing tileable textures easier.


Regards,
Mark.