I like option #1 - that way people can see what they're missing, but it's obvious that it's disabled.
For loading a test plan that uses an optional item that they don't have, I think a good error pop-up should be displayed. Ideally, we could still load the test and leave a disabled generic component in place of the component using the optional jar. -Mike On Fri, 2005-09-02 at 07:41 -0400, Peter Lin wrote: > good question. I haven't given much thought about it recently, but in the > past I've had different views on it. > > 1. show the item, but grey it out. when users selects it, we could pop up a > dialog and ask users if they want to download it > > 2. not show it and document it better > > 3. show the item, but not allow users to use it > > I'm sure there are other options. > > peter > > > On 9/2/05, sebb <[EMAIL PROTECTED]> wrote: > > > > If JMeter is used without some of the optional jars (e.g. mail, jms or > > bsh), then it will work OK so long as the relevant test elements are > > not in the test plan and no attempt is made to add them. Some warning > > messages may be logged. > > > > However, JMeter does not behave consistently when attempting to use > > missing optional jars. > > > > In some cases, if the optional jars are missing, then the test > > elements don't appear in the menus, in other cases the menu items > > appear, but attempts to add them to the plan may fail. > > > > Also, if one tries to load an exisiting test plan which refers to an > > optional component, all sorts of errors can be logged, and the plan > > may not load completely. > > > > I'd like to tidy this up a bit - but what should the strategy be? > > > > If a jar is missing, should the corresponding menu items be present or > > not? > > If the menu item is present, what should happen when the user tries to add > > it? > > If an existing test plan refers to missing jars, what should be the > > behaviour? > > > > It may not be possible to tidy this up completely, but it would be > > useful to know what to aim for. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
