Consider: Visualizer = Interface xxxVisualiser = class - except when xxx = Image
=== Likewise with Listener: These are Interfaces: AccumListener GraphAccumListener GraphListener Listener ModelListener RemoteSampleListener ... These are not Interfaces: GlobalMouseListener JMeterTreeListener ListenerNotifier ... === I agree that adding prefixes to Java names is generally not necessary because of strong type checking etc. But it is still useful to name access methods getXxx and setXxx (even if not creating Beans), and booleans isXxx etc. === S. -----Original Message----- From: Wolfram Rittmeyer [mailto:[EMAIL PROTECTED] Sent: 17 March 2003 14:42 To: JMeter Developers List Subject: AW: Proposed JavaSamplerClient changes I don't think your proposed interface-naming-scheme is any better to read. Take the "Visualizer" for example. Well the name says everything needed: It IS A Visualizer and I really would hate to read every time I need a visualizer that I would need a "IVisualizer". And the objects I instantiate are "GraphVisualizer"-objects and so on. I like it that way. I consider that to be much more readable than any other thing. I also do not like attributes to be named bIsOptionChecked (boolean values), iItemCount (int-values) and so forth (older projects here at work used to use this naming-scheme - uagh!). I also do not think a interface should always be an adjective. Adjectives are useful for, well, flags like cloneable and the like, but for real-life-objects (at least objects which represent objects in the real world)? Well these are objects and therefore should be substantives - "Visualizable" would sound strange, wouldn't it? Though this are just my personal preferences. I am indeed a bit harsh on this issue, I'm sorry. It's just that I'm so glad this has vanished here at work that I'd be quite unhappy seeing this naming-scheme return at JMeter. Greetings, Wolfram --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _________________________________________________________ This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of SchlumbergerSema. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error please notify the SchlumbergerSema Helpdesk by telephone on +44 (0) 121 627 5600. _________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
