On 16 April 2016 at 21:12, Antonio Gomes Rodrigues <[email protected]> wrote: > Hi, > > My opinion is that property are not user friendly.
For some items that's true, but for other items having to use the GUI is a nuisance. > This feature must be present in JMeter GUI to be use for the maximum of user I don't think that will work for a a feature that aims to disable what the GUI shows; by then it's too late ... > Antonio > > > > 2016-04-16 18:07 GMT+02:00 sebb <[email protected]>: > >> On 16 April 2016 at 13:44, Philippe Mouawad <[email protected]> >> wrote: >> > Hello, >> > After release of 3.1, I propose to introduce this property: >> > ux.test_profile=http,jms,jdbc.... >> > ux.profile.http=list of elements related to it >> > ux.profile.jms=list of elements related to it >> > >> > >> > This way it would be easy for users by selecting the profile they want to >> > restrain the number of elements shown to the ones they need . >> > >> > >> > Thoughts ? >> >> There's already a property which can be used to disable certain elements. >> >> A simpler solution might be to just (re)move the unwanted jars; that >> way there is no need even to scan the classes. >>
