On Tue, Apr 14, 2015 at 8:54 AM, <[email protected]> wrote: > Hi! > > This is a quick poll, triggered by comment 50 of ticket 7298 and also > comment 17 of ticket 18176. How would you like to create and save an > animation using Sage. Options (perhaps presented in a slightly biased way): > > 1. Create the animation object, then call the "save" method without any > extra arguments, hope to see a download link in the browser or a file system > path in the console, and hope the file looks OK using default settings. > 2. Start as above, then open the file to view it, and begin adding or > changing arguments to "save" till it looks OK. Which means re-downloading > from browser, and / or re-loading in your viewer app if it doesn't do so > automatically. > 3. Use "show" instead of "save" for a preview, tweak arguments to that till > I'm satisfied, then change the "show" to a "save". > 4. Use "show", tweak till satisfied, then right-click in browser to save, or > use "Save (copy) as..." in viewer application. > 5. ... (feel free to add further options you'd prefer over those presented > here.) > > The reason I'm asking this is because I feel that most people would prefer > to follow approach 3 and 4. Which means everything you can do with "save" > should be possible with "show" as well, with the possible exception of the > target file name. In the comments pointed out above, Volker Braun was of a > different opinion, arguing that "show" should simply show stuff, without too > much "confusing" flexibility, while all the power to tweak stuff should only > be available for "save". His rationale being the name of the method: if you > want to save things at the end of the day, you should be calling "save" not > "show". > > I'd like to hear your input about which method you'd prefer. > > I know I'm all for 4. and have been using that very often. If it's just me, > I'll accept that, but somehow I feel that this usage scenario is so obvious > that I'd be very surprised to be the only one employing it. Particularly > since I've asked some colleagues and they's use the same approach if given > these alternatives. @Volker, if you think I misrepresented some of the > options, it happened without ill intentions. Please feel free to clarify.
I vote for 3, which is the situation with 2d graphics for the last *9 years*, and isn't it the current situation with animations right now. I'm not sure why you don't clearly say for this poll what the current situation is, given that one has been able to save animations for a long time... I typically use show a lot to figure out the parameters of how I want something shown, then I put the result in a script and change the show to a save. I do this a lot. I did exactly this for hours yesterday: https://github.com/williamstein/rh/blob/master/rh/code/code.sage 1. is the same as 3 with no useful functionality and would be useless to me. 2. what if there is no browser involved? 3. what it is right now, if I understand correctly. 4. what if there is no browser? -- William > > Greetings, > Martin > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
