<p>What if the scratchpad were assumed to be in the same directory, with the same file name for auto open purposes? Them nothing is added to .it's.</p>
<p>Picture.ora accompanied by Picture.spd? </p>
<div class="gmail_quote">On Jul 21, 2011 9:38 AM, "David REVOY" <<a href="mailto:davidrevoy@gmail.com">davidrevoy@gmail.com</a>> wrote:<br type="attribution">> On 21/07/11 14:50, Ben O'Steen wrote:<br>
>> David,<br>>><br>>> Not to distract from this thread too much, but can you say more about<br>>> what you'd like about a self-contained palette? I've been working on<br>>> something like that for a few days:<br>
>><br>>> <a href="http://www.vimeo.com/26586840">http://www.vimeo.com/26586840</a> -- shows the more complex one showing<br>>> all the different file-saving methods.<br>> <br>> O_o wow, that's exactly the kind of palette/scratchpad I'm looking for <br>
> in Mypaint since the old palette panel of Portnov branch , just a <br>> scratchpad to pick & paint ( or 'pick context' ) brush. Cool , it looks <br>> already a very good feature. I will test your branch Asap.<br>
> <br>> The goal for me, would be to can save an *.ora in relation with a <br>> scratchpad. It mean make this scratchpad open at the same time I load a <br>> *.ora related to it. As Andrew said on the first email : /"The imagined <br>
> use case for this is that users like to continue work immediately where <br>> they left off when re-opening a saved work on a later date"/ and it's <br>> really so true when you handle multiple project. In a second time, I <br>
> also would like to can use a previous created scratchpad ( ex: my <br>> comics color palette ) to a new document, or a opened line-art.<br>> Of course , I saw in your videos the arrows to switch easily between <br>
> saved scratchpad. I think it's already really user-friendly. But to <br>> continue on the *.ora discution and possibilities ... :<br>> <br>> I can imagine 2 way :<br>> ---------------------------------------------------<br>
> <br>> #1 - *Embeded* : Save the scratchpad as a separate layer -for exemple- ; <br>> with a constant layer name ID saved in the *.ora files as hidden and <br>> make mypaint recognise by this ID while opening as a separate <br>
> informations to display in the scratchpad only.<br>> <br>> _Pros:_<br>> A file can be reopened under a 2nd PC with Mypaint and keep the same <br>> scratchpad<br>> The scratchpad can be used on other apps , the layer can be opened as a <br>
> regular layer by Gimp/Krita ( on the top, a hidden layer, with the ID <br>> name to respect = not rename )<br>> <br>> _Cons :_<br>> Gimp / Krita resaving will crunch some of the scratchpad info (stroke <br>
> map )... but it's ok.<br>> File weight, a bit more of infos are in the file.<br>> Can't share the same scratchpad to another drawing/project without <br>> adding another feature as 'open as file as scratchpad'.<br>
> <br>> ---------------------------------------------------<br>> <br>> #2 - *External* Save only the 'path' to the saved scratchpad inside the <br>> *.ora as a txt info ( surely a path inside .mypaint user preference , <br>
> like for brushes ) . With this Mypaint can load it at the same time of a <br>> related *.ora. It's my favorite design :) I also think the reference <br>> docker of Silvio Heinrich in Krita should store the ref picture this way <br>
> inside *.kra and *.ora. The dream would be the two apps use a path <br>> compatible (^ u ^)<br>> <br>> _Pros:_<br>> File weight, no embeded scratchpad, no possible bad interaction with <br>> other *.ora compatible apps.<br>
> Sharing same palette/scratchpad within multiple project is possible ; as <br>> scratchpad are saved independantly.<br>> Can share scratchpad for users , edit them etc ... as brushes ....<br>> <br>> _Cons_<br>
> Path to the scratchpad can get crunched while resaving the *.ora by <br>> other apps ?<br>> Have to share the ~/.mypaint pref to another PC to work on the file ( <br>> dialog 'path to the scratchpad missing!' ) ; but this is ok , imo.<br>
> <br>> -----------------------------------------------------<br>> <br></div>