bugMyPaint - Bugs: bug #19240, Saving Brushkeys in .ora files

Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #19240: Saving Brushkeys in .ora files

Submitted by:  Till Hartmann <tillux>
Submitted on:  Tue Jan 3 18:18:58 2012  
Severity: 1 - WishPriority: 5 - Normal
Status: WishPrivacy: Public
Assigned to: NoneOpen/Closed: Open
Release: Planned Release: None
Operating System: 

Sun Jun 29 01:20:00 2014, comment #4:

(This is a canned response, please forgive any broken formatting)

This bug tracker will shortly be moving to Github. As part of this process, we are reviewing old bug reports on gna.org.

This report appears to be a request for a new feature, but discussion has dried up and/or there are no patches or mockups attached. Please help us
to move it forward, which will ensure that it is retained during the migration.

While in the past our bug tracker here on Gna! has kept these stale feature requests around, in practice we have found that development moves too
fast for this to be a valid approach. Please consider that developers need working plans and agreement before we get stuff done.

With that in mind, if you're monitoring this report, here's what we need to be reassured that this request is still relevant:

  • If this request generated no responses, sorry.

But please treat that as a HUGE sign that
this tracker isn't receiving enough eyeballs
for your idea to have received the
discussion it needs.

There are discussion forums with greater reach:
Twitter: @MyPaintApp or #mypaint
Forums: http://forum.intilinux.com/#c9
Or even the mailing list at

Please link to any ongoing discussions,
if you haven't already done so.

  • If you think this request is not stale, please

resubmit it on github itself,
at https://github.com/mypaint/mypaint/issues
Please do this only if you have mockups, use cases,
patches or sample code implementing the feature:
if you don't yet, then it needs more discussion.
The linked resources above are the place for that.

In short, please remember that a bug report is not a widely read discussion forum, and that feature requests must be moved forward. Kindly
remember too that our developers don't have the time to monitor all the forums all of the time.

Andrew Chadwick <achadwick>
Project Administrator
Mon Nov 26 15:04:06 2012, comment #3:

The ORA spec does allow for program-specific data to be present.

But one could say that this here is a part of a bigger problem, that of embedding resources used to create the document in the document. That could potentially be standardized, of course.

Jon Nordby <jonnor>
Project Administrator
Tue Jan 17 15:56:12 2012, comment #2:

> IMO this does not belong here: it'd be a MyPaint-specific extension to the ORA format, which isn't so bad in itself although it would require wider agreement, but it's also somewhat difficult to square with the current implementation.

I believe the SVG spec allows for program-specific data. Other programs are expected to ignore and preserve it if found. Inkscape, for example, stores info specific to Inkscape in addition to standard SVG in files it creates.

ORA spec could be amended to allow something similar, so program-specific features could be saved and restored without affecting how the image is displayed in another program. It might be a lot of work for one feature, but it would open the door for other changes in the future.

A program could, for example, implement something like layer grouping needing the ORA spec modified to accommodate it. Programs could experiment and see what works, and good additions could be added to spec, while niche ones could live inside the program's custom area in the file.

Joshua Tyler <marand>
Thu Jan 5 11:41:32 2012, comment #1:

IMO this does not belong here: it'd be a MyPaint-specific extension to the ORA format, which isn't so bad in itself although it would require wider agreement, but it's also somewhat difficult to square with the current implementation. We'd have to either throw away lots of users' established prefs, or come up with some funky mediation between saving into the .ora and saving to the user's prefs as you mention.

I like the idea of being able to configure certain kinds of brushes as non-saveable to the strokemap though.

Andrew Chadwick <achadwick>
Project Administrator
Tue Jan 3 18:18:58 2012, original submission:

As I switch between different paintings, I regularly have to reassign my Brushkeys, as I use different brushes for different paintings. That of course overwrites the brushes previously assigned to those keys, which is rather annoying.
(On the other hand, I usually assign a smudge brush to e.g. Brushkey #2, so that would be the same in all .ora files anyway).
It's possible to simply pick-context the brushes I need, but that is also rather hard to do when smudging a lot (might open another wish to ignore certain brushes/kinds of brushes from pick-context [similar to https://gna.org/bugs/?19044 ]).

I'd like to hear what other people think about storing the Brushkeys per .ora rather than globally.

Or maybe add that as an option...? No, that's not the kind of option "the user" should be able to change, I guess.

Till Hartmann <tillux>
Project Member


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by jonnor (Posted a comment)
  • -unavailable- added by marand (Posted a comment)
  • -unavailable- added by achadwick (Posted a comment)
  • -unavailable- added by tillux (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Error: not logged in



    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon Nov 26 15:04:06 2012jonnorStatusNone=>Wish
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup