On 7/20/07, Fernando Perez <[EMAIL PROTECTED]> wrote: > However, it's not all gloom and doom: one can simply generate a config > file from the object description, edit it for ordering, and after that > keep it synced with changes to the object description fairly easily. > The current code only works in one direction: the file overrides the > object. It should take me about 5 minutes to add a method to go in > the other, since the code is really already there. With that, you can > then use the workflow of generating once, manually fixing it, and then > updating it from the class. > > That way, you can always keep the default file you like as internal > MPL data, but at install time, update that file as needed from runtime > config before putting it in the user's directory. It lets you keep a > nicely commented, organized file, but update it at installation time > with proper info. > > I'll code this up after I get back from lunch, and then I'll really > stop touching this code. I mean it :)
Nah, whoo needs lunch. Done: svn commit -m"Add option for class defaults to override files, so projects can impose changing defaults on files. After Darren's suggestion for MPL." This should give you a very reasonable solution for what you wanted to do. Now, I'll get lunch! Cheers, f ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
