On 11 July 2013 00:39, Milamber <[email protected]> wrote: > > Le 10/07/2013 23:29, sebb a ecrit : > >> On 11 July 2013 00:12, Milamber <[email protected]> wrote: >>> >>> Hello, >>> >>> I've use the new templates's behavior today. >>> >>> I have some improvements in my mind (and in better world) ;-) >>> >>> * Loading as templates's bundle every file with .xml extension, to allow >>> any >>> tiers provider to distribute 'templates pack' >> >> I'd had the same idea; thought I'd already sent a message - turns out >> it was sent to Commons by mistake. I've resent it here, see separate >> message. > > > Yeah! Same idea! > > >> >>> * Act as template all jmx files in /bin/templates/ even if the file isn't >>> in >>> a template.xml, to allow end user to 'create' across a easy way a >>> template >>> from their test plan. >> >> Not so sure about that - it would be expensive parsing the file for a >> template dialog entry - and how is that different from using the Open >> dialog? > > > Just for simplify the life of end user (and me). Have a single directory to > put my templates, to reuse it (without any directory navigation like > Open/Merge dialog box) > > Today, in UI design, there are always a lot of ways to do the same thing. > It's offer more ways to end user. >
I see. Not sure it's a good idea to mix indexed non-indexed templates in the same directory. The code would need to check whether the files were in the index or not otherwise they might appear twice. Maybe have a tabbed panel, one for indexed files and the other for a file list. These would be in separate directories. Since the non-indexed files don't have fancy descriptions, maybe a clickable list would be better than a drop-down. A bit like how the Apache server shows directory listings. > > >> >>> I'm not study (in this time) the way to do this. Any opinion? (I'm too >>> greedy?) >>> >>> Milamber > >
