Return-Path: X-Original-To: apmail-jmeter-dev-archive@minotaur.apache.org Delivered-To: apmail-jmeter-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B073910064 for ; Tue, 9 Jul 2013 15:21:00 +0000 (UTC) Received: (qmail 53013 invoked by uid 500); 9 Jul 2013 15:20:59 -0000 Delivered-To: apmail-jmeter-dev-archive@jmeter.apache.org Received: (qmail 53007 invoked by uid 500); 9 Jul 2013 15:20:59 -0000 Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jmeter.apache.org Delivered-To: mailing list dev@jmeter.apache.org Received: (qmail 52780 invoked by uid 99); 9 Jul 2013 15:20:59 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 15:20:59 +0000 Received: from localhost (HELO [192.168.7.235]) (127.0.0.1) (smtp-auth username milamber, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 15:20:58 +0000 Message-ID: <51DC2A58.2000003@apache.org> Date: Tue, 09 Jul 2013 15:20:56 +0000 From: Milamber Organization: Apache Software Fondation User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17.1 MIME-Version: 1.0 To: dev@jmeter.apache.org Subject: Re: New from Template silently overwrites files References: <51DBF9B7.4050104@apache.org> <51DC170E.5050600@apache.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Le 09/07/2013 14:58, sebb a ecrit : > On 9 July 2013 14:58, Milamber wrote: >> Le 09/07/2013 13:20, sebb a ecrit : >> >>> On 9 July 2013 13:01, sebb wrote: >>>> On 9 July 2013 12:53, Milamber wrote: >>>>> Le 09/07/2013 11:46, sebb a ecrit : >>>>> >>>>>> Just noticed that the "New From Template" feature creates a file in >>>>>> the current working directory. >>>>>> >>>>>> It silently overwrites any file with the same name as the template. >>>>>> >>>>>> It would be easy to lose a valuable test plan. >>>>>> >>>>>> I'm not sure why the code does not just load the content from the >>>>>> template, and leave to the user to save the test plan where they wish. >>>>> >>>>> +1, I would be better to make like "merge" (or use the merge >>>>> functionalty) >>>>> to open the template. >>>>> >>>> Yes - would need to clear any existing plan first though. >>>> >>> Just occurs to me that one might want to use templates for partial test >>> plans? >> >> Yes, I think it's natural to use the template as partial test plans (like >> "add my favorite listener") >> >> >>> If so, then it would be useful not to clear the existing plan first. >> >> Yes. Perhaps a checkbox "Replace (and remove) current test plan" or "Merge >> with current test plans". >> > If the template is a comple test plan, I'm not sure it makes sense to Merge it. > Likewise snippets must be Merged. > > Maybe the "Create" button at the bottom needs to change according to > the template type - either "Create" or "Merge" ? +1 seems the good deal. > >>> Maybe the templates.xml file could include a flag to say whether the >>> template was a complete test plan or just a snippet? >>> That would allow the dialog box to easily distinguish the two types. >> >> +1 >> >> >>> The Menu item would need to be changed to "Templates..." >> >> Philippe has already do this for french translation ("Modèles..." not >> "Nouveau depuis modèles") >> I agree "Templates..." seems better. >> >> >>>>>> After all, unless they change the template, they can just refetch it. >>>>>> >>>>>> Thoughts? >>>>>>