LAVA 1.0 Content Posted December 1, 2006 Report Share Posted December 1, 2006 Hi, XControls seem to violate the encapsulation scheme of LabVOOP as they cannot be included into a class. This means that the developer cannot class private or protected methods in an XControl. As a result the developer is forced to make some unnecessary methods public so that these methods can be used in an XControl. These methods will then become as an API of the class which may not be ideal, as this may unnecessarily expose the implementation. After all one important concept in OOP alltogether is hiding the implementation. Consider that you want to encapsulate graphics objects as a class. You only want to expose the graphics objects to an XControl, there would be no methods to query any of the properties of the graphics objects. You would like to write a dynamic method draw, but make it only accessible to the XControl, as it makes no sense outside the XControl. XControl may be integral part of the class, but LabVOOP forces it to be separated from the class. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.